Measure page load metrics and resource sizes to detect performance regressions across branches and PRs.
npx skills add https://github.com/ibalasite/gstack --skill benchmark-ibalasite
Please help me install this Agent Skill. Skill: benchmark Source: https://github.com/ibalasite/gstack/tree/main/benchmark Command: npx skills add https://github.com/ibalasite/gstack --skill benchmark-ibalasite
Detect silent performance regressions that accumulate across commits by measuring real page load metrics, Core Web Vitals, and resource sizes so you can find when and why a site got slower.
Run /benchmark https://your-site.example --baseline to capture a baseline, then run /benchmark https://your-site.example to compare the current branch against that baseline and generate a report.
High-intent search queries and answers about installing and using this skill.
You detect performance regressions in pull requests by comparing current Core Web Vitals and bundle sizes against a saved baseline. This Skill measures page load metrics across branches to alert you on regressions.
Frontend performance regression detection requires tracking TTFB, FCP, LCP, DOM timings, full load times, resource sizes, request counts, and bundle breakdowns to identify when and why a site gets slower.
You set up a performance baseline by running the benchmark command against your site URL with the baseline flag. This captures a snapshot of current Core Web Vitals and bundle sizes for future comparison.
Yes, performance benchmarking requires a browse daemon capable of navigating pages and evaluating JavaScript. This daemon collects real page load metrics and writes baseline and report files to the benchmark-reports directory.
Yes, you can audit bundle sizes and request counts in your CI workflow. This Skill integrates into pull request workflows to measure resource sizes, display historical trends, and check performance budget compliance.
You should measure Core Web Vitals before and after a dependency upgrade to ensure LCP and JS bundle size did not regress. This prevents silent performance regressions from accumulating across commits.
jonkikyCollect navigation timing and resource data to establish performance baselines and detect regressions.
JaykaijackMeasure browser performance metrics and compare them to stored baselines.
elasticReduce Kibana plugin page load bundle size and manage package limits.
achmfRun Lighthouse audits to analyze Core Web Vitals and rendering bottlenecks.
