Configure Lighthouse CI budgets that fail builds on regressions and suggest a starter budget per page type (landing, product, checkout).
Generates a Lighthouse CI configuration with performance budgets tuned to a project's current performance baseline, then wires the config into a CI step that fails on regressions. Includes per-page-type starter budgets.
urls: array of URLs to audit (must be reachable from the runner).repo_dir: project root for placing the config.target_p75_lcp: explicit budget for LCP (default 2500ms).target_total_byte_weight_kb: default 1500.npx lhci collect --url=<each url> --numberOfRuns=3 --settings.preset=desktop and capture median scores per audit./ -> landing, /products/ -> product, /checkout/ -> checkout. Assign a starter budget tier per category.maxNumericValue for the four hero metrics (LCP, INP, CLS, TBT) to 1.1 * current_p75. This locks in the current state without immediate failure.total-byte-weight budget to min(current * 1.05, target_total_byte_weight_kb * 1024).script-count, image-count, stylesheet-count based on observed counts plus 10%..lighthouserc.json at <repo_dir>/.lighthouserc.json with assertions referencing the above budgets and assertMatrix per URL..github/workflows/lighthouse.yml running on pull_request: install lhci, run lhci autorun, and upload results to a temporary public storage.docs/perf-budget.md.Three files: .lighthouserc.json, .github/workflows/lighthouse.yml, docs/perf-budget.md. Stdout prints the per-URL p75 baseline used and the resulting budget value.
Run npx lhci autorun --config=.lighthouserc.json on the current main branch; expected outcome is zero assertion failures (the budget is set to current state plus a slack). Intentionally regress one metric (load a 100KB unused JS file) and rerun; the assertion must fail. If lhci can't reach the URL (auth wall), require a LHCI_BASIC_AUTH env var rather than skip the audit silently.
lhci collect --headful with login script.--puppeteerScript to set them.numberOfRuns to 5 and use the median; flag the URL as "high-variance".Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/lighthouse-budget-enforcer.
Write five Google Ads responsive search ad copy variants from a product description and audience — each fits headline length and includes a distinct CTA.
Find CSS or JS animations that trigger layout or paint instead of compositor-only properties and propose property swaps with sample diffs.
Read a Lighthouse or CrUX report and narrate LCP, CLS, and INP scores into a prioritized fix plan with concrete code suggestions.
Tighten a Content-Security-Policy by stripping wildcards and verifying the result against actual page resource loads observed in browser logs.
Identify unused CSS classes via PurgeCSS and propose a configuration that's safe in the presence of dynamically constructed class names.
Audit a Tailwind config for color contrast in dark mode and flag every text-on-background pair below WCAG AA thresholds.