Global middleware in Laravel - Performance & Optimization

Performance: Global middleware

MEDIUM IMPACT

Global middleware affects the request handling speed and overall server response time, impacting how fast the page starts loading.

Applying middleware to all requests regardless of need

Laravel

class CheckHeavyMiddleware {
  public function handle($request, Closure $next) {
    // heavy processing
    return $next($request);
  }
}
// Registered only on specific routes or groups
Route::middleware(['checkHeavy'])->group(function () {
  Route::get('/special', function() {
    // ...
  });
});

Middleware runs only on routes that need it, reducing unnecessary processing.

📈 Performance GainSaves 100-300ms on most requests by skipping heavy middleware

Applying middleware to all requests regardless of need

Laravel

class CheckHeavyMiddleware {
  public function handle($request, Closure $next) {
    // heavy processing like complex DB queries or external API calls
    return $next($request);
  }
}
// Registered globally in Kernel.php
protected $middleware = [
  \App\Http\Middleware\CheckHeavyMiddleware::class,
];

Middleware runs on every request, even when not needed, causing unnecessary delays.

📉 Performance CostBlocks server response for extra 100-300ms per request depending on processing

Performance Comparison

Pattern	Middleware Runs	Server Delay	Impact on LCP	Verdict
Global heavy middleware on all routes	Every request	Adds 100-300ms delay	Increases LCP significantly	[X] Bad
Middleware applied only on needed routes	Selective requests	Minimal delay on most requests	Improves LCP by reducing delays	[OK] Good

Rendering Pipeline

Global middleware runs before the controller processes the request, adding to server response time which delays the browser receiving HTML to start rendering.

→Server Request Handling

→Response Generation

⚠️ BottleneckServer Request Handling due to middleware processing

Core Web Vital Affected

LCP

Global middleware affects the request handling speed and overall server response time, impacting how fast the page starts loading.

Optimization Tips

1Avoid heavy processing in global middleware to reduce server response time.

2Apply middleware only to routes that require it to improve load speed.

3Use Laravel route groups to selectively assign middleware and optimize performance.

Performance Quiz - 3 Questions

What is the main performance drawback of using global middleware in Laravel?

A It increases client-side rendering time.

B It runs on every request, adding unnecessary processing time.

C It reduces CSS loading speed.

D It causes layout shifts in the browser.

DevTools: Network and Performance panels

How to check: Open DevTools, go to Network tab, reload page and check server response time; use Performance tab to record and analyze server processing time before first paint.

What to look for: Look for long server response times before HTML starts loading, indicating middleware delays.