Query optimization in Laravel - Performance & Optimization

Performance: Query optimization

HIGH IMPACT

This affects how fast the database queries run and how quickly the page can show data to users.

Fetching related data for display

Laravel

$posts = Post::with('user')->get();
foreach ($posts as $post) {
    echo $post->user->name;
}

Loads all users in one query with posts, reducing database calls drastically.

📈 Performance Gainsingle query with eager loading, reducing queries from N+1 to 1

Fetching related data for display

Laravel

foreach ($posts as $post) {
    echo $post->user->name;
}

This runs one query for posts and one query per post to get the user, causing many database calls.

📉 Performance Costtriggers N+1 queries, causing slow page load and high database load

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
N+1 Query Pattern	Low	0	Low	[X] Bad
Eager Loading with with()	Low	0	Low	[OK] Good

Rendering Pipeline

Query optimization reduces the time waiting for data from the database before rendering can start.

→Data Fetching

→Rendering Preparation

⚠️ BottleneckDatabase query execution time

Core Web Vital Affected

LCP

This affects how fast the database queries run and how quickly the page can show data to users.

Optimization Tips

1Avoid N+1 queries by eager loading related data with with().

2Select only needed columns to reduce data size and query time.

3Use database indexes on columns used in where and join clauses.

Performance Quiz - 3 Questions

What is the main problem with the N+1 query pattern in Laravel?

A It causes many database queries, slowing down page load.

B It uses too much memory in PHP.

C It blocks JavaScript execution.

D It increases CSS rendering time.

DevTools: Laravel Debugbar or Telescope

How to check: Enable Debugbar, load the page, and check the Queries tab for number and time of queries.

What to look for: Look for many repeated queries (N+1) or long query times indicating slow database calls.