Building Faster Experiences with Continuous Performance

Posted by Mick McGuinness on 04 April 2019

continuous-performance

These days delivering a fast web application is not an option, it is an essential. Users expect fast response times otherwise the user experience is impaired and they will stop using the application.

Performance is a feature and a Slowdown is a bug

Performance should be feature #1 for any application. Without good performance, any other features you develop are almost irrelevant as they will not get used. Therefore, we would argue that an application slowdown should be treated in the same way as a functional regression. And a slowdown is a bug that you need to identify early – before it affects your end users and becomes more expensive to fix.

What is Continuous Performance?

Companies looking to deliver applications in a faster, more agile way, are adopting approaches like Continuous Integration and Continuous Delivery CI/CD. Just as you have automated testing processes to catch bugs or regressions in any new code you commit, you should also have automated tests to catch performance degradations and stop them progressing through to production where they can become costly. That is what we mean by Continuous Performance.

There are 2 kinds of websites: the quick and the dead. Which one will yours be?

If you would like to learn more about Continuous Performance and how to make it part of your CI/CD processes then download our FREE white paper.

New call-to-action

Tag: Synthetic monitoring, rum, eum, CI, CD

You might also like our WebTuna blog 

Recent Posts