Skip to main content
SiteScan.top

Scan report for linkando.com

5 pages crawled — 3595 words, 103 images and 205 links read straight off the pages and checked for accessibility, performance, SEO, security, forms, links and infrastructure. 44 distinct problems found, counted 122 times across the pages.

Report updated 2026-10-28

Category scores

Overall
89/100
SEO
86/100 · Issues: 15
Accessibility
49/100 · Issues: 36
Performance
88/100 · Issues: 16
Security
77/100 · Issues: 17
Privacy
97/100 · Issues: 1
HTML validity
87/100 · Issues: 11
Forms
100/100 · No issues found
Links
97/100 · Issues: 5
Console
93/100 · Issues: 4
Infrastructure
94/100 · Issues: 10
Mobile
97/100 · Issues: 5
Images
99/100 · Issues: 2

Quick Wins

High-impact, low-effort fixes, ranked by what this scan actually found.

  • Declare the page language on the <html> element — Screen readers pick the right pronunciation and translation tools work.
  • Give every button an accessible name — Every control announces what it does instead of being read out as a button.
  • Add an H1 heading — Both readers and crawlers get a clear statement of what the page is about.
  • Make every id on the page unique — Anchors, labels and scripts reach the element they were pointing at.
  • Give every iframe a title — Screen-reader users hear what each embedded frame contains.
  • Add loading="lazy" to the embedded frames — Embedded players and maps load when they are scrolled to, not before the page has painted.

What the site checks found

  • Low — Security — No /.well-known/security.txt — anyone who finds a vulnerability has to guess where to report it.
  • 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 — Performance — The HTML is compressed with gzip but not with Brotli, which every current browser accepts and which is typically 15–20% smaller.
  • Low — Privacy — The site loads Meta Pixel 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.