Be the first to like this
Keeping a pulse on performance is important and proves difficult in a rapidly changing environment. One release to the next can have a significant impact on performance. Introducing performance budgets can lend a relatively simple safety net to catch unintended swings in resources or changes in timing during page load, that might have otherwise go unnoticed.
I’ll discuss how to create good performance budgets, why it’s important to have them in place, and tell a true story of how Zillow was able to respond quickly in a case when budgets were exceeded.
In telling this story, I will provide supporting evidence to debunk why “onload” isn’t a good measure of perceived performance, show real business Intelligence data supporting how it’s possible to deliver content that users want without impacting perceived performance, and tie these events together with RUM data that enables the best decision for the engineering team to support the business and ultimately the customer.