Nuxt project structure in Vue - Performance & Optimization

Performance: Nuxt project structure

MEDIUM IMPACT

This affects the initial page load speed and rendering performance by organizing how components, pages, and assets are loaded and rendered.

Organizing pages and components for optimal loading

Vue

pages/
  index.vue
  about.vue
components/
  Header.vue
  Footer.vue
  BigComponent.vue

// Use automatic component import or lazy load BigComponent only where needed

Only loads components when needed, reducing initial bundle size and speeding up page load.

📈 Performance GainSaves 100-200kb on initial load, improves LCP by 200-400ms

Organizing pages and components for optimal loading

Vue

pages/
  index.vue
  about.vue
components/
  Header.vue
  Footer.vue
  BigComponent.vue

// All components imported globally in nuxt.config.js

Importing all components globally causes the entire component code to load on every page, increasing bundle size and slowing initial load.

📉 Performance CostAdds 100-200kb to initial bundle, blocking rendering longer

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Global import of all components	Low	Low	High due to large JS bundle	[X] Bad
Lazy loading components per page	Low	Low	Low due to smaller JS bundles	[OK] Good
Static assets in assets folder referenced relatively	N/A	N/A	Blocks paint until loaded	[!] OK
Static assets in public folder with caching	N/A	N/A	Non-blocking paint with caching	[OK] Good

Rendering Pipeline

Nuxt project structure influences how the browser processes HTML, CSS, and JavaScript by controlling code splitting, lazy loading, and asset delivery.

→HTML Parsing

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Execution due to large bundles from poor structure

Core Web Vital Affected

LCP

This affects the initial page load speed and rendering performance by organizing how components, pages, and assets are loaded and rendered.

Optimization Tips

1Avoid global imports of all components to keep bundles small.

2Place static assets in the public folder for caching and faster delivery.

3Use automatic component imports or lazy loading to improve page load speed.

Performance Quiz - 3 Questions

How does importing all components globally in Nuxt affect performance?

A Improves caching and speeds up load

B Increases initial bundle size and slows page load

C Has no effect on performance

D Reduces JavaScript execution time

DevTools: Performance

How to check: Record page load, look at Main thread for long JS execution and large bundle parsing times

What to look for: Long scripting times and large JS files indicate poor project structure causing slow LCP

Practice

1. In a Nuxt project, which folder automatically generates routes based on its files?

easy

A. pages folder

B. components folder

C. layouts folder

D. plugins folder

Solution

1. Step 1: Understand Nuxt routing

   Nuxt uses the pages folder to create routes automatically from the files inside it.

2. Step 2: Identify folder roles

   components holds reusable UI parts, layouts define page wrappers, and plugins add extra functionality, but none auto-generate routes.

3. Final Answer:

   pages folder -> Option A

4. Quick Check:

   Routes come from pages folder [OK]

Hint: Routes come from the pages folder files [OK]

Common Mistakes:

• Confusing components folder with pages
• Thinking layouts create routes
• Assuming plugins handle routing

2. Which of the following is the correct way to define a layout in a Nuxt project?

easy

A. Add a Vue component inside pages/ folder named layout.vue

B. Create a file in layouts/ folder and export a Vue component

C. Place a JavaScript file in plugins/ folder named layout.js

D. Create a CSS file in assets/ folder named layout.css

Solution

1. Step 1: Know where layouts go

   Layouts in Nuxt are Vue components placed inside the layouts/ folder to wrap pages.

2. Step 2: Check other options

   Pages folder is for routes, plugins are for JS extensions, assets hold styles or images, so these are incorrect for layouts.

3. Final Answer:

   Create a file in layouts/ folder and export a Vue component -> Option B

4. Quick Check:

   Layouts live in layouts folder [OK]

Hint: Layouts are Vue files inside layouts folder [OK]

Common Mistakes:

• Putting layouts inside pages folder
• Confusing plugins with layouts
• Thinking CSS files define layouts

3. Given this Nuxt project structure:

layouts/default.vue
pages/index.vue
pages/about.vue

What happens when you visit the URL /about?

medium

A. The default.vue layout is shown alone without any page

B. The index.vue page is shown without any layout

C. A 404 error occurs because about.vue is not a layout

D. The about.vue page is shown wrapped by default.vue layout

Solution

1. Step 1: Understand routing and layouts

   Visiting /about loads pages/about.vue automatically as a route.

2. Step 2: Layout wrapping behavior

   By default, pages are wrapped inside the layouts/default.vue layout unless specified otherwise.

3. Final Answer:

   The about.vue page is shown wrapped by default.vue layout -> Option D

4. Quick Check:

   Page loads with default layout [OK]

Hint: Pages load inside default layout unless changed [OK]

Common Mistakes:

• Thinking about.vue is not a route
• Assuming layouts show alone
• Ignoring default layout wrapping

4. You created a file pages/contact.vue but visiting /contact shows a 404 error. What is the most likely cause?

medium

A. The plugins/ folder is empty

B. The layouts/default.vue file is missing

C. The contact.vue file is inside components/ folder instead of pages/

D. You forgot to import contact.vue in pages/index.vue

Solution

1. Step 1: Check file location for routing

   Nuxt auto-generates routes only from files inside the pages/ folder.

2. Step 2: Identify common mistakes

   If contact.vue is inside components/, it won't create a route, causing 404 on /contact.

3. Final Answer:

   The contact.vue file is inside components/ folder instead of pages/ -> Option C

4. Quick Check:

   Pages folder files create routes [OK]

Hint: Pages must be inside pages folder for routing [OK]

Common Mistakes:

• Placing pages in components folder
• Thinking layouts cause 404
• Assuming imports needed for pages

5. You want to create a Nuxt app with two different page layouts: one for public pages and one for admin pages. How should you organize your project structure to achieve this?

hard

A. Create layouts/public.vue and layouts/admin.vue, then specify layout in each page's definePageMeta

B. Put all pages in pages/ and import layouts manually inside each page component

C. Create two separate pages/ folders named public and admin without layouts

D. Use plugins/ to switch layouts dynamically based on route

Solution

1. Step 1: Understand layout usage in Nuxt

   You can create multiple layouts inside layouts/ folder, each as a Vue component.

2. Step 2: Assign layouts per page

   Use definePageMeta in each page to specify which layout to use, e.g., layout: 'admin' or layout: 'public'.

3. Step 3: Evaluate other options

   Importing layouts manually or using plugins for layout switching is not the recommended Nuxt pattern.

4. Final Answer:

   Create layouts/public.vue and layouts/admin.vue, then specify layout in each page's definePageMeta -> Option A

5. Quick Check:

   Multiple layouts + definePageMeta = correct [OK]

Hint: Use multiple layouts and definePageMeta per page [OK]

Common Mistakes:

• Trying to import layouts manually in pages
• Not using definePageMeta for layout selection
• Misusing plugins for layout switching