Storing and retrieving cache in Laravel - Performance & Optimization

Performance: Storing and retrieving cache

MEDIUM IMPACT

This affects page load speed by reducing database queries and computation time through fast data retrieval from cache.

Caching database query results to speed up page load

Laravel

<?php
$data = Cache::remember('users', 3600, fn() => DB::table('users')->get());
// Cache stores result for 60 minutes

Data is retrieved from fast cache store after first query, reducing DB hits and response time.

📈 Performance GainReduces DB queries to 1 per 60 minutes; cuts response time by 50-200ms per request

Caching database query results to speed up page load

Laravel

<?php
$data = DB::table('users')->get();
// No caching, query runs on every request

Query runs on every page load causing slower response and higher database load.

📉 Performance CostBlocks rendering for 50-200ms depending on query complexity; increases server CPU and DB load

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No cache, direct DB query	N/A	N/A	Blocks rendering waiting for server response	[X] Bad
Cache with expiration and proper key	N/A	N/A	Fast server response enables quicker paint	[OK] Good

Rendering Pipeline

When cache is used, the server fetches data from memory or fast storage instead of querying the database, reducing backend processing time and speeding up HTML generation.

→Server Processing

→Network Transfer

→First Paint

⚠️ BottleneckServer Processing (database query time)

Core Web Vital Affected

LCP

This affects page load speed by reducing database queries and computation time through fast data retrieval from cache.

Optimization Tips

1Always cache expensive database queries to reduce server load and speed up response.

2Set appropriate cache expiration to balance freshness and performance.

3Use meaningful cache keys to avoid collisions and stale data.

Performance Quiz - 3 Questions

What is the main performance benefit of using cache in Laravel for database queries?

A Slows down page load due to cache overhead

B Increases database load by storing more data

C Reduces server response time by avoiding repeated database queries

D Has no effect on performance

DevTools: Network

How to check: Open DevTools > Network tab, reload page, check response time of API or page requests; cached responses are faster with smaller payloads.

What to look for: Look for reduced server response time and fewer database query calls in backend logs or API responses.