Per-view caching in Django - Performance & Optimization

Performance: Per-view caching

HIGH IMPACT

Per-view caching improves page load speed by storing the full response of a view, reducing server processing time on repeated requests.

Speeding up repeated page loads by caching full view responses

Django

@cache_page(60 * 15)
def my_view(request):
    data = expensive_database_query()
    return render(request, 'template.html', {'data': data})

Caches the entire response for 15 minutes, so repeated requests skip query and rendering.

📈 Performance GainReduces server processing to near zero for cached requests, improving LCP significantly

Speeding up repeated page loads by caching full view responses

Django

def my_view(request):
    data = expensive_database_query()
    return render(request, 'template.html', {'data': data})

Every request runs the expensive query and template rendering, causing slow response times.

📉 Performance CostBlocks rendering for 200-500ms per request depending on query complexity

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No caching	N/A (server-side)	N/A	High (slow response delays paint)	[X] Bad
Per-view caching	N/A (server-side)	N/A	Low (fast response enables quick paint)	[OK] Good

Rendering Pipeline

Per-view caching bypasses the server-side processing stage by serving stored HTML directly, reducing time before the browser receives content.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing (database queries and template rendering)

Core Web Vital Affected

LCP

Per-view caching improves page load speed by storing the full response of a view, reducing server processing time on repeated requests.

Optimization Tips

1Cache full view responses to reduce server processing time.

2Set appropriate cache expiration to balance freshness and speed.

3Use per-view caching to improve Largest Contentful Paint (LCP).

Performance Quiz - 3 Questions

What is the main performance benefit of using per-view caching in Django?

A It decreases the size of HTML sent to the browser.

B It reduces server processing time by serving cached full responses.

C It improves CSS rendering speed on the client.

D It automatically optimizes database queries.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page twice. Check if the second request has a faster response time and possibly a 304 status with cache headers.

What to look for: Look for reduced response time and presence of cache headers indicating cached content delivery.