Scan report for wadline.ru
4 pages crawled — 4355 words, 73 images and 737 links read straight off the pages and checked for accessibility, performance, SEO, security, forms, links and infrastructure. 28 distinct problems found, counted 62 times across the pages.
Report updated 2026-10-27
Category scores
- Overall
- 91/100
- SEO
- 89/100 · Issues: 11
- Accessibility
- 90/100 · Issues: 10
- Performance
- 84/100 · Issues: 17
- Security
- 52/100 · Issues: 17
- Privacy
- 96/100 · Issues: 2
- HTML validity
- 100/100 · No issues found
- Forms
- 94/100 · Issues: 4
- Links
- 100/100 · No issues found
- Console
- Not measured
- Infrastructure
- 100/100 · No issues found
- Mobile
- 100/100 · No issues found
- Images
- 98/100 · Issues: 1
Quick Wins
High-impact, low-effort fixes, ranked by what this scan actually found.
- Send a Strict-Transport-Security header — Browsers refuse to fall back to plain HTTP for this domain.
- Give every iframe a title — Screen-reader users hear what each embedded frame contains.
- Send a Permissions-Policy header — Camera, microphone and geolocation stay switched off for embedded content.
- Label every form field — Fields become usable with a screen reader and clickable by their label.
- Give every form a submit control — Visitors can actually send the form.
- Link the orphan pages from the site — Crawlers reach the page through the site's own links, and it gets some of their weight.
What the site checks found
- Low — Security — No /.well-known/security.txt — anyone who finds a vulnerability has to guess where to report it.
- Medium — Security — No SPF record — anyone can send email that claims to come from this domain.
- Medium — Security — No DMARC record at _dmarc — nothing tells receiving servers what to do with mail that fails the SPF check.
- Low — Security — No CAA record — any certificate authority may issue a certificate for this domain.
- Low — Security — The zone is not signed with DNSSEC, so a forged DNS answer cannot be detected.
- Low — Privacy — The site loads Google Tag Manager with no consent layer anywhere in the markup — under the GDPR and the ePrivacy Directive those tags need consent before they run.
Other sites scanned recently
Scan your own site
Get the same diagnostic report for your website in under a minute.