skills.rest
bobbo01
bobbo01COMMUNITY
Explore all skills by this author →
GitHub

benchmark

Detects web performance regressions by comparing page metrics against captured baselines.

Updated Mar 16, 2026
Search Tags:#performance#web vitals#bundle size#benchmark#baseline#regression detection#page speed
One-click install
npx skills add https://github.com/bobbo01/B2BPlatform --skill benchmark-bobbo01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/bobbo01/B2BPlatform/tree/main/.agents/skills/gstack-benchmark
Command: npx skills add https://github.com/bobbo01/B2BPlatform --skill benchmark-bobbo01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web performance degrades gradually across pull requests, and without baselines nobody notices until pages become slow. This Skill measures real page performance, captures baselines, and flags regressions before they ship. ## Core Features & Use Cases - Baseline Capture & Comparison: Record TTFB, FCP, LCP, DOM timings, transfer sizes, and request counts per page, then compare current runs against stored baselines with regression thresholds. - Resource & Bundle Analysis: Identify the slowest resources, track JS/CSS bundle sizes, and check results against industry performance budgets. - Trend Tracking: Review historical benchmark data to spot gradual performance degradation over time. - Use Case: Before merging a PR, run a benchmark against your staging URL to confirm the new feature did not inflate the JS bundle or double the LCP. ## Quick Start Ask the AI to run a performance benchmark on your local dev server URL and compare it against the saved baseline.

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 of page metrics before making changes, then run the benchmark again on your branch. The comparison flags regressions when timing metrics rise over 50% or bundle sizes grow over 25%.

What metrics does a web performance benchmark measure?▼

It measures TTFB, FCP, LCP, DOM Interactive, DOM Complete, full load time, total requests, transfer size, and JS/CSS bundle sizes. Data comes from the browser's performance.getEntries() API on real loaded pages.

Can I benchmark only the pages changed in my branch?▼

Yes, the --diff mode uses git diff against the base branch to identify affected files and benchmarks only the impacted pages. You can also pass explicit page paths with --pages.

Why do I need a baseline for performance testing?▼

Without a baseline you only get absolute numbers, which cannot reveal regressions. A 2000ms load time may be fine for a dashboard but terrible for a landing page, so comparison against your own baseline is essential.

Does the benchmark tool modify my application code?▼

No, it is read-only. It collects metrics, generates reports in .gstack/benchmark-reports, and offers recommendations, but never changes code unless you explicitly ask.

Related Skills

Explore More Software Engineering Skills→
Chang-Shih-YungChang-Shih-Yung

benchmark

Measure page performance across builds and report deltas against thresholds.

Community
Advanced
tankpkgtankpkg
1

@tank/web-performance

Diagnose slow web applications and identify performance bottlenecks across Core Web Vitals.

Official
Advanced
steadyfallsteadyfall

benchmark

Collect end-to-end web performance metrics from the browse daemon across pages.

Community
Advanced
rothwellmawela-cyberrothwellmawela-cyber

seo-performance

Analyze web performance metrics and generate SEO audit reports.

Community
Advanced