Cheat Sheet: Everything you wanted to know about web performance but were afraid to ask

[For a comprehensive directory of performance-related research, tools, and tips, visit the Web Performance Hub. To see some of the most compelling stats in visual form, check out these cool infographics.]

I don’t know about you, but I’m a freak for stats. Up until a couple of years ago, though, my jones for web performance numbers had to go unsatisfied, because the research landscape was pretty barren.

Fortunately, the landscape is looking a lot less bleak these days. Now everyone from Amazon to Google has publicized their findings – alongside research heavy hitters like Forrester and Aberdeen – about how site speed improvements affect user behavior and business metrics such as conversion and revenue.

For obvious reasons, I have a vested interest in collecting all this data. In my line of work, I never know when I’m going to need to pull out a stat on something like, say, how many stock brokers would jump ship on their brokerage as a result of poor mobile web performance. (Answer: 57%) I like to be ready for every question – and if I’m not totally ready, I at least want to have enough information that I can make a decent guess without sounding full of BS.

If you’ve ever found yourself trying to rationalize performance spending to your boss or co-workers – or if you, like me, have an unhealthy relationship with statistics – here’s a cheat sheet of stats and sources you can pull from for your next proposal or awkward elevator conversation.

User behavior and expectations about web performance

In 2006, the average online shopper expected a web page to load in 4 seconds. Today, that same shopper expects your page to load in 2 seconds or less. [Source: Forrester Consulting]

  • Web site performance is second only to security in user expectations.
  • 56% of online bankers and brokers expect web pages to load in 2 seconds or less.
  • Poor website performance leads to dissatisfaction more often than any other factor. Sixty-four percent of online US bankers and brokers have had a dissatisfying experience when servicing their accounts. Web performance is far and away the biggest reason for this dissatisfaction.
  • As online tasks get more urgent or complex, online users are less likely to try later and more likely to move to more expensive channels to complete the transactions. Fifty-six percent of online bankers would move to offline channels to ask a general account question; 54% of online brokers would move to offline channels to trade investments if the website was unavailable or slow to respond.
  • 48% of online bankers and brokers said that poor performance had an impact or significant impact on their likeliness to recommend a firm’s services to a friend or family member. [Source: Forrester Consulting]

Users who experience a 2-second site slowdown make almost 2% fewer queries, click 3.75% less often, and report being significantly less satisfied with their overall experience. [Source: Microsoft and Google]

  • 57% of online consumers will abandon a site after waiting 3 seconds for a page to load.
  • 8 out of 10 people will not return to a site after a disappointing experience.
  • Of these, 3 will go on to tell others about their experience. [Source: PhoCusWright]

A user who has to endure an 8-second download delay spends only 1% of her total viewing time looking at the featured promotional space on a landing page. In contrast, a user who receives instantaneous page rendering spends 20% of viewing time within the promotional area. [Source: Jakob Nielsen]

  • Nearly one-third (32 percent) of consumers will start abandoning slow sites between one and five seconds.
  • 39% say speed is more important than functionality for most websites, while only one in five rank greater site functionality as more important.

Between 37 to 49% of users who experience performance issues when completing a transaction will either abandon the site or switch to a competitor. Of these, 77% will share their experiences with others. [Source: Sean Power, Metrics 101]

Users have faulty perceptions of time. For example, the average person will perceive the amount of time it takes a page to load as being about 15% slower than the actual load time. And later, in recalling their memory of how long it took for the page to load, they will remember it took about 35% longer than it actually did. [Source: Stoyan Stefanov, Psychology of Performance]

Site speed and its impact on ecommerce metrics: Revenue, conversions, page views and downloads

Issues with application performance are affecting overall business revenues by up to 9%. [Source: Aberdeen Group]

A 1-second delay in page load time equals 11% fewer page views, a 16% decrease in customer satisfaction, and 7% loss in conversions. (In dollar terms, this means that if your site typically earns $100,000 a day, this year you could lose $2.5 million in sales.) [Source: Aberdeen Group]

  • A site that loads in 3 seconds experiences 22% fewer page views and a 50% higher bounce rate than a site that loads in 1 second. Impact on conversions: -22%.
  • A site that loads in 5 seconds experiences 35% fewer page views and a 105% higher bounce rate. Impact on conversions: -38%.
  • A site that loads in 10 seconds experiences 46% fewer page views and a 135% higher bounce rate. Impact on conversions: -42%. [Source: Strangeloop]

