Select queries in Laravel - Performance & Optimization

Performance: Select queries

HIGH IMPACT

Select queries affect how fast data is fetched from the database and how quickly the page can show content.

Fetching all columns from a large table without filtering

Laravel

$users = DB::table('users')->select('id', 'name', 'email')->get();

Only fetches needed columns, reducing data size and speeding up query.

📈 Performance GainReduces data transfer size and speeds up LCP by loading less data.

Fetching all columns from a large table without filtering

Laravel

$users = DB::table('users')->get();

This fetches all columns and all rows, which can be very large and slow down response time.

📉 Performance CostBlocks rendering until all data is fetched; can add hundreds of KBs to response size.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Select all columns without filter	N/A	N/A	High data transfer delays paint	[X] Bad
Select specific columns	N/A	N/A	Less data speeds paint	[OK] Good
N queries in loop	N/A	N/A	Multiple DB hits delay response	[X] Bad
Eager loading related data	N/A	N/A	Fewer queries speed paint	[OK] Good
Raw queries without caching	N/A	N/A	Repeated slow queries delay paint	[X] Bad
Cached query results	N/A	N/A	Faster repeated loads	[OK] Good

Rendering Pipeline

Select queries impact the server response time, which delays when the browser can start rendering the page content.

→Server Processing

→Network Transfer

→Rendering

⚠️ BottleneckServer Processing (database query execution)

Core Web Vital Affected

LCP

Select queries affect how fast data is fetched from the database and how quickly the page can show content.

Optimization Tips

1Select only the columns you need to reduce data size.

2Avoid running queries inside loops; use eager loading instead.

3Cache query results to speed up repeated requests.

Performance Quiz - 3 Questions

What is a performance benefit of selecting only needed columns in a Laravel query?

A Increases database CPU usage

B Reduces data size sent over network, speeding up page load

C Triggers more reflows in the browser

D Blocks JavaScript execution

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and look at the timing of API or page requests that run select queries.

What to look for: Long server response times or large payload sizes indicate slow or heavy select queries.