benchmark

Compare page load times, Core Web Vitals, and resource sizes before and after changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, Glob, AskUserQuestion, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in detecting performance regressions in web applications by comparing before and after metrics, ensuring smooth user experience.

Core Features & Use Cases

  • Performance Baseline: Establishes baselines for page load times, Core Web Vitals, and resource sizes.
  • Before/After Comparison: Compares performance metrics on every PR to track trends over time.
  • Use Case: Before deploying a new feature, use this Skill to ensure it doesn't introduce performance issues.

Quick Start

Run the benchmark skill with the command: /benchmark <url>

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 deploying a new feature?

You can detect web performance regressions by comparing page load times, Core Web Vitals, and resource sizes before and after changes. This Skill establishes a performance baseline and compares metrics on every PR to track trends and prevent issues.

How do I compare Core Web Vitals before and after code changes?

Compare Core Web Vitals by running the benchmark command with your target URL to establish a baseline, then executing it again after changes. It evaluates page load times and resource sizes to identify regressions before deployment.

Can I track page load time regressions for my web application?

Yes, you can track page load time regressions by comparing before and after metrics. It requires access to the web application and the ability to execute performance testing commands to ensure optimal performance.

What is the best way to monitor web performance trends across pull requests?

The best way to monitor web performance trends is by comparing before and after metrics on every PR. This approach tracks page load times, Core Web Vitals, and resource sizes to ensure new changes do not introduce performance issues.

Do I need command line access to run performance testing for regression detection?

Yes, you need access to the web application and the ability to execute performance testing commands via Bash. The Skill relies on command line execution to measure page load times, Core Web Vitals, and resource sizes.

Why should I establish a performance baseline for my web application?

Establishing a performance baseline is necessary to accurately detect regressions. It records initial page load times, Core Web Vitals, and resource sizes, providing a reference point to compare against future changes and ensure smooth user experience.