Performance audit

Skill ironbee-ai/ironbee-devtools-skills/skills/performance-audit

Skills for IronBee DevTools MCP/CLI

Install

npx -y skills add ironbee-ai/ironbee-devtools-skills --skill performance-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyze web and backend performance using Web Vitals, network timing, and Node.js metrics. Use when the user asks about page performance, load times, Core Web Vitals (LCP, CLS, INP), slow pages, backend bottlenecks, or SEO performance factors.

SKILL.md

4.2 KB, as published. Nobody here has run it

Performance Audit Skill

Analyze web page performance using Web Vitals and network timing metrics.

When to Use

This skill activates when:

User asks about page performance or speed
User wants to optimize load times
User mentions slow page, slow API, or poor user experience
User needs Core Web Vitals metrics
User asks about backend bottlenecks or TTFB
User asks about SEO performance factors

Capabilities

Web Vitals Analysis

ironbee-browser-devtools-cli o11y get-web-vitals
ironbee-browser-devtools-cli --json o11y get-web-vitals
ironbee-browser-devtools-cli --json o11y get-web-vitals --wait-ms 3000
ironbee-browser-devtools-cli --json o11y get-web-vitals --include-debug

Network Performance

ironbee-browser-devtools-cli --json o11y get-http-requests
ironbee-browser-devtools-cli --json o11y get-http-requests --resource-type script
ironbee-browser-devtools-cli --json o11y get-http-requests --resource-type stylesheet
ironbee-browser-devtools-cli --json o11y get-http-requests --status '{"min":400}'

Visual Analysis

ironbee-browser-devtools-cli content take-screenshot --name "above-fold"
ironbee-browser-devtools-cli content take-screenshot --name "full-page" --full-page

Performance Thresholds

Metric	Good	Needs Work	Poor
LCP	≤2.5s	2.5-4s	>4s
INP	≤200ms	200-500ms	>500ms
CLS	≤0.1	0.1-0.25	>0.25
TTFB	≤800ms	800-1800ms	>1800ms
FCP	≤1.8s	1.8-3s	>3s

Audit Workflow

SESSION="--session-id perf-audit"

# 1. Navigate to page
ironbee-browser-devtools-cli $SESSION navigation go-to --url "https://example.com"

# 2. Wait for page to settle
ironbee-browser-devtools-cli $SESSION sync wait-for-network-idle

# 3. Get Web Vitals
ironbee-browser-devtools-cli $SESSION --json o11y get-web-vitals --wait-ms 2000

# 4. Analyze network requests
ironbee-browser-devtools-cli $SESSION --json o11y get-http-requests

# 5. Check for console errors
ironbee-browser-devtools-cli $SESSION --json o11y get-console-messages --type warning

# 6. Take screenshot for reference
ironbee-browser-devtools-cli $SESSION content take-screenshot --name "performance-audit"

# 7. Cleanup
ironbee-browser-devtools-cli session delete perf-audit

Detailed Analysis

Check Large Resources

# Filter by type (one at a time: document, stylesheet, image, script, xhr, fetch, etc.)
ironbee-browser-devtools-cli --json o11y get-http-requests --resource-type script
ironbee-browser-devtools-cli --json o11y get-http-requests --resource-type stylesheet
ironbee-browser-devtools-cli --json o11y get-http-requests --resource-type image

Check Slow Requests

ironbee-browser-devtools-cli --json o11y get-http-requests
# Look for requests with high timing values

Backend Performance (ironbee-node-devtools-cli)

When TTFB or API latency suggests backend bottlenecks, inspect the Node.js process:

# Connect to API/server process
ironbee-node-devtools-cli --session-id perf debug connect --pid 12345

# Tracepoint on slow handler to capture call context
ironbee-node-devtools-cli --session-id perf debug put-tracepoint \
  --url-pattern "routes/heavy.ts" \
  --line-number 30

Common Issues

Large unoptimized images
Render-blocking CSS/JS
Too many HTTP requests
Slow server response (TTFB)
Layout shifts from dynamic content
Uncompressed resources
Missing caching headers
Third-party scripts blocking main thread

Best Practices

Run multiple times for consistent results
Wait for network idle before measuring
Use --wait-ms for LCP/CLS to settle
Check network requests for slow/large resources
Take screenshots at different load stages
Test on different network conditions (throttle if needed)
Compare before/after for optimization validation