skills.rest
rahmanayon
rahmanayonCOMMUNITY
Explore all skills by this author →
GitHub

benchmark

Run browser-based benchmarks and compare results against baselines to detect performance regressions.

Updated Apr 5, 2026
Search Tags:#performance#lighthouse#benchmark#web-vitals#bundle-size#page-load#performance-trends
One-click install
npx skills add https://github.com/rahmanayon/beehive --skill benchmark-rahmanayon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/rahmanayon/beehive/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/rahmanayon/beehive --skill benchmark-rahmanayon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection across PRs by establishing baselines for page load times, Core Web Vitals, and resource sizes, and comparing before/after on every PR.

Core Features & Use Cases

  • Baseline measurement using a browse daemon to gather page-performance data.
  • PR-ready comparisons and trend tracking over time.
  • Detailed metrics and resource/bundle analysis for debugging performance issues.

Quick Start

Run the gstack benchmark on a target URL to capture baseline and current performance data.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I detect Core Web Vitals regressions in pull requests?▼

Detect Core Web Vitals regressions by running a browse-based benchmark to capture TTFB, FCP, and LCP metrics, then compare the current PR results against established performance baselines.

What is the best way to track page load performance trends across multiple pages?▼

Track page load performance trends by capturing DOM timing and resource sizes across multiple pages during benchmark runs, which stores results for ongoing historical performance trend analysis.

How do I monitor bundle size changes before merging code?▼

Monitor bundle size changes by analyzing resource sizes and bundle analysis metrics during the benchmark process, comparing them against baseline measurements to spot regressions before merging.

Can I set performance budgets for resource sizes and page load times?▼

Set performance budgets by establishing baselines for page load times and resource sizes, applying these thresholds to PR workflows to automatically detect when code changes exceed acceptable limits.

How does a browse daemon benchmark gather page performance data?▼

A browse daemon gathers page performance data by executing browse-based benchmarks against target URLs, measuring Core Web Vitals and DOM timing to establish baselines for regression comparisons.

What should I do if my LCP metrics regress after a code change?▼

If LCP metrics regress, review the detailed metrics and resource or bundle analysis captured during the benchmark run to identify the specific performance issues causing the slowdown.

Related Skills

Explore More Software Engineering Skills→
sajalsuhanesajalsuhane

canary

Monitor production URLs for console errors, performance regressions, and page failures.

Community
Advanced
algorithmbasicsalgorithmbasics

benchmark

Execute browser-based benchmarks against URLs to detect performance regressions.

Community
Advanced
smarmen86smarmen86

benchmark

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

Community
Advanced
imonmiimonmi

benchmark

Compare baseline and PR performance metrics to detect regressions.

Community
Advanced