PageSpeed Matters
    Speed Audit
    Let's Talk
    PageSpeed Matters
    Book a Call
    Tools & Data Sources · Glossary

    Lighthouse · Definition & Explanation 2026

    Lighthouse is Google's open-source, automated tool for auditing web page quality across four categories: Performance, Accessibility, Best Practices, and SEO. It powers the lab data section of PageSpeed Insights and is built directly into Chrome DevTools, making it the most accessible and widely used performance testing tool in the world.

    The performance score (0–100) is a weighted composite of five metrics: Total Blocking Time (30%), Largest Contentful Paint (25%), Cumulative Layout Shift (25%), First Contentful Paint (10%), and Speed Index (10%). Each metric is scored against a log-normal distribution derived from HTTP Archive data — meaning the score reflects how a page compares to the broader web.

    Lighthouse simulates a mid-tier mobile device (Moto G Power) on a throttled 4G connection. This controlled environment makes results reproducible but means scores can differ significantly from real-user (CrUX) data. Understanding this distinction is critical: Lighthouse diagnoses problems; CrUX determines rankings.

    In 2026, Lighthouse 12+ includes enhanced INP diagnostics, long animation frame (LoAF) attribution, and improved third-party script identification. It remains the essential starting point for any performance optimization effort.

    Updated 2026-02-28
    M
    By Matt Suffoletto

    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:

    1. 1High TBT (30% weight) — Large JavaScript bundles, third-party scripts, no code splitting.
    2. 2Slow LCP (25% weight) — Unoptimized hero images, no preload, slow server response.
    3. 3High CLS (25% weight) — Images without dimensions, dynamic content injection, web fonts.
    4. 4Slow FCP (10% weight) — Render-blocking CSS/JS, slow TTFB.
    5. 5High Speed Index (10% weight) — All-at-once rendering, no progressive loading.

    Frequently Asked Questions

    90–100 is good (green), 50–89 needs improvement (orange), 0–49 is poor (red). Most well-optimized sites score 80–95 on mobile. A perfect 100 is achievable but often impractical for complex sites.

    Lighthouse scores vary ±5 points due to network variability, CPU load, and browser state. Run 3-5 times and use the median. Lighthouse CI averages multiple runs automatically.

    PSI runs Lighthouse on Google's servers (consistent hardware/network). DevTools runs on your machine (varies by CPU/network). PSI results are more comparable across tests.

    No — Lighthouse is a lab tool. Google uses CrUX field data for ranking decisions. However, improving Lighthouse scores typically improves CrUX scores over time.

    Focus on the highest-weighted metrics: TBT (30%) and LCP/CLS (25% each). Typically: reduce JavaScript, optimize images, fix layout shifts. Address the largest Opportunities first.

    Mobile first — Lighthouse's default mobile simulation (throttled 4G, mid-tier phone) is much harder to pass and reflects more users. Desktop scores are typically 20–30 points higher.

    Opportunities show specific fixes with estimated time savings (actionable). Diagnostics provide context and analysis (informational). Start with Opportunities.

    Yes — Lighthouse CI (lhci) runs on every deploy. Set assertions like 'performance ≥ 80' to fail builds that regress. Integrates with GitHub Actions, GitLab CI, and Jenkins.

    Struggling with Lighthouse?

    Request a free speed audit and we'll identify exactly what's holding your scores back.

    Request An Audit