Monitor production website performance with Core Web Vitals budgets and alerts.
npx skills add https://github.com/Soborbo/claudeskills --skill speed-monitoring
Please help me install this Agent Skill. Skill: speed-monitoring Source: https://github.com/Soborbo/claudeskills/tree/main/speed-monitoring Command: npx skills add https://github.com/Soborbo/claudeskills --skill speed-monitoring
This Skill provides a structured approach to detect and prevent speed regressions by implementing continuous performance measurement, budgets, and alerts.
Set up budget.json, lighthouserc.json, and a web-vitals integration to begin monitoring production performance.
High-intent search queries and answers about installing and using this skill.
To prevent website speed regressions, use performance budgets with Lighthouse CI to block deployments that exceed thresholds. You set up a budget.json file and lighthouserc.json to automatically evaluate metrics during integration and deployment processes.
Tracking Core Web Vitals requires combining Real User Monitoring (RUM) for field data with synthetic Lighthouse tests for lab data. This dual approach captures actual user experience alongside controlled environment metrics to surface performance trends over time.
Configuring performance budgets in Lighthouse CI involves creating a budget.json file to define metric thresholds like LCP and CLS. You also need a lighthouserc.json file to integrate these budgets into your continuous integration pipeline for automated checks.
Yes, you can maintain specific Core Web Vitals thresholds by implementing continuous performance monitoring. Setting up budgets, RUM, and automated alerts ensures that any new feature causing metrics like LCP to exceed 2.5s triggers a review before user impact.
Setting up automated alerts and a dashboard for Web Vitals tracking requires integrating a web-vitals library for RUM collection alongside Lighthouse CI. The collected lab and field data populates the dashboard to surface trends and trigger alerts when performance degrades.
You need both RUM and synthetic data because RUM provides real user field data while synthetic testing provides consistent lab data. Combining them ensures continuous performance monitoring accurately reflects both actual user experience and controlled baseline metrics.
DexploarerAutomate Lighthouse CI audits and enforce performance budgets in CI/CD pipelines.
adryanmoldokkr32-pixelDetect performance regressions by comparing navigation and resource timing metrics against URL baselines.
hopeovertureEnforce performance budgets on bundle sizes, Lighthouse scores, and Web Vitals in CI/CD pipelines.
josuenavarroaguadoDiagnose and fix web performance bottlenecks using Lighthouse, RUM, and profiling data.
