Kind of... HTTP/2's advantages depend on using push, and/or reducing prototcol negotiation latence and round-trip time... with HTTP/2, you don't have to negotiate a new/full TCP connection, which has overhead... also headers are compressed. The differences in compression and push become more pronounced with higher latencies and lower bandwidth.
At the very low bandwidth (2g/edge), the constraint goes the other way, where you don't gain much as the channel is pretty much flooded the entire time and the connection overhead offset is lower. ymmv.
All around, more traditional approaches can have a bigger impact... actually optimizing images, switching to svg where practical and reducing code, markup and stylesheets goes a long way. Reducing server response times is also pretty crucial. If your DBMS is taking 200ms to respond to most requests, your application is already going to be at least that slow... got multiple requests, worse still.
Effective caching strategies are how you overcome a lot of that. There are many pieces, and it's a matter of checking what your bottlenecks actually are, and minimizing your content transferred first.
Yes; Ilya Grigorik, in one of his talks, said that one of LTE’s biggest benefits is the much-lower latency for initial connections. I don’t remember which presentation, though.
At the very low bandwidth (2g/edge), the constraint goes the other way, where you don't gain much as the channel is pretty much flooded the entire time and the connection overhead offset is lower. ymmv.
All around, more traditional approaches can have a bigger impact... actually optimizing images, switching to svg where practical and reducing code, markup and stylesheets goes a long way. Reducing server response times is also pretty crucial. If your DBMS is taking 200ms to respond to most requests, your application is already going to be at least that slow... got multiple requests, worse still.
Effective caching strategies are how you overcome a lot of that. There are many pieces, and it's a matter of checking what your bottlenecks actually are, and minimizing your content transferred first.