skills.rest
tony30552001
tony30552001COMMUNITY
Explore all skills by this author →
GitHub

benchmark

Run browse daemon benchmarks to compare page load metrics against baselines on PRs.

Updated Dec 26, 2025
Search Tags:#performance#lighthouse#diff#benchmark#baseline#web-vitals
One-click install
npx skills add https://github.com/tony30552001/Genpic-master --skill benchmark-tony30552001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/tony30552001/Genpic-master/tree/main/.agents/skills/gstack/benchmark
Command: npx skills add https://github.com/tony30552001/Genpic-master --skill benchmark-tony30552001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions on web apps are hard to detect manually and can slip into PRs unnoticed. This Skill automates end-to-end benchmarking by running the browse daemon to establish baselines for page load times, Core Web Vitals, and resource sizes, and then compares new runs against those baselines on every PR.

Core Features & Use Cases

  • Baseline capture and long-term trend tracking across multiple pages and builds.
  • PR-time comparison reports that highlight regressions and warnings in key metrics like TTFB, FCP, LCP, and resource sizes.
  • Flexible page selection (all pages or a subset) and diff mode to focus on changed paths.

Quick Start

Run a performance audit on a target URL to create a baseline or compare against an existing baseline.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I automate performance regression detection on web application PRs?▼

Automate performance regression detection by running the browse daemon to establish baselines for page load times, Core Web Vitals, and resource sizes, then comparing new runs against those baselines on every PR.

What Core Web Vitals and metrics are compared against the performance baseline?▼

The performance baseline compares Core Web Vitals and key metrics including TTFB, FCP, LCP, DOM events, and resource sizes to highlight regressions and warnings on PR-time reports.

Can I benchmark only changed paths instead of all pages during a PR?▼

Yes, you can benchmark a subset of pages or use diff mode to focus only on changed paths, comparing new runs against established baselines for targeted performance regression detection.

Does performance benchmarking require a browse daemon and baseline storage?▼

Yes, performance benchmarking requires a browse daemon to capture metrics and baseline storage to save page load times, Core Web Vitals, and resource sizes for comparison across PRs and releases.

What's the best way to track long-term web performance trends across builds?▼

The best way to track long-term web performance trends is to capture baselines for page load times and Core Web Vitals across multiple pages and builds, enabling continuous regression detection during delivery.

When should I not use automated performance regression benchmarking?▼

Automated performance regression benchmarking is not suited for static sites without continuous delivery workflows, as it requires a browse daemon, baseline storage, and active PR pipelines to compare metrics effectively.

Related Skills

Explore More Software Engineering Skills→
ligianehualigianehua

benchmark

Detect web performance regressions by comparing current metrics against established baselines.

Community
Advanced
putrawitamaputrawitama
1

benchmark

Benchmark web application performance baselines and flag regressions across commits.

Community
Intermediate
The13thNodeThe13thNode
3

benchmark

Measure web performance baselines and generate markdown benchmark reports.

Community
Intermediate
SantiagoisperSantiagoisper

benchmark

Measure page load times, Core Web Vitals, and resource sizes with Lighthouse.

Community
Advanced