Else and else-if blocks in Svelte - Performance & Optimization

Performance: Else and else-if blocks

MEDIUM IMPACT

This affects how the browser updates the DOM when conditionally rendering content, impacting interaction responsiveness and visual stability.

Conditionally rendering mutually exclusive content blocks

Svelte

<script>
  let status = 'loading';
</script>

{#if status === 'loading'}
  <p>Loading...</p>
{:else if status === 'error'}
  <p>Error occurred.</p>
{:else}
  <p>Data loaded.</p>
{/if}

Using else-if and else blocks ensures only one DOM branch is active, reducing DOM operations and reflows.

📈 Performance GainTriggers a single DOM update and reflow per status change, improving interaction responsiveness.

Conditionally rendering mutually exclusive content blocks

Svelte

<script>
  let status = 'loading';
</script>

{#if status === 'loading'}
  <p>Loading...</p>
{/if}

{#if status === 'error'}
  <p>Error occurred.</p>
{/if}

{#if status === 'success'}
  <p>Data loaded.</p>
{/if}

Multiple separate if blocks cause Svelte to create and check multiple independent DOM nodes, leading to unnecessary DOM updates and reflows.

📉 Performance CostTriggers multiple DOM insertions and removals on status change, causing up to 3 reflows per update.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Separate if blocks for mutually exclusive content	Multiple nodes created and destroyed	Up to 3 reflows per update	High paint cost due to multiple DOM changes	[X] Bad
Single if block with else-if and else	Only one node created/destroyed at a time	Single reflow per update	Lower paint cost with minimal DOM changes	[OK] Good

Rendering Pipeline

Svelte compiles else and else-if blocks into mutually exclusive DOM branches. When the condition changes, only the active branch is mounted or updated, minimizing layout recalculations and paints.

→DOM Operations

→Layout

→Paint

⚠️ BottleneckLayout (reflows caused by DOM insertions/removals)

Core Web Vital Affected

INP

This affects how the browser updates the DOM when conditionally rendering content, impacting interaction responsiveness and visual stability.

Optimization Tips

1Use else and else-if blocks to render only one conditional branch at a time.

2Avoid multiple separate if blocks for mutually exclusive content to reduce DOM thrashing.

3Minimize DOM insertions and removals to improve interaction responsiveness (INP).

Performance Quiz - 3 Questions

Why is using else-if blocks better than multiple separate if blocks in Svelte?

A Because else-if blocks load all content at once, improving load time.

B Because else-if blocks render only one branch, reducing DOM updates and reflows.

C Because separate if blocks prevent any DOM updates.

D Because else-if blocks increase bundle size but improve style calculation.

DevTools: Performance

How to check: Record a performance profile while changing the condition that controls the blocks. Look for the number of layout and paint events triggered.

What to look for: Fewer layout and paint events indicate better performance with else-if blocks compared to multiple separate if blocks.

Practice

1. In Svelte, which block is used to check a second condition if the first {#if} condition is false?

easy

A. {:else}

B. {#each}

C. {:else if}

D. {#await}

Solution

1. Step 1: Understand the purpose of {#if} and {:else if}

   The {#if} block checks the first condition. If it is false, {:else if} allows checking another condition.

2. Step 2: Identify the correct block for a second condition

   {:else if} is specifically designed to check additional conditions after the first fails.

3. Final Answer:

   {:else if} -> Option C

4. Quick Check:

   Second condition check = {:else if} [OK]

Hint: Use {:else if} to test another condition after {#if} fails [OK]

Common Mistakes:

• Using {:else} to check a condition instead of fallback
• Confusing {#each} with conditional blocks
• Trying to use {#await} for conditions

2. Which of the following is the correct syntax for an else-if block in Svelte?

easy

A. {:elseif condition}

B. {:else if condition}

C. {:else-if condition}

D. {:else if (condition)}

Solution

1. Step 1: Recall Svelte syntax for else-if

   Svelte uses {:else if} followed by the condition without parentheses.

2. Step 2: Compare options to correct syntax

   {:else if condition} matches the correct syntax exactly: {:else if condition}

3. Final Answer:

   {:else if condition} -> Option B

4. Quick Check:

   Correct else-if syntax = {:else if condition} [OK]

Hint: Remember: space between else and if, no parentheses [OK]

Common Mistakes:

• Writing {:elseif} as one word
• Adding parentheses around condition
• Using hyphen in else-if

3. What will be rendered by this Svelte code?

{`\n{#if score >= 90}\n  
Excellent
\n{:else if score >= 60}\n  
Good
\n{:else}\n  
Try again
\n{/if}`}

medium

A. Good

B. Try again

C. Excellent

D. No output

Solution

1. Step 1: Evaluate the first condition

   score is 75, which is not >= 90, so the first {#if} block is false.

2. Step 2: Evaluate the else-if condition

   score is 75, which is >= 60, so {:else if} block is true and renders <p>Good</p>.

3. Final Answer:

   <p>Good</p> -> Option A

4. Quick Check:

   score 75 triggers else-if block = Good [OK]

Hint: Check conditions top-down; first true block renders [OK]

Common Mistakes:

• Assuming all blocks render instead of only one
• Misreading the score value
• Confusing else-if with else

4. Identify the error in this Svelte code snippet:

{`{#if isActive}\n  
Active
\n{:else if}\n  
Inactive
\n{/if}`}

medium

A. Missing condition after {:else if}

B. Incorrect closing tag {/if}

C. Cannot use {:else if} after {#if}

D. Missing colon before else

Solution

1. Step 1: Check {:else if} syntax

   The {:else if} block requires a condition to follow it, but none is provided here.

2. Step 2: Confirm other parts are correct

   The {#if} and {/if} tags are correctly placed, and {:else if} is allowed after {#if}.

3. Final Answer:

   Missing condition after {:else if} -> Option A

4. Quick Check:

   {:else if} needs a condition [OK]

Hint: Always add a condition after {:else if} [OK]

Common Mistakes:

• Leaving {:else if} without condition
• Confusing {:else} with {:else if}
• Misplacing {/if} tag

5. Given this Svelte code:

{`\n{#if status === 'loading'}\n  
Loading...
\n{:else if status === 'success'}\n  
Data loaded
\n{:else if status === 'error'}\n  
Error occurred
\n{:else}\n  
Idle
\n{/if}`}

What will be displayed if status is an empty string?

hard

A. Loading...

B. Data loaded

C. Error occurred

D. Idle

Solution

1. Step 1: Check each condition against empty string

   status is '', so none of the conditions 'loading', 'success', or 'error' match.

2. Step 2: Use {:else} block as fallback

   Since no conditions match, the {:else} block runs, rendering <p>Idle</p>.

3. Final Answer:

   <p>Idle</p> -> Option D

4. Quick Check:

   Empty string triggers else block = Idle [OK]

Hint: If no conditions match, {:else} block runs [OK]

Common Mistakes:

• Assuming empty string matches a condition
• Forgetting {:else} fallback
• Mixing up else-if and else blocks