web-perf

Audits web performance using Chrome DevTools MCP to measure Core Web Vitals and identify optimization opportunities.

Updated May 23, 2026
One-click install
npx skills add https://github.com/kveperedo/website --skill web-perf-kveperedo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-perf
Source: https://github.com/kveperedo/website/tree/main/.agents/skills/web-perf
Command: npx skills add https://github.com/kveperedo/website --skill web-perf-kveperedo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-devtools-mcp.

What problem does it solve? Diagnosing slow page loads and poor Lighthouse scores requires deep knowledge of performance tooling and metrics. This Skill provides a structured, five-phase audit workflow that measures Core Web Vitals, traces network behavior, and pinpoints concrete fixes with quantified impact. ## Core Features & Use Cases - Core Web Vitals Measurement: Captures LCP, INP, CLS, FCP, TBT, and Speed Index via Chrome DevTools performance traces with reload-based cold-load analysis. - Network & Rendering Analysis: Identifies render-blocking resources, network dependency chains, missing preloads, caching issues, and oversized payloads. - Codebase Analysis: Detects your framework and bundler (Vite, Webpack, Next.js, etc.) to surface tree-shaking, polyfill, minification, and dead-code issues. - Use Case: Ask for an audit of your staging site and receive a prioritized report: a Core Web Vitals summary table, top issues ranked by estimated impact, and specific fixes like "compress hero.png (450KB) to WebP". ## Quick Start Audit the performance of https://example.com and give me a prioritized list of fixes with estimated impact.

Frequently Asked Questions about web-perf

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why did my performance trace return empty or fail?▼

Traces typically fail when the page did not load correctly before recording started. Verify the page loads with navigate_page first, and if insight names don't match, inspect the trace response to discover the available insight names for your Chrome DevTools version.