benchmark

Detect performance regressions by comparing builds against established baselines.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/gaaschk/gaasch-family --skill benchmark-gaaschk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/gaaschk/gaasch-family/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/gaaschk/gaasch-family --skill benchmark-gaaschk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions in web apps can go unnoticed until users complain. This Skill establishes baselines for page load times, Core Web Vitals, and resource sizes, then detects deviations after changes.

Core Features & Use Cases

  • Baseline creation for multiple pages and deployments.
  • Automatic before/after comparisons on PRs to surface regressions.
  • Trend analysis over time to identify gradual performance drifts.

Quick Start

Run a benchmark on a target URL to initialize baselines and compare subsequent runs.

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 in my pull requests?

You can detect web performance regressions by establishing baselines for page load times and Core Web Vitals, then automatically comparing new builds against those baselines directly in your PR workflows.

What is the best way to track Core Web Vitals trends across deployments?

Tracking Core Web Vitals trends requires establishing baseline metrics for your pages and deployments, then analyzing deviations over time to identify gradual performance drifts across subsequent releases.

How do I set up a performance baseline for page load times?

To set up a performance baseline, you run a benchmark on a target URL using a browser-based measurement setup, which initializes the baseline records for page load times and resource sizes.

Can I compare resource sizes before and after a deployment automatically?

Yes, you can compare resource sizes automatically by establishing a baseline for your pages and configuring before/after comparisons to surface deviations and regressions when new builds are introduced.

Do I need a browser-based measurement setup to monitor Lighthouse scores?

Yes, monitoring Lighthouse scores and establishing performance baselines requires a browser-based measurement setup to accurately capture page load times, Core Web Vitals, and resource sizes.

Why does gradual performance drift go unnoticed in web apps?

Gradual performance drift goes unnoticed because deviations are incremental; establishing baselines and running long-term trend analysis across deployments is required to detect these slow regressions before users complain.