Start URL responds with a 200 when offline
If Lighthouse does not receive an HTTP 200
response when accessing a page from the start_url,
then either the start_url isn't correct,
or ths page is not accessible offline
(see also What is network reliability and how do you measure it?).
Lighthouse flags web apps when the start URL doesn't respond with a 200 when offline
Recommendations
- Check that the
start_urlin your manifest is correct Add a web app manifest. - 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.
Use what you learn in this step-by-step, hands-on codelab to learn how to add a service worker into your own app.
Codelabs
Learn more in Current page responds with a 200 when offline.
Each PWA audit is weighted equally in the Lighthouse PWA Score, with the exception of three manual audits: Site works cross-browser, Page transitions don't feel like they block on the network, Each page has a URL. Learn more in The Progressive Web App score.
More information
Start URL doesn't respond with 200 when offline audit source
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.