Service workers in Svelte - Performance & Optimization

Performance: Service workers

MEDIUM IMPACT

Service workers affect page load speed by enabling offline caching and background resource fetching, improving repeat visit performance and responsiveness.

Caching static assets for faster repeat page loads

Svelte

self.addEventListener('fetch', event => {
  event.respondWith(
    caches.match(event.request).then(cachedResponse => {
      return cachedResponse || fetch(event.request);
    })
  );
});

Serves cached resources instantly when available, reducing network requests and speeding up load.

📈 Performance GainReduces network latency impact, improves LCP and INP on repeat visits

Caching static assets for faster repeat page loads

Svelte

self.addEventListener('fetch', event => {
  event.respondWith(fetch(event.request));
});

Always fetches from network, ignoring cache, causing slower repeat loads and more network usage.

📉 Performance CostBlocks rendering on network latency every time, no caching benefit

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No caching in service worker	None	0	Network delays increase paint time	[X] Bad
Cache-first strategy in service worker	None	0	Faster paint due to cached resources	[OK] Good

Rendering Pipeline

Service workers intercept network requests before they reach the browser rendering pipeline, serving cached responses or fetching fresh data. This reduces network delays and can improve rendering start times.

→Network Request

→Resource Fetching

→Rendering Start

⚠️ BottleneckNetwork Request stage when service worker fetches from network

Core Web Vital Affected

LCP, INP

Service workers affect page load speed by enabling offline caching and background resource fetching, improving repeat visit performance and responsiveness.

Optimization Tips

1Use cache-first strategy to serve assets quickly on repeat visits.

2Avoid blocking service worker activation with long caching tasks.

3Monitor service worker cache size to prevent storage bloat.

Performance Quiz - 3 Questions

How does a cache-first service worker strategy affect page load performance?

A It reduces network requests and speeds up repeat page loads

B It always fetches from network causing slower loads

C It blocks rendering until all assets are fetched

D It increases bundle size significantly

DevTools: Application panel in browser DevTools

How to check: Open DevTools, go to Application > Service Workers to see registered workers and cache storage. Use Network panel to verify requests served from service worker.

What to look for: Look for 'from ServiceWorker' label on network requests and check cache storage size and contents

Practice

1. What is the main purpose of a service worker in a Svelte app?

easy

A. To enable offline support and faster loading by caching files

B. To handle user authentication and sessions

C. To manage component state and props

D. To style components dynamically

Solution

1. Step 1: Understand service worker role

   Service workers run in the background and cache files to allow offline use and faster loading.

2. Step 2: Differentiate from other app features

   User authentication, state management, and styling are handled by other parts of the app, not service workers.

3. Final Answer:

   To enable offline support and faster loading by caching files -> Option A

4. Quick Check:

   Service workers = offline support and caching [OK]

Hint: Service workers cache files for offline use [OK]

Common Mistakes:

• Confusing service workers with authentication
• Thinking service workers manage UI state
• Assuming service workers handle styling

2. Which is the correct way to register a service worker in a Svelte app?

easy

A. navigator.serviceWorker.register('/service-worker.js')

B. serviceWorker.register('/service-worker.js')

C. navigator.registerServiceWorker('/service-worker.js')

D. register.serviceWorker('/service-worker.js')

Solution

1. Step 1: Recall the correct API

   The standard API to register a service worker is navigator.serviceWorker.register().

2. Step 2: Check method and object names

   Only navigator.serviceWorker.register('/service-worker.js') uses the correct object (navigator.serviceWorker) and method (register).

3. Final Answer:

   navigator.serviceWorker.register('/service-worker.js') -> Option A

4. Quick Check:

   Use navigator.serviceWorker.register() [OK]

Hint: Use navigator.serviceWorker.register() to register [OK]

Common Mistakes:

• Using wrong method names like registerServiceWorker
• Calling register on wrong objects
• Missing navigator or serviceWorker in the call

3. What will happen if you try to register a service worker in a browser that does not support it, using this code?

if ('serviceWorker' in navigator) {
  navigator.serviceWorker.register('/sw.js')
    .then(() => console.log('Registered'))
    .catch(err => console.error('Failed', err));
} else {
  console.log('No support');
}

medium

A. Registers the service worker anyway

B. Throws an error because serviceWorker is undefined

C. Logs 'No support' and does not attempt registration

D. Logs 'Registered' even if unsupported

Solution

1. Step 1: Check the feature detection condition

   The code checks if 'serviceWorker' exists in navigator before registering.

2. Step 2: Understand behavior if unsupported

   If unsupported, the else block runs, logging 'No support' and skipping registration.

3. Final Answer:

   Logs 'No support' and does not attempt registration -> Option C

4. Quick Check:

   Feature check prevents errors = logs 'No support' [OK]

Hint: Check 'serviceWorker' in navigator before registering [OK]

Common Mistakes:

• Assuming registration runs without support
• Expecting errors instead of safe fallback
• Confusing logs from then/catch with else block

4. Identify the error in this service worker registration code snippet:

if (navigator.serviceWorker) {
  navigator.serviceWorker.register('/sw.js')
    .then(() => console.log('Registered'))
    .catch(err => console.error('Failed', err));
}

medium

A. The catch block is incorrectly placed

B. register() method is missing parentheses

C. The path '/sw.js' must be absolute URL

D. Should check 'serviceWorker' in navigator, not just navigator.serviceWorker

Solution

1. Step 1: Analyze the feature detection condition

   The code checks if navigator.serviceWorker exists directly, which can cause errors if undefined.

2. Step 2: Correct way to check support

   The proper check is 'serviceWorker' in navigator to safely detect support.

3. Final Answer:

   Should check 'serviceWorker' in navigator, not just navigator.serviceWorker -> Option D

4. Quick Check:

   Use 'serviceWorker' in navigator for support check [OK]

Hint: Use 'serviceWorker' in navigator, not navigator.serviceWorker alone [OK]

Common Mistakes:

• Checking navigator.serviceWorker directly without 'in'
• Misplacing catch block
• Thinking path must be full URL

5. You want your Svelte app to update the cached files when a new service worker version is available. Which approach correctly handles this scenario?

hard

A. Reload the page immediately after registering the service worker

B. Listen for 'updatefound' event on registration and call skipWaiting() in the new worker

C. Unregister the old service worker manually before registering a new one

D. Do nothing; service workers update automatically without extra code

Solution

1. Step 1: Understand service worker update process

   When a new service worker is found, the 'updatefound' event fires on the registration.

2. Step 2: Use skipWaiting() to activate new worker immediately

   Calling skipWaiting() on the new worker lets it take control without waiting for old pages to close.

3. Step 3: Evaluate other options

   Reloading immediately or unregistering manually is not recommended; automatic updates require event handling.

4. Final Answer:

   Listen for 'updatefound' event on registration and call skipWaiting() in the new worker -> Option B

5. Quick Check:

   Use 'updatefound' + skipWaiting() to update cache [OK]

Hint: Use 'updatefound' event and skipWaiting() to update cache [OK]

Common Mistakes:

• Ignoring updatefound event
• Reloading page too early
• Unregistering service workers unnecessarily
• Assuming automatic update without code