benchmark

Compare navigation timing, resource timing, and bundle metrics against baselines in PR workflows.

1|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/nuurpro/Converza_ai --skill benchmark-nuurpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/nuurpro/Converza_ai/tree/main/.claude/skills/benchmark
Command: npx skills add https://github.com/nuurpro/Converza_ai --skill benchmark-nuurpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection for PRs by establishing baselines for page load times, Core Web Vitals, and resource sizes, then comparing before/after data on every PR. It helps teams identify when code changes slow down pages and drift performance over time.

Core Features & Use Cases

  • Baseline creation and storage for performance metrics
  • PR-level regression detection and trend tracking
  • Per-page reports and deterministic data collection for reproducible results Use cases include validating optimizations, monitoring bundle size, and guarding against performance regressions during development.

Quick Start

Run the benchmark workflow with a URL to measure performance and compare against the current baseline.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I catch performance regressions on a pull request before merging?

To catch performance regressions, you can compare navigation timing, resource timing, and bundle metrics against established baselines on every PR. This workflow detects code changes that slow down page load times and drift Core Web Vitals.

What is performance baseline capture and when do I need it for web vitals?

Performance baseline capture records initial page load times, Core Web Vitals, and resource sizes to serve as a reference point. You need it before detecting regressions, as comparing before and after data on every PR requires a stored baseline.

How do I track bundle size and page load trends over time?

You can track bundle size and page load trends over time by collecting deterministic resource and navigation timing metrics on every PR. The workflow compares these metrics against stored baselines to monitor drift and surface actionable insights.

Does this benchmark workflow support deterministic data collection for reproducible results?

Yes, the benchmark workflow supports deterministic data collection for reproducible results. Built-in tooling enables consistent navigation and resource timing measurement, allowing reliable per-page reports and accurate baseline comparisons.

How do I generate per-page performance reports for my web application?

You generate per-page performance reports by running the benchmark workflow with a specific URL. The tool collects navigation timing, resource timing, and bundle metrics from the browse daemon to compare against current baselines.