benchmark

Measure page load times, Core Web Vitals, and resource sizes for regression detection.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill benchmark-jia-hong-peng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/Jia-Hong-Peng/jolike.com/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill benchmark-jia-hong-peng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance issues often creep in gradually through small changes, and by the time users notice, the app is significantly slower. This skill provides automated performance regression detection so teams can catch slowdowns before they reach production.

Core Features & Use Cases

  • Baseline Establishment: Captures performance baselines for page load times, Core Web Vitals, and resource sizes.
  • PR Comparison: Automatically compares performance metrics before and after every pull request.
  • Trend Tracking: Monitors performance trends over time to identify gradual degradation.
  • Use Case: A frontend team can run this skill on every PR to ensure a new dependency doesn't increase bundle size or a layout change doesn't hurt LCP.

Quick Start

Use the benchmark skill to run a full performance audit on the current site and compare it against the stored 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 in a CI/CD pipeline?

Automated performance regression detection compares page load times and Core Web Vitals before and after pull requests. By integrating this into CI/CD pipelines, teams establish quantitative baselines to prevent gradual performance degradation from reaching production.

How do I track Core Web Vitals and bundle size changes on every pull request?

Track Core Web Vitals and bundle size changes by capturing performance baselines for resource sizes and page speed. The skill automatically compares these metrics before and after every pull request to catch slowdowns caused by new dependencies or layout changes.

What is the best way to catch web performance degradation before it ships?

The best way to catch web performance degradation is real browser performance monitoring. By measuring page load times, Core Web Vitals, and resource sizes on every PR, teams identify gradual slowdowns and establish quantitative baselines before code merges.

Do I need a specific browser environment to measure Core Web Vitals in CI?

Yes, measuring Core Web Vitals in CI requires the gstack browse daemon to collect real browser performance metrics. This daemon establishes quantitative baselines for page load times and resource sizes to accurately detect regressions.

How does Lighthouse benchmark testing prevent gradual page speed slowdowns?

Lighthouse benchmark testing prevents gradual page speed slowdowns by establishing performance baselines and tracking trends over time. It applies before/after comparisons to pull request workflows, ensuring that small changes do not degrade Core Web Vitals or increase bundle size.