Web Performance Audit
Your knowledge of web performance metrics, thresholds, and tooling APIs may be outdated. Prefer retrieval over pre-training when citing specific numbers or recommendations.
Retrieval Sources
| Source |
How to retrieve |
Use for |
| web.dev |
https://web.dev/articles/vitals |
Core Web Vitals thresholds, definitions |
| Chrome DevTools docs |
https://developer.chrome.com/docs/devtools/performance |
Tooling APIs, trace analysis |
| Lighthouse scoring |
https://developer.chrome.com/docs/lighthouse/performance/performance-scoring |
Score weights, metric thresholds |
FIRST: Verify MCP Tools Available
Run this before starting. On Pi, use the MCP proxy: mcp({ search: "performance_start_trace" }) or mcp({ search: "navigate_page" }). If search returns nothing, STOP—the chrome-devtools server is not configured or Pi needs a restart after installing pi-mcp-adapter.
Pi config: ~/.pi/agent/mcp.json (chrome-devtools with --autoConnect). Slash command: /mcp.
Key Guidelines
- Be assertive: Verify claims by checking network requests, DOM, or codebase—then state findings definitively.
- Verify before recommending: Confirm something is unused before suggesting removal.
- Quantify impact: Use estimated savings from insights. Don't prioritize changes with 0ms impact.
- Skip non-issues: If render-blocking resources have 0ms estimated impact, note but don't recommend action.
- Be specific: Say "compress hero.png (450KB) to WebP" not "optimize images".
- Prioritize ruthlessly: A site with 200ms LCP and 0 CLS is already excellent—say so.
Quick Reference
| Task |
Tool Call |
| Load page |
navigate_page(url: "...") |
| Start trace |
performance_start_trace(autoStop: true, reload: true) |
| Analyze insight |
performance_analyze_insight(insightSetId: "...", insightName: "...") |
| List requests |
list_network_requests(resourceTypes: ["Script", "Stylesheet", ...]) |
| Request details |
get_network_request(reqid: <id>) |
| A11y snapshot |
take_snapshot(verbose: true) |
Workflow
Copy this checklist to track progress:
Audit Progress:
- [ ] Phase 1: Performance trace (navigate + record)
- [ ] Phase 2: Core Web Vitals analysis (includes CLS culprits)
- [ ] Phase 3: Network analysis
- [ ] Phase 4: Accessibility snapshot
- [ ] Phase 5: Codebase analysis (skip if third-party site)
Phase 1: Performance Trace
Navigate to the target URL:
navigate_page(url: "<target-url>")
Start a performance trace with reload to capture cold-load metrics:
performance_start_trace(autoStop: true, reload: true)
Wait for trace completion, then retrieve results.
Troubleshooting:
- If trace returns empty or fails, verify the page loaded correctly with
navigate_page first
- If insight names don't match, inspect the trace response to list available insights
Phase 2: Core Web Vitals Analysis
Use performance_analyze_insight to extract key metrics.
Note: Insight names may vary across Chrome DevTools versions. If an insight name doesn't work, check the insightSetId from the trace response to discover available insights.
Common insight names:
| Metric |
Insight Name |
What to Look For |
| LCP |
LCPBreakdown |
Time to largest contentful paint; breakdown of TTFB, resource load, render delay |
| CLS |
CLSCulprits |
Elements causing layout shifts (images without dimensions, injected content, font swaps) |
| Render Blocking |
RenderBlocking |
CSS/JS blocking first paint |
| Document Latency |
DocumentLatency |
Server response time issues |
| Network Dependencies |
NetworkRequestsDepGraph |
Request chains delaying critical resources |
Example:
performance_analyze_insight(insightSetId: "<id-from-trace>", insightName: "LCPBreakdown")
Key thresholds (good/needs-improvement/poor):
- TTFB: < 800ms / < 1.8s / > 1.8s
- FCP: < 1.8s / < 3s / > 3s
- LCP: < 2.5s / < 4s / > 4s
- INP: < 200ms / < 500ms / > 500ms
- TBT: < 200ms / < 600ms / > 600ms
- CLS: < 0.1 / < 0.25 / > 0.25
- Speed Index: < 3.4s / < 5.8s / > 5.8s
Phase 3: Network Analysis
List all network requests to identify optimization opportunities:
list_network_requests(resourceTypes: ["Script", "Stylesheet", "Document", "Font", "Image"])
Look for:
- Render-blocking resources: JS/CSS in
<head> without async/defer/media attributes
- Network chains: Resources discovered late because they depend on other resources loading first (e.g., CSS imports, JS-loaded fonts)
- Missing preloads: Critical resources (fonts, hero images, key scripts) not preloaded
- Caching issues: Missing or weak
Cache-Control, ETag, or Last-Modified headers
- Large payloads: Uncompressed or oversized JS/CSS bundles
- Unused preconnects: If flagged, verify by checking if ANY requests went to that origin. If zero requests, it's definitively unused—recommend removal. If requests exist but loaded late, the preconnect may still be valuable.
For detailed request info:
get_network_request(reqid: <id>)
Phase 4: Accessibility Snapshot
Take an accessibility tree snapshot:
take_snapshot(verbose: true)
Flag high-level gaps:
- Missing or duplicate ARIA IDs
- Elements with poor contrast ratios (check against WCAG AA: 4.5:1 for normal text, 3:1 for large text)
- Focus traps or missing focus indicators
- Interactive elements without accessible names
Phase 5: Codebase Analysis
Skip if auditing a third-party site without codebase access.
Analyze the codebase to understand where improvements can be made.
Detect Framework & Bundler
Search for configuration files to identify the stack:
| Tool |
Config Files |
| Webpack |
webpack.config.js, webpack.*.js |
| Vite |
vite.config.js, vite.config.ts |
| Rollup |
rollup.config.js, rollup.config.mjs |
| esbuild |
esbuild.config.js, build scripts with esbuild |
| Parcel |
.parcelrc, package.json (parcel field) |
| Next.js |
next.config.js, next.config.mjs |
| Nuxt |
nuxt.config.js, nuxt.config.ts |
| SvelteKit |
svelte.config.js |
| Astro |
astro.config.mjs |
Also check package.json for framework dependencies and build scripts.
Tree-Shaking & Dead Code
- Webpack: Check for
mode: 'production', sideEffects in package.json, usedExports optimization
- Vite/Rollup: Tree-shaking enabled by default; check for
treeshake options
- Look for: Barrel files (
index.js re-exports), large utility libraries imported wholesale (lodash, moment)
Unused JS/CSS
- Check for CSS-in-JS vs. static CSS extraction
- Look for PurgeCSS/UnCSS configuration (Tailwind's
content config)
- Identify dynamic imports vs. eager loading
Polyfills
- Check for
@babel/preset-env targets and useBuiltIns setting
- Look for
core-js imports (often oversized)
- Check
browserslist config for overly broad targeting
Compression & Minification
- Check for
terser, esbuild, or swc minification
- Look for gzip/brotli compression in build output or server config
- Check for source maps in production builds (should be external or disabled)
Output Format
Present findings as:
- Core Web Vitals Summary - Table with metric, value, and rating (good/needs-improvement/poor)
- Top Issues - Prioritized list of problems with estimated impact (high/medium/low)
- Recommendations - Specific, actionable fixes with code snippets or config changes
- Codebase Findings - Framework/bundler detected, optimization opportunities (omit if no codebase access)
1---2name: web-perf3description: Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.4---56# Web Performance Audit78Your knowledge of web performance metrics, thresholds, and tooling APIs may be outdated. **Prefer retrieval over pre-training** when citing specific numbers or recommendations.910## Retrieval Sources1112| Source | How to retrieve | Use for |13|--------|----------------|---------|14| web.dev | `https://web.dev/articles/vitals` | Core Web Vitals thresholds, definitions |15| Chrome DevTools docs | `https://developer.chrome.com/docs/devtools/performance` | Tooling APIs, trace analysis |16| Lighthouse scoring | `https://developer.chrome.com/docs/lighthouse/performance/performance-scoring` | Score weights, metric thresholds |1718## FIRST: Verify MCP Tools Available1920**Run this before starting.** On Pi, use the MCP proxy: `mcp({ search: "performance_start_trace" })` or `mcp({ search: "navigate_page" })`. If search returns nothing, STOP—the chrome-devtools server is not configured or Pi needs a restart after installing `pi-mcp-adapter`.2122Pi config: `~/.pi/agent/mcp.json` (chrome-devtools with `--autoConnect`). Slash command: `/mcp`.2324## Key Guidelines2526- **Be assertive**: Verify claims by checking network requests, DOM, or codebase—then state findings definitively.27- **Verify before recommending**: Confirm something is unused before suggesting removal.28- **Quantify impact**: Use estimated savings from insights. Don't prioritize changes with 0ms impact.29- **Skip non-issues**: If render-blocking resources have 0ms estimated impact, note but don't recommend action.30- **Be specific**: Say "compress hero.png (450KB) to WebP" not "optimize images".31- **Prioritize ruthlessly**: A site with 200ms LCP and 0 CLS is already excellent—say so.3233## Quick Reference3435| Task | Tool Call |36|------|-----------|37| Load page | `navigate_page(url: "...")` |38| Start trace | `performance_start_trace(autoStop: true, reload: true)` |39| Analyze insight | `performance_analyze_insight(insightSetId: "...", insightName: "...")` |40| List requests | `list_network_requests(resourceTypes: ["Script", "Stylesheet", ...])` |41| Request details | `get_network_request(reqid: <id>)` |42| A11y snapshot | `take_snapshot(verbose: true)` |4344## Workflow4546Copy this checklist to track progress:4748```49Audit Progress:50- [ ] Phase 1: Performance trace (navigate + record)51- [ ] Phase 2: Core Web Vitals analysis (includes CLS culprits)52- [ ] Phase 3: Network analysis53- [ ] Phase 4: Accessibility snapshot54- [ ] Phase 5: Codebase analysis (skip if third-party site)55```5657### Phase 1: Performance Trace58591. Navigate to the target URL:60 ```61 navigate_page(url: "<target-url>")62 ```63642. Start a performance trace with reload to capture cold-load metrics:65 ```66 performance_start_trace(autoStop: true, reload: true)67 ```68693. Wait for trace completion, then retrieve results.7071**Troubleshooting:**72- If trace returns empty or fails, verify the page loaded correctly with `navigate_page` first73- If insight names don't match, inspect the trace response to list available insights7475### Phase 2: Core Web Vitals Analysis7677Use `performance_analyze_insight` to extract key metrics.7879**Note:** Insight names may vary across Chrome DevTools versions. If an insight name doesn't work, check the `insightSetId` from the trace response to discover available insights.8081Common insight names:8283| Metric | Insight Name | What to Look For |84|--------|--------------|------------------|85| LCP | `LCPBreakdown` | Time to largest contentful paint; breakdown of TTFB, resource load, render delay |86| CLS | `CLSCulprits` | Elements causing layout shifts (images without dimensions, injected content, font swaps) |87| Render Blocking | `RenderBlocking` | CSS/JS blocking first paint |88| Document Latency | `DocumentLatency` | Server response time issues |89| Network Dependencies | `NetworkRequestsDepGraph` | Request chains delaying critical resources |9091Example:92```93performance_analyze_insight(insightSetId: "<id-from-trace>", insightName: "LCPBreakdown")94```9596**Key thresholds (good/needs-improvement/poor):**97- TTFB: < 800ms / < 1.8s / > 1.8s98- FCP: < 1.8s / < 3s / > 3s99- LCP: < 2.5s / < 4s / > 4s100- INP: < 200ms / < 500ms / > 500ms101- TBT: < 200ms / < 600ms / > 600ms102- CLS: < 0.1 / < 0.25 / > 0.25103- Speed Index: < 3.4s / < 5.8s / > 5.8s104105### Phase 3: Network Analysis106107List all network requests to identify optimization opportunities:108```109list_network_requests(resourceTypes: ["Script", "Stylesheet", "Document", "Font", "Image"])110```111112**Look for:**1131141. **Render-blocking resources**: JS/CSS in `<head>` without `async`/`defer`/`media` attributes1152. **Network chains**: Resources discovered late because they depend on other resources loading first (e.g., CSS imports, JS-loaded fonts)1163. **Missing preloads**: Critical resources (fonts, hero images, key scripts) not preloaded1174. **Caching issues**: Missing or weak `Cache-Control`, `ETag`, or `Last-Modified` headers1185. **Large payloads**: Uncompressed or oversized JS/CSS bundles1196. **Unused preconnects**: If flagged, verify by checking if ANY requests went to that origin. If zero requests, it's definitively unused—recommend removal. If requests exist but loaded late, the preconnect may still be valuable.120121For detailed request info:122```123get_network_request(reqid: <id>)124```125126### Phase 4: Accessibility Snapshot127128Take an accessibility tree snapshot:129```130take_snapshot(verbose: true)131```132133**Flag high-level gaps:**134- Missing or duplicate ARIA IDs135- Elements with poor contrast ratios (check against WCAG AA: 4.5:1 for normal text, 3:1 for large text)136- Focus traps or missing focus indicators137- Interactive elements without accessible names138139## Phase 5: Codebase Analysis140141**Skip if auditing a third-party site without codebase access.**142143Analyze the codebase to understand where improvements can be made.144145### Detect Framework & Bundler146147Search for configuration files to identify the stack:148149| Tool | Config Files |150|------|--------------|151| Webpack | `webpack.config.js`, `webpack.*.js` |152| Vite | `vite.config.js`, `vite.config.ts` |153| Rollup | `rollup.config.js`, `rollup.config.mjs` |154| esbuild | `esbuild.config.js`, build scripts with `esbuild` |155| Parcel | `.parcelrc`, `package.json` (parcel field) |156| Next.js | `next.config.js`, `next.config.mjs` |157| Nuxt | `nuxt.config.js`, `nuxt.config.ts` |158| SvelteKit | `svelte.config.js` |159| Astro | `astro.config.mjs` |160161Also check `package.json` for framework dependencies and build scripts.162163### Tree-Shaking & Dead Code164165- **Webpack**: Check for `mode: 'production'`, `sideEffects` in package.json, `usedExports` optimization166- **Vite/Rollup**: Tree-shaking enabled by default; check for `treeshake` options167- **Look for**: Barrel files (`index.js` re-exports), large utility libraries imported wholesale (lodash, moment)168169### Unused JS/CSS170171- Check for CSS-in-JS vs. static CSS extraction172- Look for PurgeCSS/UnCSS configuration (Tailwind's `content` config)173- Identify dynamic imports vs. eager loading174175### Polyfills176177- Check for `@babel/preset-env` targets and `useBuiltIns` setting178- Look for `core-js` imports (often oversized)179- Check `browserslist` config for overly broad targeting180181### Compression & Minification182183- Check for `terser`, `esbuild`, or `swc` minification184- Look for gzip/brotli compression in build output or server config185- Check for source maps in production builds (should be external or disabled)186187## Output Format188189Present findings as:1901911. **Core Web Vitals Summary** - Table with metric, value, and rating (good/needs-improvement/poor)1922. **Top Issues** - Prioritized list of problems with estimated impact (high/medium/low)1933. **Recommendations** - Specific, actionable fixes with code snippets or config changes1944. **Codebase Findings** - Framework/bundler detected, optimization opportunities (omit if no codebase access)
Waishnav