skills.rest
Simon-YHKim
Simon-YHKimCOMMUNITY
Explore all skills by this author →
GitHub

benchmark

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

Updated Apr 5, 2026
Search Tags:#performance#web vitals#bundle size#benchmark#baseline#regression detection#page speed
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill benchmark-simon-yhkim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/benchmark
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill benchmark-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Performance degrades gradually across pull requests, and without baselines nobody notices until the app feels slow. This Skill captures real browser performance data, stores baselines, and flags regressions before they ship. ## Core Features & Use Cases - Baseline Capture and Comparison: Save per-page metrics (TTFB, FCP, LCP, load time, transfer size) and compare current runs against them with regression thresholds. - Resource and Bundle Analysis: List the slowest resources, track JS/CSS bundle sizes, and check results against industry performance budgets. - Trend Tracking: Use --trend mode to chart performance across historical benchmark runs and spot gradual degradation. - Use Case: Before merging a PR, run a diff-scoped benchmark to confirm the branch did not inflate the JS bundle or double LCP on key pages. ## Quick Start Ask the assistant to run /benchmark against your local dev URL with --baseline first, then re-run it after your changes to see a regression report.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I detect performance regressions before merging a pull request?▼

Capture a baseline with /benchmark <url> --baseline on the main branch, then run /benchmark <url> on your branch. The report compares TTFB, FCP, LCP, transfer size, and bundle size, flagging regressions over 50% or 500ms.

How to benchmark only the pages changed in my branch?▼

Use /benchmark --diff. It runs git diff against the base branch to identify affected files and benchmarks only the impacted pages instead of the whole site.

What performance metrics does this benchmark measure?▼

It collects TTFB, FCP, LCP, DOM Interactive, DOM Complete, full load time, total requests, transfer size, and JS/CSS bundle sizes using the browser's performance.getEntries() API through the browse daemon.

Can I track web performance trends over time?▼

Yes, run /benchmark --trend to load historical baseline files and display a table of FCP, LCP, bundle size, and request counts across past runs, highlighting degradation patterns.

Why does the benchmark say NEEDS_SETUP before running?▼

The browse daemon binary must be built once before any page measurement. Run the setup script in the skill directory, which installs bun if missing and compiles the browse tool in about ten seconds.

Related Skills

Explore More Software Engineering Skills→
uzumaki-incuzumaki-inc

benchmark

Detect page load performance regressions via baseline comparison in PR workflows.

Official
Advanced
quanngynxquanngynx

vite-bundle-optimization

Optimize Vite build outputs with bundle splitting and dynamic imports.

Community
Advanced
Andy-HNUAndy-HNU

canary

Run canary checks on production web apps to detect console errors and performance regressions.

Community
Advanced
legioncodeinclegioncodeinc
84

lighthouse-pagespeed-stinger

Configures Lighthouse CI and PageSpeed Insights audits with performance budgets and lab-versus-field reconciliation.

Official
Advanced