benchmark

Measure browser performance metrics and compare them to stored baselines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web performance slowly degrades as small changes accumulate, and teams need an automated way to measure, baseline, compare, and alert on regressions before they reach users. This skill captures real browser metrics to pinpoint regressions in load time, Core Web Vitals, request counts, and bundle sizes so problems are discovered on every PR rather than after release.

Core Features & Use Cases

  • Baseline capture: Save deterministic baseline snapshots for pages and branches to enable precise before/after comparisons.
  • Comprehensive metrics: Collect TTFB, FCP, LCP, DOM timings, full load, resource sizes, request counts, and top slow resources using a headless browse daemon.
  • Comparison & thresholds: Auto-compare current runs against baselines with configurable thresholds and clear regression/warning statuses.
  • Trend analysis & reporting: Load historical baselines to show trends, generate human-readable markdown and JSON reports, and store outputs locally.
  • Use Case: Run on each pull request to detect JS bundle growth or LCP regressions and receive actionable recommendations before merging.

Quick Start

Run the benchmark against your site and save a baseline with the command "/benchmark https://example.com --baseline" then run "/benchmark https://example.com" to compare and generate a report.

Frequently Asked Questions about benchmark

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

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

To automatically detect web performance regressions on a pull request, you capture a deterministic baseline snapshot of your web page and then compare subsequent runs against it to alert on regressions before merging.

What browser performance metrics are needed to monitor Core Web Vitals and bundle size?

Monitoring Core Web Vitals and bundle size requires collecting TTFB, FCP, LCP, DOM timings, full load times, resource sizes, and request counts using a headless browse daemon.

Can I track web performance trends and generate reports locally without external services?

Yes, you can track web performance trends and generate reports locally by loading historical baselines to show trends and outputting human-readable markdown and JSON reports stored directly on your machine.

How do I configure performance regression thresholds to prevent false alerts?

You configure performance regression thresholds to prevent false alerts by setting predefined limits for automated comparisons, which categorize deviations into clear regression or warning statuses.

Does web performance regression detection require a headless browse daemon for data collection?

Yes, web performance regression detection requires a headless browse daemon to actively collect real browser metrics and identify slow resources for accurate baseline comparisons.

What is the best way to measure page load time regressions before releasing code?

The best way to measure page load time regressions before releasing code is running baseline, quick, diff, and trend mode audits on web pages to pinpoint problems on every pull request.