Eager loading (with) in Laravel - Performance & Optimization

Performance: Eager loading (with)

HIGH IMPACT

Eager loading reduces the number of database queries, improving page load speed and interaction responsiveness.

Loading related data for multiple records

Laravel

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

Loads all authors in a single query before looping, reducing database calls drastically.

📈 Performance GainSingle query for posts and authors, reducing queries from N+1 to 2, improving LCP.

Loading related data for multiple records

Laravel

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

This triggers a separate query for each post to fetch the author, causing the N+1 query problem.

📉 Performance CostTriggers N+1 database queries, blocking rendering until all queries complete.

Performance Comparison

Pattern	Database Queries	Network Requests	Server Response Time	Verdict
Lazy loading (accessing relations inside loop)	N+1 queries	Multiple	High	[X] Bad
Eager loading with 'with' method	2 queries	Few	Low	[OK] Good

Rendering Pipeline

Eager loading reduces database query count, so the server sends data faster to the browser, improving the critical rendering path.

→Data Fetching

→Server Response

→Rendering

⚠️ BottleneckDatabase query execution and network latency

Core Web Vital Affected

LCP

Eager loading reduces the number of database queries, improving page load speed and interaction responsiveness.

Optimization Tips

1Always use eager loading when accessing related data in loops.

2Avoid lazy loading inside loops to prevent multiple database queries.

3Check query count in DevTools Network tab to verify eager loading effectiveness.

Performance Quiz - 3 Questions

What is the main performance benefit of using eager loading in Laravel?

A Reduces the number of database queries

B Increases the number of database queries

C Delays data fetching until needed

D Caches data on the client side

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and count the number of API or page requests related to data fetching.

What to look for: Fewer database-related requests or API calls indicate effective eager loading.

Practice

1. What is the main purpose of using with() in Laravel Eloquent queries?

easy

A. To delete related models automatically

B. To load related models in the same query to reduce database calls

C. To paginate the results of a query

D. To sort the results by a related model's attribute

Solution

1. Step 1: Understand what with() does

   The with() method tells Laravel to load related models eagerly, meaning it fetches them in the same database query or fewer queries.

2. Step 2: Identify the benefit of eager loading

   This reduces the number of database queries, improving performance by avoiding the N+1 query problem.

3. Final Answer:

   To load related models in the same query to reduce database calls -> Option B

4. Quick Check:

   Eager loading = fewer queries = better performance [OK]

Hint: Remember: with() loads related data upfront [OK]

Common Mistakes:

• Thinking with() deletes related data
• Confusing with() with pagination
• Assuming with() sorts results

2. Which of the following is the correct syntax to eager load the 'comments' relationship on a Post model?

easy

A. Post::with('comments')->get();

B. Post::fetch('comments')->all();

C. Post::eager('comments')->all();

D. Post::load('comments')->get();

Solution

1. Step 1: Recall the correct method for eager loading

   Laravel uses the with() method to eager load relationships before fetching results.

2. Step 2: Check the syntax correctness

   Post::with('comments')->get(); correctly calls with() and then get() to retrieve posts with comments.

3. Final Answer:

   Post::with('comments')->get(); -> Option A

4. Quick Check:

   with() + get() = eager load [OK]

Hint: Use with() before get() to eager load [OK]

Common Mistakes:

• Using load() statically instead of on model instance
• Using non-existent methods like eager() or fetch()
• Calling get() before with()

3. Given the code:

 $users = User::with('posts')->get();
foreach ($users as $user) {
  echo $user->posts->count();
}

What will this code output?

medium

A. An error because posts is not loaded

B. The total number of users instead of posts

C. Always zero because posts are not counted

D. The number of posts for each user without extra queries

Solution

1. Step 1: Understand eager loading effect

   The with('posts') loads all posts for each user in one query, so $user->posts is available without extra queries.

2. Step 2: Analyze the loop output

   For each user, $user->posts->count() returns the number of posts related to that user, printed one by one.

3. Final Answer:

   The number of posts for each user without extra queries -> Option D

4. Quick Check:

   with() loads posts, count() shows posts per user [OK]

Hint: with() loads related data, so count() works without errors [OK]

Common Mistakes:

• Assuming posts are not loaded and cause errors
• Thinking count() returns total users
• Confusing eager loading with lazy loading

4. Identify the error in this code snippet:

$orders = Order::with('customer')->get();
foreach ($orders as $order) {
  echo $order->customer->name;
}

Assuming the 'customer' relation is defined correctly, what is the likely problem?

medium

A. Using with() after get() instead of before

B. Missing parentheses on customer relation call

C. Accessing customer without checking if it exists

D. Using get() instead of first()

Solution

1. Step 1: Check eager loading usage

   The with('customer') is correctly used before get(), so related customers are loaded.

2. Step 2: Identify potential null relation access

   Some orders might not have a customer, so $order->customer could be null, causing an error when accessing name without a check.

3. Final Answer:

   Accessing customer without checking if it exists -> Option C

4. Quick Check:

   Null relation access causes error, check before use [OK]

Hint: Always check if related model exists before accessing properties [OK]

Common Mistakes:

• Thinking with() must come after get()
• Assuming relation always exists
• Confusing get() and first() usage

5. You want to eager load the 'comments' and their 'author' for each post efficiently. Which code correctly achieves this?

hard

A. Post::with(['comments.author'])->get();

B. Post::load('comments.author')->get();

C. Post::with(['comments', 'author'])->get();

D. Post::with('comments', 'author')->get();

Solution

1. Step 1: Understand nested eager loading syntax

   To eager load a relation of a relation, use dot notation inside an array: with(['comments.author']).

2. Step 2: Analyze each option

   Post::with('comments', 'author')->get(); loads comments and author separately, but author is not a direct relation of Post. Post::load('comments.author')->get(); uses load() statically, which is invalid as load() is an instance method. Post::with(['comments', 'author'])->get(); loads comments and author separately as array elements, but author is not direct relation. Post::with(['comments.author'])->get(); correctly loads comments and their author nested.

3. Final Answer:

   Post::with(['comments.author'])->get(); -> Option A

4. Quick Check:

   Nested relations use dot notation inside array [OK]

Hint: Use dot notation inside array for nested eager loading [OK]

Common Mistakes:

• Passing multiple relations as separate strings without array
• Using load() statically
• Trying to load unrelated models directly