benchmark

Measure page load times, Core Web Vitals, and resource sizes to detect performance regressions.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/yocxy2/gstack3 --skill benchmark-yocxy2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/yocxy2/gstack3/tree/main/benchmark
Command: npx skills add https://github.com/yocxy2/gstack3 --skill benchmark-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents performance degradation by automating the detection of regressions in page load times, Core Web Vitals, and resource sizes before they reach production.

Core Features & Use Cases

  • Performance Baselines: Automatically establishes performance benchmarks for your application pages.
  • Regression Detection: Compares current performance metrics against historical baselines on every pull request.
  • Use Case: Use this skill to identify if a recent code change has increased the Largest Contentful Paint (LCP) or bundle size, ensuring your application remains fast as it scales.

Quick Start

Run the benchmark skill on the homepage to capture a new performance baseline.

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 in a pull request?

To detect performance regressions in a pull request, you can automate measuring page load times, Core Web Vitals, and resource sizes against historical baselines before code changes merge.

What are Core Web Vitals and how are they used in benchmarking?

Core Web Vitals are metrics like Largest Contentful Paint used in benchmarking to establish baselines and identify if recent code changes increased load times or bundle sizes.

How do I establish a performance baseline for web application pages?

You establish a performance baseline for web application pages by running the benchmark skill on your homepage to capture initial page load times, Core Web Vitals, and resource sizes for future comparison.

Do I need browser-based performance APIs to monitor web vitals?

Yes, you need browser-based performance APIs and the browse daemon to access, collect, and analyze web vitals and resource size metrics required for continuous performance monitoring.

Can I measure Largest Contentful Paint changes for every code update?

Yes, you can measure Largest Contentful Paint changes for every code update by integrating regression detection into your workflow to compare current metrics against historical baselines.

Why does performance benchmarking fail without the browse daemon?

Performance benchmarking fails without the browse daemon because it requires browser-based performance API access to collect and analyze page load times, Core Web Vitals, and resource sizes.