Incorporate performance budgets into your build process
Once you’ve defined a performance budget, it’s time to set up the build process to keep track of it. There are a number of tools that let you define thresholds for chosen performance metrics and will warn you if you go over budget. Find out how to choose one that best fits your needs and current setup. 🕵️♀️
Webpack Performance Hints
Webpack is a powerful build tool for optimizing how your code is delivered to the users. It also supports setting performance budgets based on asset size.
Turn on performance hints in the configuration file and Webpack will show you command line warnings or errors when your bundle size grows over the limit. It’s a great way to stay mindful about asset sizes throughout the development.
After the build step, Webpack outputs a color-coded list of assets and their sizes. Anything over budget is highlighted in yellow.
The default limit for both assets and entry-points is 250 KB. You can set your own targets in the configuration file.
The numbers are compared against uncompressed asset sizes. This is not an ideal situation, since most hosting platforms, CDNs and reverse proxy servers compress assets by default. You can give yourself some wiggle room during development, but keep in mind that compression speeds up only the transfer. Browsers still have to parse uncompressed files and this parsing cost is not small, especially on mobile devices.
Bundlesize is a simple npm package that tests asset size against a threshold you’ve set. It can run locally and integrate with your CI.
Run bundlesize CLI by specifying a threshold and the file that you want to test.
bundlesize -f "dist/bundle.js" -s 170kB
Bundlesize will output color-coded test results in one line.
Bundlesize for CI
You’ll get the most value out of bundlesize if you integrate it with a CI to automatically enforce size limits on pull requests. If bundlesize test fails, that pull request will not be merged. It currently works with Travis CI, CircleCI, Wercker, and Drone.
You may have a fast app today, but adding new code can often change this. Checking pull requests with bundlesize will help you avoid performance regressions. Bootstrap, Tinder, Trivago and many others use it to keep their budgets in check.
With bundlesize, it’s possible to set thresholds for each file separately. This is especially useful if you are code-splitting a bundle in your application.
By default, it tests gzipped asset sizes. You can use the compression option to switch to brotli compression or turn it off completely.
Lighthouse is an auditing tool that tests sites in a few key areas — performance, accessibility, best practices and how well your site performs as a progressive web application. You can run it in Chrome DevTools, from the command line, or as a Node module.
It’s sometimes simpler to keep an eye on a single number than individual asset budgets and Lighthouse performance score takes a lot of things into account.
Lighthouse Bot currently integrates only with Travis and runs an audit after you deploy a site to staging server. It enforces budgets based on any of the five scores. In .travis.yml file set targets with
--seo options. Aim to stay in the green zone with a performance score of at least 80.
after_success: - ./deploy.sh # Deploy the PR changes to staging server - npm run lh -- --perf=96 https://staging.example.com # Run Lighthouse test
If the scores for a pull request fall below the threshold you’ve set, Lighthouse Bot can prevent pull request from being merged. ⛔
Lighthouse Bot will then comment on your pull request with updated scores. This is a neat feature which encourages conversation about performance as code changes are happening.
If you find your pull request blocked by a poor Lighthouse score, run an audit with Lighthouse CLI or in Dev Tools. You’ll get a report with details about bottlenecks and hints for simple optimizations.
|Webpack||✅||✘||Easy to set up||Checks uncompressed sizes|
- Checks compressed sizes
- Enforces budgets on PRs
|Works only for PRs on GitHub|
- Enforces budgets on PRs
- Score history in PR comments
- Only checks scores, no other metrics (yet)
- Works only for PRs on GitHub
See it in action
Learn more and put this guide into action: