An open-source, automated tool that measures a web page's performance, accessibility, SEO, and progressive web app quality.
01What it is and how it works
Lighthouse is a headless audit tool that you can run in Chrome DevTools, as a command‑line script, or via an API. It loads the target URL, instruments the page, and runs a series of audits (performance, accessibility, SEO, best practices, and PWA). Each audit returns a pass/fail result and a weight that contributes to an overall score out of 100. The tool then produces a JSON report and a human‑readable HTML page with screenshots, suggestions, and links to further documentation.
Lighthouse checks a web page and gives scores for speed, accessibility, SEO, and PWA. It also lists steps to improve each score.
02What to do about it
You can start using Lighthouse this week by adding it to your development workflow. The most common ways are:
- Run
lighthousein the terminal against a live URL to get a quick HTML report. - Integrate the lighthouse CI step into your build pipeline to fail builds on low scores.
- Use the Chrome DevTools Audits panel for on‑the‑fly debugging.
- Schedule a nightly run and email the summary to the team.
03How it is measured or noticed
After a run, you see a performance score (0‑100) broken down into core web vitals: First Contentful Paint, Largest Contentful Paint, Cumulative Layout Shift, and Interaction to Next Paint. Accessibility shows pass/fail for ARIA and keyboard navigation. SEO includes checks for meta tags, heading structure, and link health. Best practices cover things like avoiding deprecated APIs. PWA audits verify service worker presence and offline capability. The HTML report also lists Opportunities and Diagnostics with estimated time savings.
04Common mistakes
Marketers often misuse Lighthouse data, leading to misguided optimizations.
- Treating a single run as a permanent baseline without re‑running after changes.
- Ignoring the runtime performance of the audit itself, which can skew scores.
- Applying SEO fixes based only on the “SEO” section while neglecting content quality.
- Assuming a high overall score means the page is perfect for all users.
05Limits
Lighthouse does not cover every edge case. It cannot audit client‑side JavaScript frameworks that render content dynamically without a server response. It also does not evaluate user experience factors like brand perception or emotional design. Some SEO checks are limited to basic on‑page signals; advanced ranking factors (backlinks, content relevance) are out of scope. Finally, the tool runs in a simulated environment, so network conditions and device characteristics may differ from real‑world usage.
06Worked example
`{
"categories": {
"performance": { "score": 0.92 },
"accessibility": { "score": 1 },
"seo": { "score": 0.85 },
"bestPractices": { "score": 0.98 },
"pwa": { "score": 0.76 }
},
"audits": {
"largest-contentful-paint": {
"displayValue": "2.1 s",
"score": 1,
"explanation": "The largest element is within the 2.5 s threshold."
}
}
}`
Frequently asked questions
How is Lighthouse different from a manual SEO audit?
Lighthouse is automated and runs against a single URL to produce instant scores, while a manual audit involves human judgment across many pages and qualitative factors. Use Lighthouse for quick, repeatable checks and manual audits for deeper strategic insights.
Should I run Lighthouse before or after deploying changes?
Run Lighthouse both before and after deployment to catch regressions and confirm improvements. It depends on your workflow, but integrating it into CI/CD pipelines ensures every change is validated.
Who can run Lighthouse and how?
Anyone with a browser can run Lighthouse through Chrome DevTools, and developers can use the CLI or API for automation. It requires no special permissions, just access to the page being audited.
Does Lighthouse still matter now that Google uses other ranking signals?
Yes, Lighthouse scores correlate with user experience signals that Google considers, even if they are not direct ranking factors. It remains a reliable proxy for performance and accessibility quality.
What happens if I ignore Lighthouse recommendations?
Ignoring critical issues like slow load times or poor accessibility can hurt user engagement and search visibility. You would notice higher bounce rates and lower conversion rates over time.
How long does it take to see Lighthouse score changes after fixes?
Scores update immediately after a re-run, but real-world impact on traffic may take weeks. Monitor Core Web Vitals in Search Console while iterating on improvements.
Asked out loud
spoken, not typedThe same term in the words somebody uses speaking to an assistant rather than typing into a box — written from the situation, which is why each one carries the situation it came from.
Open Chrome DevTools and run a Lighthouse audit on the page in question. It will show you the exact metrics that regressed, like Largest Contentful Paint or Cumulative Layout Shift.
Use the Lighthouse audit in Chrome on your phone or run it through a remote CI pipeline. The performance score and metric breakdowns will update within seconds of the deploy.
Run a Lighthouse SEO audit right now in DevTools to see which specific issues are flagged, like missing alt text or poor heading structure. That gives you concrete items to address immediately.