skills.rest
bajajvinamr
bajajvinamrCOMMUNITY
Explore all skills by this author →
Website𝕏@axios_iiitlGitHub

benchmark

Measure and compare web performance metrics across pull requests using the browse daemon.

Updated Apr 1, 2026
Search Tags:#reporting#benchmark#web-performance#bundle-size#pr-integration#navigation-timing
One-click install
npx skills add https://github.com/bajajvinamr/little-wins --skill benchmark-bajajvinamr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/bajajvinamr/little-wins/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/bajajvinamr/little-wins --skill benchmark-bajajvinamr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to detect and quantify performance regressions in web applications by running automated browser-based benchmarks with a dedicated browse daemon.

Core Features & Use Cases

  • Baseline capture for PR branches and mainline to establish performance targets.
  • Per-page timing and resource analysis including TTFB, FCP, LCP, and total transfer.
  • Trend analysis across builds to spot degradation and identify hotspots.

Quick Start

Provide a URL and run the benchmark to start collecting performance data.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I measure web performance regressions across pull requests?▼

To measure web performance regressions across PRs, you can run automated browser-based benchmarks using a browse daemon to compare current metrics against captured baselines. This process collects TTFB, FCP, and LCP data to detect degradation.

What web performance metrics can I benchmark for my application?▼

You can benchmark page load metrics, resource timings, and bundle sizes for your application. The skill specifically collects TTFB, FCP, LCP, DOM metrics, and network data via a browse daemon to provide a comprehensive performance overview.

How do I capture a baseline for web performance benchmarking?▼

To capture a web performance baseline, provide a URL and run the benchmark on your PR branch or mainline. The skill stores these baselines under .gstack/benchmark-reports to establish targets for future comparisons.

Can I analyze web performance trends across multiple builds?▼

Yes, you can analyze web performance trends across multiple builds to spot degradation and identify hotspots. The skill outputs JSON and Markdown reports to help you track historical comparisons and performance shifts over time.

Does this benchmarking tool require any specific dependencies to run?▼

No specific dependencies are required to run this web performance benchmarking tool. It operates independently using a dedicated browse daemon to collect navigation timing and resource data without needing external component installations.

What is the best way to compare bundle sizes between different PR branches?▼

The best way to compare bundle sizes between PR branches is to run a benchmark that captures total transfer data and resource timings. The tool then diffs these metrics against your stored baselines to highlight any size regressions.

Related Skills

Explore More Software Engineering Skills→
jonkikyjonkiky

benchmark

Collect navigation timing and resource data to establish performance baselines and detect regressions.

Community
Advanced
amanikamanik

benchmark

Measure baseline-enabled web page performance metrics via the browse daemon.

Community
Advanced
cegit27cegit27
3

benchmark

Detect web performance regressions by comparing metrics against stored baselines.

Official
Advanced
filipnyquistfilipnyquist

benchmark

Benchmark web page performance by collecting navigation and resource timings.

Community
Advanced