HTTP requests, heavy/unminified resources, and UI thread blocking should be on the mind of every front-end developer. These are just a few issues that can cause serious bottlenecks in page load times. Having a faster load time equals better search engine rankings, higher conversion rates, and an overall reduction in bandwidth costs. How do we measure all the aforementioned performance killers? How can we bring these measurements into our automated build process to ensure that our site is getting better, and not worse?
Wesley Hales is an author, occasional speaker and engineer at Shape Security. In his spare time, Wesley works on speedgun.io. You can read his ramblings, or follow him on twitter @wesleyhales.