main

Application Acceleration & OptimizationApplication Delivery

How to Find Your Website’s Performance Poverty Line

June 17, 2013 — by Tammy Everts30

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:

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:

performance-poverty-line-bounce
performance-poverty-line-pageviews
performance-poverty-line

Observations

In this case study, we can see two things clearly:

  1. 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.
  2. 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.

Tammy Everts

As a senior researcher, writer, and solution evangelist for Radware, Tammy Everts has spent years researching the technical, business, and human factor sides of web/application performance. Before joining Radware, Tammy shared her research findings through countless blog posts, presentations, case studies, whitepapers, articles, reports, and infographics for Strangeloop Networks. Tammy continues to deepen the publicly available body of web performance and UX research by regularly contributing her insights and research findings to the Radware blog, as well as the performance blog, Web Performance Today: www.webperformancetoday.com.

30 comments

Leave a Reply

Your email address will not be published. Required fields are marked *