Performance Profile

Use this skill when a web application feels slow, janky, or unresponsive. Cursor's built-in browser has CPU profiling tools that capture real call stacks and timing data.

How It Works

The cursor-ide-browser MCP provides browser_profile_start and browser_profile_stop tools that capture Chrome DevTools-format CPU profiles. Profile data is written to ~/.cursor/browser-logs/ as both raw JSON and a human-readable summary.

Steps

1. Ensure the app is running — start the dev server if it isn't already running.

2. Navigate to the slow page:

   Tool: browser_navigate
   Arguments: { "url": "http://localhost:3000/slow-page" }