Current page does not respond with a 200 when offline
Stay organized with collections
Save and categorize content based on your preferences.
The Core Progressive Web App checklist says that a PWA
should provide a custom offline page. The Optimial Progressive Web App checklist
says that a PWA should provide an offline experience where the PWA works the same offline as
it does online (wherever network connectivity isn't strictly required).
Learn more in the What is network reliability and how do you measure it? post.
How the Lighthouse offline audit fails
Lighthouse
flags pages that don't respond with an
HTTP 200 response
when offline:
Lighthouse emulates an offline connection using the Chrome Remote Debugging Protocol
and then attempts to retrieve the page using XMLHttpRequest
.
Note: In the Lighthouse report UI the full PWA badge is given when you pass all of the
audits in all of the PWA subcategories (Fast and reliable , Installable , and PWA optimized ).
How to make your PWA work offline
Success: Workbox is the recommended approach for adding
service workers to websites because it automates a lot of
boilerplate, makes it easier to follow best practices, and
prevents subtle bugs that are common when using the low-level
ServiceWorker
API directly.
Add a service worker to your app.
Use the service worker to cache files locally.
When offline, use the service worker as a network proxy to return the
locally cached version of the file.
Resources
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-04-16 UTC.
[null,null,["Last updated 2024-04-16 UTC."],[],[],null,[]]