Why Web Performance Matters Open Text Web Solutions Usergroup Anwendertagung Feb Tobias Dreyschultze Tobel Online Web Consultancy

Transcription

1 Why Web Performance Matters Open Text Web Solutions Usergroup Anwendertagung Feb Tobias Dreyschultze Tobel Online Web Consultancy

2 The Person Tobias Dreyschultze Wohnhaft in München Informatik, Universität Oldenburg : RedDot Universe : Gomez/Compuware 2012+: Independent IT Consultant

3 seconds Customer Expectation grows 5 4 What are your expectations for how quickly a web site should load? About online shoppers 79 % that site who experience a dissatisfying visit are likely to no longer buy from % reduction % important to their site loyalty 33 % stated that quick page loading is who abandoned a recent shopping session were dissatisfied with site performance Quelle: ecommerce Web Site Performance Today white paper August 2009

4 Why Performance matters found that a 2 second slowdown 4.3 % reduction in revenue/user determined that a 400 millisecond delay 0.59 % fewer searches/user view 50 % more pages/visit than users experiencing the slowest page load times leading to a reduced page load times from ~7 seconds to ~2 seconds, 7 12 % increase in revenue and reduction in hardware costs 50 % Quelle: Steve Velocity Conference

5 Seconds Seconds Why Performance matters 40% of Consumers will abandon a site if made to wait Consumer expectations for how quickly a web page should load How long consumers will wait for a page to load before abandoning <1 0,05 <1 0,01 1 0,12 1 0,02 2 0,3 2 0,1 3 0,36 3 0,27 >4 0,17 >4 0,6 0% 10% 20% 30% 40% 0% 20% 40% 60% 80% Lost revenues Increased costs Reduced customer satisfaction LOB dissatisfaction with IT Quelle: ecommerce Web Site Performance Today white paper August 2009

6 Steve Souders Creator of Yslow Browser PlugIn Google Page Speed many more Books: High Performance Web Sites Even Faster Web Sites velocityconf.com

7 The Performance Golden Rule 80-90% of the end-user response time is spent on the frontend. Start there. greater potential for improvement simpler proven to work Source: Steve Souders, Google I/O 2008,

8 The Importance of Frontend Performance 9% 91% 17 % 83% igoogle, primed cache igoogle, empty cache Source: Steve Souders, Google I/O 2008,

9 14 Rules 1. Make fewer HTTP requests 2. Use a CDN 3. Add an Expires header 4. Gzip components 5. Put stylesheets at the top 6. Put scripts at the bottom 7. Avoid CSS expressions 8. Make JS and CSS external 9. Reduce DNS lookups 10. Minify JS 11. Avoid redirects 12. Remove duplicate scripts 13. Configure ETags 14. Make AJAX cacheable Source: Steve Souders, Google I/O 2008,

10 Assembled in the browser Inside the firewall Outside the firewall User s browser Flash animation Search Shopping cart Ads from Adserver Web analytics CMS content Source: Video from media server CDN content

11 Challenge: ADC The Application Delivery Chain Data Center Virtual/Physical Environment Cloud Private Public 3rd Party/ Cloud Services Local ISP Browsers Customers Mainframe DB Servers App Servers Web Servers Load Balancers Major ISP Storage Web Services Mobile Components Network WAN Optimization Employees Content Delivery Networks Mobile Carrier Devices Employees Source:

12 Challenge: ADC The Application Delivery Chain Data Center Virtual/Physical Environment Cloud Private Public 3rd Party/ Cloud Services Local ISP Browsers Customers Mainframe DB Servers App Servers Web Servers Load Balancers Major ISP Storage Web Services Mobile Components Network WAN Optimization Employees Content Delivery Networks Mobile Carrier Devices Employees Source:

13 Challenge: ADC The Application Delivery Chain Data Center Mainframe Storage Web Services Source: Virtual/Physical Environment DB Servers App Servers Mobile Components Network Web Servers Load Balancers WAN Optimization Cloud Private Public Employees Major ISP 3rd Party/ Cloud Services Content Delivery Networks Backbone Local ISP Mobile Carrier Last Mile Browsers Devices Customers Real User Monitoring Employees

14 Backbone: opentext.de DE Nodes CA Nodes

15 Backbone: opentext.de

16 Performance Circle Baseline Gathering baseline data so you know what is normal and can see trends Diagnose Using the baseline data and other indicators to diagnose the root problem Fix Fixing the problem with a well designed, costeffective solution Validate Validating the solution actually fixed the problem

17 Tools Yslow Browser PlugIn Google Page Speed /page-speed/ dynatrace AJAX Edition ntent/find-and-fix-fast.aspx Gomez

18 Tobias Dreyschultze