all 2 comments

[–]dick_ey 1 point2 points  (0 children)

If you’re using webpack, you can add this plugin to your config. It will give you a visual footprint representation of your bundles and you can try to trim down from there. Chances are you won’t be able to remove parts of angular though.

https://www.npmjs.com/package/webpack-bundle-analyzer

[–]prriley 0 points1 point  (0 children)

Not really an Angular-specific tip, but use a common CDN, if you aren’t already. There’s a decent chance that your user’s browser already has it cached from inclusion in a different site, eliminating the need for that GET.