TL;DR — Quick Summary
Lighthouse is Google's open-source auditing tool scoring performance (TBT 30%, LCP 25%, CLS 25%, FCP 10%, SI 10%), accessibility, best practices, and SEO. Runs in Chrome DevTools, CLI, CI/CD, and powers PSI's lab data. The essential first step for performance optimization.
What is Lighthouse?
Lighthouse is an open-source tool by Google that audits web page quality. The performance score is weighted: TBT 30%, LCP 25%, CLS 25%, FCP 10%, Speed Index 10%. It provides specific, actionable recommendations organized as Opportunities (potential time savings) and Diagnostics (additional information). Runs in Chrome DevTools, as a CLI tool, as a Node module, or via PageSpeed Insights.
History & Evolution
Key milestones:
- •2016 — Lighthouse launched as a Chrome extension for Progressive Web App auditing.
- •2017 — Integrated into Chrome DevTools. Performance auditing added.
- •2018 — Lighthouse 3.0: new performance scoring model, accessibility audits.
- •2020 — Lighthouse 6.0: TBT and CLS added. Performance scoring reweighted for CWV alignment.
- •2022 — Lighthouse 10: TTI removed from scoring. TBT weight increased to 30%.
- •2024 — INP diagnostics added. FID-related audits removed.
- •2025–2026 — Lighthouse 12+: LoAF attribution, enhanced third-party identification, improved mobile simulation.
How Lighthouse is Measured
Lighthouse measures performance by simulating a page load on a mid-tier mobile device (Moto G Power, ~$200 phone) with throttled 4G connection (1.6 Mbps down, 150ms RTT). The simulation captures five metrics, each weighted in the final score.
Running Lighthouse:
- •Chrome DevTools — Lighthouse tab → Generate report. Easiest for manual testing.
- •PageSpeed Insights — pagespeed.web.dev → Enter URL. Includes both lab and field data.
- •CLI — `npx lighthouse https://example.com --output=html`. Best for scripting.
- •CI/CD — Lighthouse CI (`lhci`) for automated regression testing on every deploy.
- •Node module — Programmatic access for custom dashboards.
Key rule: Field data (CrUX) determines Google rankings. Lab data (Lighthouse, WebPageTest) is for debugging and iteration.
Common Causes of Poor Lighthouse Scores
Common causes of low Lighthouse performance scores:
- 1High TBT (30% weight) — Large JavaScript bundles, third-party scripts, no code splitting.
- 2Slow LCP (25% weight) — Unoptimized hero images, no preload, slow server response.
- 3High CLS (25% weight) — Images without dimensions, dynamic content injection, web fonts.
- 4Slow FCP (10% weight) — Render-blocking CSS/JS, slow TTFB.
- 5High Speed Index (10% weight) — All-at-once rendering, no progressive loading.
Frequently Asked Questions
For step-by-step optimization, platform-specific fixes, code examples, and case studies, read our full guide:
The Ultimate Guide to Website Performance Measurement, Tools & Data: Lab, Field & Everything Between in 2026Struggling with Lighthouse?
Request a free speed audit and we'll identify exactly what's holding your scores back.