Build optimization for production in Vue - Performance & Optimization

Performance: Build optimization for production

HIGH IMPACT

This affects the page load speed by reducing bundle size and improving resource loading efficiency.

Preparing a Vue app for production deployment

Vue

vite build --mode production
// or
vue-cli-service build --mode production --modern

Production builds minify code, remove dev-only code, and enable tree shaking to reduce bundle size.

📈 Performance GainSaves 300-500kb, reduces blocking time, improves LCP by up to 2 seconds

Preparing a Vue app for production deployment

Vue

vite build --mode development
// or
vue-cli-service build --mode development

Development builds include extra debugging code and unminified assets, increasing bundle size and slowing load.

📉 Performance CostAdds 300-500kb to bundle, blocks rendering longer, delays LCP by 1-2 seconds

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Development build	Normal	Multiple due to larger scripts	High due to blocking scripts	[X] Bad
Production build with minification	Normal	Single or fewer reflows	Lower paint cost	[OK] Good
Import full library	Normal	Multiple reflows due to heavy scripts	High paint cost	[X] Bad
Import only used components	Normal	Fewer reflows	Lower paint cost	[OK] Good
Unoptimized images	Normal	Reflows triggered by late image load	High paint cost and CLS	[X] Bad
Optimized images with lazy loading	Normal	Minimal reflows	Low paint cost and stable layout	[OK] Good

Rendering Pipeline

Build optimization reduces the size and complexity of JavaScript and assets, which speeds up parsing, style calculation, layout, and paint stages.

→Parsing & Compilation

→Style Calculation

→Layout

→Paint

⚠️ BottleneckParsing & Compilation due to large JS bundles

Core Web Vital Affected

LCP

This affects the page load speed by reducing bundle size and improving resource loading efficiency.

Optimization Tips

1Always build Vue apps in production mode for deployment.

2Import only the components you use to keep bundles small.

3Optimize and lazy load images to improve load speed and visual stability.

Performance Quiz - 3 Questions

Which build mode should you use for the fastest Vue app load in production?

A Production build with minification and tree shaking

B Development build with source maps

C Build with all debug tools enabled

D Build without minification

DevTools: Performance

How to check: Open DevTools > Performance tab > Record page load > Look at Main thread activity and Loading waterfall

What to look for: Check for long scripting tasks, large JS bundles, and blocking resources delaying LCP

Practice

1. What is the main purpose of running npm run build in a Vue project?

easy

A. To create optimized files for production use

B. To start the development server with hot reload

C. To install project dependencies

D. To run unit tests on components

Solution

1. Step 1: Understand the command purpose

   npm run build compiles and optimizes the Vue app for production deployment.

2. Step 2: Compare with other commands

   Starting the dev server or installing dependencies are done with other commands like npm run dev or npm install.

3. Final Answer:

   To create optimized files for production use -> Option A

4. Quick Check:

   Build command = production optimization [OK]

Hint: Build means prepare app for production use [OK]

Common Mistakes:

• Confusing build with starting dev server
• Thinking build installs dependencies
• Assuming build runs tests

2. Which of the following is the correct way to run a production build in a Vue 3 project using npm?

easy

A. npm start build

B. npm run start

C. npm build run

D. npm run build

Solution

1. Step 1: Recall npm script syntax

   To run scripts defined in package.json, the correct syntax is npm run <script-name>.

2. Step 2: Identify the build script

   The build script is named "build", so the correct command is npm run build.

3. Final Answer:

   npm run build -> Option D

4. Quick Check:

   npm run + script name = correct command [OK]

Hint: Use 'npm run' before script name [OK]

Common Mistakes:

• Using 'npm start build' instead of 'npm run build'
• Swapping order of 'run' and 'build'
• Confusing 'npm run start' with build command

3. After running npm run build in a Vue project, which folder typically contains the optimized production files?

medium

A. src

B. dist

C. public

D. node_modules

Solution

1. Step 1: Understand folder roles

   src holds source code, public holds static assets, node_modules holds dependencies.

2. Step 2: Identify build output folder

   The build process outputs optimized files into the dist folder by default.

3. Final Answer:

   dist -> Option B

4. Quick Check:

   Build output folder = dist [OK]

Hint: Look for 'dist' folder after build completes [OK]

Common Mistakes:

• Confusing src with output folder
• Thinking public folder contains build files
• Looking inside node_modules for build output

4. You ran npm run build but the output files are very large. Which of these is NOT a recommended way to reduce the build size?

medium

A. Use code splitting to load parts on demand

B. Remove unused dependencies from the project

C. Disable minification in the build config

D. Analyze bundle size with build report tools

Solution

1. Step 1: Review optimization techniques

   Code splitting, removing unused dependencies, and analyzing bundle size help reduce build size.

2. Step 2: Understand minification role

   Disabling minification increases file size, so it is NOT recommended to reduce build size.

3. Final Answer:

   Disable minification in the build config -> Option C

4. Quick Check:

   Minification off = larger files [OK]

Hint: Minification off makes files bigger, avoid it [OK]

Common Mistakes:

• Thinking disabling minification reduces size
• Ignoring code splitting benefits
• Skipping bundle analysis tools

5. You want to improve your Vue app's production build by lazy-loading a large component only when needed. Which Vue feature helps achieve this during build optimization?

hard

A. Dynamic import with defineAsyncComponent

B. Using v-if to hide the component

C. Registering the component globally in main.js

D. Importing the component normally at the top of the file

Solution

1. Step 1: Understand lazy loading in Vue

   Lazy loading means loading a component only when needed, reducing initial bundle size.

2. Step 2: Identify correct syntax for lazy loading

   Vue supports lazy loading via dynamic import combined with defineAsyncComponent.

3. Step 3: Evaluate other options

   Using v-if only hides the component but does not delay loading. Global registration and normal import load the component eagerly.

4. Final Answer:

   Dynamic import with defineAsyncComponent -> Option A

5. Quick Check:

   Lazy load = dynamic import + defineAsyncComponent [OK]

Hint: Use dynamic import with defineAsyncComponent for lazy loading [OK]

Common Mistakes:

• Using v-if to delay loading (only hides component)
• Importing component normally loads it eagerly
• Registering globally loads all components upfront