that's not the case; here are some good reasons against bundling (from a Stack Overflow post):
- Bundling can lead to trivial cache misses. Any change to any part of your app invalidates the browser cache.
- Bundling can make it harder to leverage a cache of common libraries. If you're using the same version of jquery from the same cdn as everyone else there's a good chance your users will never have to even hit your servers for it.
- Bundling means missing out on HTTP/2's ability to handle multiple asset requests in parallel.
here are some real life numbers from the CloudFlare website:
Access via HTTP Protocol Version Average Page Load time
HTTP 1.x 9.07 sec.
SPDY/3.1 7.06 sec.
HTTP/2 4.27 sec.
yes, we may still need bundling, but for some totally different reasons than performance.
UPDATE: here are other interesting numbers showing latency in the biggest player here: if you expect a high latency then you gain almost nothing by concatenating: but, if you expect low latency concatenating could be in fact much better:
having said that, my initial proposal to bundle on a add-on base makes a lot of sense.
for Plone, bundling for anonymous and authenticated users, leaving the common libraries out, sounds like the best approach.