benchmark

Detect web performance regressions by comparing Core Web Vitals and resource sizes against baselines.

Updated Jul 21, 2025
One-click install
npx skills add https://github.com/robertzengcn/aiFetchly --skill benchmark-robertzengcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/robertzengcn/aiFetchly/tree/main/.agents/skills/gstack/benchmark
Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill benchmark-robertzengcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web applications often accumulate small, unnoticeable performance regressions over time that degrade user experience until they become critical, making it difficult to identify which code change caused the slowdown.

Core Features & Use Cases

  • Baseline Performance Tracking: Establishes benchmarks for page load times, Core Web Vitals, and resource sizes for key application pages.
  • PR Regression Detection: Compares current performance metrics against baselines for every code change to catch regressions early in the review process.
  • Trend Analysis: Tracks performance metrics across multiple benchmark runs to identify gradual degradation that might slip past single-PR checks.
  • Use Case: A frontend team can run this skill on every PR to ensure new features do not add more than 500ms to LCP or bloat JavaScript bundles by more than 25% before merging.

Quick Start

Use the benchmark skill to run a full performance audit and regression check on your production site at https://your-app.com.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I detect web performance regressions in Core Web Vitals before merging a pull request?

Web performance regression detection tracks Core Web Vitals and page load times against baselines during PR review. It compares current metrics against established thresholds to catch slowdowns before merging code changes.

What is the best way to track gradual page speed degradation across multiple releases?

Tracking gradual page speed degradation involves trend analysis across multiple benchmark runs. By comparing Core Web Vitals and resource sizes over time, you can identify incremental performance drops that single PR checks might miss.

Can I benchmark Lighthouse scores and JavaScript bundle size on a running web instance?

Yes, you can benchmark Lighthouse scores and bundle sizes on a running web instance. The skill requires a live web application and the gstack browse daemon to collect real user performance metrics via browser APIs.

How do I automate performance benchmarking for frontend code changes?

Automate performance benchmarking for frontend code changes by integrating regression checks into PR review workflows. The skill measures page load times and resource sizes, flagging changes that exceed LCP or bundle size thresholds.

Do I need the gstack browse daemon to measure Core Web Vitals for ongoing performance monitoring?

Yes, the gstack browse daemon is required to measure Core Web Vitals for ongoing performance monitoring. It enables the skill to collect real user performance metrics via browser APIs and generate comparative regression reports.