When it comes to web performance, it’s always a give and take game. Do you really need that script or 3rd party asset, and if so, what purpose or functionality does it serve? Is it something you can live without? There is always a good balance that must be found between performance, functionality, UX, and design. That is why it is important to calculate and set what we call a web performance budget and try to stick to it as close as possible. On average, 39 percent say speed is more important than functionality for most websites. – Compuware Survey Web Performance Budget What is a web performance budget? A web performance budget is a group of limits to certain values that affect site performance that should not be exceeded in the design and development of any web project. This could be the total size of a page, size of images you are uploading, or even the number of HTTP requests that your webpage generates. The term “performance budget” has come up quite a few times in the past as bridging the gap between design and performance is always a tricky one. Brad Frost touched on the subject in his post about performance as design. Tim Kadlec discussed the importance
Share This

We are using cookies on our website

Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.