Site scanner
Find out what is slowing your site down
— and what is keeping it out of search
Enter a domain. You get real request timings, a live TLS inspection, crawlability and indexing checks, DNS and mail posture, and on-page SEO — each with the specific change that fixes it.
Resolving DNS…
What a scan covers
Real timings, not estimates
DNS, TCP, TLS handshake and time-to-first-byte are measured from socket events on an actual request, so you can tell a slow application from a slow network.
TLS read from a live handshake
Certificate chain, expiry, SAN coverage, negotiated protocol and ALPN — which is how HTTP/2 support is detected rather than assumed.
Crawlability, properly tested
robots.txt parsed by user-agent group, the sitemap fetched and counted, the HTTP→HTTPS redirect followed, and a nonexistent URL requested to catch soft 404s.
Subresources actually weighed
Up to twelve referenced assets are requested for their real size, compression and cache headers, instead of trusting the markup — and aborted at the headers, so next to nothing is transferred.
DNS and mail posture
A, AAAA, MX, NS, CAA, SPF and DMARC, because the records that break a site are rarely the ones in the HTML.
Every finding says how to fix it
Not a score and a shrug. Each result explains what was measured, why it matters, and the configuration change that resolves it.
Six categories, weighted by what actually costs you traffic
Performance
Payload, latency and transport
On-page SEO
Titles, headings, metadata, structure
Crawl & indexing
What search engines can reach
Security & TLS
Certificate and HTTP hardening
Mobile & UX
Viewport, images, usability signals
Infrastructure
DNS, mail authentication, server config
A pass earns full weight, a warning half, a failure none. Checks the scanner cannot fairly judge are reported but not scored — the methodology page lists every request it makes and everything it cannot see, including why no single-request tool can report Core Web Vitals.
Then fix it
Findings link into a reference library written for the person who has to make the change, not the person who has to report it.
Plus a directory of tools and primary sources — performance testing, TLS, DNS, email authentication, server configuration and accessibility, each with a note on when to reach for it.