skills.rest
a29paul
a29paulCOMMUNITY
Explore all skills by this author →
GitHub

benchmark

Detect web performance regressions by comparing browser metrics against baselines.

1|Updated Apr 13, 2026
Search Tags:#performance#monitoring#web vitals#bundle size#benchmarking#regression detection#page speed
One-click install
npx skills add https://github.com/a29paul/hexlens --skill benchmark-a29paul
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/a29paul/hexlens/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/a29paul/hexlens --skill benchmark-a29paul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web performance regressions often slip into production because they are hard to detect without continuous monitoring. This skill automates performance testing by capturing real browser metrics, establishing baselines, and flagging degradations before code is merged.

Core Features & Use Cases

  • Baseline Capture: Record performance metrics including Core Web Vitals, load times, and bundle sizes for key pages.
  • Regression Comparison: Automatically compare current PR changes against baselines to detect timing or size increases.
  • Trend Tracking: Monitor performance over time to catch gradual declines that individual PRs might miss.
  • Use Case: A frontend team can run this skill on every pull request to ensure a new dependency or image does not push Largest Contentful Paint beyond the 2.5-second threshold.

Quick Start

Use the benchmark skill to run a full performance audit on your application's homepage and compare the results against the stored baseline.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I catch web performance regressions in continuous integration?▼

You can catch web performance regressions in continuous integration by automating performance benchmarking, which captures real browser metrics from live pages and compares them against established baselines before merging code.

What metrics are measured for Core Web Vitals regression detection?▼

Core Web Vitals regression detection measures real browser metrics including Largest Contentful Paint, resource timings, page speed, and bundle sizes captured directly from live pages.

How do I set up performance budgets for pull requests?▼

Performance budgets for pull requests are enforced by establishing a baseline of web vitals and bundle sizes, then automatically comparing PR changes against these thresholds to flag timing or size increases.

Do I need a specific browser daemon to monitor page speed?▼

Yes, monitoring page speed requires the gstack browse daemon to capture Core Web Vitals, resource timings, and bundle sizes from live pages for regression comparison.

Can I track gradual performance declines over time across multiple pull requests?▼

Yes, trend tracking monitors performance over time to catch gradual declines that individual pull requests might miss, comparing historical metrics against current baselines.

What's the best way to validate frontend changes against historical performance trends?▼

Validating frontend changes against historical performance trends is best achieved through automated benchmarking that compares current Core Web Vitals and bundle sizes against stored baselines and historical data.

Related Skills

Explore More Software Engineering Skills→
shekerkammashekerkamma

benchmark

Measure Core Web Vitals and resource sizes to detect gradual performance regressions.

Community
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

benchmark

Detect performance regressions by comparing navigation and resource timing metrics against URL baselines.

Community
Advanced
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced
smarmen86smarmen86

benchmark

Detects performance regressions by measuring page loads, Core Web Vitals, and resource sizes.

Community
Advanced