SSR vs CSR mental model in Vue - Performance Comparison

Performance: SSR vs CSR mental model

HIGH IMPACT

This concept affects how fast the main content appears and how quickly users can interact with the page.

Rendering initial page content quickly for better user experience

Vue

import { createSSRApp } from 'vue';
const app = createSSRApp(App);
// Server sends fully rendered HTML
app.mount('#app'); // Hydrates on client

Content is visible immediately from server HTML, improving perceived load speed.

📈 Performance GainLCP improves significantly; content appears before JS hydration.

Rendering initial page content quickly for better user experience

Vue

const app = createApp(App);
app.mount('#app'); // Pure CSR: no server HTML

Page shows blank until JavaScript loads and runs, delaying content visibility.

📉 Performance CostBlocks LCP until JS is downloaded and executed, causing slower perceived load.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Pure CSR	Many DOM nodes created after JS runs	Multiple reflows during JS execution	High paint cost due to delayed content	[X] Bad
SSR with Hydration	DOM nodes sent from server, hydrated on client	Single reflow on initial paint	Lower paint cost, faster content visibility	[OK] Good

Rendering Pipeline

SSR sends fully rendered HTML from the server, so the browser can paint content immediately. Then client JS hydrates to add interactivity. CSR sends minimal HTML and relies on JS to build the page, delaying paint until JS runs.

→HTML Parsing

→Style Calculation

→Layout

→Paint

→JavaScript Execution

⚠️ BottleneckJavaScript Execution during hydration or initial render

Core Web Vital Affected

LCP, INP

This concept affects how fast the main content appears and how quickly users can interact with the page.

Optimization Tips

1Use SSR to improve Largest Contentful Paint by sending ready HTML.

2Hydration in SSR can delay Interaction to Next Paint; optimize JS size.

3CSR delays content but can improve interactivity with code splitting.

Performance Quiz - 3 Questions

Which rendering method shows content fastest to the user?

A Server-side rendering (SSR)

B Client-side rendering (CSR)

C Static site generation (SSG)

D None of the above

DevTools: Performance

How to check: Record page load and look for 'First Contentful Paint' and 'Time to Interactive' markers; check JS execution blocking time.

What to look for: Shorter time to first paint indicates good SSR; shorter JS blocking time indicates good hydration or CSR optimization.

Practice

1. What does SSR (Server-Side Rendering) mean in Vue applications?

easy

A. The server builds the full HTML page before sending it to the browser.

B. The browser builds the page after loading JavaScript.

C. The page is built only when the user clicks a button.

D. The server sends only data, and the browser builds the page.

Solution

1. Step 1: Understand SSR concept

   SSR means the server prepares the full HTML content before sending it to the browser.

2. Step 2: Compare with other options

   The options describing browser building the page after loading JavaScript and server sending only data describe CSR behavior, while the button-click option is unrelated to SSR.

3. Final Answer:

   The server builds the full HTML page before sending it to the browser. -> Option A

4. Quick Check:

   SSR = Server builds page first [OK]

Hint: SSR means server sends ready HTML, not just data [OK]

Common Mistakes:

• Confusing SSR with CSR
• Thinking SSR means browser builds page
• Assuming SSR only sends data, not HTML

2. Which Vue code snippet correctly represents a CSR approach?

easy

A. fetch('/api/data').then(res => res.json())

B. export default { ssr: true, setup() { return {} } }

C. const app = Vue.createSSRApp({ template: 'Hello' })

D. const app = Vue.createApp({ data() { return { count: 0 } } }).mount('#app')

Solution

1. Step 1: Identify CSR code pattern

   CSR uses Vue.createApp() to mount app in browser after loading.

2. Step 2: Check other options

   export default { ssr: true, setup() { return {} } } mentions SSR flag, C uses SSR app creation, A is just data fetching.

3. Final Answer:

   const app = Vue.createApp({ data() { return { count: 0 } } }).mount('#app') -> Option D

4. Quick Check:

   CSR uses createApp and mounts in browser [OK]

Hint: CSR uses createApp and mounts in browser [OK]

Common Mistakes:

• Confusing createApp with createSSRApp
• Thinking SSR flag means CSR
• Assuming fetch alone is CSR

3. Given a Vue app using SSR, what will the user see immediately after the server sends the page?

medium

A. The fully rendered HTML page visible instantly.

B. A blank page until JavaScript loads and runs.

C. Only a loading spinner with no content.

D. An error message about missing components.

Solution

1. Step 1: Understand SSR output

   SSR sends fully rendered HTML, so the user sees content immediately.

2. Step 2: Contrast with CSR behavior

   CSR shows blank or spinner until JS runs; SSR avoids this delay.

3. Final Answer:

   The fully rendered HTML page visible instantly. -> Option A

4. Quick Check:

   SSR = instant HTML visible [OK]

Hint: SSR shows full page immediately, no blank screen [OK]

Common Mistakes:

• Thinking SSR waits for JavaScript to load
• Confusing loading spinner with SSR
• Assuming SSR causes errors on load

4. You have a Vue SSR app, but the page stays blank after loading. What is a likely cause?

medium

A. The client-side JavaScript failed to hydrate the server HTML.

B. The server did not send any HTML content.

C. The browser does not support JavaScript.

D. The Vue app was created with createApp instead of createSSRApp.

Solution

1. Step 1: Understand SSR delivery

   In SSR, the server must send fully rendered HTML; a blank page indicates the server rendered no content or sent empty HTML.

2. Step 2: Rule out client-side issues

   Hydration failure leaves static HTML visible; no JS support shows static HTML; using createApp may cause flicker but content appears.

3. Final Answer:

   The server did not send any HTML content. -> Option B

4. Quick Check:

   Blank SSR page = no HTML from server [OK]

Hint: Blank page in SSR means server sent no HTML content [OK]

Common Mistakes:

• Thinking hydration failure causes blank (leaves static HTML)
• Blaming browser JS support (shows static without JS)
• Assuming createApp causes blank (re-renders on client)

5. You want fast initial load and good SEO for a Vue app with dynamic user data. Which approach fits best?

hard

A. Use SSR but disable hydration to speed up loading.

B. Use CSR only, loading data after page loads in browser.

C. Use SSR to render the page on the server, then hydrate on client.

D. Use CSR with server sending only JSON data.

Solution

1. Step 1: Analyze requirements

   Fast initial load and SEO need server-rendered HTML visible to search engines.

2. Step 2: Match approach to needs

   SSR renders HTML on server, improving SEO and load speed; hydration enables interactivity.

3. Step 3: Evaluate other options

   CSR delays content rendering, SSR without hydration loses interactivity, CSR with JSON only delays content.

4. Final Answer:

   Use SSR to render the page on the server, then hydrate on client. -> Option C

5. Quick Check:

   SSR + hydration = fast load + SEO + interactivity [OK]

Hint: SSR with hydration balances speed, SEO, and interactivity [OK]

Common Mistakes:

• Choosing CSR only for SEO needs
• Disabling hydration losing interactivity
• Assuming JSON data alone improves SEO