Skip to main content
SiteScan.top

Scan report for zess.by

5 pages crawled — 5483 words, 109 images and 420 links read straight off the pages and checked for accessibility, performance, SEO, security, forms, links and infrastructure. 47 distinct problems found, counted 126 times across the pages.

Report updated 2026-10-26

Category scores

Overall
87/100
SEO
87/100 · Issues: 14
Accessibility
42/100 · Issues: 34
Performance
77/100 · Issues: 23
Security
60/100 · Issues: 29
Privacy
94/100 · Issues: 6
HTML validity
98/100 · Issues: 2
Forms
100/100 · No issues found
Links
99/100 · Issues: 2
Console
89/100 · Issues: 6
Infrastructure
100/100 · No issues found
Mobile
95/100 · Issues: 7
Images
98/100 · Issues: 3

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.
  • Add alt text to the images that are missing it — Search engines can index the images and screen-reader users learn what they show.
  • Give every button an accessible name — Every control announces what it does instead of being read out as a button.
  • Turn on gzip or brotli compression for HTML — HTML transfers shrink by roughly 70%, cutting load time on every visit.
  • Send X-Content-Type-Options: nosniff — Browsers stop guessing content types and executing files as scripts.
  • Send an X-Frame-Options header — The site cannot be framed for click-jacking.

What the site checks found

  • Medium — Security — The server sends no intermediate certificate, so clients that have not cached it refuse the connection.
  • 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 sent with no Cache-Control, Expires, ETag or Last-Modified — every visit re-downloads it in full.
  • Low — Privacy — The site loads Google Analytics 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.