The performance poverty line is the plateau at which your website’s load time ceases to matter because you’ve hit close to rock bottom in terms of business metrics. If your pages are well below the performance poverty line, making them a couple of seconds faster doesn’t help your business. Here’s how to find the poverty line for your site.
Why you need to know your site’s performance poverty line
What’s the ideal load time for a typical web page? I encounter this question a lot, and there’s no single correct answer. Depending on whom you ask, you’ll hear a range of answers, including:
- 100 milliseconds
- 400 milliseconds
- 1 second
- 2 seconds
- 3 seconds
- And so on.
Having an ambitious performance goal, such as delivering pages in 2 seconds or less, is an essential part of your web strategy. But in conjunction with that goal, you also need to know at what point your site bottoms out in terms of delivering conversions, page views, revenue, stickiness, or whatever metrics are key for your business.
To illustrate this, we recently looked at data for five of our ecommerce customers’ sites, comparing sets of their 2010 and 2012 numbers for bounce rate, page speed, and conversion rate. After plotting the data on a set of graphs, a clear snapshot emerged:
Observations
In this case study, we can see two things clearly:
- The performance poverty line for these sites was around 7-8 seconds across all three metrics. What’s noteworthy here isn’t just this number, but how incredibly consistent it is across all metrics.
- When pages are slow, business metrics suffer more now than they did two years ago. For example, look at the final graph. A page that took 6 seconds to load in 2010 suffered a -40% conversion hit. Today, a 6-second page takes a -50% hit. Or look at the second graph, where you see that a relatively fast 4-second page suffers a -30% hit in page views per visit in 2010, but in 2012 a 4-second page takes more than a -40% hit. This indicates a substantial change in consumer expectations. Simply put, people are less willing than ever to suffer slow pages.
How to measure the poverty line for your own site
Your results may vary: 7 seconds may not be the poverty line for your site. Fortunately, the process for identifying the low end of your site’s performance threshold is fairly straightforward. All you need is access to a statistically significant amount of your web data, plus whatever analytics tool you use for tracking key metrics.
Step 1: Identify the metrics you want to measure.
If you run an ecommerce site, then you’ll obviously want to measure revenue. If you’re a SaaS, then you may focus on conversions. If you’re a media site, then page views and bounce rate matter.
Step 2: Gather data.
To ensure that you get statistically relevant results, the more data you can gather, the better. When we conducted our tests, we aggregated millions of transactions that took place over a single month.
Step 3: Plot data.
We found that using the x axis for load time and the y axis for the metric yielded easily readable graphs.
Step 4 (optional): Compare to previous time frames.
If you want to find out if your customers’ load time expectations have changed over time, as we found in our test, repeat steps 1 through 3 for an earlier time period. Depending on how far back your data goes, it would be extremely interesting to track changes year over year.
Step 5: Share your findings.
Evangelize your results within your organization. Knowing how low your bar can go is, in its own way, as critical as knowing how high you want it to be. And incidentally, as you may have already noted when looking at the graphs above, this process will also give you valuable insight into how your metrics are affected at other points on your graphs.
I’m very curious to find out if our 7-second poverty line is consistent across other sites, or if it varies. If you go through this exercise, I’d love to hear your results.
Very cool stuff.
I love the term “performance poverty line”. The Gates Foundation should be exhorting the world to push 90% of websites to move above the poverty line by 2030. 🙂
What exactly is being shown in the graphs?
– Are your lines connecting data points or best fit?
– How many points are used in the aggregations?
– What’s the size of the aggregation buckets?
Did you decide to pump window.performance metrics into your analytic solution to get the average page load time? Im trying to understand how you determine the page load time for those millions of transactions.
[…] Tammy Everts, RADWARE,LTDのブログによれば、Eコマースサイトのページが表示されるまで3秒を経過していると、約4割のお客様がサイトから離れていく(Fall-off)とレポートされています。 […]
[…] How to Find Your Website’s Performance Poverty Line […]
[…] web “performance poverty line” still rings true. You can find a more recent reworking here, although the graphs are the […]
[…] The demand for loading speed increases with time. For example, a page that took six seconds to load in 2010 suffered a -40 percent conversion hit, while the same loading time in 2014 results in a -50 percent conversion hit. (source) […]
[…] Radware also discovered in another study that the demand for loading speed has increased over time. For example, in 2010 a page that took six seconds to load witnessed a -40 percent conversion hit. In 2014? That same loading time suffered -50 percent conversion hit. […]
[…] In 2010, Radware reported : […]
[…] your site’s performance poverty line. Or use our findings that, for a typical ecommerce site, the performance poverty line is around 8 seconds. (Performance poverty line = the plateau at which your website’s load time ceases to matter […]
[…] Η ζήτηση για ταχύτερα sites έχει αυξηθεί με την πάροδο του χρόνου. Για παράδειγμα, το 2010 μια σελίδα που χρειαζόταν 6 δευτερόλεπτα για να “φορτώσει” παρουσίαζε μείωση των conversions κατά 40%. Το 2014, για τον ίδιο χρόνο τα conversions μειώθηκαν έως και 50%! [πηγή] […]
[…] Η ζήτηση για ταχύτερα sites έχει αυξηθεί με την πάροδο του χρόνου. Για παράδειγμα, το 2010 μια σελίδα που χρειαζόταν 6 δευτερόλεπτα για να “φορτώσει” παρουσίαζε μείωση των conversions κατά 40%. Το 2014, για τον ίδιο χρόνο τα conversions μειώθηκαν έως και 50%! [πηγή] […]
[…] Just a few seconds of lost time can crush conversion rates, as this graph indicates: […]
[…] they won’t rank it highly. A good place to start is to figure out where your site’s performance poverty line is and go from […]
[…] Radware also discovered in another study that the demand for loading speed has increased over time. For example, in 2010 a page that took six seconds to load witnessed a -40 percent conversion hit. In 2014? That same loading time suffered -50 percent conversion hit. […]
[…] How to Find Your Website’s Performance Poverty Line […]
[…] and a delay of even a single second can lead to drastic results for your conversions. According to a study by Radware, a six second page load time meant a 40% drop in conversions for an average website in 2010. Fast […]
[…] Radware reports that as of 2014 a website taking 6 seconds to load showed a decrease of 50% in their conversion rate. (Conversion rate is the percentage of users who take the action you want them to on your website. This may be purchasing products online or simply contacting you.) […]
[…] Radware also discovered in another study that the demand for loading speed has increased over time. For example, in 2010 a page that took six seconds to load witnessed a -40 percent conversion hit. In 2014? That same loading time suffered -50 percent conversion hit. […]
[…] Y es que la demanda de velocidad e carga ha aumentado con el paso del tiempo. De esta forma, una página con una velocidad de carga de 6 segundos podía reducir su porcentaje de conversión en un 40% mientras que en 2015 esa misma web perdería un 50% del porcentaje de conversión, tal como analizó Radware en un estudio. […]
[…] During a different study, Radware revealed that website users are becoming more demanding of web speed, that is they have higher expectations, than even merely a few years ago. But what do users expect? […]
[…] This study has come to the conclusion that the demand for superior loading speeds has increased over the last few years. A page clocking in at six seconds would mean a 40 percent hit in conversions four years ago. Today, I guess that figure would be well above 50 percent. […]
[…] This study has come to the conclusion that the demand for superior loading speeds has increased over the last few years. A page clocking in at six seconds would mean a 40 percent hit in conversions four years ago. Today, I guess that figure would be well above 50 percent. […]
[…] How to find your website’s performance poverty line […]
Our Report gives you the full picture on how your site loads and helps you detect where bottlenecks are.
What’s up Dear, are you genuinely visiting this web site daily,
if so then you will without doubt take good know-how.
It’s hard too come by knowledgeable people iin this particular topic, however, you seem like you know what you’re talking
about! Thanks
What’s up Dear, are you truly visiting this website regularly, if so after that you will absolutely obtain pleasant know-how.
How you guys figured this out is beyond me. Very interesting take. I had to re-read 4 times before I grasped it. very good. thanks!
It’s genuinely very complex in this busy life to listen news on TV,
so I only use world wide web for that purpose,
and obtain the latest information.
Great information on page performance poverty line.
[…] How to Find Your Website’s Performance Poverty Line […]
Great information on page performance poverty line.
[…] How to Find Your Website’s Performance Poverty Line […]
[…] effect on the conversion rate is maximum as research by Radware stated that only a 4-second delay can take up to -40% hit in the conversion graph. This sums up […]