Lighthouse CI in CI/CD pipeline
Why it matters
Performance regressions introduced by a dependency update, an accidental eager import, or a new feature are invisible without automated measurement. By the time a user reports that the site "feels slow," the regression may have been live for weeks and has already impacted SEO rankings, conversion rates, and Core Web Vitals scores. ISO 25010:2011 time-behaviour captures the measurement requirement; Lighthouse CI enforces a performance floor in the same pipeline that would otherwise let the regression ship undetected.
Severity rationale
High because without Lighthouse CI in the deployment pipeline, performance regressions merge and ship silently, compounding over time with no automated gate to catch degradation before it reaches production.
Remediation
Add Lighthouse CI to your GitHub Actions workflow using treosh/lighthouse-ci-action. Set a budgetPath to enforce score thresholds — fail the build if the performance score drops more than 5 points from the previous run.
# .github/workflows/lighthouse.yml
jobs:
lighthouse:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: treosh/lighthouse-ci-action@v11
with:
urls: 'https://your-preview-url.vercel.app'
budgetPath: './lighthouse-budget.json'
uploadArtifacts: true
In lighthouse-budget.json, set "numericValue": 2500 for LCP and a minimum performance score of 85.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Performance Deep Dive Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- iso-25010:2011 · time-behaviour — Time Behaviour (performance efficiency)
Taxons
History
- 2026-04-18·v1.0.0·Initial import from performance-deep-dive·automated