A GitHub Action for running Lighthouse audits and performance tests with Lighthouse CI in your CI/CD pipeline.
Lighthouse CI Action is a GitHub Action that automates Lighthouse performance audits and integrates Lighthouse CI into GitHub workflows. It allows developers to test URLs against performance budgets, run custom Lighthouse assertions, and store results directly within their CI/CD pipeline. The tool helps maintain web performance standards by catching regressions before they reach production.
Web developers, DevOps engineers, and teams using GitHub Actions who need to integrate automated performance testing and monitoring into their continuous integration workflows.
Developers choose this action for its tight integration with GitHub Actions, eliminating the need for separate performance monitoring setups. It provides a fast, configurable way to enforce performance budgets and run Lighthouse audits directly in CI, with results visible in the GitHub interface.
Audit URLs using Lighthouse and test performance with Lighthouse CI.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Initializes in under a second, as stated in the README, ensuring minimal overhead and quick feedback in CI pipelines without slowing down workflows.
Supports multiple storage options including temporary public storage, private LHCI servers, and GitHub artifacts, allowing teams to choose based on privacy and persistence needs, as detailed in the inputs section.
Enables use of Lighthouse CI configuration files for advanced assertions, Chrome flags, and plugin integration, demonstrated in recipes like custom Lighthouse config and plugin usage.
Displays failed tests directly in the action interface and integrates outputs with other GitHub Actions, making it easy to catch regressions and compose workflows, as shown in the output examples.
Temporary public storage uploads reports to a public Google Cloud URL by default, which may expose sensitive data and is automatically deleted after 7 days, limiting long-term privacy and retention.
For private, secure result storage, it requires setting up and maintaining a separate LHCI server, adding infrastructure complexity and maintenance overhead beyond the action itself.
The README warns that single runs can lead to flaky performance assertions, necessitating multiple runs for reliability, which increases CI time and resource usage without guarantees.