The document discusses how poor application performance is analogous to a car that takes a long time to start or has other issues. It notes that the average car drive is 32 minutes while the average application session is only 71.56 seconds. To improve performance, it recommends making fewer HTTP requests, reducing image sizes, and reducing cookie sizes. It invites reading more success stories and contacting the company for more information.
You are entering your car, sit in your car and start you engine. You wait. And you wait. Because the car designer knew that this might be a problem – they added a nice progress bar. Starting… Starting… Starting… And if you have even a cool progress bar – it will probably show “warming up the tires, stretching the engine, drinking some coffee”
BoA – good Wifi – 10 seconds to login
TripAdvisor – good 3G, 15 seconds to login
You turn on your radio and you get the option to use facebook connect. You agree to connect and it takes you to FB… and it shows the nice grey progress line. 1.5 minutes?
You continue driving towards work. When suddenly the car appears to be stuck. You wait a few seconds and then you get a little X on the bottom part of the screen.
Page size has a close correlation to performance. According to our latest quarterly ecommerce performance state of the union, the median top 100 ecommerce page has a payload of 1492 KB, making it 48% larger than it was just a year and a half ago.
http://blog.radware.com/applicationdelivery/applicationaccelerationoptimization/2015/01/8-web-performance-resolutions-for-2015/
Page size has a close correlation to performance. According to our latest quarterly ecommerce performance state of the union, the median top 100 ecommerce page has a payload of 1492 KB, making it 48% larger than it was just a year and a half ago.
http://blog.radware.com/applicationdelivery/applicationaccelerationoptimization/2015/01/8-web-performance-resolutions-for-2015/