benchmark

Measure and compare web performance metrics across pull requests to detect regressions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection across PRs by collecting baseline web performance metrics and comparing with current runs to identify degradations.

Core Features & Use Cases

  • Baseline capture and trend analysis for page load and Web Vitals.
  • Per-page metrics extraction including TTFB, FCP, LCP, DOM Interactive, DOM Complete, and Full Load.
  • Regression reporting and recommendations to guide optimizations.

Quick Start

Run the benchmark against a target URL to collect current metrics and compare them to the existing 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 measure and compare current web performance metrics against stored baseline data to identify degradations in page load speeds.

What web performance metrics can I track for baseline trend analysis?

For baseline trend analysis, you can track web performance metrics including TTFB, FCP, LCP, DOM Interactive, DOM Complete, and Full Load on a per-page basis.

How does automated baseline capture work for page load analysis?

Automated baseline capture works by evaluating JavaScript to extract page load and Web Vitals metrics, storing them as JSON baselines to compare against current runs for historical trend reporting.

Do I need the browse daemon to measure Web Vitals and track regressions?

Yes, you need the browse daemon to function end-to-end, as it is required to run the JavaScript evaluation and JSON baseline storage needed to measure Web Vitals and track regressions.

What is the best way to report performance degradations found in PR checks?

The best way to report performance degradations found in PR checks is to generate regression reports that provide specific recommendations to guide your code optimizations.

Can I use this approach for historical trend reporting of Web Vitals?

Yes, you can use this approach for historical trend reporting of Web Vitals by continuously capturing baseline metrics and comparing them across historical runs to visualize performance changes.