Performance check
Full-stack performance audit against framework best practices.
Where is it slow and why
Performance problems are sneaky. Everything feels fine during development, then real users on real connections start complaining. A page loads in 200ms on your machine and 4 seconds on someone's phone.
Inside Claude Code, type /performance. It runs a thorough audit across your entire stack. Not just frontend lighthouse scores. It checks your database queries, your API response times, your caching strategy, your bundle sizes, and your rendering approach against the framework's best practice guidelines.
What gets checked
Frontend: Are your server components actually staying on the server? Are client bundles pulling in dependencies they shouldn't? Are you sending data to the browser that should be cached? Are images optimized? Are fonts loaded without layout shift?
Backend: Are database queries using indexes? Are there N+1 patterns hiding in your API procedures? Is your caching strategy actually preventing redundant work? Are background jobs structured to avoid timeout issues?
Architecture: Does the data flow match the framework's patterns? Are there loading waterfalls where parallel fetching should be? Are server and client boundaries in the right places?
What you get
A report organized by severity. Issues that affect real users right now at the top. Optimizations that would help at scale further down. Each finding includes the specific file, what's wrong, why it matters, and how to fix it.
Recent changes get extra attention. If you just added a feature, the audit focuses on what that feature introduced.