API routes in Laravel - Performance & Optimization

Performance: API routes

MEDIUM IMPACT

API routes affect server response time and how quickly the client receives data, impacting perceived page speed and interaction responsiveness.

Defining API routes for handling client requests

Laravel

Route::get('/users', [UserController::class, 'index']);

// In UserController:
public function index() {
    $users = User::select('id', 'name', 'email')->get();
    return response()->json($users);
}

Separates logic into controller, allows query optimization and caching, reducing response time.

📈 Performance Gainreduces server processing time; enables caching and query optimization

Defining API routes for handling client requests

Laravel

Route::get('/users', function() {
    $users = User::all();
    return response()->json($users);
});

Using closure routes with heavy database calls directly in the route can slow down response and increase server load.

📉 Performance Costblocks response until DB query completes; increases server CPU usage

Performance Comparison

Pattern	Server Processing	Database Queries	Response Time	Verdict
Closure route with direct DB call	High CPU usage	Unoptimized full table scan	Slow response	[X] Bad
Controller route with optimized query	Lower CPU usage	Selective fields, possible caching	Faster response	[OK] Good

Rendering Pipeline

API routes are processed on the server before any client rendering. Efficient routing reduces server processing time, speeding up data delivery to the browser.

→Server Request Handling

→Database Query

→Response Generation

⚠️ BottleneckDatabase Query and server-side processing

Core Web Vital Affected

INP

API routes affect server response time and how quickly the client receives data, impacting perceived page speed and interaction responsiveness.

Optimization Tips

1Avoid heavy database queries directly in route closures.

2Use controllers to separate logic and enable query optimization.

3Cache API responses when possible to reduce server load.

Performance Quiz - 3 Questions

What is a performance drawback of defining API routes using closures with heavy database queries in Laravel?

A It automatically caches the response, which can cause stale data.

B It reduces server CPU usage by offloading queries to the client.

C It blocks the server response until the query finishes, increasing response time.

D It speeds up response by running queries asynchronously.

DevTools: Network

How to check: Open DevTools, go to Network tab, filter XHR requests, select API call, and check timing details.

What to look for: Look at 'Waiting (TTFB)' and 'Content Download' times; lower values indicate faster API response.