benchmark

Detect web performance regressions by comparing metrics against baselines.

Updated May 9, 2026
One-click install
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill benchmark-kk20300113-png
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/benchmark
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill benchmark-kk20300113-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web performance regressions often slip into production because they are hard to detect manually and easy to overlook in code review. This Skill automates performance monitoring by establishing baselines and comparing every change, catching slow page loads, bloated bundles, and degraded Core Web Vitals before they reach users.

Core Features & Use Cases

  • Baseline Capture: Record performance metrics including TTFB, FCP, LCP, DOM timings, bundle sizes, and request counts for any set of pages.
  • Regression Detection: Compare current runs against baselines with configurable thresholds, flagging timing increases, bundle growth, and request spikes as regressions or warnings.
  • Trend Analysis: View historical performance data to identify gradual degradation across multiple benchmarks.
  • Use Case: Before merging a PR that adds a new dashboard widget, run /benchmark <url> to confirm the change didn't increase LCP by 800ms or add 300KB of JavaScript.

Quick Start

Use the benchmark skill to run a full performance audit on your web application by providing the target 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 in a pull request?

Detect web performance regressions in continuous integration by comparing current metrics against established baselines. This skill flags timing increases, bundle growth, and degraded Core Web Vitals before merging code changes.

What metrics are included in a Core Web Vitals and bundle size benchmark?

A Core Web Vitals and bundle size benchmark captures TTFB, FCP, LCP, DOM timings, bundle sizes, and request counts. It gathers real performance data from running pages using JavaScript evaluation.

How do I establish a baseline for page load times and resource bundle sizes?

Establish a baseline for page load times and resource bundle sizes by recording performance metrics for any set of pages. The recorded baseline is then used to flag regressions or warnings in subsequent runs based on configurable thresholds.

Can I use this benchmark skill to track gradual performance degradation over time?

You can track gradual performance degradation over time using trend analysis features. This allows you to view historical performance data across multiple benchmark runs to identify slow declines in web application speed.

Do I need a running web application to measure LCP and page speed metrics?

You need a running web application to measure LCP and page speed metrics because the skill requires the browse daemon's perf command. It uses JavaScript evaluation to gather real performance data directly from the active pages.

What is the best way to prevent bloated bundles from reaching production?

The best way to prevent bloated bundles from reaching production is to automate regression detection in your CI workflow. Comparing every pull request against a baseline catches bundle growth and request spikes before users are impacted.