googlechrome/lighthouse

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

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 46 minutes ago
Added to GitGenius on September 1st, 2026
Created on March 8th, 2016
Open Issues & Pull Requests: 464 (+0)
GitHub issues: Enabled
Number of forks: 9,759
Total Stargazers: 30,743 (+0)
Total Subscribers: 613 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

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.