SEO & Performance
Service Worker Cache Planner
Pick the request categories your app handles, choose a caching strategy for each, and get ready-to-ship service worker code. Everything is planned locally — your plan never leaves the page.
Caching strategies at a glance
How it works
Each row maps a category of requests to a caching strategy and a URL match expression.
Routes are registered top to bottom, so the first match wins — more specific
categories are placed before catch-alls such as third-party requests. The Workbox output
uses registerRoute() with the matching strategy class, while the vanilla
output writes a plain fetch handler using the Cache API. Nothing is
uploaded; the whole plan is generated in your browser and the current plan is mirrored
in the URL fragment so it can be bookmarked or shared.