benchmark

Compare baseline and PR performance metrics to detect regressions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions on PRs go unnoticed, causing slow pages and poor user experience. This Skill captures baselines for page load times, Core Web Vitals, and resource sizes, then compares new results against those baselines to surface regressions.

Core Features & Use Cases

  • Establish baselines for page load times, Core Web Vitals, and resource sizes.
  • Compare before/after on every PR and track performance trends over time.
  • Integrate with CI to alert on regressions and explore trends across builds.

Quick Start

Run the benchmark on a URL to capture a baseline, then compare current results against that baseline in your CI workflow.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I detect frontend performance regressions on a pull request?

To detect frontend performance regressions on a pull request, capture baseline metrics for page load times and Core Web Vitals, then compare new PR results against that baseline to surface any drift.

What is the best way to track Core Web Vitals trends over time in CI?

Tracking Core Web Vitals trends over time in CI involves collecting historical timing data across builds, comparing current results against established baselines, and analyzing performance drift to enforce measurement accuracy.

Can I run a quick performance check on specific pages locally?

Yes, you can run a quick performance check on specific pages locally by applying the benchmark to a defined page list, capturing automated timing data, and comparing results in diff mode.

How do I establish a baseline for resource sizes and page load times?

Establishing a baseline for resource sizes and page load times requires running the benchmark on a URL to capture initial metrics, which then serves as the reference point for future PR comparisons.

Does this benchmark approach work for tracking performance without external dependencies?

Yes, this benchmark approach works without external dependencies by using the browse daemon to collect automated timing data, enforce measurement accuracy, and provide clear regression signaling for web pages.

Why should I use baseline-driven comparisons instead of isolated performance tests?

Baseline-driven comparisons are preferred over isolated performance tests because they track historical trends, apply consistent diff comparisons against captured metrics, and provide clear regression signaling for web pages.