Tim Kaldec has measured the JavaScript bytes and the JavaScript CPU time for a bunch of sites.
Right now, if you’re using a framework to build your site, you’re making a trade-off in terms of initial performance—even in the best of scenarios.
Some trade-off may be acceptable in the right situations, but it’s important that we make that exchange consciously.
No surprises there. Perhaps the folks at Jira should take a good look at this 😉
The Cost of Javascript Frameworks →
Related: The Cost of JavaScript (2017) and The Cost of JavaScript in 2018 by Addy Osmani.