benchmark

Audit full-page performance metrics and generate JSON and Markdown reports.

Updated Oct 25, 2025
One-click install
npx skills add https://github.com/shaythegay13/serenity-pocket-app-final --skill benchmark-shaythegay13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/shaythegay13/serenity-pocket-app-final/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/shaythegay13/serenity-pocket-app-final --skill benchmark-shaythegay13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions quietly creep in as apps evolve; this skill provides automated baselines and regression detection to ensure performance stability.

Core Features & Use Cases

  • Baseline capture and comparison across commits/PRs to identify regressions
  • Comprehensive per-page metrics: TTFB, FCP, LCP, DOM Interactive, DOM Complete, and Full Load
  • Resource and bundle analysis to pinpoint large scripts or assets
  • Diff and trend analyses to monitor performance changes over time
  • Human-readable Markdown reports and structured JSON for integration with dashboards

Quick Start

Run /benchmark https://example.com to start a full performance audit and compare it to the 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 for web page loads?

Capture a performance baseline of TTFB, FCP, and LCP for a URL, then diff subsequent page load audits against it. This detects regressions across commits or PRs by generating structured JSON reports and Markdown summaries to guide optimization.

What web vitals and page load metrics are needed for a full performance baseline?

A full performance baseline requires TTFB, FCP, LCP, DOM Interactive, DOM Complete, and Full Load metrics. It also captures resource timing and bundle sizes to pinpoint large scripts or assets affecting page load performance.

How do I track web performance trends across commits or pull requests?

Track web performance trends by running full-page audits across commits or PRs and comparing captured metrics. This generates trend analyses monitoring performance changes over time, outputting human-readable Markdown reports to guide optimization efforts.

Can I benchmark a specific list of targeted pages instead of a full site audit?

Yes, you can benchmark a targeted list of pages. The audit supports targeted page lists, allowing you to capture specific metrics and diff against changed pages rather than evaluating the entire application.

How do I identify large scripts and bundle sizes affecting page load?

Identify large scripts and bundle sizes by running a full-page performance audit that collects resource timing data. The audit pinpoints large assets and outputs structured JSON reports to guide bundle optimization efforts.