Lifecycle hooks in Composition API in Vue - Performance & Optimization

Performance: Lifecycle hooks in Composition API

MEDIUM IMPACT

This affects the timing of code execution during component rendering and updates, impacting interaction responsiveness and rendering smoothness.

Running heavy synchronous code inside lifecycle hooks

Vue

import { onMounted } from 'vue';
onMounted(() => {
  setTimeout(() => {
    // heavy task deferred
    for (let i = 0; i < 1_000_000_000; i++) {}
  }, 0);
});

Deferring heavy tasks lets the browser render first and respond to user input faster.

📈 Performance GainNon-blocking mount, improves INP by 80-90%.

Running heavy synchronous code inside lifecycle hooks

Vue

import { onMounted } from 'vue';
onMounted(() => {
  // heavy synchronous task
  for (let i = 0; i < 1_000_000_000; i++) {}
});

Heavy synchronous code blocks the main thread during component mount, delaying rendering and user interaction.

📉 Performance CostBlocks rendering for 100+ ms, causing poor INP and delayed LCP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy synchronous code in onMounted	Minimal	Blocks rendering causing multiple reflows	High due to delayed paint	[X] Bad
Deferred heavy code with setTimeout	Minimal	Single reflow after render	Low paint cost	[OK] Good
Direct DOM style changes in multiple hooks	Multiple style changes	2+ reflows per update	High paint cost causing jank	[X] Bad
Reactive state with watchEffect for DOM updates	Single batched DOM update	Single reflow	Low paint cost	[OK] Good

Rendering Pipeline

Lifecycle hooks run JavaScript code at specific component phases, affecting style calculation, layout, and paint depending on DOM changes triggered.

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Execution blocking Style Calculation and Layout

Core Web Vital Affected

INP

This affects the timing of code execution during component rendering and updates, impacting interaction responsiveness and rendering smoothness.

Optimization Tips

1Avoid heavy synchronous code inside lifecycle hooks to prevent blocking rendering.

2Defer expensive tasks using timers or async methods to improve input responsiveness.

3Use reactive state and watchers to batch DOM updates and minimize reflows.

Performance Quiz - 3 Questions

What is the main performance risk of running heavy synchronous code inside onMounted?

A It increases bundle size significantly.

B It blocks rendering and delays user interaction.

C It causes layout shifts after paint.

D It reduces network request speed.

DevTools: Performance

How to check: Record a performance profile during component mount and update; look for long tasks and scripting blocking time.

What to look for: Look for long scripting tasks during lifecycle hooks and multiple reflows or layout thrashing in the flame chart.