Unless the service worker cache storage check is implemented poorly by browsers (that is, it acts like HTTP 1 instead of h2) it should be transferring the same amount of bytes as it does now, only faster. With h2 it’s making the first load (and the check for files from offline) much faster. The service worker adds to the internal cache so the user perceives the page to load faster.
Now, if one only wanted to make the images and JavaScript faster with the SW, but not the original document, then the page will transfer more bytes with h2 as it would serve the document + additional images/JS parts that it would use in the initial request.
Unless I’m wrong about this entirely. If so then someone will hopefully correct me. :p
Brian LePore
@Mantish,
Unless the service worker cache storage check is implemented poorly by browsers (that is, it acts like HTTP 1 instead of h2) it should be transferring the same amount of bytes as it does now, only faster. With h2 it’s making the first load (and the check for files from offline) much faster. The service worker adds to the internal cache so the user perceives the page to load faster.
Now, if one only wanted to make the images and JavaScript faster with the SW, but not the original document, then the page will transfer more bytes with h2 as it would serve the document + additional images/JS parts that it would use in the initial request.
Unless I’m wrong about this entirely. If so then someone will hopefully correct me. :p