benchmark

Compare web performance baselines and current runs to detect regressions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time". (gstack) Voice triggers (speech-to-text aliases): "speed test", "check performance".

Core Features & Use Cases

  • Phase-driven benchmarking workflow including setup, baseline capture, page discovery, data collection, comparison, trend analysis, and reporting.
  • Automatic JS evaluation and resource profiling to produce actionable performance insights.
  • Generate baselines, compare current runs, and save reports for PR-driven performance governance.

Quick Start

Run the benchmark against a target URL to start collecting 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 catch web performance regressions on pull requests?

To catch web performance regressions on pull requests, you can establish JSON-based baselines for Core Web Vitals and bundle sizes, then compare current runs against them to detect changes automatically during PR workflows.

What web vitals and resource metrics can I track for page load benchmarking?

Page load benchmarking tracks TTFB, FCP, LCP, and DOM metrics, alongside resource profiling and bundle sizes for multiple pages to provide actionable performance insights and historical trends.

How does automated performance data collection work for multiple pages?

Automated performance data collection works by using the browse daemon for data gathering and executing JavaScript evaluation on target pages to measure metrics across entire page sets without manual intervention.

Can I use this benchmarking workflow to analyze historical performance trends?

Yes, you can analyze historical performance trends by saving JSON-based reports from each run, allowing you to track Core Web Vitals, resource sizes, and page load times over time.

What is the best way to establish a performance baseline before adding new features?

The best way to establish a performance baseline is to run the benchmark against your target URL during the setup phase, capturing initial TTFB, FCP, LCP, and bundle size metrics into a JSON report for future comparison.

Do I need the browse daemon to measure Core Web Vitals and detect regressions?

Yes, the browse daemon is required to satisfy the requirements for automated data gathering, enabling JavaScript evaluation and resource profiling to measure Core Web Vitals and detect regressions accurately.