benchmark

Automate web performance benchmarking with browse daemon and JS evaluation.

9|3|Updated Jan 29, 2022
One-click install
npx skills add https://github.com/I194/PMTools_2.0 --skill benchmark-i194
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/I194/PMTools_2.0/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/I194/PMTools_2.0 --skill benchmark-i194

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection across pages and PRs by collecting real metrics with a browse daemon and JS evaluation, establishing baselines and surfacing trends.

Core Features & Use Cases

  • Baseline capture and comparison across builds for pages and resources
  • Per-page timing metrics (TTFB, FCP, LCP, DOM thresholds) and resource analysis
  • Trend analysis and reporting to guide optimizations on PRs or sprints

Quick Start

Run the benchmark on your target URL to start collecting performance data.

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

To detect web performance regressions on a PR, you can capture a baseline and compare current metrics against it. This Skill automates benchmarking using a browse daemon to collect real metrics and surface regressions on every PR.

What web vitals and timing metrics are captured during a baseline benchmark?

A baseline benchmark captures per-page timing metrics including TTFB, FCP, LCP, and DOM thresholds. It also performs resource analysis to measure real web vitals from running pages using JS evaluation.

How do I generate a performance trend report for my web pages?

You generate a performance trend report by running a simple reporting pipeline that outputs JSON and markdown. This analyzes collected baselines and current metrics to guide optimizations across pages and resources.

Do I need a local browse daemon setup to collect real web performance metrics?

Yes, collecting real web performance metrics requires a local setup with the browse daemon. You also need baseline storage and a reporting pipeline to fully automate the end-to-end benchmarking process.

What is the best way to compare current page performance against a historical baseline?

The best way to compare current page performance against a historical baseline is to automate end-to-end benchmarking. This Skill captures baselines, compares current results on every PR, and surfaces trends across pages.