javascript - Service workers and page performance -


i'm stuck @ wedding reception don't want @ , i'm driving, i'm reading service workers. i'm on phone can't play thinking if they're viable option improving page performance?

images biggest killer on site , i'm half thinking use service worker cache them page load times down. can tell, browser still makes http request, it's response sw cache, not file location. missing here? there therefore actual benefit doing this?

while regular http cache has lot of overlap serviceworker cache, 1 thing former can't handle dynamically generated html used in many client-side javascript applications. when resources of app cache hits, there still delay javascript compiled , executed before app usable.

addy osmani has demonstrated how serviceworker can used cache shell of app. when dom modified on client, updated in cache. next time url requested, serviceworker replies html ready use before app has booted.

the other advantage regards lie-fi: when seems network available, not enough packets getting through. serviceworkers can afford have near-imperceptible timeout, because can serve cache and wait response load (if ever).


Comments

Popular posts from this blog

get url and add instance to a model with prefilled foreign key :django admin -

css - Make div keyboard-scrollable in jQuery Mobile? -

ruby on rails - Seeing duplicate requests handled with Unicorn -