Performance
Lighthouse's weighted performance score for the chosen device (mobile by default, with simulated slow-4G and CPU throttling). See how to read a Lighthouse report.
Where every number in a report comes from, how scores are calculated and what the audit cannot see.
This page explains where each number in a report comes from, so you can judge how far to trust it.
We check that the address is a public http(s) page on port 80 or 443. We resolve the host name ourselves and refuse private, loopback, link-local and other non-public addresses, including after redirects.
Our server fetches the page (following up to 5 redirects, reading up to 3 MB, with time limits), tests the HTTPS handshake, requests http:// to see whether it redirects, and reads robots.txt and the sitemap. From that we compute the Security and SEO scores and the basic accessibility checks.
We run Google Lighthouse in headless Chrome on our own server, one test at a time. It provides the Performance, Accessibility and Best Practices scores, Core Web Vitals lab metrics and speed findings. If the test times out, the quick checks are still shown.
Lighthouse's weighted performance score for the chosen device (mobile by default, with simulated slow-4G and CPU throttling). See how to read a Lighthouse report.
Lighthouse's automated accessibility score. Only a subset of accessibility issues can be detected automatically.
Lighthouse's Best Practices score.
Our weighted on-page checklist below. It is not Lighthouse's SEO score, which is stricter about some things and does not look at social tags, sitemaps or redirects.
Our weighted checklist of HTTPS and response headers below.
score = 100 × (points earned ÷ points possible)
Checks that do not apply to a page (for example image alt text on a page with no images) are left out. We deliberately do not combine the scores into one overall grade, because that would hide which area needs attention.
Each check earns its weight in points. Longer bars matter more.
The weights are our judgement of how much each item matters for most sites. They are not an industry standard. Informational checks appear in the report with severities but carry no score weight:
Structured dataHTTP/2Page sizeResponse timeViewportCompression
Likely to hurt visitors, security or search visibility on its own (for example noindex, an invalid certificate, a missing title, or a speed fix worth a second or more).
A real weakness worth fixing soon (for example a missing HSTS header or canonical, or roughly 300 ms of possible speed savings).
Polish and defence in depth.
The check found nothing to fix.
Every severity is shown as a label and an icon as well as a colour. Lighthouse findings take their severity from Lighthouse's own weighting for accessibility and best practices, and from the estimated time savings for speed.
The tools under Free tools use the same hardened fetcher as the audit but skip Lighthouse, so they answer in seconds. The accessibility, mobile-friendly and tech stack checkers analyse the HTML, headers and linked CSS only: they are static checks, not a rendered browser test. The speed test and Core Web Vitals test pages run the full Lighthouse audit. They read one page and never crawl.
A weighted grade out of 100:
Weak settings earn half marks (CSP with unsafe-inline, short HSTS lifetime).
A page served over plain HTTP is capped at F.
Reads title, description, canonical, robots, Open Graph and Twitter tags, then loads the social image through the same restricted fetcher (3 MB cap, re-encoded to a small preview). Previews are approximations.
Follows up to ten server redirects with per-hop time, then follows the four http/https and www/non-www variants of the host.
Reads one page and checks up to 50 unique links (internal first), at most two requests at a time per host, HEAD first and GET as fallback, within a 38 second budget. Sites that answer 401, 403 or 429 are reported as "can't verify", not broken.
A few tools make a small, fixed number of extra requests to the site you check: the sitemap validator tests up to 10 listed URLs, the image and page weight checkers measure up to 25 files, the hreflang checker fetches up to 8 alternate pages, the llms.txt checker tests up to 8 listed URLs, the mobile-friendly checker reads up to 5 stylesheets, the carbon calculator measures up to 25 files, and the broken link checker tests up to 50 links. The website down checker makes one request, and a second one after a short pause if the first fails. Requests to any one site run at most two at a time. Results are not stored; each tool keeps its answer in the page only (and caches it for five minutes, or twenty seconds for the down checker, to be polite to the site being checked).
The speed numbers come from a controlled test: one load, from one server location, on an emulated device. They are repeatable and good for finding problems. INP cannot be measured in a lab run, so we report Total Blocking Time as a labelled proxy. Results will vary slightly between runs, and the audit does not scroll, click or log in.
Lab numbers are not what Google uses to assess Core Web Vitals, which comes from real Chrome users over 28 days.
Every report shows the Lighthouse version that produced it. When we change a check or a weight we will update this page, which was last reviewed on November 15, 2026.
To learn who runs the service and what our crawler fetches, read the about page. For what we store when you run an audit, see the privacy policy.