skills.rest
stayconnectquick
stayconnectquickCOMMUNITY
Explore all skills by this author →
GitHub

benchmark

Compare navigation and resource timing data against a stored baseline to identify performance regressions.

Updated May 6, 2026
Search Tags:#lighthouse#benchmark#web-performance#pr-analysis#baselines#page-load
One-click install
npx skills add https://github.com/stayconnectquick/gstack --skill benchmark-stayconnectquick
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/stayconnectquick/gstack/tree/main/benchmark
Command: npx skills add https://github.com/stayconnectquick/gstack --skill benchmark-stayconnectquick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions in web apps can accumulate across PRs and escapes detection until it's too late. This Skill provides baseline-based measurements to surface regressions in page load times, Core Web Vitals, and resource sizes so teams can act early.

Core Features & Use Cases

  • Baseline capture and per-PR comparison to identify regressions.
  • Timing metrics: TTFB, FCP, LCP, DOMInteractive, DOMContentLoaded, and total load time.
  • Resource and bundle analysis: transfer sizes, top slow resources, and network summary.
  • Use Case: When reviewing a PR, run this to ensure performance does not regress compared to the baseline.

Quick Start

Run a URL through the benchmark tool to start a baseline-enabled performance audit on that page.

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?▼

Baseline-driven web performance benchmarking compares navigation and resource timing data from a target URL against a stored baseline. It captures metrics like TTFB, FCP, and LCP to identify regressions across PRs before they accumulate.

How do I capture a performance baseline for a web page?▼

Capture a performance baseline by running a target URL through the benchmark tool with the --baseline option. This stores initial timing metrics and resource transfer sizes to compare against future pull requests.

What timing metrics are included in a web performance benchmark report?▼

A web performance benchmark report includes TTFB, FCP, LCP, DOMInteractive, DOMContentLoaded, and total load time. It also provides resource and bundle analysis covering transfer sizes, top slow resources, and network summary.

Does the benchmark tool save results in structured formats for review?▼

Yes, the benchmark tool saves results in structured JSON and markdown reports for review. This ensures performance audit data from the target URL is easily accessible for analyzing Core Web Vitals and resource regressions.

Can I analyze resource and bundle sizes using a baseline comparison?▼

Yes, you can analyze resource and bundle sizes using a baseline comparison. The benchmark collects transfer sizes and network summaries to identify slow resources and bundle bloat introduced in new PRs.

Why does page load time regress across PRs without detection?▼

Page load time regresses across PRs without detection when performance issues accumulate silently. Baseline-driven benchmarks solve this by auditing Core Web Vitals and resource sizes per PR to surface regressions early.

Related Skills

Explore More Software Engineering Skills→
OmerFarukOrucOmerFarukOruc
2

benchmark

Benchmark web performance by capturing timing metrics and comparing them against stored baselines.

Community
Advanced
Ronin15Ronin15
14

hammer-benchmark-regression

Compare SDL3 HammerEngine metrics against baselines to flag performance regressions.

Community
Intermediate
gwpjpgwpjp
3

performance-auditor

Measure navigation timings, core web vitals, and network usage in Chrome.

Community
Intermediate
npc-chrisnpc-chris
1

benchmark

Automate website performance benchmarking with page load times and Core Web Vitals.

Community
Advanced