benchmark

Measure web performance metrics and compare against baselines using browser timing data.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/mgher668/surf-ai --skill benchmark-mgher668
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/mgher668/surf-ai/tree/main/.agents/skills/gstack/benchmark
Command: npx skills add https://github.com/mgher668/surf-ai --skill benchmark-mgher668

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify performance regressions early by establishing baselines and comparing current builds against historical data using a browser-based daemon.

Core Features & Use Cases

  • Baseline capture and comparison against PRs to surface regressions in TTFB, FCP, LCP, and total load.
  • Page set discovery and measurement across URLs, with per-page timing and resource analysis.
  • Reports and trends: save benchmarks, generate comparison reports, and analyze performance trends over time.

Quick Start

Run /benchmark <url> to start a full performance audit and compare it against your baseline.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I measure web performance metrics like TTFB, FCP, and LCP for my pages?

To measure web performance metrics, this Skill collects deterministic resource timing data via browser performance APIs. It computes TTFB, FCP, LCP, DOM interactions, and bundle sizes using a browser-based browse daemon for accurate page load analysis.

How do I detect web performance regressions when comparing a PR against historical builds?

To detect web performance regressions, you can capture a performance baseline and compare current PR changes against it. This process surfaces timing deviations in TTFB, FCP, LCP, and total load across builds to identify regressions early.

Can I analyze page load performance trends across multiple URLs and builds?

You can analyze page load performance trends by applying the benchmark to page sets. It supports saving benchmarks, generating JSON exports, and tracking performance trends over time across multiple URLs and builds for comprehensive page set discovery.

What is the best way to automate web performance benchmarking for continuous integration?

Automating web performance benchmarking involves applying the measurement process to PR changes with a quick mode. It uses baseline storage and deterministic timing data to consistently measure and compare page load speeds and bundle sizes across builds.

Do I need a browse daemon to collect resource timing data for web vitals benchmarking?

Yes, a browse daemon is required to collect deterministic resource timing data for web vitals benchmarking. The daemon interfaces with browser performance APIs to gather the necessary timing data for computing metrics like TTFB, FCP, and LCP.