First, I'm going to tell you that my WebPack view and other packers is a little different from your vision. And they may have other users who will disagree with that view bridge that I will give you.Perhaps the main benefit of WebPack is the Developer. Actually at my point of view the end user of WebPack is the own must and not the user who will access the site. I'll explain why.I believe that the main advantage of packagers is to do a part of the work of developers and automate various routines... I justifi with these examples. WebPack goes prefix all your CSS styles to vc have no problem crossbrowser. He will compile your SASS, SCSS, LESS or Stylus on a standard style sheet .CSS that the browser will be able to read. It will make the includes of everything you vc want in the document, it will use something like Babel for example to treat your compatibility Java Script for old browsers. He will minify your code, remove comments etc...Then I see that the end user is Dev. and not the user who will access the platform. But logically I see pro user advantages of tb system as vc will deliver to it an optimized code, but that could have been optimized in hand, not necessarily with a Webpack of life. Until pq, in fact much of what WebPack is good practices that everyone should do, because they are the ones that will directly impact the user of the system as minify the code and prefix the properties of css, or convert images to Base64 or generate sprites, this will bring a better user experience and a better delivery performance, but this is all good practices and that with WebPack it gets easier to do.