One-to-one (hasOne, belongsTo) in Laravel - Performance & Optimization

Performance: One-to-one (hasOne, belongsTo)

MEDIUM IMPACT

This affects database query performance and page load speed by controlling how related data is fetched and rendered.

Fetching related model data in a one-to-one relationship

Laravel

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

Eager loading fetches all profiles in one query, reducing database calls.

📈 Performance Gainsingle additional query instead of N+1, faster data retrieval and rendering

Fetching related model data in a one-to-one relationship

Laravel

foreach ($users as $user) {
    echo $user->profile->bio;
}

This triggers a separate database query for each user's profile, causing N+1 query problem.

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

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Lazy loading one-to-one relation	Minimal DOM nodes	Multiple reflows due to delayed data	Higher paint cost due to slower data	[X] Bad
Eager loading one-to-one relation	Minimal DOM nodes	Single reflow after data ready	Lower paint cost with faster data	[OK] Good

Rendering Pipeline

The one-to-one relation affects the data fetching stage before rendering. Inefficient queries delay data availability, blocking layout and paint.

→Data Fetching

→Layout

→Paint

⚠️ BottleneckData Fetching due to multiple database queries

Core Web Vital Affected

LCP

This affects database query performance and page load speed by controlling how related data is fetched and rendered.

Optimization Tips

1Always use eager loading (with) for one-to-one relations to avoid N+1 queries.

2Batch fetch related models to reduce database round trips and speed up page load.

3Monitor database queries in DevTools Network tab to detect inefficient patterns.

Performance Quiz - 3 Questions

What is the main performance problem when accessing a one-to-one relation without eager loading?

A Multiple database queries causing delays

B Too many DOM nodes created

C CSS selector complexity increases

D JavaScript bundle size grows

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, filter by XHR to see database API calls, count number of queries.

What to look for: Multiple repeated API calls for related data indicate N+1 problem; a single batched call indicates good eager loading.