Keep-alive for expensive components in Vue - Performance & Optimization

Performance: Keep-alive for expensive components

MEDIUM IMPACT

This affects the rendering speed and responsiveness by caching component state and DOM to avoid re-creation on each render.

Rendering a component with heavy setup multiple times

Vue

<template>
  <keep-alive>
    <ExpensiveComponent v-if="show" />
  </keep-alive>
</template>
<script setup>
import ExpensiveComponent from './ExpensiveComponent.vue'
import { ref } from 'vue'
const show = ref(true)
</script>

Component is cached in memory; toggling only shows/hides without re-creating, saving setup time.

📈 Performance GainAvoids repeated setup and DOM rebuild, reducing blocking time to near zero on toggle.

Rendering a component with heavy setup multiple times

Vue

<template>
  <ExpensiveComponent v-if="show" />
</template>
<script setup>
import ExpensiveComponent from './ExpensiveComponent.vue'
import { ref } from 'vue'
const show = ref(true)
</script>

Component is destroyed and recreated on each toggle, causing repeated expensive setup and DOM construction.

📉 Performance CostTriggers full re-render and setup on each toggle, blocking interaction for 100+ ms depending on complexity.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Without keep-alive	Creates and destroys DOM nodes each toggle	Triggers full reflow on each toggle	High paint cost due to DOM rebuild	[X] Bad
With keep-alive	Reuses cached DOM nodes, minimal DOM ops	No reflow from component recreation	Low paint cost, only visibility changes	[OK] Good

Rendering Pipeline

When using keep-alive, Vue caches the component instance and its DOM nodes after first render. On subsequent toggles, Vue skips the full creation and layout steps, reusing cached DOM.

→Component Initialization

→Layout

→Paint

⚠️ BottleneckComponent Initialization and Layout during re-creation

Core Web Vital Affected

INP

This affects the rendering speed and responsiveness by caching component state and DOM to avoid re-creation on each render.

Optimization Tips

1Use keep-alive to cache expensive components that toggle frequently.

2Avoid unnecessary component destruction to reduce layout and paint costs.

3Check performance profiles to confirm reduced scripting and layout times.

Performance Quiz - 3 Questions

What is the main performance benefit of using keep-alive for expensive Vue components?

A It reduces the initial bundle size by code splitting.

B It lazy loads the component only when needed.

C It caches the component instance to avoid re-creation on toggling.

D It automatically optimizes CSS for the component.

DevTools: Performance

How to check: Record a performance profile while toggling the component visibility. Look for scripting and rendering time spikes.

What to look for: Without keep-alive, expect long scripting and layout times on each toggle. With keep-alive, these times should be minimal.

Practice

1. What is the main purpose of using <keep-alive> in Vue?

easy

A. To cache components and preserve their state when toggled

B. To permanently remove components from the DOM

C. To force components to reload every time they are shown

D. To style components with CSS animations

Solution

1. Step 1: Understand what <keep-alive> does

   <keep-alive> caches components so they don't reload when toggled.

2. Step 2: Compare options to this behavior

   Only 'To cache components and preserve their state when toggled' describes caching and preserving state, which is the main purpose.

3. Final Answer:

   To cache components and preserve their state when toggled -> Option A

4. Quick Check:

   Keep-alive caches components [OK]

Hint: Remember: keep-alive means keep component state alive [OK]

Common Mistakes:

• Thinking keep-alive removes components
• Confusing keep-alive with styling or animations
• Assuming keep-alive forces reloads

2. Which of the following is the correct syntax to wrap a dynamic component with keep-alive in Vue 3?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall Vue 3 syntax for keep-alive

   The <keep-alive> tag wraps the dynamic <component> with :is binding.

2. Step 2: Check each option's correctness

   <keep-alive><component :is="currentView" /></keep-alive> correctly wraps <component :is="currentView" /> inside <keep-alive>. Others misuse attributes or tags.

3. Final Answer:

   <keep-alive><component :is="currentView" /></keep-alive> -> Option A

4. Quick Check:

   Wrap dynamic component inside keep-alive tags [OK]

Hint: Wrap inside tags [OK]

Common Mistakes:

• Using keep-alive as a self-closing tag with :is
• Adding keep-alive as a prop on component
• Nesting currentView as a tag inside component

3. Given this Vue template:

<keep-alive include="CompA,CompB">
  <component :is="currentComp" />
</keep-alive>

If currentComp changes from 'CompA' to 'CompC' and back to 'CompA', what happens to the state of 'CompA'?

medium

A. State is preserved only if 'CompC' is also included

B. State is lost because 'CompA' is not included in keep-alive

C. State is preserved because 'CompA' is included in keep-alive

D. State is always reset on component switch

Solution

1. Step 1: Understand include prop effect

   The include attribute caches only components named 'CompA' and 'CompB'.

2. Step 2: Analyze component switching

   Switching to 'CompC' unloads it (not cached). Returning to 'CompA' restores cached state.

3. Final Answer:

   State is preserved because 'CompA' is included in keep-alive -> Option C

4. Quick Check:

   Include caches listed components [OK]

Hint: Only included components keep state cached [OK]

Common Mistakes:

• Assuming all components are cached regardless of include
• Thinking state resets on every switch
• Confusing include with exclude

4. Consider this Vue code snippet:

<keep-alive exclude="CompB">
  <component :is="currentComp" />
</keep-alive>

When switching from 'CompA' to 'CompB', the state of 'CompA' is lost. Why?

medium

A. Because 'CompB' is excluded, switching to it destroys cached components including 'CompA'

B. Because 'CompB' is excluded, only 'CompB' is not cached; 'CompA' should keep state

C. Because 'CompB' is excluded, keep-alive disables caching for all components

D. Because exclude disables keep-alive entirely

Solution

1. Step 1: Understand exclude behavior

   The exclude attribute prevents caching only for 'CompB'. Other components like 'CompA' remain cached.

2. Step 2: Analyze why 'CompA' state is lost

   If 'CompA' state is lost, likely the component is unmounted or recreated outside keep-alive scope, not due to exclude.

3. Final Answer:

   Because 'CompB' is excluded, only 'CompB' is not cached; 'CompA' should keep state -> Option B

4. Quick Check:

   Exclude only skips caching excluded components [OK]

Hint: Exclude skips caching only for listed components [OK]

Common Mistakes:

• Thinking exclude disables caching for all components
• Assuming exclude destroys other cached components
• Confusing exclude with disabling keep-alive

5. You have two expensive components, CompX and CompY. You want to cache CompX but not CompY. Which is the best way to use <keep-alive> to achieve this?

hard

A.

B.

C.

D.

Solution

1. Step 1: Identify caching goal

   You want to cache only CompX, not CompY.

2. Step 2: Use include to cache specific components

   Setting include="CompX" caches only CompX. CompY won't be cached.

3. Step 3: Check other options

   Exclude CompX caches everything except CompX (wrong). Include CompY caches only CompY (wrong). No filters caches all (wrong).

4. Final Answer:

   <keep-alive include="CompX"><component :is="currentComp" /></keep-alive> -> Option D

5. Quick Check:

   Include caches only listed components [OK]

Hint: Use include to cache only desired components [OK]

Common Mistakes:

• Using exclude to cache only one component
• Including the wrong component name
• Not using include or exclude and caching all