benchmark

Detect performance regressions by comparing PR metrics against established baselines.

1|2|Updated Jan 4, 2024
One-click install
npx skills add https://github.com/NaKMiers/Port4lio --skill benchmark-nakmiers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/NaKMiers/Port4lio/tree/main/.agents/skills/benchmark
Command: npx skills add https://github.com/NaKMiers/Port4lio --skill benchmark-nakmiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and tracks performance regressions across PRs by establishing baselines for page load times, Core Web Vitals, and resource sizes using the browse daemon and automated data collection.

Core Features & Use Cases

  • Baseline creation for page timing, web vitals, and resource budgets to anchor performance measurements.
  • Automated comparison of current PR metrics against baselines to surface regressions and trends.
  • Trend analysis over time across commits, branches, and pages to identify degradation patterns.
  • End-to-end workflow from data collection to reporting, with optional script-driven measurements and JS evaluations.

Quick Start

Run /benchmark https://example.com to start a performance audit and baseline capture.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I detect performance regressions in a pull request workflow?

You can detect performance regressions by establishing baselines for page load times, Core Web Vitals, and resource sizes, then automatically comparing current PR metrics against those baselines to surface degradations.

What are performance baselines and when do I need them for web vitals?

Performance baselines are fixed reference points for page timing, web vitals, and resource budgets. You need them to anchor measurements and identify degradation patterns across commits and branches over time.

How do I set up automated performance monitoring for Core Web Vitals?

You can set up automated performance monitoring by running a browse daemon for data collection, extracting JavaScript performance metrics, and generating JSON baseline reports to track web vitals continuously.

Can I track resource size budgets and page load times across multiple branches?

Yes, you can establish baselines for resource sizes and page load times, then apply automated comparison and trend analysis across commits, branches, and pages to identify degradation patterns.

Does performance regression detection work with script-driven measurements and JS evaluations?

Yes, the workflow supports end-to-end data collection from the browse daemon to reporting, including optional script-driven measurements and JavaScript performance evaluations for customized metric extraction.