API authentication patterns in Svelte - Performance & Optimization

Performance: API authentication patterns

MEDIUM IMPACT

This affects page load speed and interaction responsiveness by controlling how authentication data is fetched and stored.

Authenticating API requests in a Svelte app

Svelte

import { onMount } from 'svelte';
let user;
onMount(async () => {
  const response = await fetch('/api/auth', { 
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({ username, password })
  });
  user = await response.json();
});

// Using async/await allows non-blocking rendering and faster interaction

Async fetch does not block rendering, improving input responsiveness.

📈 Performance GainNon-blocking fetch reduces INP by 50-70%

Authenticating API requests in a Svelte app

Svelte

import { onMount } from 'svelte';
let user;
onMount(() => {
  const xhr = new XMLHttpRequest();
  xhr.open('POST', '/api/auth', false);
  xhr.setRequestHeader('Content-Type', 'application/json');
  xhr.send(JSON.stringify({ username, password }));
  user = JSON.parse(xhr.responseText);
});

// Synchronous XMLHttpRequest blocks rendering

Synchronous XMLHttpRequest blocks rendering and delays user interaction, causing poor responsiveness.

📉 Performance CostBlocks rendering for 100-300ms depending on network, increases INP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous XHR blocking rendering	Minimal	0	Blocks paint until fetch completes	[X] Bad
Async fetch with await	Minimal	0	Non-blocking paint, faster interaction	[OK] Good
Access token from localStorage on every request	Minimal	0	Small main thread blocks per request	[!] Bad
Access token from in-memory reactive store	Minimal	0	No blocking, smooth interaction	[OK] Good

Rendering Pipeline

API authentication patterns affect the browser's main thread during JavaScript execution and network request handling, impacting the timing of rendering and user interaction readiness.

→JavaScript Execution

→Network Request

→Rendering

→Composite

⚠️ BottleneckJavaScript Execution blocking rendering due to synchronous token access or blocking fetch calls

Core Web Vital Affected

INP

This affects page load speed and interaction responsiveness by controlling how authentication data is fetched and stored.

Optimization Tips

1Always use async fetch calls for authentication to avoid blocking rendering.

2Store tokens in memory or reactive stores, not localStorage, for faster access.

3Avoid synchronous localStorage access on every API request to reduce main thread blocking.

Performance Quiz - 3 Questions

Which API authentication pattern improves input responsiveness (INP) in a Svelte app?

A Reading token from localStorage on every request synchronously

B Using synchronous fetch calls without await

C Using async/await fetch calls for authentication

D Blocking rendering until authentication completes

DevTools: Performance

How to check: Record a performance profile while loading and interacting with the app. Look for long tasks caused by synchronous fetch or localStorage access.

What to look for: Look for long blocking tasks on the main thread during authentication and API calls. Shorter tasks and async patterns indicate better performance.

Practice

1. What is the main purpose of API authentication in a Svelte app?

easy

A. To verify the identity of the user or app making the request

B. To speed up the API response time

C. To change the API data format

D. To style the API response

Solution

1. Step 1: Understand API authentication role

   API authentication checks who is making the request to keep the app secure.

2. Step 2: Identify the correct purpose

   Speed, data format, and styling are unrelated to authentication.

3. Final Answer:

   To verify the identity of the user or app making the request -> Option A

4. Quick Check:

   Authentication = Verify identity [OK]

Hint: Authentication means checking who you are [OK]

Common Mistakes:

• Confusing authentication with performance optimization
• Thinking authentication changes data format
• Assuming authentication styles the response

2. Which of the following is the correct way to add a Bearer token in a fetch request header in Svelte?

easy

A. fetch(url, { headers: { 'Bearer': token } })

B. fetch(url, { headers: { 'Auth': 'Bearer ' + token } })

C. fetch(url, { headers: { 'Authorization': 'Bearer ' + token } })

D. fetch(url, { headers: { 'Authorization': token } })

Solution

1. Step 1: Recall Bearer token header format

   The standard header key is 'Authorization' with value 'Bearer ' plus the token.

2. Step 2: Match correct syntax

   fetch(url, { headers: { 'Authorization': 'Bearer ' + token } }) correctly uses 'Authorization' and concatenates 'Bearer ' with the token.

3. Final Answer:

   fetch(url, { headers: { 'Authorization': 'Bearer ' + token } }) -> Option C

4. Quick Check:

   Bearer token header = Authorization: Bearer token [OK]

Hint: Use 'Authorization' header with 'Bearer ' prefix [OK]

Common Mistakes:

• Using wrong header key like 'Auth' or 'Bearer'
• Omitting 'Bearer ' prefix before token
• Passing token without header key

3. What will be the output of this Svelte code snippet when fetching an API with Basic Auth?

const response = await fetch('https://api.example.com/data', {
  headers: {
    'Authorization': 'Basic ' + btoa('user:pass')
  }
});
const data = await response.json();
console.log(data.message);

Assuming the API returns {"message": "Success"} on correct auth.

medium

A. SyntaxError

B. Success

C. Authorization error

D. undefined

Solution

1. Step 1: Understand Basic Auth header

   The code correctly encodes 'user:pass' with btoa and sets 'Authorization' header.

2. Step 2: Predict API response

   With correct credentials, API returns JSON with message 'Success', logged to console.

3. Final Answer:

   Success -> Option B

4. Quick Check:

   Correct Basic Auth returns API success message [OK]

Hint: Basic Auth uses base64 encoded 'user:pass' in Authorization [OK]

Common Mistakes:

• Not encoding credentials with btoa
• Using wrong header key
• Expecting error without wrong credentials

4. Identify the error in this Svelte fetch call for API authentication:

fetch('https://api.example.com/data', {
  headers: {
    'Authorization': 'Bearer token123'
  }
})
.then(response => response.json())
.then(data => console.log(data));

medium

A. Missing await keyword for async fetch

B. Bearer token should be in lowercase

C. Headers object should be outside fetch options

D. No error, code is correct

Solution

1. Step 1: Check fetch usage with promises

   Using .then() is valid without await; async/await is optional here.

2. Step 2: Verify header format and placement

   'Authorization' header with 'Bearer token123' is correct and inside headers object.

3. Final Answer:

   No error, code is correct -> Option D

4. Quick Check:

   fetch with .then and correct headers = valid code [OK]

Hint: Using .then() is valid without await [OK]

Common Mistakes:

• Thinking await is mandatory with fetch
• Assuming 'Bearer' must be lowercase
• Misplacing headers outside fetch options

5. You want to securely store and use an API token in a Svelte app to authenticate requests. Which approach is best practice?

hard

A. Store the token in a Svelte writable store and include it in fetch headers

B. Hardcode the token directly in the fetch call inside the component

C. Save the token in localStorage and read it on every fetch request

D. Send the token as a URL query parameter in fetch requests

Solution

1. Step 1: Evaluate token storage options

   Writable stores in Svelte keep token in memory, safer than localStorage or hardcoding.

2. Step 2: Assess token usage in fetch

   Including token in headers from store is secure and flexible; URL query parameters expose token publicly.

3. Final Answer:

   Store the token in a Svelte writable store and include it in fetch headers -> Option A

4. Quick Check:

   Use writable store for secure token handling [OK]

Hint: Use Svelte stores, avoid hardcoding or URL tokens [OK]

Common Mistakes:

• Hardcoding tokens exposes secrets in code
• Using localStorage risks token theft via XSS
• Sending tokens in URL leaks them in logs