3 ms·
Here's a pattern: since your Service Workers won't run the first time a user visits a page, you should send server-side rendered content to the user that also h
by muthdra 8y ago
Here's a pattern: since your Service Workers won't run the first time a user visits a page, you should send server-side rendered content to the user that also has a line that installs a Service Worker after the page is fully loaded from base HTML with useful data.
The second time the user visits your page, the Service Worker will ideally be installed and will run, intercept the call and download your components separately, when they're needed, and save them on cache, as opposed to let the server render the components to base HTML.
Third time forwards, components are loaded directly from cache and rendered by the Service Workers.
- sebazzz 8y agoWith a service worker you will often also cache the initial html, so it is then really all dependent on the speed of the code.
- kinlan 8y agoThis is exactly the pattern I use in https://github.com/PaulKinlan/webgde-deck https://github.com/PaulKinlan/webgde-deck and whilst is a little harder to mange it's incredibly fast https://webdev.topicdeck.com/ https://webdev.topicdeck.com/ is an example of it hosted.
- mxstbr 8y agoFYI I'm getting "542: An error occured with your deployment" when clicking that link!