Performance Audit

When to use

• The user wants a ranked report of caching and indexing opportunities — uncached hot paths, missing indexes, opcache disabled — prioritised by ROI so the cheapest big wins come first.
• The user needs to locate N+1 query patterns, unbounded loops issuing queries, or slow hot paths in a PHP or ORM codebase and quantify their cost per request.
• The user asks to performance-audit or profile an existing PHP codebase for N+1 queries, missing database indexes, disabled opcache, or uncached hot paths, wanting ranked findings.

When NOT to use