|
|
|
|
|
|
by jiggawatts
638 days ago
|
|
|
> if you have a site with regular user engagement. Ah, gotcha: this is a new Google standard that helps Google sites when browsed using Google Chrome. Everyone else will discover that keeping the previous version of a library around at build time doesn’t fit into the typical build process and won’t bother with this feature. Only Facebook and maybe half a dozen similar other orgs will enable this and benefit. The Internet top-to-bottom is owned by the G in FAANG with FAAN just along for the ride. |
|
|
Just about any e-commerce site will involve a few pages to go through search, product pages and checkout.
Most news sites will likely see at least 2-3 pages loaded by a given user over the span of a few months. Heck, even this site could shave 20-50% for each of the pages a user visits by compressing out the common HTML: https://use-as-dictionary.com/generate/result.php?id=d639194...
Any place you'd justify building a SPA, by definition, could also be a multi-page app with dictionaries.
If you have a site that visitors always bounce immediately and only visit one page in their lifetime then it can't help, but those tend to be a lot less common.
It doesn't have to be a huge site to benefit, it just needs users that regularly visit to show large gains.
As CDNs implement support, the effort involved in supporting it will also drop, likely to the point where it can just be a checkbox to generate and use dictionary-based compression.