I’m a technical writer for Google, trying my level best to help make the web faster for everyone, everywhere.
The Service Worker API is the Dremel of the web platform. It offers the ability to intercept requests and respond to them, while also improving reliability and performance through offline access and caching. Even so, service workers can do more than what we’ve commonly used them for. That goes double for improving the performance of multipage websites when we add streaming to the mix.
Streaming isn’t a new concept. You request a resource, but rather than wait for the resource to arrive in its entirety before processing it, you process it in chunks as it arrives over the wire. On the web, this leads to faster rendering. When applied to service workers, this involves placing the markup for common user interface elements of a page in the service worker cache, then combining and streaming that cached markup of the page with markup from the network.
The results are more compelling than you might think, and the end result is a faster and more resilient experience for more people in more situations, and can substantially improve performance even in places where network connectivity is scant. In this session, you’ll find out how to apply this technique, and see how it can improve the user experience.
|The Weird, Yet Practical World of Paint Worklets||CSSConf Budapest||September 2019|
|Make it Boring||JSConf US||August 2019|
|Making a Difference with Differential Serving||Smashing Conference||April 2019|
|Take a (Client) Hint!||FullStack Fest||September 2018|
|Demystifying Performance Timings||Prairie Dev Con||June 2018|
|Faster Fonts for Speed Fanatics||Prairie Dev Con||June 2018|
|Demystifying Performance Timings||PerfMatters Conf||March 2018|
|Faster Fonts for Speed Fanatics||CSSConf AU||March 2018|