GoogleChrome/lighthouse
Automated auditing, performance metrics, and best practices for the web.
From the publisher
README & documentation
Source previewRead the project’s overview, installation instructions and usage examples. The original README is the source of truth.
Lighthouse is integrated directly into the Chrome DevTools, under the "Lighthouse" panel. Installation: install Chrome. Run it: open Chrome DevTools, select the Lighthouse panel, and hit "Generate report". The Chrome extension was available prior to Lighthouse being available in Chrome Developer Tools, and offers similar functionality. Installation: install the extension from the Chrome Web Store. Run it: follow the extension quick-start guide. The Node CLI provides the most flexibility in how Lighthouse runs can be configured and reported. Users who want more advanced usage, or want to run Lighthouse in an automated fashion should use the Node CLI. Installation: Run it: lighthouse https://airhorner.com/ By default, Lighthouse writes the report to an HTML file. You can control the output format by passing flags. You can run a subset of Lighthouse's lifecycle if desired via the --gather-mode (-G) and --audit-mode (-A) CLI flags. The first time you run the CLI you will…
Read the full README ↗ · Preview checked 2026-11-01T07:56:35.835Z
Inside the original README — Document outline
- Lighthouse [](https://github.com/GoogleChrome/lighthouse/actions/workflows/ci.yml) [](https://github
- Using Lighthouse in Chrome DevTools
- Using the Chrome extension
- Using the Node CLI
- CLI options
- Output Examples
- Lifecycle Examples
- Notes on Error Reporting
- Using the Node module
- Viewing a report
- Online Viewer
- Docs & Recipes
Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.
Links from the README
References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.
Documentation belongs to its respective authors. Reported project/model license: Apache-2.0. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.
What this repository does
Automated auditing, performance metrics, and best practices for the web.
Repository facts
- Owner
- GoogleChrome
- Primary language
- JavaScript
- Stars
- 30,988
- Forks
- 9,781
- Open issues + pull requests
- 428
- License
- Apache-2.0
- Archived
- No
- Default branch
- main
- Created
- 2016-03-08T01:03:11.000Z
- Last push
- 2026-10-30T20:36:50.000Z
Topics and intended use
Owner-supplied topics: audit, best-practices, chrome-devtools, developer-tools, performance-analysis, performance-metrics, pwa, web
Review the README for scope, installation, examples and limitations. We do not run repository code or certify it.
Evaluate before installing
Review licensing and dependencies, inspect recent commits and unresolved issues, and test in an isolated environment before production use. Stars and forks alone cannot answer these questions.
Source and freshness
Source: GitHub. Metadata observed 2026-10-31T12:19:26.881Z. Daily imports are snapshots, not real-time monitoring.
Popularity and source listings do not establish security, suitability, licensing rights or benchmark performance.