What's a good Lighthouse score?
Lighthouse is Google's open-source tool for auditing web pages. It loads your page the way a visitor on a mid-range phone would and scores it from 0 to 100 in four categories. Developers use it to find what makes a site slow, hard to use with assistive technology, or hard for search engines to understand.
The four scores
- Performance
- How fast it loads
How fast the page loads and becomes usable. Weighted from Total Blocking Time (30%), Largest Contentful Paint (25%), Cumulative Layout Shift (25%), First Contentful Paint (10%) and Speed Index (10%).
- Accessibility
- Usable by everyone
Whether people using screen readers, keyboards or low vision can use the page: contrast, labels, alt text, headings and focus order.
- Best practices
- Safe, modern code
Modern, safe web standards: HTTPS, no console errors, no deprecated APIs, correctly sized images and safe third-party scripts.
- SEO
- Easy for Google to read
Basics search engines need: a title and meta description, crawlable links, a valid robots.txt, readable font sizes and mobile-friendly viewport settings.
Core Web Vitals: the numbers to hit
Google uses Core Web Vitals from real visitors as a ranking signal. Lighthouse measures the lab versions of the same experience, so improving one usually improves the other.
| Metric | Measures | Good |
|---|---|---|
| LCP — Largest Contentful Paint | When the main content appears | ≤ 2.5 s |
| INP — Interaction to Next Paint | How fast the page reacts to taps and clicks | ≤ 200 ms |
| CLS — Cumulative Layout Shift | How much the layout jumps while loading | ≤ 0.1 |
| TBT — Total Blocking Time (lab) | Main-thread blocking; the lab stand-in for INP | ≤ 200 ms |
| FCP — First Contentful Paint | When anything first appears | ≤ 1.8 s |
Quick wins
- →Compress images. WebP/AVIF, right size, lazy-load.
- →Ship less JavaScript. Split bundles, drop unused libraries.
- →Set image sizes. Stops the layout jumping.
- →Self-host fonts. Faster first paint, no extra request.
- →Delay third-party scripts. Chat widgets and tags load last.
Lighthouse only sees the surface
A green Lighthouse report means the page loads well. It says nothing about the code behind it — leaked API keys, routes anyone can call without logging in, errors that fail silently, loops that run up your cloud bill, or legal gaps that can get you fined. Periderm scans your codebase for those in under a minute, with 150+ checks built for apps made with AI.
FAQ
What is a good Lighthouse score?+
90–100 is good, 50–89 needs work, under 50 is poor. Aim for 90+ in every category.
Is this the same as PageSpeed Insights?+
Same Lighthouse engine, same scores — plus an AI fix plan you can copy into your AI assistant.
Why does my score change between runs?+
Network, server speed and third-party scripts vary. Compare a few runs, not one.
Does the score affect Google rankings?+
Not directly. Google uses Core Web Vitals from real visitors — but the same fixes improve both.
Is it free? Do I need an account?+
Free, no account. Sign up only to save reports and track progress.
Can I check localhost or a staging site?+
Only public URLs. For local builds, use Chrome DevTools or the Periderm CLI.
What doesn't Lighthouse check?+
Your code: leaked keys, open routes, silent errors, legal gaps. Periderm scans those.