Course contentsShow
← React
Lesson 1557 of 2,39638. Server Components FundamentalsFree lesson

Server-Side Rendering Isn't Enough

Why SSR still ships all component code to the client for hydration, resulting in duplicate work and large bundles.

Server-Side Rendering Isn't Enough

You'll learn why traditional SSR only solves half the performance problem by sending HTML fast, but still shipping all your React code to the browser.

The SSR Illusion of Speed

Server-Side Rendering feels like a complete solution: your server generates HTML and sends it immediately, so users see content fast. No blank white screen!

But here's the catch: SSR still requires sending your entire component tree's JavaScript to the browser for hydration.

The Duplicate Work Problem

Think of SSR like receiving a completed jigsaw puzzle (the HTML) but also receiving all the individual pieces (the JavaScript) with instructions to rebuild it from scratch. That's hydration.

When React hydrates:

  1. The browser downloads all component code
  2. React re-runs every component's logic
  3. React attaches event handlers to the existing HTML
  4. Only then can users interact with the page

You're doing the same work twice: once on the server (to generate HTML) and once on the client (to make it interactive).

The Bundle Size Reality

Every component you render on the server? Its code still ships to the client. That formatDate utility, the markdown parser, the data transformation logic—all of it becomes part of your JavaScript bundle, even if it only ever ran once on the server.

Traditional SSR gives you fast initial paint but not fast interactivity. Users see content quickly but must wait for a large bundle to download, parse, and execute before anything becomes clickable.

Key Takeaway: SSR improves perceived performance by showing HTML quickly, but hydration still requires shipping and re-executing all your component code on the client, resulting in large bundles and duplicate rendering work.