Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920)

Trying to get a concrete picture of the problem here. Someone shout up if this is wrong.

The loading strategy is:

* Load UI sans-content from the cache
* JS loads content 'include' from network

And the problem is:

* On initial navigation the service worker bootup time (200ms?) delays cached shell render and delays subsequent network request for content

It's still unclear to me how that delay compares to the benefits of rendering without the network. Even if it's only the shell that's rendered without the network, getting the shell & JS from the cache should come with a benefit vs the network.

But yes, as a site adopts SW, there may be particular navigation routes that simply defer to default browser behaviour.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/920#issuecomment-230246297