Course contentsShow
← Web Development
Lesson 1720 of 2,98232. Server-Side Rendering ConceptsFree lesson

SSR Performance Characteristics

Analyzing First Contentful Paint improvements and Time to Interactive considerations with SSR.

SSR Performance Characteristics

You'll learn: How server-side rendering affects the key performance metrics that shape user experience, specifically First Contentful Paint and Time to Interactive.

The Performance Trade-off

SSR shifts the rendering workload from the browser to the server, which fundamentally changes when users see content versus when they can interact with it. Understanding this distinction is crucial for choosing the right rendering strategy.

First Contentful Paint (FCP) Improvements

With SSR, the server sends fully-rendered HTML in the initial response. This means users see meaningful content almost immediately after the page loads—no waiting for JavaScript to download, parse, and execute before seeing anything.

The analogy: It's like receiving a finished painting versus receiving a canvas and paint supplies. With SSR, you immediately see the painting (HTML). With CSR, you must wait to paint it yourself (JavaScript rendering).

This dramatically improves FCP, especially on slow networks or devices, because HTML is typically much smaller than JavaScript bundles and requires no processing to display.

Time to Interactive (TTI) Considerations

Here's the trade-off: while users see content faster, the page isn't fully interactive until JavaScript downloads and "hydrates" the static HTML. During this gap, buttons may look clickable but don't respond yet.

This creates a potential "uncanny valley" where the page appears ready but isn't. On slow connections, this delay can frustrate users who try to interact too early.

SSR works best when you prioritize fast initial content display and can minimize JavaScript bundle size to reduce the hydration gap.

Key Takeaway: SSR improves First Contentful Paint by sending pre-rendered HTML, but introduces a gap before Time to Interactive while JavaScript hydrates—optimize by reducing JS bundle size and clearly indicating loading states during hydration.