Error handling in load in Svelte - Performance & Optimization

Performance: Error handling in load

MEDIUM IMPACT

This affects page load speed and user experience by controlling how errors during data fetching impact rendering and interactivity.

Handling errors during data fetching in the load function

Svelte

export async function load({ fetch }) {
  try {
    const res = await fetch('/api/data');
    if (!res.ok) {
      return { data: null, error: 'Failed to load data' };
    }
    const data = await res.json();
    return { data };
  } catch (e) {
    return { data: null, error: 'Network error' };
  }
}

Returns fallback data and error info to render a user-friendly message without blocking main content rendering.

📈 Performance GainAvoids blocking rendering, reduces LCP delay, and prevents layout shifts caused by late error UI injection

Handling errors during data fetching in the load function

Svelte

export async function load({ fetch }) {
  const res = await fetch('/api/data');
  if (!res.ok) {
    throw new Error('Failed to load data');
  }
  const data = await res.json();
  return { data };
}

Throwing an error without fallback causes the page to fail rendering or show a blank screen, blocking LCP and causing poor user experience.

📉 Performance CostBlocks rendering until error is handled, increasing LCP by 500ms+ depending on network

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Throw error without fallback	Minimal DOM nodes but blocks rendering	0 reflows but blocks layout	Delays paint until error handled	[X] Bad
Catch error and return fallback data	Adds error message nodes	1 reflow for error UI	Paints fallback UI quickly	[OK] Good

Rendering Pipeline

The load function runs before the page renders. If it throws errors without fallback, rendering is blocked until error handling completes or fails. Proper error handling allows the browser to proceed with rendering fallback UI quickly.

→Data Fetching

→Layout

→Paint

⚠️ BottleneckData Fetching blocking Layout and Paint

Core Web Vital Affected

LCP

This affects page load speed and user experience by controlling how errors during data fetching impact rendering and interactivity.

Optimization Tips

1Always catch errors in load and return fallback data to avoid blocking rendering.

2Avoid throwing uncaught errors in load to prevent delaying Largest Contentful Paint.

3Render simple error UI immediately to maintain visual stability and responsiveness.

Performance Quiz - 3 Questions

What is the main performance risk of throwing an error directly in the load function without fallback?

A It causes excessive CSS recalculations

B It increases the number of DOM nodes unnecessarily

C It blocks rendering and delays Largest Contentful Paint

D It reduces JavaScript bundle size

DevTools: Performance

How to check: Record a page load with error in load function. Look for long tasks blocking rendering and delayed Largest Contentful Paint.

What to look for: Long blocking time before first paint or LCP, and absence of fallback UI in the DOM during load

Practice

1. What is the main purpose of using error handling in the load function in SvelteKit?

easy

A. To style the page dynamically

B. To speed up the loading of data

C. To keep the app stable when data fails to load

D. To preload images before rendering

Solution

1. Step 1: Understand the role of load in SvelteKit

   The load function fetches data before the page renders.

2. Step 2: Identify why error handling is needed

   If data fetching fails, error handling prevents the app from crashing and shows a proper message.

3. Final Answer:

   To keep the app stable when data fails to load -> Option C

4. Quick Check:

   Error handling in load = stability [OK]

Hint: Error handling keeps your app stable on data failure [OK]

Common Mistakes:

• Thinking error handling speeds up loading
• Confusing error handling with styling
• Assuming error handling preloads images

2. Which of the following is the correct way to throw an error with status 404 inside a load function?

easy

A. throw new Error(404, 'Not found')

B. throw error(404, 'Not found')

C. return { error: 404, message: 'Not found' }

D. throw { status: 404, message: 'Not found' }

Solution

1. Step 1: Recall SvelteKit's error helper usage

   SvelteKit provides an error function to throw HTTP errors with status and message.

2. Step 2: Match the correct syntax

   The correct syntax is throw error(404, 'Not found'). Other options are invalid or incomplete.

3. Final Answer:

   throw error(404, 'Not found') -> Option B

4. Quick Check:

   Throw error helper = throw error(404, message) [OK]

Hint: Use throw error(status, message) in load [OK]

Common Mistakes:

• Using new Error() with status code
• Returning error object instead of throwing
• Throwing plain objects without error helper

3. Given this load function, what will be the output if the fetch fails with a 500 status?

export async function load() {
  try {
    const res = await fetch('/api/data');
    if (!res.ok) {
      throw error(res.status, 'Failed to load data');
    }
    const data = await res.json();
    return { data };
  } catch (err) {
    return { status: err.status || 500, error: err.message };
  }
}

medium

A. { status: 500, error: 'Failed to load data' }

B. { data: undefined }

C. Page crashes with unhandled error

D. { status: 404, error: 'Not found' }

Solution

1. Step 1: Analyze fetch failure handling

   If fetch returns a 500 status, res.ok is false, so throw error(500, 'Failed to load data') runs.

2. Step 2: Understand catch block behavior

   The thrown error is caught, and the function returns an object with status and error from the error.

3. Final Answer:

   { status: 500, error: 'Failed to load data' } -> Option A

4. Quick Check:

   Catch returns error object with status and message [OK]

Hint: Catch returns error object with status and message [OK]

Common Mistakes:

• Expecting data to be returned on fetch failure
• Assuming page crashes without catch
• Confusing 404 with 500 status

4. Identify the error in this load function that causes the error handling to fail:

export async function load() {
  try {
    const res = await fetch('/api/data');
    if (!res.ok) {
      return error(res.status, 'Failed to load');
    }
    const data = await res.json();
    return { data };
  } catch (err) {
    return { status: err.status, error: err.message };
  }
}

medium

A. Not checking res.ok before parsing JSON

B. Missing await before fetch

C. Not returning data inside catch block

D. Using return error(...) instead of throw error(...)

Solution

1. Step 1: Check error throwing vs returning

   The code uses return error(...) which does not throw an error but returns a value, so error handling is bypassed.

2. Step 2: Correct usage in SvelteKit

   To trigger error handling, it must throw error(...) so the catch block or error page activates.

3. Final Answer:

   Using return error(...) instead of throw error(...) -> Option D

4. Quick Check:

   Throw error to activate error handling [OK]

Hint: Throw error(...) to trigger error handling, not return [OK]

Common Mistakes:

• Returning error instead of throwing
• Forgetting to await fetch
• Ignoring res.ok check

5. You want to show a custom error page when your API returns a 403 status inside load. Which approach correctly handles this and passes the error to the page?

hard

A. Throw error(403, 'Access denied') inside load and create an error.svelte page to display it

B. Return { status: 403, error: 'Access denied' } and handle it manually in the page script

C. Use console.error and return empty data to show default page

D. Redirect to a different page using goto('/login') inside load

Solution

1. Step 1: Understand error propagation in load

   Throwing error(403, 'Access denied') inside load tells SvelteKit to show the error page.

2. Step 2: Use error.svelte to customize error display

   Creating an error.svelte page lets you show custom messages based on the error status and message.

3. Final Answer:

   Throw error(403, 'Access denied') inside load and create an error.svelte page to display it -> Option A

4. Quick Check:

   Throw error + error.svelte = custom error page [OK]

Hint: Throw error and use error.svelte for custom error pages [OK]

Common Mistakes:

• Returning error object instead of throwing
• Using console.error without error propagation
• Redirecting instead of showing error page