benchmark

Measure web performance with the browse daemon and compare results against baselines.

5|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/drt0927/tw-overlay --skill benchmark-drt0927
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/drt0927/tw-overlay/tree/main/.gemini/skills/gstack-benchmark
Command: npx skills add https://github.com/drt0927/tw-overlay --skill benchmark-drt0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection and baseline measurement for web pages using the browse daemon. The tool compares current results against baselines to surface regressions in load times and Core Web Vitals.

Core Features & Use Cases

  • Baseline capture for page loads, bundles, and resource sizes.
  • PR and CI integration to validate performance changes across commits.
  • Trend analysis over time to identify slow regressions and performance drift.

Quick Start

Run a baseline benchmark against a target URL and compare results to identify regressions.

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 CI pipeline?

Detect web performance regressions in CI by capturing baseline metrics for page loads and Core Web Vitals, then comparing current build results against those baselines to surface regressions across commits.

What is performance baseline measurement for web pages?

Performance baseline measurement records initial load times, bundle sizes, and Core Web Vitals for web pages. It uses in-page JavaScript evaluation and the browse daemon to gather real performance data from running pages as a reference point.

Can I use Lighthouse metrics for ongoing performance monitoring?

Yes, you can use Lighthouse metrics for ongoing performance monitoring by measuring Core Web Vitals and resource sizes over time, which helps identify slow regressions and performance drift across page updates.

How do I benchmark Core Web Vitals using a browse daemon?

Benchmark Core Web Vitals using the browse daemon perf command to measure real performance data from running pages. It evaluates in-page JavaScript to gather metrics and compare them against saved baselines.

What's the best way to validate performance changes in PR checks?

The best way to validate performance changes in PR checks is to run a baseline benchmark against a target URL, then compare the results to identify any regressions in load times or Core Web Vitals before merging.