RouterView for rendering in Vue - Performance & Optimization

Performance: RouterView for rendering

MEDIUM IMPACT

RouterView affects page load speed and rendering by controlling which components are mounted and displayed based on the route, impacting initial render and updates.

Rendering route components in a Vue app

Vue

const routes = [
  { path: '/', component: () => import('./Home.vue') },
  { path: '/about', component: () => import('./About.vue') }
];

// Use <router-view v-slot="{ Component }">
//   <keep-alive>
//     <component :is="Component" />
//   </keep-alive>
// </router-view>

Lazy loads route components and caches them with keep-alive to avoid re-mounting, reducing load and reflows.

📈 Performance Gainsingle reflow on first load, faster navigation with cached components

Rendering route components in a Vue app

Vue

const routes = [
  { path: '/', component: () => import('./Home.vue') },
  { path: '/about', component: () => import('./About.vue') }
];

// In App.vue template
<router-view />

// No caching

Route components re-mount fully on each navigation, causing slower navigation and repeated reflows.

📉 Performance Costblocks rendering for extra 100-200ms on navigation, triggers multiple reflows

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
RouterView without caching	High (remounts the route component on navigation)	Multiple reflows per navigation	High paint cost due to full remount	[X] Bad
RouterView with lazy loading and keep-alive	Low (mounts only needed components, caches them)	Single reflow on first load	Low paint cost on navigation	[OK] Good

Rendering Pipeline

RouterView controls which Vue components are mounted or unmounted based on the current route, affecting the browser's layout and paint stages when components change.

→Layout

→Paint

→Composite

⚠️ BottleneckLayout due to mounting/unmounting components and DOM changes

Core Web Vital Affected

LCP

RouterView affects page load speed and rendering by controlling which components are mounted and displayed based on the route, impacting initial render and updates.

Optimization Tips

1Use lazy loading for route components to improve initial load speed.

2Wrap RouterView components in keep-alive to cache and avoid remounts.

3Avoid mounting unnecessary components to reduce layout thrashing.

Performance Quiz - 3 Questions

What is the main performance benefit of using <keep-alive> with RouterView in Vue?

A It caches route components to avoid remounting on navigation

B It preloads all route components at startup

C It disables routing to speed up rendering

D It reduces CSS selector complexity

DevTools: Performance

How to check: Record a performance profile while navigating routes. Look for long scripting or layout times during route changes.

What to look for: High layout or scripting times indicate heavy remounting; lower times with cached components show better performance.

Practice

1. What is the main purpose of RouterView in a Vue application?

easy

A. To define routes and their components

B. To display the component that matches the current route URL

C. To style the navigation bar

D. To fetch data from an API

Solution

1. Step 1: Understand RouterView role

   RouterView is a placeholder that Vue Router uses to show the component for the current URL.

2. Step 2: Differentiate from other router parts

   Defining routes is done in the router config, not in RouterView. Styling and data fetching are unrelated.

3. Final Answer:

   To display the component that matches the current route URL -> Option B

4. Quick Check:

   RouterView shows current page = A [OK]

Hint: RouterView shows the page for the URL [OK]

Common Mistakes:

• Confusing RouterView with route definitions
• Thinking RouterView styles navigation
• Assuming RouterView fetches data

2. Which of the following is the correct way to use RouterView in a Vue component template?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall Vue Router syntax

   The official tag for rendering matched components is <router-view> in kebab-case.

2. Step 2: Check case sensitivity

   Vue components and tags are case-sensitive. RouterView (PascalCase) is not valid in templates, nor is routerView or router_view.

3. Final Answer:

   <router-view></router-view> -> Option C

4. Quick Check:

   Use kebab-case tag [OK]

Hint: Use lowercase with dash: [OK]

Common Mistakes:

• Using PascalCase <RouterView> in template
• Using camelCase or underscores in tag name
• Forgetting closing tag

3. Given this Vue Router setup and component usage, what will be rendered inside <router-view> when the URL is /about?

const routes = [
  { path: '/', component: Home },
  { path: '/about', component: About }
];

// In App.vue template:
// <router-view></router-view>

medium

A. The About component content

B. The Home component content

C. Nothing, because no component is matched

D. An error because routes are not defined properly

Solution

1. Step 1: Match URL to route

   The URL /about matches the route with path /about which uses the About component.

2. Step 2: Understand RouterView rendering

   <router-view> renders the component for the matched route, so it will show About's content.

3. Final Answer:

   The About component content -> Option A

4. Quick Check:

   URL /about shows About component [OK]

Hint: RouterView shows component for current URL [OK]

Common Mistakes:

• Assuming root component always shows
• Thinking RouterView shows nothing if not root
• Believing routes need special syntax to match

4. What is wrong with this Vue component template using RouterView?

<template>
  <div>
    <RouterView />
  </div>
</template>

medium

A. The RouterView tag should be lowercase as router-view

B. RouterView cannot be self-closing

C. RouterView must be inside a <router> tag

D. RouterView requires a slot to render content

Solution

1. Step 1: Check tag casing rules

   In Vue templates, the router-view component must be written in kebab-case, all lowercase with a dash.

2. Step 2: Validate other options

   Self-closing is allowed in Vue 3. There is no <router> tag, and router-view does not require slots to render matched components.

3. Final Answer:

   The <RouterView> tag should be lowercase as <router-view> -> Option A

4. Quick Check:

   Use lowercase tag [OK]

Hint: Use lowercase , not PascalCase [OK]

Common Mistakes:

• Writing <RouterView> instead of
• Thinking self-closing is invalid
• Expecting a <router> wrapper tag

5. You want to create a nested route in Vue where /dashboard shows a Dashboard component and inside it, /dashboard/settings shows a Settings component. How should you use RouterView to render the nested Settings component inside Dashboard?

hard

A. Place <router-view> only in the main App.vue template

B. Nest <router-view> inside <router-link> in Dashboard

C. Use two <router-view> tags side by side in App.vue

D. Place <router-view> inside the Dashboard component template where Settings should appear

Solution

1. Step 1: Understand nested routes rendering

   Nested routes render their child components inside the parent's RouterView. So Dashboard must have a <router-view> to show Settings.

2. Step 2: Check other options

   Placing RouterView only in App.vue won't render nested children inside Dashboard. Two side-by-side RouterView tags or nesting inside router-link are incorrect usage.

3. Final Answer:

   Place <router-view> inside the Dashboard component template where Settings should appear -> Option D

4. Quick Check:

   Nested routes need RouterView inside parent [OK]

Hint: Put inside parent component for nested routes [OK]

Common Mistakes:

• Not placing RouterView inside parent component
• Trying to render nested routes only in App.vue
• Misusing router-link as container