benchmark

Measure page performance and detect regressions against saved baselines.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chriswestt/claude-skills --skill benchmark-chriswestt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/chriswestt/claude-skills/tree/main/gstack/benchmark
Command: npx skills add https://github.com/chriswestt/claude-skills --skill benchmark-chriswestt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects performance regressions by establishing baselines for page load times, Core Web Vitals, and resource sizes, and by comparing current results against previous runs on every PR and tracking trends over time.

Core Features & Use Cases

  • Baseline creation: capture performance metrics for a set of pages or a URL.
  • Regression detection: identify meaningful deltas between current runs and baselines.
  • Trend analysis: visualize performance over time across branches and PRs to anticipate issues.

Quick Start

Run the benchmark against a URL to baseline, measure, and compare performance across pages.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I detect web performance regressions in my page load times?

To detect web performance regressions, you establish performance baselines for page load times and Core Web Vitals, then compare current measurement runs against those saved baselines to identify meaningful deltas.

What is the best way to track Core Web Vitals trends across pull requests?

Tracking Core Web Vitals trends across branches and PRs requires capturing baseline metrics for your pages, then comparing subsequent runs against those baselines to visualize performance changes over time and anticipate issues.

Can I capture baseline performance metrics for a full set of pages?

Yes, you can capture performance baselines for a full set of pages or a single URL. The measurement process collects navigation timing, resource timings, and JavaScript metrics to establish your baseline.

How do I run a quick page performance audit against a saved baseline?

You can run a quick audit by measuring current page performance against a previously saved baseline. This compares current navigation timing and resource metrics to baseline data to quickly identify regressions.

Do I need a specific browse-based timing tool to measure resource timings?

Yes, this baseline and regression detection process requires a browse-based timing tool to actively collect navigation timing, resource timings, and JavaScript metrics needed for baseline capture and trend reports.

What limitations exist when comparing current page performance to baselines?

Regression detection relies on comparing current results to saved baselines, meaning you must first capture baseline metrics for your pages before you can measure deltas or perform trend analysis on subsequent runs.