Skip to content
Learn Measure Blog Case studies About
On this page
  • How the Lighthouse Application Cache audit fails
  • Use the Cache API instead of the Application Cache
  • Resources

Uses Application Cache

May 2, 2019 — Updated Aug 28, 2019
Appears in: Best Practices audits
On this page
  • How the Lighthouse Application Cache audit fails
  • Use the Cache API instead of the Application Cache
  • Resources

The Application Cache, also known as AppCache, is deprecated.

How the Lighthouse Application Cache audit fails #

Lighthouse flags pages that use the Application Cache:

Lighthouse audit showing that a page uses the Application Cache

This audit fails when Lighthouse finds a reference to the Application Cache manifest in a page's <html> tag. For example, this markup causes the audit to fail:

<html manifest="example.appcache">
...
</html>
Each Best Practices audit is weighted equally in the Lighthouse Best Practices Score. Learn more in The Best Practices score.

Use the Cache API instead of the Application Cache #

To pass this audit, remove the manifest from your page, and use the Cache API via a service worker instead.

To migrate from the Application Cache to service workers, consider using the sw-appcache-behavior library. This library generates a service-worker-based implementation of the behavior defined in an Application Cache manifest.

See the Current page does not respond with a 200 when offline post for more information about using service workers to make your site work offline.

Resources #

  • Source code for Uses Application Cache audit
  • MDN's Cache page
  • Current page does not respond with a 200 when offline
Last updated: Aug 28, 2019 — Improve article
Return to all articles
Share
subscribe

Contribute

  • File a bug
  • View source

Related content

  • developer.chrome.com
  • Chrome updates
  • Web Fundamentals
  • Case studies
  • Podcasts
  • Shows

Connect

  • Twitter
  • YouTube
  • Google Developers
  • Chrome
  • Firebase
  • Google Cloud Platform
  • All products
  • Terms & Privacy
  • Community Guidelines

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.