Pages and file-based routing in Vue - Performance & Optimization

Performance: Pages and file-based routing

MEDIUM IMPACT

This affects the initial page load speed and navigation responsiveness by controlling how routes are resolved and components are loaded.

Defining routes for pages in a Vue app

Vue

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

Components are lazy-loaded on demand, reducing initial bundle size and speeding up first paint.

📈 Performance GainSaves 100-200ms on initial load; improves LCP and INP by loading only needed code.

Defining routes for pages in a Vue app

Vue

import Home from './pages/Home.vue';
import About from './pages/About.vue';

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

All page components are imported upfront, increasing initial bundle size and delaying first content paint.

📉 Performance CostBlocks rendering for extra 100-200ms depending on component size; increases LCP time.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Eager import of all pages	Low (few nodes initially)	1 reflow on load	High paint cost due to large bundle	[X] Bad
Lazy load pages with file-based routing	Low (few nodes initially)	1 reflow on load	Lower paint cost due to smaller bundle	[OK] Good

Rendering Pipeline

File-based routing maps URLs to components automatically. When routes are lazy-loaded, the browser fetches component code only when needed, reducing initial parsing and rendering work.

→Network

→Parse & Compile

→Style Calculation

→Layout

→Paint

⚠️ BottleneckNetwork and Parse & Compile stages due to large upfront bundles

Core Web Vital Affected

LCP, INP

This affects the initial page load speed and navigation responsiveness by controlling how routes are resolved and components are loaded.

Optimization Tips

1Always lazy load page components in file-based routing to reduce initial bundle size.

2Avoid importing all pages eagerly to prevent blocking the main thread during load.

3Use DevTools Performance panel to measure impact on LCP and interaction responsiveness.

Performance Quiz - 3 Questions

What is the main performance benefit of lazy loading pages in file-based routing?

A Reduces initial bundle size and speeds up first content paint

B Increases the number of DOM nodes on load

C Triggers more reflows during navigation

D Blocks rendering until all pages are loaded

DevTools: Performance

How to check: Record a page load and navigation; look for long scripting or parsing tasks and large bundle sizes in the summary.

What to look for: Look for shorter scripting times and smaller JS download sizes indicating lazy loading is working.

Practice

1. In Vue file-based routing, what does a file named about.vue inside the pages folder represent?

easy

A. A route accessible at /about

B. A nested route under /pages

C. A dynamic route capturing a parameter

D. A global component, not a route

Solution

1. Step 1: Understand file-based routing basics

   Files inside the pages folder automatically become routes matching their file names.

2. Step 2: Map file name to route path

   The file about.vue creates a route at /about directly.

3. Final Answer:

   A route accessible at /about -> Option A

4. Quick Check:

   File name = route path [OK]

Hint: File name equals route path without extension [OK]

Common Mistakes:

• Thinking files create nested routes automatically
• Confusing dynamic routes with static file names
• Assuming files are just components, not routes

2. Which of the following is the correct way to define a dynamic route for a user profile page capturing userId in Vue file-based routing?

easy

A. pages/user/[userId].vue

B. pages/user/:userId.vue

C. pages/user/_userId.vue

D. pages/user/userId.vue

Solution

1. Step 1: Recall dynamic route syntax

   Vue file-based routing uses square brackets to define dynamic segments in file names.

2. Step 2: Match syntax to options

   The correct syntax is [userId].vue inside the folder representing the route.

3. Final Answer:

   pages/user/[userId].vue -> Option A

4. Quick Check:

   Dynamic route uses [param] syntax [OK]

Hint: Use square brackets for dynamic route params [OK]

Common Mistakes:

• Using colon syntax like in Vue Router config
• Using underscore prefix which is invalid here
• Naming file literally as param name without brackets

3. Given the following folder structure inside pages:

pages/
  blog/
    [slug].vue
  index.vue

What URL path will render the component in blog/[slug].vue when visiting /blog/vue-routing?

medium

A. The component renders but slug is undefined

B. The component receives slug = 'vue-routing' as a route param

C. The URL /blog/vue-routing does not match any route

D. The component renders but with slug = 'blog/vue-routing'

Solution

1. Step 1: Identify dynamic route usage

   The file [slug].vue inside blog folder captures the segment after /blog/ as slug.

2. Step 2: Match URL to route param

   Visiting /blog/vue-routing sets slug to 'vue-routing' for the component.

3. Final Answer:

   The component receives slug = 'vue-routing' as a route param -> Option B

4. Quick Check:

   Dynamic segment captures URL part [OK]

Hint: Dynamic file name captures URL segment as param [OK]

Common Mistakes:

• Assuming slug is undefined without explicit props
• Thinking URL must exactly match file name
• Confusing nested folder names with param values

4. You have a file pages/blog/[postId].vue but visiting /blog/123 shows a 404 error. What is the most likely cause?

medium

A. The route parameter is not passed as a prop to the component

B. The file name should be _postId.vue instead of using brackets

C. The pages folder is missing or misnamed

D. The dynamic route file is inside the wrong folder

Solution

1. Step 1: Check folder structure

   For file-based routing to work, the pages folder must exist at the correct location.

2. Step 2: Understand 404 cause

   If pages folder is missing or misnamed, routes won't be generated, causing 404 errors.

3. Final Answer:

   The pages folder is missing or misnamed -> Option C

4. Quick Check:

   Missing pages folder causes no routes [OK]

Hint: Check if pages folder exists and is correctly named [OK]

Common Mistakes:

• Confusing dynamic file syntax with underscore prefix
• Assuming props passing affects route matching
• Placing dynamic file in wrong folder without realizing

5. You want to create nested routes for a blog with categories and posts, where URLs look like /blog/tech/vue-routing. Which folder and file structure inside pages correctly sets this up?

hard

A. pages/blog/category/post.vue

B. pages/blog/[category-post].vue

C. pages/blog/[category]/post.vue

D. pages/blog/[category]/[post].vue

Solution

1. Step 1: Understand nested dynamic routes

   Nested folders represent URL segments; dynamic segments use square brackets for variables.

2. Step 2: Match URL pattern to folder structure

   The URL /blog/tech/vue-routing has two dynamic parts after /blog: category and post.

3. Step 3: Verify correct file path

   Using pages/blog/[category]/[post].vue matches the URL segments correctly.

4. Final Answer:

   pages/blog/[category]/[post].vue -> Option D

5. Quick Check:

   Nested folders with [param] files match nested dynamic routes [OK]

Hint: Use nested folders with bracketed files for nested dynamic routes [OK]

Common Mistakes:

• Combining params in one file name incorrectly
• Using static folder names for dynamic segments
• Misplacing files causing route mismatches