benchmark

Measure web page performance and compare results against saved baselines.

Updated May 7, 2026
One-click install
npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill benchmark-tumeloramaphosa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/TumeloRamaphosa/StudEx-Valley-OS/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill benchmark-tumeloramaphosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents unnoticed slowdowns by measuring real page performance, comparing results to a saved baseline, and flagging regressions before they ship.

Core Features & Use Cases

  • End-to-end page timing and web-vital signals: Collects navigation and rendering metrics like TTFB, FCP, LCP, and load timing to quantify perceived slowness.
  • Resource and bundle analysis: Summarizes requests, transfer size, and top slowest resources to pinpoint why performance changed.
  • PR-ready baselining and comparison: Saves baseline measurements, compares current results to the baseline, and produces regression thresholds for quick decision-making.

Quick Start

Run the benchmark against your URL by asking: /benchmark https://your-app.example --baseline when capturing the starting point, then run /benchmark https://your-app.example after the change to see what regressed.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I catch Core Web Vitals regressions in my CI pipeline?

You can catch page speed regressions in CI by collecting real runtime navigation timing and Core Web Vitals from live URLs, saving a baseline, and comparing subsequent runs against deterministic regression thresholds.

What is browse-based performance benchmarking for web observability?

Browse-based performance benchmarking is the process of collecting real runtime navigation timing, core rendering metrics, and resource characteristics from live URLs to quantify perceived slowness and monitor web observability.

How do I detect bundle size and transfer-size regressions before shipping?

Detect bundle size regressions before shipping by measuring transfer size and summarizing top slowest resources from live URLs during PR workflows, then comparing current results to a persisted baseline to flag increases.

Can I benchmark page speed across multiple pages in a pull request?

Yes, you can benchmark page speed across multiple pages in a pull request by running browse-driven performance captures on several live URLs and producing deterministic comparison output with regression thresholds for each.

Does page speed benchmarking work with custom JavaScript evaluation during capture?

Page speed benchmarking supports optional JavaScript evaluation during the browse-driven performance capture, allowing you to collect custom metrics alongside standard navigation timing and Core Web Vitals signals.

What is the best way to set a performance baseline for web vitals monitoring?

The best way to set a performance baseline for web vitals monitoring is to capture initial TTFB, FCP, and LCP measurements from your live URL using a benchmark tool, then persist those results for future deterministic comparison.