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.

Practice

1. What is the purpose of query parameters in a Laravel application URL?

easy

A. To define the database schema

B. To style the webpage with CSS

C. To send extra information to control the data returned by the server

D. To store user session data on the server

Solution

1. Step 1: Understand what query parameters do

   Query parameters are parts of the URL that send extra info to the server, usually after a question mark.

2. Step 2: Identify their use in Laravel

   In Laravel, query parameters help control what data the server returns based on the extra info sent.

3. Final Answer:

   To send extra information to control the data returned by the server -> Option C

4. Quick Check:

   Query parameters control returned data = B [OK]

Hint: Query parameters add info after ? in URL to filter data [OK]

Common Mistakes:

• Confusing query parameters with database schema
• Thinking query parameters style the page
• Assuming query parameters store session data

2. Which is the correct Laravel syntax to get a query parameter named page from a request?

easy

A. $request->param('page')

B. $request->input('page')

C. $request->getQuery('page')

D. $request->query('page')

Solution

1. Step 1: Recall Laravel method for query parameters

   Laravel uses $request->query('key') to get query parameters from the URL.

2. Step 2: Match the correct syntax

   Among options, only $request->query('page') correctly accesses the query parameter named 'page'.

3. Final Answer:

   $request->query('page') -> Option D

4. Quick Check:

   Use $request->query('key') for query params = A [OK]

Hint: Use $request->query('key') to get query params in Laravel [OK]

Common Mistakes:

• Using $request->input() which also works but includes POST data
• Using non-existent methods like getQuery or param
• Confusing query() with input() for query parameters

3. Given this Laravel route code:

Route::get('/search', function (Request $request) {
    $term = $request->query('term', 'default');
    return $term;
});

What will be the output if the URL is /search?term=laravel?

medium

A. laravel

B. default

C. null

D. term

Solution

1. Step 1: Understand query parameter retrieval with default

   The code uses $request->query('term', 'default'), which returns the 'term' parameter if present, else 'default'.

2. Step 2: Check the URL query parameter

   The URL has ?term=laravel, so 'term' is 'laravel', not missing.

3. Final Answer:

   laravel -> Option A

4. Quick Check:

   Query param 'term' present = 'laravel' [OK]

Hint: If query param exists, default is ignored [OK]

Common Mistakes:

• Assuming default value is always returned
• Confusing parameter name with its value
• Expecting null when parameter is present

4. Identify the error in this Laravel code snippet that tries to get a query parameter sort:

Route::get('/items', function (Request $request) {
    $sort = $request->query['sort'];
    return $sort;
});

medium

A. Request class not imported

B. Using array syntax instead of method call for query parameters

C. Incorrect route method; should be post() instead of get()

D. Missing semicolon after return statement

Solution

1. Step 1: Check how query parameters are accessed

   The code uses $request->query['sort'], which is incorrect because query is a method, not an array.

2. Step 2: Correct syntax for query parameters

   The correct way is $request->query('sort') to get the 'sort' parameter.

3. Final Answer:

   Using array syntax instead of method call for query parameters -> Option B

4. Quick Check:

   Use $request->query('key'), not $request->query['key'] [OK]

Hint: query() is a method, not an array; use parentheses [OK]

Common Mistakes:

• Using square brackets instead of parentheses
• Confusing get() with query() method
• Assuming query is a property, not a method

5. You want to get a query parameter filter in Laravel but provide a default value of all if it is missing or empty. Which code correctly handles this?

hard

A. $filter = $request->query('filter') ?: 'all';

B. $filter = $request->input('filter', 'all');

C. $filter = $request->query('filter', 'all');

D. $filter = $request->query('filter') ?? 'all';

Solution

1. Step 1: Understand default value behavior in query()

   The second argument in query('filter', 'all') returns 'all' only if the parameter is missing, but not if empty.

2. Step 2: Handle empty values as well

   Using $request->query('filter') ?: 'all' returns 'all' if the parameter is missing or empty (falsy).

3. Step 3: Check other options

   $filter = $request->input('filter', 'all'); uses input() which includes POST data, not just query. $filter = $request->query('filter') ?? 'all'; uses null coalescing which does not treat empty string as missing.

4. Final Answer:

   $filter = $request->query('filter') ?: 'all'; -> Option A

5. Quick Check:

   Use ?: to handle missing or empty query params = C [OK]

Hint: Use ?: to cover missing or empty query parameters [OK]

Common Mistakes:

• Assuming default in query() covers empty strings
• Using input() which mixes POST and query data
• Using ?? which ignores empty strings