explaingit

googlechrome/lighthouse

30,157JavaScriptAudience · developerComplexity · 2/5Setup · easy

TLDR

An automated tool that analyzes any web page and scores it 0, 100 on speed, accessibility, best practices, and SEO, then gives you a prioritized list of specific things to fix.

Mindmap

mindmap
  root((lighthouse))
    What it checks
      Performance
      Accessibility
      Best practices
      SEO
    How it works
      Loads the page
      Runs audits
      Scores 0 to 100
    Output formats
      HTML report
      JSON data
    How to run
      Chrome DevTools
      CLI tool
      Node module
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

Things people build with this

USE CASE 1

Run a health check on your website to find out exactly why it loads slowly and which fixes will have the biggest impact.

USE CASE 2

Check that your web page is accessible to users with disabilities and get a specific list of issues to address.

USE CASE 3

Add Lighthouse to your build pipeline to automatically catch performance or SEO regressions before a site goes live.

USE CASE 4

Get a prioritized list of SEO improvements for a landing page so it ranks better in search results.

Tech stack

JavaScriptNode.js

Getting it running

Difficulty · easy Time to first run · 5min

In plain English

Lighthouse is an automated tool that analyzes web pages and produces a scored report covering performance, accessibility, best practices, and SEO (search engine optimization). Think of it as a health check for a website: you point it at a URL, it loads the page in a controlled environment, measures how fast it loads and how well it is built, and then gives you a score from 0 to 100 in each category along with specific recommendations for improvement. It works by launching a browser in the background, loading the page, collecting data (how long key content takes to appear, whether images have descriptive labels for screen readers, whether the page is secure, and so on), and then running those measurements through a set of audits, checks against defined best practices. The results are saved as an HTML report you can open in a browser, or as JSON for automated pipelines. You can run Lighthouse in several ways: directly from the Lighthouse tab in Chrome's built-in developer tools, as a browser extension, or as a command-line tool for automated or repeated testing. The command-line version is useful for running audits as part of a build process so that performance regressions are caught before a site goes live. It can also be imported as a module into your own JavaScript code. You would use it whenever you want objective measurements of a web page's quality and a prioritized list of specific things to fix. The tech stack is JavaScript, running on Node.

Copy-paste prompts

Prompt 1
Using the Lighthouse CLI, run an audit on my website and walk me through the top 3 things I should fix to improve the performance score.
Prompt 2
Help me add Lighthouse to my CI pipeline so it fails the build automatically if the performance score drops below 80.
Prompt 3
I got a Lighthouse accessibility score of 62. Walk me through the most common issues it flags and how to fix each one.
Prompt 4
Show me how to import Lighthouse as a Node.js module and run a programmatic audit that saves the full results as a JSON file.
Open on GitHub → Explain another repo

← googlechrome on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.