benchmark

Measure web performance metrics to detect regressions across routes and branches.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection across changes using the browse daemon. It establishes baselines for page load times, Core Web Vitals, and resource sizes, and compares results before/after changes to surface regressions.

Core Features & Use Cases

  • Baseline capture and comparison for PRs
  • Page-level performance metrics (TTFB, FCP, LCP, DOMInteractive, DOMComplete, etc.)
  • Resource and bundle size analysis
  • Trend analysis across historical benchmarks
  • Save and view reports locally in .gstack/benchmark-reports

Quick Start

Run the benchmark on a URL to capture a baseline or compare current results against the baseline.

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?

To detect web performance regressions across pull requests, you can capture baseline metrics for page load times and Core Web Vitals, then compare current results against that baseline to surface changes. This requires the browse daemon and a local JSON store under .gstack/benchmark-reports.

What Core Web Vitals and DOM metrics can I collect for baseline performance analysis?

For baseline performance analysis, you can collect TTFB, FCP, LCP, DOMInteractive, and DOMComplete events. The benchmark also gathers resource and bundle size data to provide a comprehensive view of page-level performance regressions.

How do I compare performance metrics between diff branches before and after changes?

You can compare performance metrics between diff branches by running the benchmark on a URL to capture current results, which are then compared against the saved baseline JSON store under .gstack/benchmark-reports to surface regressions across deployments.

Do I need the browse daemon to measure page load times and resource sizes?

Yes, you need the browse daemon to measure page load times and resource sizes. It is required to establish baselines for Core Web Vitals and bundle data, and to save and view the resulting reports locally in .gstack/benchmark-reports.

Can I track historical performance trends for multiple routes?

Yes, you can track historical performance trends for multiple routes. The benchmark saves reports locally in .gstack/benchmark-reports, allowing you to analyze trend data across historical benchmarks and surface performance changes over time.