benchmark

Benchmark web pages against baselines to detect performance regressions.

15|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/howdeploy/NekoFree --skill benchmark-howdeploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/howdeploy/NekoFree/tree/main/skills/benchmark
Command: npx skills add https://github.com/howdeploy/NekoFree --skill benchmark-howdeploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions slip into production quietly. This Skill provides a repeatable way to baseline, collect, and compare web performance data across PRs.

Core Features & Use Cases

  • Establishes baselines and detects regressions for page load metrics (TTFB, FCP, LCP, DOM timings) using the browse daemon.
  • Runs end-to-end measurements across selected pages and compiles detailed performance reports.
  • Helps teams track trends over time and identify hotspots in JavaScript bundles and network usage.

Quick Start

Type /benchmark <url> to start a full performance audit 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 detect web performance regressions in a pull request?

To detect web performance regressions in a pull request, you benchmark web pages against an established baseline. This process collects page load metrics like TTFB, FCP, and LCP via a browse daemon, aggregating results to spot degradation early.

What web vitals and metrics are collected during a performance benchmark?

A performance benchmark collects core web vitals and DOM timings, specifically measuring TTFB, FCP, and LCP. It uses a browse daemon to run end-to-end measurements across selected pages, compiling the data into detailed trend analysis reports.

Can I track performance trend analysis across multiple releases?

Yes, you can track performance trend analysis across multiple releases. The benchmarking process establishes baselines and aggregates results over time, helping teams identify hotspots in JavaScript bundles and network usage as code evolves.

What is the best way to establish a baseline for web page performance?

The best way to establish a baseline for web page performance is running a full audit on a stable build. This captures initial DOM timings and web vitals metrics, providing a reference point to compare future PRs and spot regressions.

Does the benchmark tool work without external dependencies?

Yes, the benchmark tool works without external dependencies. It relies on an internal browse daemon to collect metrics and generate comparison reports, requiring no additional component installations to measure web page performance regressions.