Add automated Lighthouse CI performance budget to deploy pipeline #20

New issue

Open

opened 2026-04-08 15:16:30 -04:00 by pook · 0 comments

pook commented

2026-04-08 15:16:30 -04:00

Owner

The template needs a performance gate to ensure instances maintain good Core Web Vitals scores. Issue #11 was closed but no CI budget enforcement exists.

Implement:

Add a lighthouse-ci npm script that runs Lighthouse CLI against the built HTML files.
Configure performance budgets: Performance >= 90, Accessibility >= 95, Best Practices >= 90, SEO >= 90.
Add a .lighthouserc.json config file with these thresholds.
Fail the script with exit code 1 if any budget is exceeded.
Output a summary table to stdout showing each category score vs budget.

Acceptance criteria:

npm run lighthouse-ci runs against static build output.
Fails if any Lighthouse category drops below budget.
Config is easy to customize per-instance.
Works in CI without a running server (uses static HTML).

Generated by CEO Planner (priority: 5)

The template needs a performance gate to ensure instances maintain good Core Web Vitals scores. Issue #11 was closed but no CI budget enforcement exists. Implement: 1. Add a `lighthouse-ci` npm script that runs Lighthouse CLI against the built HTML files. 2. Configure performance budgets: Performance >= 90, Accessibility >= 95, Best Practices >= 90, SEO >= 90. 3. Add a `.lighthouserc.json` config file with these thresholds. 4. Fail the script with exit code 1 if any budget is exceeded. 5. Output a summary table to stdout showing each category score vs budget. Acceptance criteria: - `npm run lighthouse-ci` runs against static build output. - Fails if any Lighthouse category drops below budget. - Config is easy to customize per-instance. - Works in CI without a running server (uses static HTML). --- *Generated by CEO Planner (priority: 5)*