web-perf

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

Updated Oct 15, 2019
One-click install
npx skills add https://github.com/kkkaoru/dotfiles --skill web-perf-kkkaoru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-perf
Source: https://github.com/kkkaoru/dotfiles/tree/main/.agents/skills-stroage/web-perf
Command: npx skills add https://github.com/kkkaoru/dotfiles --skill web-perf-kkkaoru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-devtools-mcp.

What problem does it solve? Diagnosing slow page loads and poor Lighthouse scores requires correlating traces, network requests, and code, which is tedious and error-prone when done manually. This Skill automates performance audits through Chrome DevTools MCP, producing prioritized, quantified findings. ## Core Features & Use Cases - Core Web Vitals Measurement: Captures LCP, INP, CLS, FCP, TBT, and Speed Index via automated performance traces with reload, then rates each against standard thresholds. - Network & Render Analysis: Detects render-blocking resources, dependency chains, missing preloads, caching issues, and oversized payloads from live network request data. - Codebase Analysis: Detects the framework and bundler (Webpack, Vite, Next.js, etc.) to surface tree-shaking, polyfill, minification, and dead-code issues. - Use Case: Point the Skill at a staging URL, and it returns a Core Web Vitals summary table, a prioritized issue list with estimated impact, and specific fixes like compressing a named hero image or deferring a blocking script. ## Quick Start Ask the assistant to audit the performance of your site URL and report Core Web Vitals with prioritized recommendations.

Frequently Asked Questions about web-perf

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

FAQPage Schema
How do I measure Core Web Vitals for my website?

Core Web Vitals are measured by navigating to the target URL and starting a performance trace with reload via Chrome DevTools MCP. The trace captures LCP, INP, CLS, FCP, TBT, and Speed Index, which are then rated against standard good/needs-improvement/poor thresholds.

How to find render-blocking resources on a page?

Render-blocking resources are found by listing network requests for scripts and stylesheets and checking for JS/CSS in the head without async, defer, or media attributes. The RenderBlocking insight from the performance trace also quantifies their estimated impact in milliseconds.

What MCP server is required for Chrome DevTools performance audits?

The chrome-devtools MCP server is required, configured with the command npx -y chrome-devtools-mcp@latest. If tools like navigate_page or performance_start_trace are unavailable, the audit cannot proceed until this server is added to the MCP config.

Can I audit a third-party website without codebase access?

Yes, performance traces, Core Web Vitals analysis, network inspection, and accessibility snapshots all work on any public URL. Only the codebase analysis phase, which inspects bundler configs and framework settings, is skipped for third-party sites.

Why does performance_analyze_insight fail with an unknown insight name?

Insight names vary across Chrome DevTools versions, so a hardcoded name may not exist in your trace. Inspect the insightSetId from the trace response to discover the available insight names, then retry with a valid one.