Web Performance Optimization & Lighthouse · Lesson

Server-Side Rendering (SSR) Impact

Evaluate the performance trade-offs of Server-Side Rendering (SSR) versus Client-Side Rendering (CSR) and their impact on TTI.

Server-Side Rendering (SSR) Impact is a free Web Performance Optimization & Lighthouse lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Web Performance Optimization & Lighthouse learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

SSR vs. CSR: The Core Idea

Welcome to understanding how web pages get built! Today, we'll explore two fundamental ways web content reaches your browser: Client-Side Rendering (CSR) and Server-Side Rendering (SSR).

Both have unique impacts on performance, especially how quickly a user can see and interact with your page.

How Client-Side Rendering Works

With CSR, your browser receives a minimal HTML file, often just a blank page with a link to a JavaScript bundle. It's like an empty canvas.

Browser downloads HTML: Very small, quickly.
Browser downloads JavaScript: This is the main part, often large.
JavaScript fetches data & builds UI: After loading, JS executes, calls APIs, and dynamically injects content into the page.

The user sees content only after these steps complete.

CSR Performance & Initial Load

CSR can feel slow initially. The user might see a blank screen or a loading spinner for a noticeable period. This impacts metrics like First Contentful Paint (FCP) and Largest Contentful Paint (LCP).

However, once loaded, subsequent navigation within the app can be very fast, as only data (not full pages) needs to be fetched.

Try this simple CSR example:

<!DOCTYPE html>
<html>
<head>
  <title>CSR Demo</title>
  <style>
    body { font-family: sans-serif; text-align: center; }
    #app { border: 1px solid #ccc; padding: 20px; margin: 20px auto; max-width: 300px; min-height: 50px; }
  </style>
</head>
<body>
  <div id="app"><p>Loading content...</p></div>
  <script>
    document.addEventListener('DOMContentLoaded', () => {
      setTimeout(() => {
        document.getElementById('app').innerHTML = '<h2>Welcome!</h2><p>Content rendered by JS.</p><button>Click Me</button>';
      }, 1000); // Simulate network/processing delay
    });
  </script>
</body>
</html>

How Server-Side Rendering Works

With SSR, the server does the heavy lifting. When a user requests a page, the server processes the request, fetches any necessary data, and constructs the full HTML response.

Browser requests page: Sends request to server.
Server builds HTML: Fetches data, renders the complete page on the server.
Browser receives full HTML: Gets a ready-to-display page.

The user sees content almost immediately as the HTML arrives.

SSR Performance & Initial Load

SSR generally leads to much faster First Contentful Paint (FCP) and Largest Contentful Paint (LCP). Users see meaningful content very quickly, improving perceived performance and SEO.

However, the server must generate the HTML for every request, which can add latency on the server side if not optimized. Let's see an SSR-like output:

<!DOCTYPE html>
<html>
<head>
  <title>SSR Demo</title>
  <style>
    body { font-family: sans-serif; text-align: center; }
    .content { border: 1px solid #ccc; padding: 20px; margin: 20px auto; max-width: 300px; }
  </style>
</head>
<body>
  <div class="content">
    <h2>Welcome!</h2>
    <p>Content rendered directly by the server.</p>
    <button onclick="alert('Hello from SSR!')">Click Me</button>
  </div>
</body>
</html>

Understanding Time To Interactive (TTI)

Time To Interactive (TTI) measures how long it takes for a page to become fully interactive. This means:

The page has displayed useful content (FCP/LCP).
Event handlers are registered for most visible UI elements.
The page responds to user interactions within 50 milliseconds.

TTI is critical because a user can see content but still be unable to click buttons or type into fields if the page isn't interactive.

SSR's TTI Challenge: Hydration

While SSR delivers content quickly, it often sends static HTML. To make this HTML dynamic and interactive, the client-side JavaScript still needs to load and 'take over' the DOM. This process is called hydration.

During hydration, JavaScript attaches event listeners and builds the virtual DOM. If this JS bundle is large, or takes a long time to execute, it can delay TTI even after the content is visible.

Comparing TTI: SSR vs. CSR

The TTI impact differs:

CSR: TTI often aligns closely with FCP/LCP, as all content and interactivity are loaded together. If the JS bundle is small, TTI can be fast.
SSR: FCP/LCP are fast, but TTI can be delayed if hydration is slow. Users might see content but experience a frustrating 'dead zone' where nothing responds.

The goal is to minimize this gap between visible content and interactive content.

Choosing the Right Approach

Deciding between SSR and CSR depends on your project's needs:

SSR is great for: Content-heavy sites (blogs, e-commerce), good SEO, fast initial load for users on slow connections.
CSR is great for: Highly interactive web applications (dashboards, social media feeds), where initial load time is less critical than rich user experience post-load.

Hybrid approaches like Static Site Generation (SSG) or Progressive Hydration also exist to combine benefits.

Quick Check: Rendering Strategies

Based on what we've learned, which statements correctly describe the performance trade-offs between Server-Side Rendering (SSR) and Client-Side Rendering (CSR)?

Recap: SSR, CSR & TTI

In this lesson, we explored Server-Side Rendering (SSR) and Client-Side Rendering (CSR). You learned:

CSR defers rendering to the browser, potentially slowing initial content display but offering dynamic experiences.
SSR renders HTML on the server, providing fast initial content (FCP/LCP) but can delay interactivity (TTI) due to hydration.
Time To Interactive (TTI) is crucial, measuring when a page is fully usable.

Choosing between them involves balancing initial load speed, interactivity needs, and the impact of hydration on TTI.

Frequently asked questions

Is the “Server-Side Rendering (SSR) Impact” lesson free?

Yes — the full text of “Server-Side Rendering (SSR) Impact” is free to read here on the web, and the Web Performance Optimization & Lighthouse course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Web Performance Optimization & Lighthouse course, upgrade to CoddyKit PRO.

What will I learn in “Server-Side Rendering (SSR) Impact”?

Evaluate the performance trade-offs of Server-Side Rendering (SSR) versus Client-Side Rendering (CSR) and their impact on TTI. You practise Web Performance Optimization & Lighthouse with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Web Performance Optimization & Lighthouse?

No prior experience is required. Web Performance Optimization & Lighthouse on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Server-Side Rendering (SSR) Impact” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Web Performance Optimization & Lighthouse lesson?

Yes. Every Web Performance Optimization & Lighthouse lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Web Performance Optimization & Lighthouse