skills.rest
sadie100
sadie100COMMUNITY
Explore all skills by this author →
GitHub

benchmark

Detect web page performance regressions by comparing before/after metrics on pull requests.

Updated Apr 8, 2026
Search Tags:#benchmarking#web performance#page speed#performance regression#load time
One-click install
npx skills add https://github.com/sadie100/claude-dotfiles --skill benchmark-sadie100
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/sadie100/claude-dotfiles/tree/main/skills/benchmark
Command: npx skills add https://github.com/sadie100/claude-dotfiles --skill benchmark-sadie100

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, Glob, AskUserQuestion, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically detects performance regressions in web pages, allowing for quick identification of performance issues introduced in new code changes.

Core Features & Use Cases

  • Performance Benchmarking: Compares before/after performance metrics like load time, resource size, and Core Web Vitals.
  • Automated PR Checks: Runs automatically on every Pull Request to track performance over time.
  • Use Case: After making changes to a web application, use this Skill to check for performance degradation without manually running tests.

Quick Start

Run the 'benchmark' skill to analyze the performance of the given URL.

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?â–¼

Detect web performance regressions by comparing before and after metrics like load time, resource size, and Core Web Vitals automatically on every pull request to identify code changes that degrade page speed.

What is performance benchmarking for web pages?â–¼

Performance benchmarking for web pages is the process of measuring load time and Core Web Vitals before and after code changes to track performance trends and catch regressions early.

How do I automate page speed monitoring for new code changes?â–¼

Automate page speed monitoring by running performance benchmarking on every pull request, comparing current metrics against a baseline to flag regressions without manual testing.

Do I need a browse daemon to measure load time and Core Web Vitals?â–¼

Yes, measuring load time and Core Web Vitals requires integrating with the browse daemon for performance testing, along with Bash, Read, Write, Glob, and AskUserQuestion dependencies for interactive prompts and script execution.

What web performance metrics are compared during regression detection?â–¼

Web performance regression detection compares before and after metrics including page load time, resource size, and Core Web Vitals to identify performance degradation introduced by new code.

Can I track performance trends automatically without manual testing?â–¼

Yes, you can track performance trends automatically by running benchmarking on every pull request, eliminating the need to manually run web performance tests after making application changes.

Related Skills

Explore More Software Engineering Skills→
mulyovedmulyoved

benchmark

Benchmarks web page performance metrics and detects regressions on pull requests.

Community
Advanced
mpsuessermpsuesser

web-perf

Measure Core Web Vitals and diagnose page-load bottlenecks using Chrome DevTools traces.

Community
Advanced
ShmurdocShmurdoc

benchmark

Compare web performance metrics against baselines to detect regressions.

Community
Advanced
26mitch2626mitch26

benchmark

Compare web application performance metrics before and after changes to detect regressions.

Community
Advanced