Why lifecycle hooks run code at key moments in Svelte - Performance Evidence

Performance: Why lifecycle hooks run code at key moments

MEDIUM IMPACT

This affects how efficiently code runs during component creation, update, and destruction, impacting interaction responsiveness and visual stability.

Running code only when the component is ready or about to be removed

Svelte

import { onMount, onDestroy } from 'svelte';

onMount(() => {
  expensiveCalculation();
});

onDestroy(() => {
  cleanupResources();
});

function expensiveCalculation() {
  // heavy logic
}

function cleanupResources() {
  // cleanup logic
}

Runs heavy code only once when component mounts and cleans up on destroy, avoiding repeated costly runs.

📈 Performance Gainsingle execution on mount, no repeated blocking, improves INP significantly

Running code only when the component is ready or about to be removed

Svelte

import { onMount } from 'svelte';

// Running heavy code repeatedly inside reactive statements instead of lifecycle hooks
$: {
  expensiveCalculation();
}

function expensiveCalculation() {
  // heavy logic
}

Running heavy code reactively causes it to run on every state change, leading to slow interaction and janky UI.

📉 Performance Costblocks rendering for 50+ ms on each state update, causing poor INP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy code in reactive statements	Multiple per state change	Multiple reflows per update	High paint cost due to frequent layout changes	[X] Bad
Heavy code in onMount/onDestroy hooks	Single or few operations	Single reflow on mount/destroy	Low paint cost, stable layout	[OK] Good

Rendering Pipeline

Lifecycle hooks run code at specific moments: before the component appears, after it appears, or before it disappears. This timing controls when the browser must recalculate layout or repaint.

→JavaScript Execution

→Layout

→Paint

⚠️ BottleneckJavaScript Execution when heavy code runs repeatedly

Core Web Vital Affected

INP

This affects how efficiently code runs during component creation, update, and destruction, impacting interaction responsiveness and visual stability.

Optimization Tips

1Run heavy or setup code inside onMount to avoid repeated execution.

2Use onDestroy to clean up resources once when the component is removed.

3Avoid putting expensive logic inside reactive statements that run on every state change.

Performance Quiz - 3 Questions

Why is it better to run heavy code inside onMount instead of reactive statements in Svelte?

A Because onMount runs code before the component is created.

B Because reactive statements never run after the component mounts.

C Because onMount runs code only once when the component appears, avoiding repeated work.

D Because reactive statements run only once on destroy.

DevTools: Performance

How to check: Record a performance profile while interacting with the component. Look for long tasks or repeated JavaScript execution during state changes.

What to look for: Check if heavy JavaScript runs repeatedly on updates (bad) or only once on mount/destroy (good). Look for reduced scripting time and smoother interaction.

Practice

1. What is the main purpose of lifecycle hooks in Svelte components?

easy

A. To handle user input events

B. To style components dynamically

C. To define component props

D. To run code at important moments during a component's life

Solution

1. Step 1: Understand lifecycle hooks

   Lifecycle hooks are special functions that run at specific times in a component's life, like when it appears or disappears.

2. Step 2: Identify their main role

   The main role is to run code at these key moments, such as setup or cleanup tasks.

3. Final Answer:

   To run code at important moments during a component's life -> Option D

4. Quick Check:

   Lifecycle hooks = run code at key moments [OK]

Hint: Lifecycle hooks run code at key moments in component life [OK]

Common Mistakes:

• Thinking lifecycle hooks are for styling
• Confusing hooks with event handlers
• Believing hooks define props

2. Which Svelte lifecycle hook is used to run code right after the component is added to the page?

easy

A. onMount

B. onDestroy

C. beforeUpdate

D. afterUpdate

Solution

1. Step 1: Recall lifecycle hook purposes

   onMount runs code after the component appears on the page, perfect for setup tasks.

2. Step 2: Match hook to timing

   onDestroy runs when component is removed, beforeUpdate and afterUpdate run around updates, not mounting.

3. Final Answer:

   onMount -> Option A

4. Quick Check:

   Code after component appears = onMount [OK]

Hint: onMount runs code after component appears [OK]

Common Mistakes:

• Using onDestroy for setup
• Confusing beforeUpdate with onMount
• Thinking afterUpdate runs on mount

3. Consider this Svelte code:

import { onMount, onDestroy } from 'svelte';

let timer;
onMount(() => {
  timer = setInterval(() => console.log('tick'), 1000);
});
onDestroy(() => {
  clearInterval(timer);
});

What happens when this component is removed from the page?

medium

A. The timer keeps running and logs 'tick' forever

B. An error occurs because clearInterval is missing

C. The timer stops and no more 'tick' logs appear

D. The component reloads automatically

Solution

1. Step 1: Understand onMount and onDestroy usage

   onMount starts a timer that logs 'tick' every second. onDestroy clears that timer when component is removed.

2. Step 2: Predict behavior on removal

   When removed, onDestroy runs and clears the timer, stopping the logs.

3. Final Answer:

   The timer stops and no more 'tick' logs appear -> Option C

4. Quick Check:

   onDestroy clears timer = stops logs [OK]

Hint: onDestroy cleans up timers to stop actions [OK]

Common Mistakes:

• Assuming timer runs forever
• Forgetting to clear timers causes memory leaks
• Thinking component reloads on removal

4. This Svelte code uses lifecycle hooks:

import { onMount } from 'svelte';

onMount(() => {
  console.log('Mounted');
});

onMount(() => {
  console.log('Setup');
});

What is the problem here?

medium

A. Only the first onMount runs, the second is ignored

B. Both onMount hooks run correctly without error

C. Multiple onMount hooks cause a syntax error

D. onMount must be inside a component function

Solution

1. Step 1: Check multiple onMount usage

   Svelte allows multiple onMount calls; all run in order when component mounts.

2. Step 2: Confirm no syntax or scope errors

   Both hooks run and log messages; no syntax error or ignoring occurs.

3. Final Answer:

   Both onMount hooks run correctly without error -> Option B

4. Quick Check:

   Multiple onMount hooks run fine [OK]

Hint: Multiple onMount hooks run in order, no error [OK]

Common Mistakes:

• Thinking multiple hooks cause errors
• Believing only one hook runs
• Assuming onMount must be inside a function

5. You want to fetch data when a Svelte component appears and cancel the fetch if the component is removed before it finishes. Which lifecycle hooks should you use and why?

hard

A. Use onMount to start fetch and onDestroy to cancel it

B. Use beforeUpdate to start fetch and afterUpdate to cancel it

C. Use onDestroy to start fetch and onMount to cancel it

D. Use afterUpdate to start fetch and beforeUpdate to cancel it

Solution

1. Step 1: Identify when to start fetch

   Fetching data should start when component appears, so onMount is the right hook.

2. Step 2: Identify when to cancel fetch

   If component is removed before fetch finishes, onDestroy runs to cancel or clean up the fetch.

3. Final Answer:

   Use onMount to start fetch and onDestroy to cancel it -> Option A

4. Quick Check:

   Start onMount, cancel onDestroy [OK]

Hint: Start fetch onMount, cancel onDestroy for cleanup [OK]

Common Mistakes:

• Using update hooks for fetch start/cancel
• Starting fetch onDestroy (too late)
• Canceling fetch onMount (too early)