How Slow Load Times Hurt Your Bottom Line
•Download as PPTX, PDF•
167 likes•22,743 views
This document discusses how slow page load times can hurt a website's bottom line. It notes that a 2% increase in conversions is seen for every 1 second improvement in load times. Examples are given of companies that cut load times in half and increased conversions by 9% and increased downloads by 15.4%. The document outlines two main causes of slow performance: pages being too big in size and pages being too complex. It provides tips on how to address these issues, such as compressing assets, lazy loading images, consolidating resources, and optimizing third-party scripts.
Recommended
Recommended
More Related Content
What's hot
What's hot (18)
Similar to How Slow Load Times Hurt Your Bottom Line
Similar to How Slow Load Times Hurt Your Bottom Line (20)
More from Tammy Everts
More from Tammy Everts (11)
Recently uploaded
Recently uploaded (20)
How Slow Load Times Hurt Your Bottom Line
- 1. How Slow Load Times Hurt Your Bottom Line @tameverts Web Unleashed 2015 #WebU
- 3. Do MOST people consider page speed an important part of user engagement?
- 4. “I myself wouldn’t consider it very important. Granted, if a page is too slow, it loses users, but I believe if a page loads in 5 or 6 seconds, it doesn’t make much difference.”
- 5. @tameverts
- 8. 2% increase in conversions for every 1 second of improvement @tameverts
- 9. Increased conversions by 9% Cut load times in half @tameverts
- 10. Reduced average load time by 2.2 seconds and increased total downloads by 15.4% 10 million additional downloads per year @tameverts
- 11. @tameverts
- 12. How do visitors feel about slow sites? (hint: not good)
- 13. @tameverts
- 14. @tameverts
- 15. 17 things you can do to deliver a faster user experience
- 16. Steve Souders, author, ‘High Performance Web Sites’ “80-90% of end-user response time is at the front end. Start there.” @tameverts
- 17. 1 Page size 2 Page complexity Two main performance problems @tameverts
- 18. Problem 1: Pages are too big @tameverts
- 19. @tameverts
- 20. More bandwidth isn’t the answer http://www.soasta.com/blog/more-bandwidth-isnt-a-magic-bullet-for-web-performance/
- 21. Single greatest indicator of fast performance? Faster pages are less than 1MB in size @tameverts
- 22. Know where your page weight is coming from Create a performance budget Monitor, monitor, monitor Solutions @tameverts
- 25. @tameverts
- 26. Setting a performance budget http://timkadlec.com/2013/01/setting-a- performance-budget/ Performance budget metrics http://timkadlec.com/2014/11/performanc e-budget-metrics/ @tameverts
- 27. HTTP Archive, June 2015 @tameverts
- 28. @tameverts
- 30. Problem 2: Pages are too complex @tameverts
- 32. @tameverts
- 33. @tameverts
- 34. @tameverts
- 35. @tameverts
- 36. webpagetest.org
- 37. Monitor Consolidate page resources Make sure stylesheets are in the document HEAD Host your fonts Optimize your pop-up scripts Solutions @tameverts
- 38. Third-party content can make up >50% of page requests @tameverts
- 39. Increase page weight Increase number of hosts and connections Introduce additional latency Prevent pages from loading Problems @tameverts
- 41. Defer scripts Use asynchronous versions (when possible) Know your scripts and their performance penalties Monitor constantly Solutions @tameverts
- 42. @tameverts
Editor's Notes
- Massive hero images
- Custom fonts, RWD, multiple hosts stylesheets, blocking JS, latency