benchmark

Benchmark URL performance against historical baselines using the browse daemon.

Updated Mar 11, 2026

Search Tags:#performance #lighthouse #benchmark #baseline #web-vitals #pages

Ready to run

npx skills add https://github.com/TwoToned/gearflow --skill benchmark-twotoned

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/TwoToned/gearflow/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/TwoToned/gearflow --skill benchmark-twotoned

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions in web pages are hard to detect manually across PRs; this skill automates detection by collecting baselines for core metrics and tracking trends over time.

Core Features & Use Cases

Capture core web vitals (TTFB, FCP, LCP) and resource timing metrics for test pages.
Compare current measurements against historical baselines and highlight regressions or trends.
Support different workflows: baseline capture, quick checks, per-page diffs, and trend analysis across branches.

Quick Start

Benchmark a URL by running /benchmark <url> to capture baselines and compare the results against historical data.

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 across pull requests?▼

Detect web performance regressions automatically by collecting core web vitals like TTFB, FCP, and LCP for test pages, then comparing current measurements against historical baselines to highlight regressions and trends over time.

How do I benchmark a URL and capture baseline performance metrics?▼

Benchmark a URL by running the benchmark command on your target page to collect resource timing metrics and core web vitals, which captures and stores baseline data for subsequent performance comparisons.

Can I track web vitals trends and compare performance diffs across different branches?▼

Track web vitals trends across branches using per-page selections and diff comparisons, comparing current measurements against stored historical baselines to surface actionable regressions for faster debugging.

Does web performance benchmarking work for quick checks without setting up full baselines?▼

Quick checks are supported as a distinct workflow alongside baseline capture, per-page diffs, and trend analysis, allowing you to measure current page performance without committing full historical baselines.

What core web vitals and timing metrics are captured during a page performance benchmark?▼

Core web vitals captured include TTFB, FCP, and LCP, along with resource timing metrics, providing a comprehensive performance profile stored as baselines for generating comparison reports.

Why does my web vitals comparison report show performance regressions?▼

Performance regressions are surfaced when current web vitals measurements degrade compared to stored historical baselines, and the generated comparison report highlights these actionable deviations to accelerate debugging.