Karolina Szczur
October 12, 2023
We’ve always been strong advocates of proactive web performance approach. As a small team, we even more so understand how hard it is to undo already shipped changes or prioritise work that’s often considered non-business critical. For that reason, over three years ago, we released Pull Request Reviews to help teams monitor performance before releasing to production, directly in their pull requests. Since then, we’ve learned a lot about complexities of comparisons and what we could do to offer the most clear and actionable web performance report at the point when it matters most.
From those trials, errors and challenges faced by our customers and the wider community, we defined key points to solve with the next iteration of Pull Request Reviews:
With the new iteration of Pull Request Reviews, we addressed most of the common pain points described above. Now, with Pull Request Reviews, your team can:
We reimagined the report posted when a Pull Request Review is completed to highlight the most important information to take action:
If your team isn’t using GitHub, you can get the same markdown report through the Pull Request Reviews CLI command (with the --markdown > your-file.md flag) described below.
Not every team uses GitHub to collaborate on code. If that’s you, or your team would like to perform tests in continuous integration and delivery tools, you can use the same Pull Request Review functionality thanks to the new calibre site create-pull-request-review command:
1calibre site create-pull-request-review \2 --site "my-shopfront-production" \3 --title "(feat): add lightbox to PDP" \4 --url "https://pr-123.example.com" \5 --branch "feat/add-lightbox-to-pdp" \6 --sha="1234567890abcdef1234567890abcdef12345678" \7 --waitForResult \8 --failOnUnmetBudget \9 --markdown > comparison_report.md
The command line interface makes it trivial to perform comparisons between two environments, such as staging and production, work in progress branch and production, and so on. You can use Bitbucket, GitLab, CircleCI, Jenkins or any other CI/CD tool of your choice.
If you’d like to be more proactive than relying entirely on performance budget alerts (happening post release), you can fail checks when budgets are exceeded. With the check in place, negative changes to performance are much less likely to reach your audience.
If you’d like to find out more about Pull Request Reviews, here are a few helpful resources:
If you’re new to Calibre, you can sign up for a free 15-day trial. Need more time? We’ll happily extend the trial period, too.
We will send you articles, tools, case studies and more, so you can become a better performance advocate.
Harry Roberts
Consultant Web Performance Engineer