benchmark

Compare web performance metrics against baselines to detect regressions.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill benchmark-shmurdoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-benchmark
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill benchmark-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web applications gradually degrade in performance through small, cumulative changes that are difficult to detect until users complain. This Skill establishes performance baselines and automatically compares every PR against them, catching regressions in page load times, Core Web Vitals, and resource sizes before they reach production.

Core Features & Use Cases

  • Baseline Capture: Record performance metrics for critical pages to create a reference point.
  • Regression Comparison: Analyze before/after metrics on every PR with threshold-based alerts for timing, bundle size, and request count changes.
  • Trend Tracking: Monitor performance trends over time to identify gradual degradation.
  • Use Case: A frontend team can ensure that a new UI library does not increase LCP by more than 50% or push JavaScript bundle size beyond the 25% regression threshold.

Quick Start

Use the benchmark skill to audit the performance of the current page and highlight any regressions against the saved baseline.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I catch web performance regressions in a pull request?

Catch web performance regressions by comparing current metrics against established baselines within your continuous integration workflow. This process validates every pull request for page load times, Core Web Vitals, and resource size changes before they reach production.

How does baseline comparison work for Core Web Vitals and bundle size?

Baseline comparison works by recording initial performance metrics for critical pages, then automatically analyzing before and after metrics on subsequent updates. It triggers threshold-based alerts when timing, bundle size, or request count changes exceed defined regression limits.

Do I need a specific environment to run continuous integration performance benchmarks?

You need the gstack browse daemon running to execute continuous integration performance benchmarks. This daemon executes JavaScript performance APIs and generates the comparative regression reports required to validate page load times and resource sizes.

What is the best way to track gradual web performance degradation over time?

Track gradual web performance degradation by monitoring performance trends over time using saved baselines. This identifies cumulative slowdowns caused by small changes, ensuring metrics like Largest Contentful Paint do not degrade unnoticed across updates.

Can I set custom threshold alerts for JavaScript bundle size and LCP regressions?

You can set custom threshold alerts for JavaScript bundle size and LCP regressions. The comparison analysis triggers alerts when specific metrics exceed your configured percentage thresholds, such as blocking PRs that increase bundle size beyond 25%.