benchmark

Detect page load performance regressions via baseline comparison in PR workflows.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/uzumaki-inc/uzustack --skill benchmark-uzumaki-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/uzumaki-inc/uzustack/tree/main/_upstream/gstack/benchmark
Command: npx skills add https://github.com/uzumaki-inc/uzustack --skill benchmark-uzumaki-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions quietly accumulate across pages and PRs, making it hard to spot slowdowns before they reach users.

Core Features & Use Cases

  • Baseline capture of page load times, Core Web Vitals, and resource sizes
  • PR-wide comparison and trend analysis over time
  • Page-specific diffing and quick canary runs for targeted pages

Quick Start

Run the benchmark on a target URL to capture baselines and compare current performance.

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 across multiple pages in a PR?

Capture baselines of page load times and Core Web Vitals, then compare current PR measurements against them. You can run page-specific diffs or quick canary runs for targeted pages to isolate regressions.

What is baseline-driven performance regression detection?

Baseline-driven performance regression detection captures initial page load metrics as a reference, then compares subsequent measurements against this baseline to track performance trends and spot slowdowns across PRs over time.

Do I need Bun to measure Core Web Vitals and track performance trends?

Yes, you need a local environment with Bun and the browse daemon to measure Core Web Vitals. These are required to execute baseline capture, page selection, diff, and trend analysis modes.

Can I run a quick performance canary test on a specific page?

Yes, you can run quick canary tests on targeted pages using page selection flags. This allows you to capture page-specific diffs and compare current page load metrics against the baseline without scanning the entire workflow.

What is the best way to track page load metrics over time across PRs?

The best way to track page load metrics over time is to use trend mode. It compares current measurements against historical baselines across multiple PRs, enabling consistent monitoring of page load times and resource sizes.