[dalore]

Adding http2 is easier then reducing the number of requests.

And infact reducing the number of requests using things like spritemaps, bundling js and css is actually an antipattern with http2.

[jacquesm]

> And infact reducing the number of requests using things like spritemaps, bundling js and css is actually an antipattern with http2.

Those are just ways to lose some of the impact of bloat without addressing the bloat itself.

If you address bloat directly it will benefit all users.

[dalore]

If you shard on http2 it will take longer since now it makes multiple ssl connections which have have the ssl handshake.

With http2 it's all multiplexed into one connection. So you have the one ssl connection, but that one connection has multiplexed connections inside it. And since it's one tcp, the tcp sliding window has opened up and is actually faster then opening a new tcp connection.

[tuxracer]

If you migrate to HTTP2 or move to a host that already supports it then cutting down on "round trips" is an obsolete concern altogether.

[jacquesm]

HTTP2 does not magically bundle all connections to one. It still very much depends on how you build up your page.

[floatboth]

It does not magically split one connections into many. One domain == one connection. Sure it won't undo your "domain sharding" hacks and merge your CDNs, yeah :)