Why Svelte exists - Performance Evidence

Performance: Why Svelte exists

HIGH IMPACT

Svelte affects page load speed and runtime rendering by compiling components to minimal JavaScript that updates the DOM directly.

Building a fast web app with minimal runtime overhead

Svelte

<script>
  let count = 0;
  function increment() {
    count += 1;
  }
</script>
<button on:click={increment}>{count}</button>

Svelte compiles to direct DOM updates without a virtual DOM, reducing bundle size and runtime work.

📈 Performance Gainsaves ~30kb+ bundle size, single reflow per update

Building a fast web app with minimal runtime overhead

Svelte

import React from 'react';
function App() {
  const [count, setCount] = React.useState(0);
  return <button onClick={() => setCount(count + 1)}>{count}</button>;
}
export default App;

React includes a runtime library and virtual DOM diffing which adds bundle size and runtime CPU work.

📉 Performance Costadds ~40kb+ to bundle, triggers multiple reflows on updates

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
React Virtual DOM	Multiple nodes updated via diffing	Multiple reflows per update	Moderate paint cost	[X] Bad
Svelte Compiled DOM Updates	Direct node updates	Single reflow per update	Lower paint cost	[OK] Good

Rendering Pipeline

Svelte compiles components to efficient JavaScript that updates the DOM directly, bypassing virtual DOM diffing and reducing style recalculations.

→JavaScript Execution

→Layout

→Paint

⚠️ BottleneckJavaScript Execution and Layout due to runtime diffing in other frameworks

Core Web Vital Affected

LCP

Svelte affects page load speed and runtime rendering by compiling components to minimal JavaScript that updates the DOM directly.

Optimization Tips

1Shift work from runtime to compile time to reduce JavaScript execution during page load.

2Minimize bundle size by compiling away framework runtime code.

3Use direct DOM updates to reduce layout recalculations and reflows.

Performance Quiz - 3 Questions

What is the main reason Svelte improves page load speed compared to React?

A It loads fewer CSS files

B It uses a virtual DOM to batch updates

C It compiles components to efficient JavaScript that updates the DOM directly

D It delays JavaScript execution until user interaction

DevTools: Performance

How to check: Record a profile while interacting with the app, then inspect scripting and rendering times.

What to look for: Lower scripting time and fewer layout recalculations indicate better performance.

Practice

1. Why does Svelte exist as a framework for building web apps?

easy

A. To force developers to write more complex code

B. To add more runtime code for better animations

C. To compile code ahead of time and reduce browser work

D. To replace HTML with a new markup language

Solution

1. Step 1: Understand Svelte's main goal

   Svelte compiles your app code before it runs in the browser, reducing the work the browser must do.

2. Step 2: Compare options to this goal

   Only To compile code ahead of time and reduce browser work describes compiling ahead of time to reduce browser work, which matches Svelte's purpose.

3. Final Answer:

   To compile code ahead of time and reduce browser work -> Option C

4. Quick Check:

   Compile ahead = less browser work [OK]

Hint: Remember Svelte compiles before running, not during runtime [OK]

Common Mistakes:

• Thinking Svelte adds more runtime code
• Believing Svelte changes HTML syntax
• Assuming Svelte makes code more complex

2. Which of the following is the correct way to start a Svelte component file?

easy

A.

B. function Component() { return Hello; }

C. class Component extends React.Component {}

D. Hello

Solution

1. Step 1: Identify Svelte component syntax

   Svelte components use a <script> tag to declare variables and logic.

2. Step 2: Check options for Svelte style

   <script> export let name; </script> uses <script> with export let, which is correct Svelte syntax. Others are React or Vue syntax.

3. Final Answer:

   <script> export let name; </script> -> Option A

4. Quick Check:

   Svelte uses <script> with export let [OK]

Hint: Svelte components start with <script> tag, not functions or templates [OK]

Common Mistakes:

• Using React or Vue syntax in Svelte files
• Forgetting to export props with 'export let'
• Trying to use class components in Svelte

3. Given this Svelte code, what will be shown in the browser?

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

<button on:click={increment}>Clicked {count} times</button>

medium

A. A button showing 'Clicked 1 times' initially

B. A button that does not update the count when clicked

C. A syntax error because on:click is invalid

D. A button showing 'Clicked 0 times' that updates count on each click

Solution

1. Step 1: Understand the initial state and event

   The count starts at 0. The button shows 'Clicked {count} times'. Clicking triggers increment() which adds 1 to count.

2. Step 2: Predict behavior on clicks

   Initially, the button shows 'Clicked 0 times'. Each click increases count and updates the text.

3. Final Answer:

   A button showing 'Clicked 0 times' that updates count on each click -> Option D

4. Quick Check:

   Initial count 0, updates on click [OK]

Hint: Remember Svelte updates UI reactively when variables change [OK]

Common Mistakes:

• Thinking on:click is invalid syntax
• Assuming count starts at 1
• Believing the button text won't update

4. What is wrong with this Svelte code snippet?

<script>
  let name = 'Alice'
  function greet() {
    alert('Hello ' + name)
  }
</script>

<button on:click={greet} >Greet</button>

medium

A. No error; code works as expected

B. The alert function is not allowed in Svelte

C. Missing semicolon after let name declaration

D. The on:click event handler syntax is incorrect

Solution

1. Step 1: Check JavaScript syntax in Svelte

   JavaScript semicolons are optional; missing semicolon is not an error here.

2. Step 2: Verify event handler and alert usage

   on:click={greet} is correct Svelte syntax. alert() is valid JavaScript and works in Svelte.

3. Final Answer:

   No error; code works as expected -> Option A

4. Quick Check:

   Optional semicolons and valid event syntax [OK]

Hint: JS semicolons optional; on:click syntax is correct [OK]

Common Mistakes:

• Thinking missing semicolon causes error
• Believing alert is disallowed in Svelte
• Confusing event handler syntax with React

5. How does Svelte improve performance compared to frameworks like React or Vue?

hard

A. By running all code on the server instead of the browser

B. By compiling components to efficient JavaScript at build time, reducing runtime overhead

C. By using a virtual DOM to minimize updates

D. By requiring developers to write manual DOM updates

Solution

1. Step 1: Understand Svelte's compilation approach

   Svelte compiles components into minimal JavaScript during build, so the browser does less work at runtime.

2. Step 2: Compare with other frameworks

   React and Vue use virtual DOM at runtime, adding overhead. Svelte avoids this by compiling ahead.

3. Final Answer:

   By compiling components to efficient JavaScript at build time, reducing runtime overhead -> Option B

4. Quick Check:

   Compile time optimization = better performance [OK]

Hint: Svelte compiles ahead, no virtual DOM overhead [OK]

Common Mistakes:

• Confusing Svelte with server-side rendering only
• Thinking Svelte uses virtual DOM
• Believing manual DOM updates are required