benchmark

Benchmark web page navigation timings and web vitals against a saved baseline.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents slowdowns from creeping into web apps by measuring real page performance, comparing results to a known baseline, and surfacing regressions with actionable signals.

Core Features & Use Cases

  • Baselines and comparisons: Captures timing and resource metrics, then compares before/after on every run to detect regressions rather than relying on guesswork.
  • Comprehensive web vitals & resource analysis: Measures navigation timings (TTFB/FCP/LCP/interactive/complete/load) and summarizes resource counts, transfer sizes, and slowest assets.
  • Trend tracking over time: Loads historical benchmark artifacts to show performance trends (including bundle/request growth) to support investigations across multiple PRs and days.

Quick Start

Run /benchmark https://example.com --baseline to capture your baseline, then run /benchmark https://example.com to compare and identify regressions.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I detect performance regressions in my web app across pull requests?

Detect performance regressions by benchmarking navigation timings and web vitals against a saved baseline. The benchmark skill compares before and after metrics on every run to surface slowdowns with actionable signals in PR-based workflows.

What web vitals and resource metrics are measured during page load benchmarking?

Page load benchmarking measures navigation timings including TTFB, FCP, LCP, interactive, complete, and load. It also summarizes resource counts, transfer sizes, and identifies slowest assets to provide comprehensive web vitals and resource analysis.

Can I track Core Web Vitals and bundle size trends over time across multiple PRs?

Yes, you can track Core Web Vitals and bundle size trends over time. The benchmark loads historical artifacts from date-stamped reports to show performance trends and support investigations across multiple PRs and days.

How do I capture a performance baseline and compare page load time for diffing?

Run the benchmark command with the --baseline flag to capture your baseline. Then run the benchmark command without the flag to compare current results against the baseline and identify regressions for diffing impacted pages.

Do I need a specific browse daemon to run performance benchmarking and regression detection?

Yes, performance benchmarking requires a browse daemon that supports goto, perf, and eval commands. This environment is necessary to capture timing metrics, apply timing and bundle thresholds, and classify regressions accurately.

When should I not use automated regression detection for page performance?

Automated regression detection is not suitable for environments lacking a compatible browse daemon supporting goto, perf, and eval. Without these capabilities, the tool cannot capture baselines, measure timings, or classify regressions effectively.