Who it is forA developer chasing a slow page load who does not want to read flame charts.
The problemPerformance traces are dense and hard to turn into fixes.
The outcomeA short list of the biggest performance problems on the page and what to change.
What you need first
- Node.js and npm
- Chrome
- An MCP client or a coding agent that can run shell commands
Steps
- Install the MCP server in your client
- Prompt: Check the performance of https://developers.chrome.com (or your own URL)
- Read the insights the agent extracts from the trace
- Ask it to apply the top fix and re-run the trace
Prompt for your agent
Using ChromeDevTools/chrome-devtools-mcp, record a performance trace of <url>, list the top 3 insights with their likely cause in my code, and re-measure after fixing the first one.
Caveat.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for ChromeDevTools/chrome-devtools-mcp and "Have an agent record a performance trace and explain it"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer