tick function in Svelte - Performance & Optimization

Performance: tick function

MEDIUM IMPACT

The tick function affects how updates are batched and when the DOM reflects state changes, impacting rendering speed and interaction smoothness.

Waiting for DOM updates before running code

Svelte

import { tick } from 'svelte';

let count = 0;

async function increment() {
  count++;
  await tick();
  const height = document.getElementById('box').offsetHeight;
  console.log(height);
}

tick waits for the DOM to update only after this change, batching updates and avoiding extra reflows.

📈 Performance Gainsingle reflow per update, smoother interaction

Waiting for DOM updates before running code

Svelte

import { afterUpdate } from 'svelte';

let count = 0;

function increment() {
  count++;
  // Immediately query DOM here
  const height = document.getElementById('box').offsetHeight;
  console.log(height);
}

// Using afterUpdate causes code to run after every update, not just this one

Using afterUpdate runs code after every component update, causing unnecessary DOM reads and potential layout thrashing.

📉 Performance Costtriggers multiple reflows if updates are frequent

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Using afterUpdate for DOM reads	Multiple reads after every update	Multiple forced reflows	High paint cost due to layout thrashing	[X] Bad
Using tick to await DOM update	Single read after update	Single reflow per update	Lower paint cost, smoother rendering	[OK] Good

Rendering Pipeline

The tick function schedules code to run after Svelte flushes DOM updates, ensuring the browser has applied changes before reading layout.

→Update Scheduling

→Layout

→Paint

⚠️ BottleneckLayout (reflow) caused by reading DOM properties too early

Core Web Vital Affected

INP

The tick function affects how updates are batched and when the DOM reflects state changes, impacting rendering speed and interaction smoothness.

Optimization Tips

1Use tick to wait for DOM updates before reading layout properties.

2Avoid reading DOM properties immediately after state changes to prevent forced reflows.

3Batch DOM reads and writes to reduce layout thrashing and improve interaction responsiveness.

Performance Quiz - 3 Questions

What is the main performance benefit of using Svelte's tick function?

A It prevents any DOM updates from happening

B It immediately forces the browser to repaint

C It batches DOM updates and delays code until after the DOM is updated

D It increases the number of reflows for accuracy

DevTools: Performance

How to check: Record a performance profile while interacting with the component. Look for layout thrashing or multiple forced reflows in the flame chart.

What to look for: Fewer layout events and shorter long tasks indicate better use of tick for batching updates.

Practice

1. What is the main purpose of the tick function in Svelte?

easy

A. To wait until Svelte finishes updating the DOM before running code

B. To delay code execution by a fixed time

C. To immediately update the component state

D. To fetch data from an API asynchronously

Solution

1. Step 1: Understand what tick does

   The tick function waits for Svelte to complete DOM updates after state changes.

2. Step 2: Compare options with this behavior

   Only To wait until Svelte finishes updating the DOM before running code describes waiting for DOM updates before running code, matching tick's purpose.

3. Final Answer:

   To wait until Svelte finishes updating the DOM before running code -> Option A

4. Quick Check:

   tick waits for DOM update = C [OK]

Hint: Remember: tick waits for screen update before next code runs [OK]

Common Mistakes:

• Thinking tick delays by fixed time instead of waiting for update
• Confusing tick with immediate state update
• Assuming tick fetches data

2. Which of the following is the correct way to use tick inside a Svelte component?

easy

A. await tick(); // inside an async function

B. tick(callbackFunction);

C. tick.then(() => console.log('done'));

D. const result = tick(); console.log(result);

Solution

1. Step 1: Recall how tick is used

   tick returns a Promise and must be awaited inside an async function.

2. Step 2: Check each option's syntax

   await tick(); // inside an async function correctly uses await tick(); inside an async function. Others misuse tick as a normal function or callback.

3. Final Answer:

   await tick(); // inside an async function -> Option A

4. Quick Check:

   tick returns Promise, use await = D [OK]

Hint: Always use await tick() inside async functions [OK]

Common Mistakes:

• Calling tick without await
• Trying to pass a callback to tick
• Using tick as a normal function returning value

3. Consider this Svelte code snippet:

import { tick } from 'svelte';

let count = 0;

async function increment() {
  count += 1;
  await tick();
  console.log(document.getElementById('count').textContent);
}

What will be logged when increment() is called?

medium

A. '0'

B. '1'

C. undefined

D. An error is thrown

Solution

1. Step 1: Understand the code flow

   The function increments count, then waits for DOM update with await tick().

2. Step 2: Check what is logged after tick

   After tick, the DOM updates, so the element with id 'count' shows the new count '1'. Thus, console logs '1'.

3. Final Answer:

   '1' -> Option B

4. Quick Check:

   tick waits for DOM update, so logged text is updated count = A [OK]

Hint: tick ensures DOM updates before reading elements [OK]

Common Mistakes:

• Expecting old value before DOM update
• Forgetting tick is async and must be awaited
• Assuming console logs undefined or error

4. This Svelte code tries to log the updated DOM text after changing a variable:

import { tick } from 'svelte';

let name = 'Alice';

function updateName() {
  name = 'Bob';
  tick();
  console.log(document.getElementById('name').textContent);
}

What is the problem here?

medium

A. tick cannot be imported from 'svelte'

B. console.log syntax is incorrect

C. name variable cannot be reassigned

D. tick is not awaited, so DOM may not update before console.log

Solution

1. Step 1: Identify how tick is used

   tick returns a Promise and must be awaited to wait for DOM update.

2. Step 2: Analyze the effect of missing await

   Without await, console.log runs immediately before DOM updates, so it logs old text.

3. Final Answer:

   tick is not awaited, so DOM may not update before console.log -> Option D

4. Quick Check:

   Missing await causes premature log = B [OK]

Hint: Always await tick() to ensure DOM updates before next code [OK]

Common Mistakes:

• Not awaiting tick()
• Thinking tick is synchronous
• Assuming variable reassignment is the issue

5. You want to update a list of items in Svelte and then focus the last item's input field after the DOM updates. Which code correctly uses tick to achieve this?

hard

A. async function addItem() {
items.push('new');
document.querySelector('input:last-of-type').focus();
await tick();
}

B. function addItem() {
items.push('new');
tick();
document.querySelector('input:last-of-type').focus();
}

C. async function addItem() {
items.push('new');
await tick();
document.querySelector('input:last-of-type').focus();
}

D. function addItem() {
items.push('new');
setTimeout(() => document.querySelector('input:last-of-type').focus(), 0);
}

Solution

1. Step 1: Understand the need to wait for DOM update

   After adding an item, the DOM must update before focusing the new input.

2. Step 2: Check which option waits correctly

   async function addItem() { items.push('new'); await tick(); document.querySelector('input:last-of-type').focus(); } uses await tick() after pushing the item, ensuring DOM updates before focusing.

3. Step 3: Identify why others fail

   function addItem() { items.push('new'); tick(); document.querySelector('input:last-of-type').focus(); } misses await, so focus runs too early. async function addItem() { items.push('new'); document.querySelector('input:last-of-type').focus(); await tick(); } focuses before DOM update. function addItem() { items.push('new'); setTimeout(() => document.querySelector('input:last-of-type').focus(), 0); } uses setTimeout, which is less reliable than tick.

4. Final Answer:

   async function addItem() { items.push('new'); await tick(); document.querySelector('input:last-of-type').focus(); } -> Option C

5. Quick Check:

   await tick before DOM access = A [OK]

Hint: Push item, await tick(), then access DOM to ensure update [OK]

Common Mistakes:

• Not awaiting tick before DOM access
• Accessing DOM before update
• Using setTimeout instead of tick