Hydration behavior in Vue - Performance & Optimization

Performance: Hydration behavior

HIGH IMPACT

Hydration affects how quickly a server-rendered Vue app becomes interactive on the client side.

Making a server-rendered Vue app interactive on the client

Vue

const app = createSSRApp(App);
app.mount('#app'); // lazy hydrate parts or use partial hydration

Hydrating only needed parts or deferring hydration reduces main thread blocking.

📈 Performance Gainreduces blocking time by 50-80%, improves INP significantly

Making a server-rendered Vue app interactive on the client

Vue

const app = createSSRApp(App);
app.mount('#app'); // full hydration of entire app immediately

Hydrating the entire app at once blocks the main thread and delays interactivity.

📉 Performance Costblocks rendering for 100-300ms depending on app size, increases INP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Full hydration of entire app	High (all nodes processed)	Multiple reflows during hydration	High paint cost due to updates	[X] Bad
Partial or lazy hydration	Lower (only interactive parts)	Fewer reflows	Lower paint cost	[OK] Good

Rendering Pipeline

Hydration reuses server-rendered HTML and attaches Vue's reactive behavior. It involves parsing HTML, running JavaScript to bind events, and updating the DOM.

→DOM Parsing

→JavaScript Execution

→Layout

→Paint

⚠️ BottleneckJavaScript Execution during hydration blocks main thread and delays interactivity

Core Web Vital Affected

INP

Hydration affects how quickly a server-rendered Vue app becomes interactive on the client side.

Optimization Tips

1Avoid hydrating the entire app at once to prevent main thread blocking.

2Use partial or lazy hydration to improve input responsiveness.

3Monitor hydration scripts in DevTools Performance panel to find bottlenecks.

Performance Quiz - 3 Questions

What is the main performance issue with full hydration of a Vue SSR app?

A It causes layout shifts after hydration

B It blocks the main thread causing delayed interactivity

C It increases the size of server HTML

D It reduces the number of DOM nodes

DevTools: Performance

How to check: Record a performance profile during page load and look for long tasks caused by hydration scripts.

What to look for: Look for long scripting tasks blocking main thread and delayed Time to Interactive (TTI) markers.

Practice

1. What is the main purpose of hydration in Vue when using server-side rendering?

easy

A. To connect the static HTML from the server with Vue's client-side code for interactivity

B. To generate HTML on the client without any server involvement

C. To replace all server-rendered HTML with new client-rendered HTML

D. To disable JavaScript on the client for faster loading

Solution

1. Step 1: Understand hydration concept

   Hydration links the server-rendered HTML with Vue's client code to make the page interactive without re-rendering everything.

2. Step 2: Compare options

   To connect the static HTML from the server with Vue's client-side code for interactivity correctly describes hydration. Options B, C, and D misunderstand hydration's role.

3. Final Answer:

   To connect the static HTML from the server with Vue's client-side code for interactivity -> Option A

4. Quick Check:

   Hydration = connect server HTML + client code [OK]

Hint: Hydration links server HTML to client Vue code [OK]

Common Mistakes:

• Thinking hydration generates HTML only on client
• Believing hydration replaces server HTML entirely
• Assuming hydration disables JavaScript

2. Which of the following Vue code snippets correctly enables hydration for a server-rendered app?

easy

A. createApp(App).mount('#app')

B. new Vue({ el: '#app' })

C. createSSRApp(App).mount('#app')

D. Vue.hydrate(App, '#app')

Solution

1. Step 1: Identify hydration method in Vue 3 SSR

   Vue 3 uses createSSRApp() to create an app that supports hydration of server-rendered HTML.

2. Step 2: Evaluate options

   createSSRApp(App).mount('#app') uses createSSRApp(). createApp(App).mount('#app') is for client-only apps. new Vue({ el: '#app' }) is Vue 2 syntax. Vue.hydrate(App, '#app') is invalid.

3. Final Answer:

   createSSRApp(App).mount('#app') -> Option C

4. Quick Check:

   SSR hydration uses createSSRApp() [OK]

Hint: Use createSSRApp() for hydration in Vue 3 SSR [OK]

Common Mistakes:

• Using createApp() instead of createSSRApp() for hydration
• Using Vue 2 syntax in Vue 3 projects
• Assuming Vue has a hydrate() method

3. Given this Vue 3 SSR hydration code snippet, what will be the console output?

const app = createSSRApp({
  data() { return { count: 0 } },
  mounted() { console.log('Mounted with count:', this.count) }
})
app.mount('#app')

medium

A. No output because mounted is not called during hydration

B. Mounted with count: 0

C. Error: createSSRApp is not a function

D. Mounted with count: undefined

Solution

1. Step 1: Understand mounted hook during hydration

   During hydration, the mounted hook runs after the client connects to server HTML, so it logs the current data state.

2. Step 2: Check data initialization

   Data count is initialized to 0, so the console logs 'Mounted with count: 0'.

3. Final Answer:

   Mounted with count: 0 -> Option B

4. Quick Check:

   Mounted logs count 0 during hydration [OK]

Hint: Mounted runs after hydration with initialized data [OK]

Common Mistakes:

• Thinking mounted does not run during hydration
• Assuming data is undefined at mount
• Confusing createSSRApp with createApp

4. You notice that after hydration, your Vue app's client-side interactivity is broken and console shows a mismatch warning. What is the most likely cause?

medium

A. The server-rendered HTML does not match the client-side template output

B. You forgot to import Vue in your client entry file

C. You used createApp() instead of createSSRApp() on the server

D. The mounted hook is missing in your component

Solution

1. Step 1: Understand hydration mismatch warning

   Vue warns when server HTML and client render output differ, causing hydration failure.

2. Step 2: Analyze options

   The server-rendered HTML does not match the client-side template output correctly identifies mismatch as cause. You forgot to import Vue in your client entry file causes import errors, not mismatch. You used createApp() instead of createSSRApp() on the server is about server setup, not client mismatch. The mounted hook is missing in your component does not cause hydration mismatch.

3. Final Answer:

   The server-rendered HTML does not match the client-side template output -> Option A

4. Quick Check:

   Mismatch = server HTML ≠ client template [OK]

Hint: Mismatch warning means server and client HTML differ [OK]

Common Mistakes:

• Ignoring mismatch warnings
• Confusing import errors with hydration issues
• Assuming missing mounted hook breaks hydration

5. You have a Vue 3 SSR app that renders a list of items on the server. Some items have a dynamic property that changes on the client only. How should you handle hydration to avoid mismatch errors?

hard

A. Ignore mismatch warnings since they don't affect user experience

B. Render all dynamic properties on the server to keep HTML identical

C. Disable hydration and fully re-render on client with createApp()

D. Use v-if or v-show to conditionally render client-only parts after hydration

Solution

1. Step 1: Identify client-only dynamic content issue

   Dynamic properties that differ between server and client cause hydration mismatches.

2. Step 2: Use conditional rendering for client-only parts

   Using v-if or v-show to render client-only content after hydration avoids mismatch.

3. Step 3: Evaluate other options

   Render all dynamic properties on the server to keep HTML identical is impractical if data is truly client-only. Disable hydration and fully re-render on client with createApp() disables hydration benefits. Ignore mismatch warnings since they don't affect user experience ignores errors.

4. Final Answer:

   Use v-if or v-show to conditionally render client-only parts after hydration -> Option D

5. Quick Check:

   Client-only content = conditional render after hydration [OK]

Hint: Render client-only parts conditionally after hydration [OK]

Common Mistakes:

• Trying to render client-only data on server
• Disabling hydration unnecessarily
• Ignoring mismatch warnings