Published on Jun 20, 2026 by Dev Patel
A practical Laravel performance audit checklist covering Eloquent N+1 queries, indexes, caching, Redis queues, scheduled jobs, logs, and deployment settings.
Author
Performance and production rescue consultant
Laravel performance problems usually show up as slow dashboards, timeout errors, delayed queues, heavy MySQL load, or admin pages that become painful as data grows. A good performance audit does not start with random caching. It starts with measurement.
First, identify the slow routes and jobs. Check request duration, database query count, memory usage, queue wait time, failed jobs, scheduled tasks, and external API calls. Many Laravel apps are slow because one page loads too many relationships or runs the same query repeatedly. Eloquent is powerful, but N+1 queries can quietly turn one dashboard into hundreds of database calls.
Second, inspect database indexes. Search filters, foreign keys, status columns, date ranges, and reporting queries often need thoughtful indexing. A marketplace app may query approved gigs, published demos, developer profiles, payment status, hire requests, and blog posts frequently. Without indexes, these pages slow down as records increase.
Third, use caching carefully. Cache stable data such as navigation counts, public landing-page collections, expensive reports, and repeated lookups. Avoid caching private user data without a clear invalidation plan. Redis can help, but bad cache keys and stale records create new problems.
Fourth, review queues and scheduled jobs. Long-running tasks should not block HTTP requests. Email, AI calls, PDF generation, imports, exports, notifications, and heavy reports belong in queued jobs with retries, timeouts, and failure logging. Queue workers should be monitored and restarted safely during deployment.
Finally, check production settings. Debug mode must be disabled. Logs should be rotated. PHP OPcache should be enabled. Environment variables should be correct. Backups and rollback plans should exist before risky changes.
A Laravel performance audit should end with a prioritized fix list: quick wins, database changes, code changes, infrastructure changes, and monitoring improvements. That makes the work useful for both developers and business owners.