benchmark

Measure web performance metrics and compare them against baselines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams detect when a web app gets slower, heavier, or more expensive to load so performance regressions are caught before they reach users.

Core Features & Use Cases

  • Baseline and compare page performance across branches, pull requests, and release candidates.
  • Measure key web metrics such as TTFB, FCP, LCP, DOM timing, load time, request counts, and transfer size.
  • Inspect resource and bundle impact to spot oversized scripts, CSS, images, and other blocking assets.
  • Track trends over time with baseline files and historical reports for repeated audits.
  • Use case: compare a feature branch against a known-good baseline to find which page or asset caused a slowdown.

Quick Start

Ask the benchmark skill to audit a URL and compare it against an existing baseline or capture a new baseline first.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I catch Core Web Vitals regressions in a pull request?

To catch Core Web Vitals regressions in a pull request, you can audit a URL and compare load timing, resource usage, and bundle size against a known-good baseline file.

What web performance metrics are needed to detect page speed slowdowns?

Detecting page speed slowdowns requires measuring key web metrics like TTFB, FCP, LCP, DOM timing, load time, request counts, and transfer size to spot blocking assets.

Does browser automation work for tracking page load timing trends over time?

Yes, browser automation tracks page load timing trends over time by capturing historical reports and baseline files for repeated audits across branches and release candidates.

What is the best way to measure bundle size impact on page load speed?

The best way to measure bundle size impact on page load speed is to inspect resource usage and compare oversized scripts, CSS, and images against a baseline during release checks.

Can I compare a feature branch against a baseline to find which asset caused a slowdown?

Yes, you can compare a feature branch against a baseline to identify which specific page or asset caused a web performance regression before it reaches users.