Website Health · free · no account
Find what’s broken
on your website.
76+ automated checks across QA & structural, SEO, performance, security, accessibility and usability, and a score out of 100 — then, for every check that failed, the evidence behind it and the fix for your stack.
Only scan sites you own or are authorised to test. Terms
Free, no account, usually under a minute — every check and every finding visible. Nothing is stored: the report is delivered to your tab and erased from the server as it leaves.
49
Held at 49 by one expired certificate
71 ran · 62 passed · 9 failed
QA
86
Good
SEO
71
Needs work
PERF
94
Good
SEC
40
Poor
A11Y
78
Needs work
UX
100
Good
One mark per check, in the order they ran. Taller and darker is worse, so the faults are findable before they are read — here, a critical one in security.
Illustrative — not a real scan
Includes an AI readiness score. Other tools check whether you have let ChatGPT and Claude in. This one also checks whether there is anything on the page once they arrive. What that means.
how it works
One address in, one report out.
- 01
Enter the address of a page
Any public page of a site you own or are authorised to test. No account, nothing to install.
- 02
We run 74 checks on it
Usually under a minute. The scanner fetches the page itself and, where it is available, asks Google's PageSpeed Insights for a real Chrome run of it.
- 03
Read the score, then the findings
A score out of 100 across six categories. Every failure comes with the evidence behind it and the fix for your stack; a check that could not decide says why.
- 04
Keep it, share it, or go wider
Export it, share a link that lasts 30 days, or crawl up to 10 more pages of the same site — also free.
The free scan, and the free crawl
Both are free and both produce the same kind of report. The crawl is how you find what is wrong on the pages you did not think to scan.
| Property | Free scan | Free crawl |
|---|---|---|
| What is scanned | The page you enter | Up to 10 more pages: the ones your page links to first, then your sitemap |
| Checks | 74 on the page | The same on every page, plus 3 that compare pages (duplicate meta tags, error pages, pages nothing links to) |
| What it needs | Nothing | An email address — the finished report is sent to it |
| How to start | The box above | From the finished report of a scan |
| Where the report lives | In your tab; our server erases it as it is delivered | In your tab, and in your inbox |
not just another score
A score tells you something is wrong.
Every finding tells you what to do.
Each failing check comes back with the evidence behind it and a fix written for your stack — not a recommendation to go and read about it. This is one real check, exactly as the report renders it.
Every check, explained — what each one looks for, why it matters, and the fix.
security-csp
Missing Content-Security-Policy header
- evidence
- No Content-Security-Policy in the response headers for https://example.com/
- how to fix
- Send a Content-Security-Policy header, starting in report-only mode so you can see what it would block before you enforce it.
- nginx
add_header Content-Security-Policy-Report-Only "default-src 'self'" always;
The report picks the snippet for the stack it detected on your site and puts that one first. Apache, Next.js and Netlify forms are shown too — a guess from response headers is not good enough to hide the others behind.
services
Want this across your whole site, every week?
We run full-site audits, monitoring and alerts, speed tracking, Search Console and AI visibility for a small number of clients, set up with you by a person. No signup: book a demo and we will show you what it finds on your own site.