GoogleChrome/lighthouse

Automated auditing, performance metrics, and best practices for the web.

View on GitHub ↗Jump to charts ↓Open shareable report →

GoogleChrome/lighthouse has 30k+ stars and 9.5k+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 1st, 2026
Created on March 8th, 2016
Open Issues & Pull Requests: 463 (+0)
GitHub issues: Enabled
Number of forks: 9,765
Total Stargazers: 30,886 (+0)
Total Subscribers: 611 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.6 hours
Mean response time: 100.2 days
90th percentile: 56.2 days
Tracked items: 664

Maintainer activity

4 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 16% of issues opened in the past year have never received a reply. 70% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "P1.5" is answered fastest, typically in under an hour, while "feature" waits about 14 days. 35% of tracked open issues have had no activity in three months. 64% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 240
New in 7 days: 6
Closed in 7 days: 10
Avg open age: 1,260 days
Stale 30+ days: 188
Stale 90+ days: 165

Recent activity

Opened in 7 days: 4
Closed in 7 days: 3
Comments in 7 days: 15
Events in 7 days: 22

Top labels

  • bug (232)
  • P3 (138)
  • P2 (123)
  • P1.5 (74)
  • needs-investigation (70)
  • needs-priority (65)
  • simulation / lantern (42)
  • feature (39)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Lighthouse is an automated auditing tool that analyzes web applications and pages to collect performance metrics and identify deviations from developer best practices.

The tool addresses the need for comprehensive web quality assessment by running a series of audits against live pages or applications. It collects modern performance metrics alongside checks for accessibility, progressive web app compliance, SEO, and general best practices. Lighthouse operates by instrumenting the page under test, gathering diagnostic data during page load and interaction, and then scoring and reporting on the findings through a structured audit report.

Lighthouse suits developers and teams who want to systematically measure and improve web quality. It works well for continuous integration pipelines where automated audits can catch regressions, for one-off performance investigations during development, and for tracking quality metrics over time. The tool is accessible through multiple interfaces: integrated directly into Chrome DevTools for quick ad-hoc audits, as a Node CLI for programmatic use and advanced configuration, and as a Chrome extension. The Node CLI offers the most flexibility for automated and customized runs, while the DevTools integration provides the lowest friction entry point for developers already using Chrome.

The project maintains active continuous integration with multiple test workflows covering unit tests, smoke tests, and code coverage tracking. Development activity shows consistent attention to the codebase with regular updates and a structured testing approach across different test categories.