Detect performance regressions in web applications by benchmarking Core Web Vitals and resource sizes.
npx skills add https://github.com/fghaffar/faystack --skill benchmark-fghaffar
Please help me install this Agent Skill. Skill: benchmark Source: https://github.com/fghaffar/faystack/tree/main/benchmark Command: npx skills add https://github.com/fghaffar/faystack --skill benchmark-fghaffar
Teams struggle to notice subtle performance degradations that accumulate over many pull‑requests, leading to slower pages, higher bounce rates, and increased infrastructure costs.
Run /benchmark https://example.com --baseline to create a performance baseline for the site.
High-intent search queries and answers about installing and using this skill.
To detect web performance regressions in pull requests, you can run a benchmark against a stored baseline to compare Core Web Vitals, resource sizes, and load timings, flagging any degradation before it merges.
Core Web Vitals are key metrics for web page load speed and user experience. You can benchmark them by capturing an automated baseline and comparing current metrics against it to identify performance drift.
You can enforce performance budgets in CI by running a benchmark on every PR that compares current load times and resource sizes against a stored baseline, preventing regressions from reaching production.
Yes, you need a git repository context to track page load metrics over time. The benchmark also requires the gstack browse daemon and Bash command execution to collect data and generate trend reports.
The best way to visualize long-term performance drift is by running trend reporting across multiple benchmark runs, which compares current Core Web Vitals against stored baselines to spot gradual degradations.
You should monitor resource sizes and load timings on PR changes because subtle degradations accumulate over many pull requests, leading to slower pages, higher bounce rates, and increased infrastructure costs.
steadyfallCollect end-to-end web performance metrics from the browse daemon across pages.
AGIBuildCompare BenchmarkDotNet JSON results against GitHub Actions artifact baselines.
CaltexBevoMeasure page timings and resource usage against stored baselines to identify performance regressions.
yocxy2Measure page load times, Core Web Vitals, and resource sizes to detect performance regressions.
