The busiest online shopping season is about to start and it’s time to make a quick check on whether the top shopping sites are prepared for the big consumer rush or whether they are likely going to fail because their pages are not adhering to Web performance best practices.
The holiday rush seems to start ramping earlier and earlier each year, the Gomez Website Performance Pulse showed an average degradation in performance satisfaction of +13% among the top 50 retail sites in the past 24 hours when compared to a typical non-peak period. For some, like this website below, the impact began a week ago. It’s important to understand not only whether there is a slowdown, but also why – is it the Internet or my app?
Before we provide a deep dive analysis on Cyber Monday looking at the pages that ran into problems we want to look at the Top 50 Retail Pages and see whether they are prepared for the upcoming weekend. We will be using the free SpeedOfTheWeb Service as well as deep dive dynaTrace Browser Diagnostics. We compiled the Top Problems we saw along the 5 Parts of the Web Delivery Chain that are on these analyzed pages today, 3 days before Black Friday 2011. These top problems have the potential to lead to actual problems once these pages are pounded by millions of Christmas shoppers.
User Experience: Optimizing Initial Document Delivery and Page Time
The actual User Experience can be evaluated by 3 key metrics: First Impression, OnLoad and Fully Loaded. Looking at one of the Top Retail sites we see values that are far above the average for the Shopping Industry (calculated on a day-to-day basis based on URLs of the Alexa Shopping Index):
Problem #1: Too many Redirects result in delayed First Impression
The browser can’t render any content until there is content to render. From entering the initial URL until the browser can render content there are several things that happen: Resolving DNS, establishing connections, following every HTTP redirect, downloading HTML content. One thing that can be seen on some of the retail sites is the excessive use of HTTP Redirects. Here is an example. From entering the initial URL until retrieved from the initial HTML document the browser had to follow 4 redirects taking 1.3seconds:
The following problems can be seen on the page shown in the timeline above:
- Most of the 3rd Party content is loaded late – which is actually a good practice
Problem #3: Complex CSS Selectors failing on IE8
On multiple pages we can see complex CSS Selectors such as the following that take a long time to execute:
Problem #4: 3rd Party Plugins such as Superfish
Content: Size and Caching
Problem #5: Large Content leads to long load times
Even on high-speed Internet connections a size that is 4 times the industry average is not optimal. When accessing pages of that size from a slow connection – maybe from a mobile device – loading all content to display the site can take a very long time leading to frustration of the end user.
Problem #6: Browser Caching not leveraged
Browser Side Caching is an option web-sites have to cache mainly static content on the browser to improve page load time for revisiting users. Many of the tested retail sites show hardly any cached objects. The following report shows one example where caching basically wasn’t used at all:
For more information check out our Best Practices on Browser Caching.
Network: Too many resources and slow DNS Lookups
Analyzing the network characteristics of the resources that get downloaded from a page can give a good indication whether resources are distributed optimally across the domains they get downloaded from.
Problem #7: Wait and DNS Time
The following is a table showing resources downloaded per domain. The interesting numbers are highlighted. There seems to be a clear problem with a DNS Lookup to one of the 3rd party content domains. It is also clear that most of the content comes from a single domain which leads to long wait times as the browser can’t download all of them in parallel:
Reducing resources is a general best practice which will lower the number of roundtrips and also wait time per domain. Checking on DNS and Connection times – especially with 3rd party domains – allows you to speed up these network related timings.
Server: Too many Server-Requests and Long Server Processing Time
Problem #8: Too much Server Side Processing Time
Looking at the Server Request Report gives us an indication on how much time is spent on the Web servers as well as application servers to deliver the dynamic content.
Long server-side processing time can have multiple reasons. Check out the latest blog on the Impact of 3rd Party Service Calls on your eBusiness as well as our other server-side related articles on the dynaTrace Blog for more information on common application performance problems.
Waiting for Black Friday and Cyber Monday
This analysis shows that, with only several days until the busiest online shopping season of the year starts, most of the top eCommerce sites out there still have the potential to improve their websites in order to not deliver a frustrating User Experience once shoppers go online and actually want to spend money. We will do another deep dive blog next week and analyze some of the top retail pages in more detail providing technical as well as business impact analysis.