skills.rest
tblakex01
tblakex01COMMUNITY
Explore all skills by this author →
GitHub

benchmark

Baseline and detect web page performance regressions across pull requests.

1|Updated Apr 26, 2026
Search Tags:#benchmark#web-vitals#pr-testing#performance-regression#page-load#browse-daemon
One-click install
npx skills add https://github.com/tblakex01/conductor-playground --skill benchmark-tblakex01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/tblakex01/conductor-playground/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/tblakex01/conductor-playground --skill benchmark-tblakex01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to proactively detect performance regressions by establishing baselines for page load times, Core Web Vitals, and resource sizes, and comparing new runs against historical data on every PR.

Core Features & Use Cases

  • Baseline and compare PR performance using the browse daemon's perf tooling.
  • Track performance trends over time and surface regressions early.
  • Support multi-page audits and targeted page sets with --pages, --diff, or --trend.

Quick Start

Run the benchmark on a target URL to start data collection, baseline setup, and 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 on a pull request?▼

You can detect web performance regressions on a PR by baselining page load times, Core Web Vitals, and resource sizes, then comparing new runs against historical data. This Skill automates that collection and diffing process using the browse daemon.

Can I track Core Web Vitals across multiple pages for long-term trend analysis?▼

Yes, you can track Core Web Vitals trends over time by running multi-page audits. It supports a trend mode to measure targeted page sets and surface long-term performance changes across your historical data.

What do I need to set up before collecting page load metrics?▼

You need the browse daemon and perf tooling set up in your environment to collect page load metrics. Once running, the tool measures load times, Core Web Vitals, and resource sizes to establish your baseline.

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

The best way to compare current performance against a baseline is using the diff mode. It automatically measures new page load metrics and resource sizes, then compares them against your previously established historical data.

Does this benchmark tool support evaluating custom JavaScript during a page audit?▼

Yes, the benchmark tool supports optional JavaScript evaluation during multi-page audits. This allows you to collect custom metrics alongside standard Core Web Vitals and page load times.

When should I use the quick mode versus the full pages mode for performance testing?▼

Use quick mode for immediate, lightweight performance checks on a target URL, and use pages mode for comprehensive multi-page audits. Both modes collect Core Web Vitals and resource sizes for regression detection.

Related Skills

Explore More Software Engineering Skills→
txema-puchtxema-puch
1

benchmark

Detect performance regressions by comparing before/after baselines on PRs.

Community
Advanced
steadyfallsteadyfall

benchmark

Collect end-to-end web performance metrics from the browse daemon across pages.

Community
Advanced
Prompt-or-Die-LabsPrompt-or-Die-Labs
7

lighthouse-ci-integrator

Automate Lighthouse performance testing and assertions in CI/CD workflows.

Official
Intermediate
charl-krugercharl-kruger
5

web-perf

Measure Core Web Vitals and profile resource timing with Chrome DevTools MCP.

Community
Advanced