This is exactly why it's important that they publish their figures - so you can make a decision if it's works for you after weighing the tradeoffs. For high-traffic properties (Google, CDNs, Netflix), 3% can easily translate to millions of dollars saved - they could hire an entire team just to deal with the HTTP complications.

Don't forget the 7% throughput increase on mobile. That's a big deal, especially given that mobile users account for the majority of network traffic these days.

And 3% is still a lot if you're looking at global Internet traffic.

My PiHole is currently dropping about 20% of all requests. How about we get rid of all of those and see a REAL speed boost, especially on mobile?

3% of HTTP traffic is a lot.

Web page weight has increased 300% on average in the last decade only.

Most of it is garbage that doesn't need to be there and is shoved in people's faces because it makes other people money/power.

Ex: Why does clicking on a location link in google search load a big slow SPA to display a list of "cards" instead of just having a maps/web link in the search results?

I thought it's because Google isn't allowed to promote Google Maps in its search results, but a cursory search didn't yield any evidence.

Presumably if Search did link to Google Maps, other geographic information systems would have to be represented, just like various streaming platforms are represented in the video tab.

3% less garbage is still a lot. Would you rather more garbage?

3% less garbage is good, but 100% less would be preferable.

Unless you maintain web servers or http proxies (Maintain as in, nginx/IIS/etc core team) Then it really makes no difference as a user.

Nobody has moved over to HTTP2 yet, let alone HTTP3.