Handling navigation requests
Navigation requests are requests for HTML made whenever you enter a new URL in the navigation bar, or follow a link on a page. This is where service workers make their biggest impact on performance: by using a service worker to respond without waiting for the network, you can ensure that navigations are reliably fast and resilient.
Home Articles Resources Network reliability Handling navigation requests Stay organized with collections Save and categorize content based on your preferences. Respond to navigation requests without waiting on the network by using a service worker. Jeff Posnick Navigation requests are requests for HTML documents made by your browser whenever you enter a new URL in the navigation bar, or follow a link on a page taking you to a new URL. This is where service workers make their biggest impact on performance: if you use a service worker to respond to navigation requests without waiting for the net
Explore this link on the map →related reading
- Service worker overview | Workbox | Chrome for Developersdeveloper.chrome.com
- Service worker registration | Articles | web.devweb.dev
- The service worker lifecycle | Articles | web.devweb.dev
- Use the Service Worker Static Routing API to bypass the service worker for specific paths | Blog | Chrome for Developersdeveloper.chrome.com
- Service Worker API - Web APIs | MDNdeveloper.mozilla.org
- A service worker's life | Workbox | Chrome for Developersdeveloper.chrome.com
- How's Linear so fast? A technical breakdownperformance.dev
- Populating the page: how browsers work - Performance | MDNdeveloper.mozilla.org
- The service worker lifecycle | Articles | web.devweb.dev
- workbox-precaching | Modules | Chrome for Developersdeveloper.chrome.com
- What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? · Issue #124 · w3c/navigation-timing · GitHubgithub.com
- Web Applications 101 - Robin Wieruchrobinwieruch.de