Skip to content
RT Softs

Laravel performance checklist: the twelve items that actually matter

Work through these in order. The first four usually explain a slow page; the rest keep it fast once traffic arrives.

A Admin
September 8, 2026 3 min read Updated Nov 19, 2026

Performance work is mostly measurement followed by removing something obvious. This is the order we audit a Laravel app in, cheapest and highest-impact first.

Start with the request, not the server

Time a page with the profiler before touching configuration. If the database accounts for 900 ms of a 1 s response, no amount of OPcache tuning will help. Measure, fix the dominant cost, measure again.

  • 1. Kill N+1 queries with eager loading
  • 2. Add indexes for the WHERE and ORDER BY columns you actually use
  • 3. Cache expensive read-only fragments, not whole pages, first
  • 4. Move anything longer than a second into a queue

Then reduce what the server has to do

Cache configuration and routes in production (php artisan optimize), enable OPcache with a sensible memory allocation, use PHP-FPM with enough workers, and put the database on the same network rather than across the internet. Those changes are free and measurable.

Then reduce what the browser has to do

Serve images in the size displayed, use a CDN for static assets, enable compression, and drop unused JavaScript. A Laravel app can have an excellent TTFB and still fail Core Web Vitals because it ships a 2 MB hero image.

Then add capacity

Only after the above: Redis for sessions and cache, a read replica for reporting queries, horizontal scaling behind a load balancer with shared sessions. Reaching for these first is how teams end up with a bigger bill and the same latency.

What we usually find

On a typical inherited project: 40–80 queries per listing page, no indexes on foreign keys, images served at full resolution, and config cached but routes not. Those four fixes often take a 1.5 s page to 300 ms without touching architecture.

Site slow and getting slower?
We audit Laravel apps against this checklist and hand over a prioritised list. Read more.

Frequently asked questions

Is Octane worth it?

After everything above, yes for steady high traffic. It keeps the framework booted between requests, which saves a few milliseconds each time. It also changes assumptions about static state, so test carefully.

How do I know the page is fast enough?

Aim for under 200 ms server time for typical pages and a largest contentful paint under 2.5 s on 4G. Field data from real users beats lab scores.

Do I need a CDN?

For any site with visitors outside your server region, yes. Cloudflare's free plan covers the basics and takes minutes to enable.

More on this topic: Performance & SEO articles.

A

Admin

Related articles