benchmark

Automate web page performance benchmarking to detect regressions in load times and Core Web Vitals.

1|Updated May 25, 2026
One-click install
npx skills add https://github.com/chiruu12/nudge --skill benchmark-chiruu12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/chiruu12/nudge/tree/main/.agents/skills/gstack-benchmark
Command: npx skills add https://github.com/chiruu12/nudge --skill benchmark-chiruu12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lighthouse, puppeteer, puppeteer-core, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the detection of performance regressions in web pages, providing insights into page load times, Core Web Vitals, and resource sizes.

Core Features & Use Cases

  • Performance Regression Detection: Automatically establishes baselines for performance metrics and compares them before and after changes.
  • Page Load Time Analysis: Measures and compares page load times, including TTFB, FCP, LCP, and Full Load times.
  • Resource Size Analysis: Analyzes and compares resource sizes, such as JavaScript and CSS bundle sizes.
  • Use Case: Before deploying a new feature or change to a web application, use this Skill to ensure that performance has not regressed.

Quick Start

Run the 'benchmark' command with the URL of the web page you want to test, e.g., nudge benchmark https://example.com.

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

Automate performance regression detection by establishing baseline metrics for page load times and Core Web Vitals, then comparing them against current metrics before deploying changes.

Can I use Lighthouse and Puppeteer to measure Core Web Vitals regressions?

Yes, you can use Lighthouse and Puppeteer to measure Core Web Vitals regressions by profiling web pages and comparing current TTFB, FCP, and LCP scores against established performance baselines.

What is the best way to establish a baseline for web performance benchmarking?

Establish a baseline for web performance benchmarking by measuring initial page load times and resource sizes, which are then used to identify any subsequent regressions in JavaScript or CSS bundle sizes.

How do I analyze resource sizes like JavaScript and CSS bundles before deployment?

Analyze JavaScript and CSS resource sizes by profiling the web page before deployment, comparing current bundle sizes against baseline metrics to ensure web optimization has not regressed.

Does this performance benchmarking approach work for pre-deployment web optimization workflows?

Yes, this performance benchmarking approach works for pre-deployment web optimization workflows by automatically comparing baseline and current metrics to prevent introducing regressions into the web application.

What web performance metrics are compared to identify regressions?

Web performance metrics compared to identify regressions include page load times, Core Web Vitals such as LCP and FCP, TTFB, Full Load times, and overall JavaScript and CSS resource sizes.