Lighthouse CI
Use Lighthouse CI after you know which budgets and audits matter.
Community support
Upvotes come from SearchEngineAnswer members. GitHub stars and reader reviews are counted separately.
Claim this tool if you maintain it.
- Best for
- Performance
- Setup required
- Node.js and a build pipeline
- Costs to check
- Hardware/hosting, integration and maintenance time; optional services are separate
- License in catalog
- Apache-2.0
Project screenshot
GitHub repository
- GitHub stars
- 7,134
- Forks
- 731
- Last push
- 2026-11-03
- Primary language
- JavaScript
GitHub snapshot from . Stars count GitHub bookmarks. Reader ratings appear separately below.
How to install Lighthouse CI
-
Add the Lighthouse CI CLI to a test project and use the same browser and runner for each build.
npm install --save-dev @lhci/cli - Create a Lighthouse CI configuration with one route and a small set of assertions. Follow the README’s collection settings for your build.
First tutorial for Lighthouse CI
- Run the same build repeatedly to establish variation, then introduce a known regression in a test branch.
- Check that the assertion reports the affected route and metric. Adjust tolerances if normal lab noise triggers failures.
Where Lighthouse CI fits
Run Lighthouse checks in a build pipeline and catch meaningful performance regressions.
- When to choose another tool
- Start with Lighthouse alone if you are still investigating the baseline and have no stable test environment.
- First evaluation
- Run the same build several times to establish normal variation. Set a tolerance for one metric on one stable route, then deliberately exceed it in a test branch and verify that the build reports the failure.
- How to interpret the result
- Keep the runner, browser and tested URL consistent. Avoid making small score swings a release blocker.
Reviews and discussion
Reader reviews
Be the first to share your experience with this tool.
Discussion
Ask a question or share a setup tip.
Flag an outdated detail
Include the field that needs updating and a source link. Copy your draft, then use the corrections policy to contact the editorial team.
Write a review or join the discussion