benchmark

Benchmark real page load metrics against stored baselines to detect regressions.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/yashs33244/my-mac-claude --skill benchmark-yashs33244
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/gstack/benchmark
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill benchmark-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions slip into production when teams only rely on intuition or one-off checks, and then users notice slow page loads. This Skill measures real page performance, stores a baseline, and flags changes introduced by each PR.

Core Features & Use Cases

  • Measure real browser performance: Collects navigation timing and resource data using the browse daemon and in-page JavaScript evaluation for TTFB, FCP, LCP, DOM timing, load time, requests, and transfer size.
  • Baseline and compare per PR: Captures benchmark baselines with branch and timestamp context, then compares current results against the saved baseline to detect timing and bundle/resource regressions.
  • Make slowdowns actionable: Identifies the slowest resources and produces performance budget and trend-style summaries to guide targeted fixes.

Use case: you are preparing a PR that changes frontend bundles and you want to verify that LCP, load time, request count, and bundle size did not worsen compared to the last known good baseline.

Quick Start

Run benchmark for your site by telling the AI: "Benchmark https://example.com with --baseline before changes, then benchmark again after the changes and report any regressions."

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 a pull request?

To detect web performance regressions in a pull request, benchmark real page load metrics against stored baselines. This Skill compares current PR results with saved baseline data to flag timing, transfer size, and bundle size regressions.

How does baseline comparison work for Core Web Vitals monitoring?

Baseline comparison for Core Web Vitals works by capturing initial benchmark metrics with branch and timestamp context, then evaluating subsequent page loads against that stored baseline to identify any timing or resource regressions.

Can I track bundle size and transfer size changes across specific routes?

Yes, you can track bundle size and transfer size changes across specified routes or automatically discovered pages. The benchmarking process applies rule-based regression thresholds to monitor these resource variations per PR.

What real browser performance metrics are collected for trend analysis?

Real browser performance metrics collected for trend analysis include TTFB, FCP, LCP, DOM timing, load time, request count, and transfer size, extracted using in-page JavaScript evaluation and navigation timing data.

Do I need a browse daemon to measure page load metrics?

Yes, you need a browse daemon for page navigation to measure page load metrics. The daemon enables in-page JavaScript evaluation to extract performance entries and collect real browser timing data for baseline comparison.

How do I make slowdowns actionable after identifying performance regressions?

To make slowdowns actionable after identifying performance regressions, review the generated performance budget and trend summaries. These outputs identify the slowest resources to guide targeted fixes for the detected page speed regressions.