• Jordan LittleJordan Little, 3 years ago

    In my state there are hundreds of thousands using internet that’s spotty at best. Sub-1mbs connections that are often blanket rural wifi or satellite (high latency).

    By using a service worker and an app frame, you can cache the critical aspects of the site, including content, upon initial load which allows the user to go on browsing even if their connection is weak.

    And it doesn’t specifically cater to those with that need, it makes for a much faster browsing experience even for modern connections. I’ve seen studies showing that for every half-second decrease in perceived load time, revenue goes up 7%.

    All this being said, do what makes sense for the situation. If a brochure site can do its job as a one page HTML doc and you see no benefit to the extra overhead, then it’s no skin from anyone’s back. PWA tech is still being figured out and most browsers don’t support a lot of the requirements.

    0 points
    • Marc EdwardsMarc Edwards, 3 years ago

      Thanks. That’s a good example.

      Shouldn’t browser caching solve that fairly well? Using a service worker means the site can periodically update in the background. Doesn’t that mean it’ll typically use more bandwidth, not less?

      (FWIW, my connection here is not good, and it’s very obvious when a site was built by someone with a fast connection who didn’t consider those without one.)

      0 points