Query parameters in Laravel - Performance & Optimization

Performance: Query parameters

MEDIUM IMPACT

Query parameters affect server response time and client-side rendering speed by influencing database queries and URL parsing.

Filtering database results using query parameters in a URL

Laravel

Route::get('/products', function (Request $request) {
    $query = DB::table('products');
    if ($category = $request->query('category')) {
        $query->where('category', $category);
    }
    if ($minPrice = $request->query('min_price')) {
        $query->where('price', '>=', $minPrice);
    }
    if ($maxPrice = $request->query('max_price')) {
        $query->where('price', '<=', $maxPrice);
    }
    $products = $query->get();
    return view('products.index', ['products' => $products]);
});

Builds precise WHERE conditions only when parameters exist, enabling database indexes to optimize queries and reduce server load.

📈 Performance GainReduces server response time by 30-70%; lowers CPU usage and speeds up LCP

Filtering database results using query parameters in a URL

Laravel

Route::get('/products', function (Request $request) {
    $products = DB::table('products')
        ->where('category', $request->query('category'))
        ->orWhere('price', '>', $request->query('min_price'))
        ->orWhere('price', '<', $request->query('max_price'))
        ->get();
    return view('products.index', ['products' => $products]);
});

This code builds a query with multiple OR conditions without validating or indexing, causing slow database queries and longer server response.

📉 Performance CostBlocks rendering for 200-500ms on large datasets; increases server CPU usage

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Unfiltered query parameters causing broad DB queries	N/A	N/A	Blocks rendering due to slow server response	[X] Bad
Filtered and validated query parameters with indexed DB columns	N/A	N/A	Fast server response enables quick paint	[OK] Good

Rendering Pipeline

Query parameters are parsed by the server to build database queries. Efficient parsing and query building reduce server processing time, which speeds up the critical rendering path on the client.

→Server Processing

→Database Query

→Network Transfer

→Client Rendering

⚠️ BottleneckDatabase Query execution time

Core Web Vital Affected

LCP

Query parameters affect server response time and client-side rendering speed by influencing database queries and URL parsing.

Optimization Tips

1Validate and sanitize all query parameters before use.

2Build database queries conditionally based on existing parameters.

3Use database indexes on columns filtered by query parameters.

Performance Quiz - 3 Questions

How do unvalidated query parameters affect Laravel app performance?

A They can cause inefficient database queries and slow server response.

B They improve caching and speed up page load.

C They reduce network payload size.

D They have no impact on performance.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page with query parameters, and inspect the server response time for the request.

What to look for: Look for long server response times indicating slow query processing; shorter times mean better performance.