skills.rest
smarmen86
smarmen86COMMUNITY
Explore all skills by this author →
GitHub

benchmark

Detects performance regressions by measuring page loads, Core Web Vitals, and resource sizes.

Updated Jun 5, 2026
Search Tags:#performance#web vitals#optimization#lighthouse#regression#benchmark
One-click install
npx skills add https://github.com/smarmen86/claude-code-kit --skill benchmark-smarmen86
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/smarmen86/claude-code-kit/tree/main/skills/benchmark
Command: npx skills add https://github.com/smarmen86/claude-code-kit --skill benchmark-smarmen86

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents performance degradation by automating the detection of regressions in page load times, Core Web Vitals, and resource sizes during the development lifecycle.

Core Features & Use Cases

  • Automated Benchmarking: Establishes performance baselines and compares them against current PR changes.
  • Resource Analysis: Identifies heavy assets, large bundles, and slow-loading scripts that impact user experience.
  • Trend Tracking: Monitors performance metrics over time to ensure application speed remains consistent as features are added.

Quick Start

Run the benchmark skill on the current page to compare its performance against the established baseline.

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 before merging a pull request?▼

You can detect web performance regressions by automating Core Web Vitals measurement and resource size auditing against an established baseline. This skill compares current PR changes to historical performance trends to identify slow-loading scripts and heavy assets.

What is automated benchmarking for Core Web Vitals and when do I need it?▼

Automated benchmarking for Core Web Vitals measures page load times and resource sizes to establish performance baselines. You need it during web development workflows requiring continuous performance monitoring to prevent application speed degradation as features are added.

Can I track historical performance trends for page load times in a continuous monitoring workflow?▼

Yes, you can track historical performance trends for page load times by applying automated timing analysis across development cycles. A browser daemon measures Core Web Vitals and resource sizes, monitoring metrics over time to ensure application speed remains consistent.

How do I audit bundle size and identify heavy assets impacting user experience?▼

You can audit bundle size and identify heavy assets by running resource analysis on the current page. This process identifies large bundles and slow-loading scripts that impact user experience, comparing them against established performance baselines to flag regressions.

Does this performance regression testing require a specific browser daemon setup?▼

This performance regression testing uses a browser daemon to measure page load times, Core Web Vitals, and resource sizes. It applies to web development workflows requiring continuous performance monitoring and PR-based regression testing without additional external dependencies.

Related Skills

Explore More Software Engineering Skills→
Jia-Hong-PengJia-Hong-Peng

benchmark

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

Community
Advanced
GenEducationGenEducation

benchmark

Measure page load, Core Web Vitals, and resource usage against a saved baseline.

Official
Advanced
PP-NamiasPP-Namias
2

performance-auditing

Automate website performance audits with Lighthouse and Core Web Vitals tracking.

Community
Advanced
SantiagoisperSantiagoisper

benchmark

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

Community
Advanced