whatisgithub

What is lighthouse-ci?

googlechrome/lighthouse-ci — explained in plain English

Analysis updated 2026-06-24

6,963JavaScriptAudience · developerComplexity · 3/5Setup · moderate

In one sentence

Lighthouse CI automatically runs Google Lighthouse audits on your website inside your CI pipeline, catching performance, accessibility, and SEO regressions in pull requests before they reach your users.

Mindmap

mindmap
  root((repo))
    What it does
      Automated audits
      Score thresholds
      Regression detection
    Audit Categories
      Performance
      Accessibility
      SEO
      Best practices
    Setup Options
      GitHub Actions
      Custom CI server
      History dashboard
    Audience
      Web developers
      DevOps teams
      Quality engineers
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Automatically fail a pull request if a code change drops the site's performance or accessibility score below your set threshold.

USE CASE 2

Track how Lighthouse scores change across every commit to spot gradual performance degradation over time.

USE CASE 3

Compare two builds of your site side by side to identify which specific pages got slower or worse.

USE CASE 4

Run Lighthouse audits on every push using the ready-to-copy GitHub Actions workflow in the README.

What is it built with?

JavaScriptNode.jsGitHub Actions

How does it compare?

googlechrome/lighthouse-ciaheckmann/gmmomo707577045/m3u8-downloader
Stars6,9636,9786,978
LanguageJavaScriptJavaScriptJavaScript
Setup difficultymoderatemoderateeasy
Complexity3/52/51/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires a CI pipeline and a build command that produces your site, the GitHub Actions example in the README can be copy-pasted to get started quickly.

License not specified in the explanation.

So what is it?

Lighthouse CI is a set of tools from Google Chrome that automatically checks your website's quality every time you push code changes. It is built on top of Lighthouse, a tool that audits web pages and scores them on performance, accessibility, SEO, and how well they follow web best practices. The CI part means it runs those audits automatically in your continuous integration pipeline, the automated system that runs checks whenever code changes are submitted. The main use case is catching problems before they reach your users. If a code change makes your site slower, breaks something for screen reader users, or drops your SEO score, Lighthouse CI can flag that change and block it from being merged. You set thresholds for the scores you care about, and the system fails the check if any score drops below them. Over time, you can also track how your scores change across commits and compare two versions of your site to see which specific files or pages got better or worse. To use it, you add a short configuration to your project's CI workflow file. The README includes a ready-to-copy example for GitHub Actions that installs Lighthouse CI and runs it against your built site on every push. For teams that want to store and view historical results, there is an optional server component you can run yourself that provides a dashboard for browsing past reports and comparing runs. The tooling is aimed at web developers who want to make quality checks part of their regular development process rather than something done manually and occasionally. A getting-started guide and introductory documentation for people unfamiliar with CI are both linked from the README. There is also a community-built GitHub Action that requires no separate server infrastructure if you just want to run checks on pull requests.

Copy-paste prompts

Prompt 1
Show me how to add Lighthouse CI to my GitHub Actions workflow to check performance and accessibility on every pull request, with a fail threshold of 80 for the performance score.
Prompt 2
I want to set up the optional Lighthouse CI server so my team can view historical score trends in a dashboard. Walk me through the deployment options.
Prompt 3
My Lighthouse CI check is failing on a pull request but I cannot tell which file caused the regression. How do I use the comparison report to find the problem?
Prompt 4
How do I configure Lighthouse CI to audit only specific URLs on my site instead of scanning every page?
Prompt 5
I want Lighthouse CI to block merges if the accessibility score drops below 90. Show me the exact configuration file entries I need.

Frequently asked questions

What is lighthouse-ci?

Lighthouse CI automatically runs Google Lighthouse audits on your website inside your CI pipeline, catching performance, accessibility, and SEO regressions in pull requests before they reach your users.

What language is lighthouse-ci written in?

Mainly JavaScript. The stack also includes JavaScript, Node.js, GitHub Actions.

What license does lighthouse-ci use?

License not specified in the explanation.

How hard is lighthouse-ci to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is lighthouse-ci for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.