benchmark

Detect web performance regressions from cumulative code changes across pull requests.

11|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill benchmark-ajsai47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/ajsai47/holyclaude/tree/main/skills/team/benchmark
Command: npx skills add https://github.com/ajsai47/holyclaude --skill benchmark-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web performance degrades incrementally with every PR — small bundle bloat, slow resource loads, and worsening Core Web Vitals add up to slow page loads and poor user experience that no one notices until it is too late. This Skill eliminates that blind spot by measuring actual performance data and comparing it against baselines.

Core Features & Use Cases

  • Baseline Capture: Record performance metrics (load times, Core Web Vitals, resource sizes) for your site before making changes.
  • PR Regression Checks: Compare pre-merge performance against baselines to catch slowdowns before they ship.
  • Trend Tracking: Monitor performance drift over time to identify gradual degradation.
  • Use Case: A frontend team can run this skill on every PR to ensure new code or dependencies do not increase page load time beyond acceptable thresholds.

Quick Start

Use the benchmark skill to run a full performance audit and baseline comparison for your production site's homepage.

Frequently Asked Questions about benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catch web performance regressions before merging a pull request?

Catch web performance regressions by running pre-merge checks that compare current Core Web Vitals and bundle size against baseline measurements. This detects incremental slowdowns caused by code or dependency changes before they ship to users.

What is the best way to track Core Web Vitals and bundle size drift over time?

Track Core Web Vitals and bundle size drift by recording baseline performance metrics and monitoring performance trends continuously. This approach identifies gradual degradation in page load time and resource sizes across cumulative code changes.

Can I use headless browser performance APIs to measure page speed for internal web applications?

Yes, you can use headless browser performance APIs to measure page speed for internal web applications. The benchmarking process captures load times and resource sizes for both public and internal sites to establish performance baselines.

How do I set up configurable regression threshold alerting for web vitals?

Set up configurable regression threshold alerting by defining acceptable performance limits for Core Web Vitals and bundle sizes during baseline capture. The system then alerts you when pre-merge PR checks detect metrics exceeding these configured thresholds.

Why does web performance degrade incrementally with every pull request?

Web performance degrades incrementally because small bundle bloat, slow resource loads, and worsening Core Web Vitals accumulate across pull requests. Continuous benchmarking against a baseline catches these cumulative code and dependency changes before user experience suffers.