Shopzilla sped up its average page load time from 6 seconds to 1.2 seconds and experienced a 12% increase in revenue and a 25% increase in page views. It also doubled the number of sessions from search engine marketing and cut the number of required servers in half. [Source: Shopzilla]

Amazon found that it increased revenue by 1% for every 100 milliseconds of improvement. [Source: Amazon]

Mozilla shaved 2.2 seconds off their landing pages, thereby increasing download conversions by 15.4%, which they estimate will result in 60 million more Firefox downloads per year. [Source: Mozilla]

Performance optimization improved conversion rate by 16.07% and cart size by 5.51%. [Source: Watching Websites]

Yahoo increased traffic by 9% for every 400 milliseconds of improvement. [Source: Yahoo]

Visitors in the top ten percentile of site speed viewed 50% more pages than visitors in the bottom ten percentile. [Source: AOL]

Speed and the mobile web

“Sixteen percent of consumers have shopped via mobile phones or smartphones, but 27% of them report that it is dissatisfying due to the mobile shopping experience being too slow. One-third of consumers report wanting to shop via their smartphones in the future, with 5% indicating that this will be an important aspect of their loyalty to online retailers. [Source: Forrester Consulting]

  • More than half of mobile device users say that they expect sites to download as quickly on their mobile devices as they do on their home computers.
  • 60% of mobile web users have had a problem when accessing a website in the past year.
  • Slow load time was the number one issue faced by almost three quarters of them.
  • Three out of 5 say that poor performance will make them less likely to return to the site.
  • 40% said they’d likely visit a competitor’s site next.
  • The majority of study participants said they expect to be able complete simple transactions like checking their bank balance in a minute or less, or they will abandon the site. [Source: Equation Research]

From Nov. 1-15, the average response time for 14 industry-leading mobile retail sites was 4.73 seconds. Amazon led with a response time of 2.85 seconds. [Source: Mobile Commerce Daily]

Interesting side note: “Generation Y” generally gets slapped with the label of being impatient when it comes to page load times, but did you know that mobile web users over the age of 45 are actually the most impatient of all? The folks at Equation Research tell us this is so.

If none of those numbers convince your powers that be, then your organization may have bigger problems than just the speed of your website.

This cheat sheet is a work in progress. I’ll be re-posting it any time I make significant updates. And if you come across any new performance studies, fire me an email at joshua@webperformancetoday.com.

Related posts:

