Performance is measured, not predicted
Timings come from this server's single fetch of your page: DNS, connect, TLS, first byte and download. That is one observation from one location, not field data from real visitors and not a Lighthouse run.
Audit your website
One address, a few seconds, and a report that shows what was measured — not a score with nothing behind it.
- No account needed
- Every measurement shown
- English and Spanish
Start the audit
We fetch the page once, from our server, and report exactly what came back.
We fetch the page once, measure it, and keep the source only for a few days. Nothing is sold or shared.
What happens when you press the button
No crawler farm, no synthetic lab, no third-party score pasted into a template.
- The address is validated first: private, internal and reserved ranges are refused before anything is requested.
- We request the page once, like a browser would, and keep the response, its headers and its timing.
- Each check reads that one response — the markup, the headers, the certificate — and records what it found.
- The report shows the measured value next to every verdict, so you can check our work.
What this audit covers today
The catalogue defines 101 checks and 101 of them run in this version. None are waiting: every rule in the catalogue is measured, and every score traces back to a check that actually ran.
| Category | Checks | Weight in the score | Status |
|---|---|---|---|
| Availability & connectivity Whether the site answers at all: reachable over HTTPS, responding in reasonable time, without redirect loops and serving the right content type. | 11 | 12/100 | 11 running now |
| Technical foundations The plumbing crawlers and browsers rely on: robots.txt, sitemap, canonical tags, structured data, mobile viewport and clean HTML. | 8 | 12/100 | 8 running now |
| On-page SEO Titles, meta descriptions, headings, links, images and Open Graph tags — measured on the page as it was served, not guessed. | 15 | 16/100 | 15 running now |
| Performance Real network and payload measurements: server response, total weight, number of requests, compression, caching and render-blocking resources. | 12 | 12/100 | 12 running now |
| Accessibility Automated checks of language, title, landmarks, heading order, alternative text, labels, contrast and keyboard support. Automated checks find part of the picture; manual WCAG testing is still recommended. | 17 | 12/100 | 17 running now |
| User experience What a visitor meets on the page: clear navigation, readable content, working contact routes, no intrusive interstitials, mobile-friendly targets. | 11 | 8/100 | 11 running now |
| Security posture Passive, public checks only: TLS validity, security headers, cookie flags, exposed files and third-party origins. Nothing is probed or exploited. | 11 | 12/100 | 11 running now |
| Content quality Whether the page has real substance: word count, structure, readability signals, duplicate content hints and contact information. | 4 | 8/100 | 4 running now |
| AI search readiness How easily an AI assistant or answer engine can read this page: machine-readable structure, an organization it can identify, services, location, contact details and answers shaped to be quoted. No ranking claims — nobody outside those systems knows how they rank. | 12 | 8/100 | 12 running now |
Weights are configurable by the site owner and are shown in every report, so the score can always be traced back to the checks behind it.
What this audit cannot tell you
Accessibility is automated only
Automated rules catch a share of WCAG 2.2 issues — missing labels, low contrast, empty headings — but they cannot judge meaning, reading order or keyboard flows. Manual testing with assistive technology is still recommended.
Security checks are passive
We look at public information only: headers, TLS settings, exposed files, cookie flags. No exploitation, no brute force, no port scanning, no injection attempts. A clean result here is not a penetration test.