benchmark

Name: benchmark
Availability: InStock
Author: scanbott

Measures web performance metrics and compares them to baselines to detect regressions.

Updated Apr 21, 2026

Search Tags:#performance #lighthouse #benchmark #web-vitals #bundle-size #page-load #perf-monitoring

Ready to run

npx skills add https://github.com/scanbott/claude-skills --skill benchmark-scanbott

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/scanbott/claude-skills/tree/main/gstack/benchmark
Command: npx skills add https://github.com/scanbott/claude-skills --skill benchmark-scanbott

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection across pages by establishing baselines and monitoring PR changes.

Core Features & Use Cases

Baseline and compare page load times, Core Web Vitals, and resource sizes.
Track performance trends over time and on every PR.
Supports per-page analysis across multiple routes and pages.

Quick Start

Run the benchmark against a URL to collect metrics and compare them to your 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 on a pull request?▼

You detect web performance regressions on a pull request by measuring Core Web Vitals and resource sizes against an established baseline. This applies per-page analysis across multiple routes and outputs JSON and Markdown reports for PR reviews.

What metrics are needed for tracking web performance trends over time?▼

Tracking web performance trends over time requires measuring per-page metrics like TTFB, FCP, LCP, DOM timings, and transfers. These metrics establish baselines to monitor page load changes and bundle sizes across multiple routes.

How does per-page benchmark analysis work for multiple routes?▼

Per-page benchmark analysis works by collecting web performance metrics like TTFB, FCP, and LCP across multiple routes to establish baselines. It compares subsequent measurements against these baselines to detect page load regressions.

Do I need a browse daemon to collect Core Web Vitals for baseline maintenance?▼

Yes, collecting Core Web Vitals for baseline maintenance requires a browse daemon perf tool. This tool facilitates per-page metric collection including TTFB, FCP, LCP, and DOM timings to generate accurate JSON and Markdown reports.

What is the best way to compare bundle sizes and page load times across PRs?▼

The best way to compare bundle sizes and page load times across PRs is to establish a performance baseline and run per-page metric collection on changes. This approach outputs JSON and Markdown reports highlighting regressions in web vitals and transfers.