benchmark

Measures page performance metrics in a real browser and detects regressions against saved baselines.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill benchmark-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/gstack/benchmark
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill benchmark-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web performance degrades gradually across pull requests, and without baselines nobody notices until load times become unacceptable. This Skill captures real browser timing data, compares it against stored baselines, and flags regressions before they ship. ## Core Features & Use Cases - Real-browser measurement: Collects TTFB, FCP, LCP, DOM timings, resource sizes, and request counts via performance.getEntries() in an actual browser session. - Baseline comparison and regression detection: Saves baselines per page and flags regressions using relative thresholds for timing, bundle size, transfer size, and request count. - Budget checks and trend analysis: Grades pages against industry performance budgets and tracks metric trends across historical benchmark runs. - 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 LCP compared to the baseline. ## Quick Start Ask the AI to run a performance benchmark on your staging URL and compare the results against the saved baseline to detect any regressions.

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 the --baseline flag on your main branch, then run the benchmark on your PR branch. The skill compares TTFB, FCP, LCP, bundle size, and transfer size against the baseline and flags regressions using relative thresholds.

How to measure Core Web Vitals like LCP and FCP from the command line?

The skill drives a real browser session and reads performance.getEntries() directly from the live page, extracting FCP from paint entries and LCP via a PerformanceObserver. This gives real measured values rather than lab estimates.

What counts as a performance regression in the benchmark report?

Timing metrics regress when they increase more than 50% or more than 500ms absolutely; bundle size and total transfer regress above 25% growth. Increases above 20% for timing or 10% for size are flagged as warnings instead.

Can I benchmark only the pages affected by my current branch?

Yes, the --diff flag compares your branch against the base branch using git diff and benchmarks only the pages touched by changed files. This keeps PR checks fast on large sites.

Why does the benchmark need a baseline before it can detect regressions?

Without a baseline the skill can only report absolute numbers and budget checks, since regression detection is relative to your own historical measurements. Run once with --baseline to establish the comparison point.