56 thoughts on “Cheat Sheet: Everything you wanted to know about web performance but were afraid to ask

  1. Pingback: Tweets that mention Cheat Sheet: Everything you wanted to know about web performance but were afraid to ask — Web Performance Today -- Topsy.com

  2. Pingback: Everything You Wanted to Know About Web Performance but Were Afraid to Ask (Video Edition) — Web Performance Today

  3. Pingback: VIDEO: Everything you wanted to know about web performance but were afraid to ask, part 2 — Web Performance Today

  4. Pingback: UPDATED: Everything you wanted to know about web performance but were afraid to ask — Web Performance Today

  5. Pingback: O’Reilly interview: Web performance for mortal companies — Web Performance Today

  6. Pingback: Optimizing Web Performance: Why 2010 is the year you should care — Web Performance Today

  7. Pingback: The Time it Takes to Load a Page and Viewer Behavior | (iverson's) currentbuzz

  8. Pingback: The 90-Minute Optimization Life Cycle: “Faster by default” before our eyes? — Web Performance Today

  9. Pingback: Friday Four: Giving away your birthday, paying to comment, and writing like Dan Brown — Web Performance Today

  10. Pingback: Cheat Sheet: Everything you wanted to know about web performance but … | Mad Economics

  11. Pingback: Velocity Workshop 90-Minute Optimization Life Cycle « Seven Seconds

  12. Pingback: Page Test Tools: Which results should you trust? — Web Performance Today

  13. Pingback: Mobile Web Performance: Desperately seeking data — Web Performance Today

  14. Pingback: Never Take Your Eye Off the Ball: Four mistakes Shopzilla made so you don’t have to — Web Performance Today

  15. Pingback: Psychology and Web Performance: Some quick facts and ideas — Web Performance Today

  16. Pingback: The three biggest performance problems with third-party content (and how to fix them) — Web Performance Today

  17. Pingback: Web Performance Consulting: Five questions for Andrew King — Web Performance Today

  18. Pingback: RPW 07/09/10 : performances web et business, quels mobiles supporter, overflow:scroll pour iphone, HTML5 | BrainCracking - Veille technologique sur les applications Web

  19. Pingback: UPDATE: Everything you wanted to know about web performance but were afraid to ask — Web Performance Today

  20. Pingback: You are the worst judge of your site’s performance. Here’s why. — Web Performance Today

  21. Pingback: Are your performance goals audacious enough? — Web Performance Today

  22. Pingback: Crosspost: Is your website slowing you down? — Web Performance Today

  23. Pingback: Downtime may grab headlines, but slow performance is the silent-but-deadly #1 enemy — Web Performance Today

  24. Pingback: Use of content delivery networks doesn’t correlate to faster websites for the Alexa Retail 1000 — Web Performance Today

  25. Pingback: Content Management System Comparison: Performance Optimization « Online Marketing Solutions | Ashford Davis – San Antonio, TX

  26. Pingback: How to perform a 5-minute page speed/revenue analysis of your ecommerce site — Web Performance Today

  27. Pingback: How to perform a 5-minute page speed/revenue analysis of your ecommerce site « Web Performance Guru

  28. Pingback: Announcing the Strangeloop Speed:Revenue Calculator — Web Performance Today

  29. Pingback: Web Performance Hub launches today — Web Performance Today

  30. Pingback: Performance Impact, Part Two: More findings from the front lines of website acceleration — Web Performance Today

  31. Pingback: If a page takes too long to load, after how long will a user give up and re-load or go elsewhere? Drija

  32. Pingback: Third-party tools promise cool new functionality, but are they secret conversion-killers? [Infographic] | Unbounce

  33. Pingback: New findings: Mobile web users are more disappointed than ever — Web Performance Today

  34. Pingback: Friday Link Party | Grinding Gears

  35. Pingback: Web Response Times | Performance Testing Professional

  36. Pingback: Web performance just became seriously mainstream

  37. Pingback: Measuring Typical User Bandwidth | Stuart Gunter

  38. Pingback: Infographics: Putting a human face on web performance

  39. Thank you very much for this cheatsheet, I was looking over two hours to find something like this. I’d like to know more about the firstbyte and would appreciate an article especially about that topic.

  40. Pingback: The Official Rackspace Blog - Content Management System Comparison: Performance Optimization

  41. Pingback: 26 Técnicas de Otimização de Sites « Base de Bugs do Dadonas

  42. I’m curious to find out what blog system you are utilizing? I’m experiencing some small security problems with my latest blog and I’d like to find something more safeguarded. Do you have any suggestions?

  43. Pingback: Sprites automáticos com Compass » Guilherme Garnier

  44. Pingback: Sprites automáticos com Compass | Planeta Globo.com

  45. Pingback: Responsive design is not an excuse for poor site performance

  46. Pingback: Discuss: If you’re in the web performance business, you’re in the happiness business.

  47. Pingback: Discuss: If you’re in the web performance business, you’re in the happiness business.

  48. Pingback: Performance 101: An opinionated guide to the 22 links that every developer should read

  49. Aw, this was an extremely good post. Spending
    some time and actual effort to produce a really good article… but what can I say… I procrastinate a whole lot
    and never seem to get anything done.

  50. Pingback: Everything you wanted to know about website performance

  51. Pingback: Important Site Speed And Performance Tools | PremiumCoding

  52. Pingback: Page not found

  53. Pingback: simple responsive images in wordpress with Hammy

Leave a Reply

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

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>