The various studies claim many different things when it comes to the impact that the performance of the system has on user experience. Some of the most frequently quoted “facts” are:
- Adding 1 second to the search time, the number of searches in Bing dropped by 1.5%.
- A/B tests in Amazon revealed that each 100ms in the time it took to load a page reduced the sales of Amazon by 1%.
- According to Akamai, 75% of online shoppers who experience a crash, freeze or slow render time will no longer buy from that site.
These quotes seem to carry weight but when you dig deeper, there is not much evidence to back these claims. The statements either describe individual applications, are missing the datasets the claims build upon or expose the results of surveys instead of monitoring actual user experience.
So if you are running a digital business, what kind of an impact does a poorly performing application really have? In this series of articles we are approaching the subject based on the hard facts, we have extracted from real-world applications monitored by Plumbr.
Let us start by analyzing the impact that performance has on the amount of users who abandon the original operation. The best way to think of this is to imagine waiting for a slow page to load. How quickly do you start reloading the page, close the browser tab or just go back to Google to find alternatives? Apparently we have the answer:
To interpret the data visualized in the chart above, let us look at the following examples:
- With response times less than 2 seconds, 3% of the users abandoned such operations.
- With operations taking from 2 up to 4 seconds, the number of users aborting the transactions grew to 6%.
- When the user-initiated operation took more than 32 seconds to complete, 34% of the users just gave up.
To summarize, we can say that a two-fold increase in response time makes the user 63% more likely to abandon the transaction.
The data above represents five billion user interactions with 500 different web-based applications. Whenever a user aborted an operation, it triggered a specific event captured by Plumbr. Based on these events, we aggregated, cleaned and clustered the data. In the following posts, we are going to expose the dataset itself along with a more detailed analysis.