Initial Load Time Comparison
You'll learn how to measure and compare the actual speed of different rendering strategies using key performance metrics.
Now that you understand CSR, SSR, and SSG conceptually, it's time to compare their real-world speed using three critical metrics: Time to First Byte (TTFB), First Contentful Paint (FCP), and Largest Contentful Paint (LCP).
The Three Key Metrics
Time to First Byte (TTFB) measures how long until the browser receives the first byte of the HTML response. SSG typically wins here (static files served instantly), followed by SSR (server must render), then CSR (minimal HTML arrives fast, but that's misleading—see below).
First Contentful Paint (FCP) tracks when the user sees any content. SSR and SSG shine because meaningful HTML arrives immediately. CSR shows a blank screen longer while JavaScript downloads and executes.
Largest Contentful Paint (LCP) measures when the main content becomes visible. This is what users actually care about. SSG usually leads, SSR follows closely, and CSR lags because it must download JS, parse it, fetch data, then render.
The Comparison
Think of it like ordering food:
- SSG: Pre-packaged meal ready instantly (best TTFB, FCP, LCP)
- SSR: Chef cooks your order fresh (good TTFB, excellent FCP/LCP)
- CSR: You receive a recipe card first, then must cook yourself (misleading TTFB, poor FCP/LCP)
CSR's TTFB might look competitive, but that empty HTML shell doesn't help users. The perceived load time—what matters for user experience—is typically slowest with CSR, especially on slower networks or devices.
Key Takeaway: SSG delivers the fastest initial load across all metrics for static content, SSR balances dynamic needs with good performance, and CSR trades slower initial loads for rich interactivity afterward.