benchmark

Measure web performance metrics and compare against baselines to detect regressions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents performance degradation by establishing baselines and tracking metrics like page load times and Core Web Vitals, ensuring that new code changes do not silently slow down your application.

Core Features & Use Cases

  • Automated Benchmarking: Automatically measures TTFB, FCP, LCP, and bundle sizes for specified pages.
  • Regression Detection: Compares current performance against historical baselines to identify regressions introduced in a PR.
  • Use Case: Run a performance audit on your dashboard page before merging a large refactor to ensure that bundle size and load times remain within acceptable thresholds.

Quick Start

Invoke the benchmark skill to run a full performance audit on the current page with baseline comparison.

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 a CI/CD pipeline?

Performance benchmarking tracks metrics like TTFB, FCP, LCP, and bundle sizes to prevent performance degradation. By establishing historical baselines, it ensures new code changes do not silently slow down your application.

How do I measure Core Web Vitals and bundle sizes for my web pages?

To measure Core Web Vitals and bundle sizes, the skill requires the browse daemon and browser-based performance API access. It automatically gathers accurate timing data for metrics like TTFB, FCP, and LCP for specified pages during local development or CI workflows.

Can I compare current page load times against a historical performance baseline?

Yes, comparing current page load times against historical baselines identifies regressions introduced in a pull request. The skill audits dashboard pages before large refactors to verify bundle size and load times stay within acceptable thresholds.

Do I need the browse daemon to track Core Web Vitals locally?

Yes, the browse daemon is required to track Core Web Vitals locally. The skill relies on the browse daemon and browser-based performance API access to gather accurate timing data for monitoring page speed trends during development.

What is the best way to automate performance audits before merging a large refactor?

Automating performance audits before merging a large refactor involves running a benchmark skill in your pipeline. It executes a full performance audit on the current page with baseline comparison to prevent silent application slowdowns.

What web performance metrics should I monitor to prevent page speed regression?

To prevent page speed regression, you should monitor Core Web Vitals like TTFB, FCP, and LCP, along with bundle sizes. Tracking these metrics establishes baselines and detects when new code changes negatively impact application load times.