Re: [w3c/ServiceWorker] Questions regarding inevitable nature of performance gains and losses of ServiceWorker (Issue #1667)

> A1

- There will always be a startup overhead cost to a ServiceWorker; this can be partially mitigated by [navigation preload](https://w3c.github.io/ServiceWorker/#navigation-preload-manager) creating a racing request to the server.
- If someone told me their site performance was bad, a ServiceWorker is one of the last things on the list of things I would suggest to them unless their site is explicitly expected to be used in scenarios with bad network connectivity like a transit app for subway riders and profiling demonstrated their problems were due to network flakiness.  [Alex Russell](https://infrequently.org/) of Service Workers fame has written a lot in the space of site performance, which is a much larger discussion than just Service Workers, but is discussed in his analyses in that larger context, and I would suggest checking out his extensive writings on the subject.

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

Message ID: <w3c/ServiceWorker/issues/1667/1399802696@github.com>