Smaller HTML Payloads with Service Workers

Viewing 4 replies - 1 through 4 (of 4 total)
  • Jose Varghese

    (@josevarghese)

    5 years, 11 months ago

    Thanks for the suggestion, would like to let you know that somewhat a better method is over my mind for better experience and loading. But still this time, I still don’t know whether it can be shipped with SuperPWA or not.

    Ruslan

    (@devprollc)

    5 years, 11 months ago

    Please improve Offline compability, maybe think of PRO version of plugin

    Thread Starter Rookie

    (@alriksson)

    5 years, 11 months ago

    @josevarghese That would be great. Why wouldn’t it be able, just curious to know?

    How is the service worker today as significant improvements can be made for a better experience and loading times.

    Thread Starter Rookie

    (@alriksson)

    5 years, 9 months ago

    @josevarghese Any update on this one? If it wouldn’t be shipped with SuperPWA what would it be shipped with?

    Tell us more, what’s the idea?

    Very interested of improving this:

    Smaller HTML Payloads with Service Workers improves

    By only requesting the contents of a page, the networks payloads become substantially smaller, and the pages can load quite a bit faster. For example, on this site over the past 30 days, page loads from a service worker had a 47.6% smaller network payloads, and a median First Contentful Paint (FCP) that was 52.3% faster than page loads without a service worker (416ms vs. 851ms). In the graph below, you can clearly see the entire distribution shifted to the left:

    • This reply was modified 5 years, 9 months ago by Rookie.
Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Smaller HTML Payloads with Service Workers’ is closed to new replies.