At that size you are probably still getting the initial, unoptimized experience. There are tools that already work under the hood, though not quite surfaced for

At that size you are probably still getting the initial, unoptimized experience. There are tools that already work under the hood, though not quite surfaced for easy consumption quite yet, which perform Angular 2 template compilation as part of your build process therefore avoiding the need to ship a substantial chunk of the JavaScript to the browser. This shrinks download size, and also makes applications start faster. You can play with it today, using a seed projects like the one I link below. Sometime soon (work in progress, did not announce) the official Angular 2 CLI will also make this very easy. https://github.com/mgechev/angular2-seed https://github.com/mgechev/angular2-seed Build time template compilation helps a lot, though depending on what all features you're using the base size might still be bigger than Angular 1. Still, for most applications the dominant cost is not the number of bytes on the wire, it is the development labor to make it an application work. A2 so far appears to be very strong on this axis.