offline-fallback
/offline-fallback
Use when adding PWA capabilities, implementing a service worker, or improving the experience for users on unreliable network connections.
- Author
- thedaviddias ↗
- Repository
- front-end-checklist ↗
- Licence
- MIT
- Last repository change
- 06.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when adding PWA capabilities, implementing a service worker, or improving the experience for users on unreliable network connections.
Original author description
Use when adding PWA capabilities, implementing a service worker, or improving the experience for users on unreliable network connections.
How it works
- Quick Reference
- Check
- Fix
- Explain
- Code Review
SKILL.md preview
---
name: offline-fallback
description: "Use when adding PWA capabilities, implementing a service worker, or improving the experience for users on unreliable network connections."
metadata:
category: performance
priority: low
difficulty: beginner
estimatedTime: "20"
source: frontendchecklist.io
url: https://frontendchecklist.io/rules/performance/offline-fallback
---
# Provide an offline fallback page
The browser's default offline error screen ("No internet connection") is confusing and completely outside your brand. A custom offline page maintains the user experience, reinforces trust, and can surface cached content or useful actions — such as enabling users to continue reading a cached article or queuing a form submission for later.
## Quick Reference
- Create a minimal /offline HTML page that works without any network requests
- Pre-cache the offline page during the service worker install event
- Intercept failed navigation requests and serve the offline page instead
- Include helpful guidance so users know what to do while offline
## Check
Check whether the site shows a custom offline fallback page when the network is disconnected and a navigation request cannot be fulfilled.
## Fix
Create a self-contained /offline page and configure the service worker to pre-cache it and serve it for failed navigation requests.
## Explain
Explain how a service worker can intercept failed network requests and return a cached offline fallback page to the user.
## Code Review
Review the service worker fetch handler and the offline page markup. Verify the offline page is pre-cached at install time, that it does not depend on external resources, and that the fallback is only served for navigation requests (not sub-resources).
---
For full implementation details, code examples, and framework-specific guidance,
see `references/rule.md`.
Rule page: https://frontendchecklist.io/rules/performance/offline-fallback
Files in this package (2)
- SKILL.md 2 KB
- references/rule.md 7 KB
Versions
The database has no other skills named offline-fallback.
Database snapshot: 13.11.2026 · package version 5d8e55f210a0 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100pwa-stinger
Implement browser PWA manifest, service-worker lifecycle and bounded public offline assets. Use for scoped PWA/offline changes. Read README.md for the guide map. - 100service-worker
Use when auditing repeat-visit performance, adding offline support, or evaluating PWA readiness for a web application. - 90fec-pwa-implementation
Use when adding or reviewing Progressive Web App capabilities such as installability, manifest metadata, Service Worker registration, Workbox caching, offline fallback, app update prompts, maskable icons, or iOS PWA compatibility. Do not use for general API caching or… - 100enhance-pwa
Add or upgrade PWA features: manifest, service worker, offline mode, install prompt, push, background sync. Use when "make it a PWA", "offline support", or "install prompt". Native → mobile-capacitor-platform. - 95pwa-development
Progressive Web App development for installable, offline-capable web applications. Use when building PWAs, implementing service workers, or creating offline-first experiences. - 95pwa
Progressive Web App with Next.js — service workers, offline support, push notifications, install prompts, caching strategies. Use when adding offline capabilities, push notifications, app-like install experience, or background sync.