benchmark

Compare page navigation timing and bundle data against baselines in pull requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gfires/motion-analysis --skill benchmark-gfires
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/gfires/motion-analysis/tree/main/benchmark
Command: npx skills add https://github.com/gfires/motion-analysis --skill benchmark-gfires

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions slip into PRs because real-user page timings drift after changes. This Skill automates measurement, baselining, and comparison to surface regressions early.

Core Features & Use Cases

  • Baseline capture and drift analysis across PRs
  • Per-page timing metrics (TTFB, FCP, LCP, DOM metrics, Full Load)
  • Resource and bundle size analysis with top offenders
  • Trend analysis over historical data to spot deterioration
  • Human-readable reports and machine-friendly JSON outputs

Quick Start

Run /benchmark <url> to start a full performance audit and baseline comparison

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

Detect web performance regressions by collecting navigation timing, resource usage, and bundle data from real pages, then comparing current measurements against stable baselines to highlight regressions and warnings directly in pull requests.

What web vitals and timing metrics are needed for baseline drift analysis?

Baseline drift analysis requires per-page timing metrics including TTFB, FCP, LCP, DOM metrics, and Full Load, alongside resource and bundle size data, to accurately spot performance deterioration over historical data trends.

How do I audit bundle size and identify top resource offenders in a web app?

Audit bundle size and identify top resource offenders by collecting resource usage and bundle data from real pages during a performance audit, which highlights the largest assets contributing to page weight and latency regressions.

Do I need a browse daemon to automate performance benchmarking?

Yes, automated performance benchmarking requires a browse daemon to actively collect navigation timing and resource data from real pages, ensuring consistent reporting output for both machine-readable JSON and human-friendly summaries.

Can I get machine-readable JSON outputs for performance trend analysis?

Yes, performance trend analysis generates machine-friendly JSON outputs containing current measurements and baseline comparisons, allowing you to programmatically track deterioration and integrate performance data into CI/CD pipelines.

What is the best way to compare current page timings against historical performance baselines?

The best way to compare page timings against historical baselines is to run a full performance audit that captures stable baseline metrics first, then automatically highlights regressions and warnings across multiple pages when new timings drift.