Single File Components concept in Vue - Performance & Optimization

Performance: Single File Components concept

MEDIUM IMPACT

This affects initial page load speed and rendering performance by how Vue bundles and processes component code.

Organizing Vue app code with components

Vue

<template>
  <ChildComponent />
</template>
<script>
import { defineAsyncComponent } from 'vue';

export default {
  components: {
    ChildComponent: defineAsyncComponent(() => import('./ChildComponent.vue'))
  }
};
</script>

Smaller components allow code splitting and faster parsing of smaller chunks.

📈 Performance Gainreduces initial bundle size by 30%, faster LCP

Organizing Vue app code with components

Vue

<template><div>...</div></template>
<script>export default { /* large logic */ }</script>
<style>/* large styles */</style>

One huge single file component with all logic and styles causes large bundle size and slower parsing.

📉 Performance Costblocks rendering for 150ms+ on slow devices

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
One large SFC	Moderate (single root)	1 reflow	High paint cost due to delayed script	[X] Bad
Multiple small SFCs with lazy loading	Multiple small DOM trees	Few reflows	Lower paint cost due to faster script load	[OK] Good

Rendering Pipeline

Single File Components are compiled into JavaScript modules that the browser parses and executes. Large components increase parsing and script evaluation time, delaying style calculation and layout.

→Parsing

→Script Evaluation

→Style Calculation

→Layout

⚠️ BottleneckScript Evaluation

Core Web Vital Affected

LCP

This affects initial page load speed and rendering performance by how Vue bundles and processes component code.

Optimization Tips

1Avoid very large Single File Components to reduce script parsing time.

2Split components logically to enable lazy loading and code splitting.

3Use smaller components to improve Largest Contentful Paint (LCP).

Performance Quiz - 3 Questions

How does using one very large Single File Component affect page load?

A It increases script parsing and delays rendering.

B It reduces bundle size and speeds up load.

C It has no effect on performance.

D It improves style calculation speed.

DevTools: Performance

How to check: Record page load and look at scripting time and main thread activity to see script parsing and evaluation delays.

What to look for: Long scripting blocks and delayed LCP indicate large SFCs impacting performance.

Practice

1. What is the main purpose of a Vue Single File Component (SFC)?

easy

A. To write only JavaScript code without any HTML or CSS

B. To separate HTML, CSS, and JavaScript into different files

C. To keep template, script, and style in one file for better organization

D. To create components without any styling or templates

Solution

1. Step 1: Understand the structure of a Vue SFC

   A Vue Single File Component combines template (HTML), script (JavaScript), and style (CSS) in one file for easier management.

2. Step 2: Compare options with this concept

   To keep template, script, and style in one file for better organization correctly describes this purpose. Options B, C, and D contradict the idea of combining all parts in one file.

3. Final Answer:

   To keep template, script, and style in one file for better organization -> Option C

4. Quick Check:

   Single File Component = Combined template, script, style [OK]

Hint: SFC means all parts in one file for neatness [OK]

Common Mistakes:

• Thinking SFC separates files instead of combining
• Believing SFC is only JavaScript code
• Ignoring the style section in SFC

2. Which of the following is the correct way to define the style section in a Vue Single File Component to apply styles only to this component?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall how scoped styles work in Vue SFC

   Using the uses the correct 'scoped' attribute. Others like 'global', 'module', or 'isolated' are incorrect or unrelated here.

2. Final Answer:

   <style scoped> ... </style> -> Option A

3. Quick Check:

   Scoped style = <style scoped> [OK]

Hint: Use 'scoped' attribute to limit styles to component [OK]

Common Mistakes:

• Using <style> without scoped causes global styles
• Confusing 'module' with 'scoped' attribute
• Trying non-existent attributes like 'isolated'

3. Given this Vue SFC snippet, what will be displayed when the component renders?

<template>
  <div>{{ message }}</div>
</template>

<script setup>
const message = 'Hello Vue!'
</script>

medium

A. undefined

B. Hello Vue!

C. {{ message }}

D. Error: message is not defined

Solution

1. Step 1: Understand template interpolation

   The template uses {{ message }} which displays the value of the 'message' variable from the script.

2. Step 2: Check the script setup variable

   The script setup defines 'message' as 'Hello Vue!'. This value will replace {{ message }} in the template.

3. Final Answer:

   Hello Vue! -> Option B

4. Quick Check:

   Template interpolation shows variable value [OK]

Hint: Variables in script setup show in template with {{ }} [OK]

Common Mistakes:

• Thinking {{ message }} prints literally
• Assuming message is undefined without export
• Confusing script setup with normal script

4. Identify the error in this Vue Single File Component:

<template>
  <button @click='increment'>Count: {{ count }}</button>
</template>

<script setup>
let count = 0
function increment() {
  count++
}
</script>

medium

A. The script setup block cannot contain functions

B. The increment function is missing parentheses in the template

C. The template syntax for event binding is incorrect

D. The count variable should be a ref to be reactive

Solution

1. Step 1: Check reactivity of count variable

   In Vue 3 script setup, to make a variable reactive and update the template, it must be a ref or reactive object.

2. Step 2: Analyze the code

   Here, count is a plain number, so incrementing it won't update the template. It should be defined as const count = ref(0).

3. Final Answer:

   The count variable should be a ref to be reactive -> Option D

4. Quick Check:

   Reactive state needs ref() or reactive() [OK]

Hint: Use ref() for reactive variables in script setup [OK]

Common Mistakes:

• Forgetting to import ref from 'vue'
• Thinking functions can't be in script setup
• Misusing event binding syntax

5. You want to create a reusable Vue Single File Component that accepts a title prop and displays it inside an <h1> tag. Which of the following is the correct way to define the prop and use it in the template?

hard

A.
{{ title }}

B.
{{ props.title }}

C.
{{ title }}

D.
{{ title }}

Solution

1. Step 1: Understand how to define props in script setup

   In Vue 3 script setup, props are defined using defineProps(), which returns an object with prop values.

2. Step 2: Check how to use props in template

   Since defineProps returns an object named props, you can destructure or use the props object. But Vue automatically exposes props keys as variables, so {{ title }} works if you assign props to a variable.

3. Step 3: Analyze options

   {{ title }}

   correctly defines props and uses {{ title }} in template.

   {{ props.title }}

   incorrectly uses {{ props.title }} in template (props is not exposed automatically).

   {{ title }}

   wrongly assigns defineProps to title.

   {{ title }}

   does not use defineProps.

4. Final Answer:

   Option A correctly defines and uses the title prop -> Option A

5. Quick Check:

   Use defineProps() and {{ title }} for props [OK]

Hint: Use defineProps() and {{ title }} to access props [OK]

Common Mistakes:

• Using props.title in template without destructuring
• Assigning defineProps() result to wrong variable
• Not using defineProps() at all