Online Shoppers Waited Upwards of 30 Seconds for Pages to Load
An outage at Google's DoubleClick division had a significant impact on the retail industry last week. According to data collected at Yottaa, the outage affected almost all ecommerce websites between 3pm and 6pm ET on Tuesday (3-13-18). Any website utilizing Google DoubleClick services on their website (for serving, tracking, re-targeting, etc.) experienced longer than usual page load times. These delays were caused by problems with Google tags connecting with the Google servers.
Google Latency Costs Hundreds of Millions in Sales
Research has found that 79% of customers will never come back to a site that takes too long to load. If that's the case, the outage may have cost retailers billions.
What did the Slow Down Look Like?
Here is some performance data from one retail ecommerce website during the outage. The first graph shows last byte time, which is the amount of time it took for the last byte of information to be received by the browser.
The second graph shows a 4x change in the number of times when Google services failed to load on this retailer's site.
Pages Failed to Load
Even websites using asynchronous loading for the Google tags would still have been hit with significant performance degradations.
Who Was Protected?
Not all websites experienced the delay. We found that retailers who had optimized their traffic using ecommerce acceleration technology were able to mitigate the Google issue. In the graph below, you can see the comparison between optimized and unoptimized traffic to an affected website. The dark purple line shows the impact on optimized pages (this specific website was using Yottaa acceleration technology). The light purple line demonstrates the impact on unoptimized pages.
In this case, which was representative of other websites we analyzed, the visitors to non-optimized pages saw a 3x greater delay relative to visitors on optimized pages. In fact, we found that 95% of websites using similar acceleration technology experienced minimal to zero impact from the outage.
Behind Every Tag is an Application That Can Fail
We should all pause to take stock of what we can learn from this outage. First, go back to your decision to add 3rd party features to your site. A major selling point was probably how simple it is to add these tags to your website. "Just cut and paste this tag into your tag manager and 'boom' - start reaping the benefits" they will tell you. What's not discussed is the complexity of the application behind this tag that is now operating as a piece of your website.
Once the tag is inserted onto your web page, every customer visit initiates a series of actions required for each feature to load correctly:
Browser loads the tag code
Browser fetches configuration file from 3rd party server
System manipulates the application UI in the browser
Sends data back to 3rd party servers
Repeats as necessary
Today's ecommerce sites can have as many as 50-100 third party tags loading on their pages to deliver features and capabilities. And each tag requires an average of 15 requests to their 3rd party servers to successfully load. That represents hundreds of potential points of failure related to third party tags every time your page loads. You can see how serious a problem this can become if not monitored and managed correctly.
Controlling 3rd Parties Requires More than Point Optimization
This problem of complex 3rd party tags delaying page load times is common, and frequently solved by stripping tags from the site. But eventually new tags are inserted back onto the site, and each one is just as likely to suffer a failure as the faulty one you removed. If tag problems can impact Google's DoubleClick services or cause delays on Amazon.com during Prime Day, it can happen to anyone.
Control Your Vulnerability to 3rd Party Problems
Many web teams will throw up their hands on days like this and say it's a google problem. "What can we do?" as if it is so big that no one is protected from such significant failure.
But you control this. Learn yesterday's latency and lost sales prepared for the next time a major 3rd party application impacts the experience on your site. take steps now to put in place processes technology, Yottaa's ecommerce acceleration platform, which governs these applications, before 3-hour outage puts business red. You want a system that can monitor and remove 3rd party tags from the critical rendering path when events like the DoubleClick outage occurs.
Control Your Vulnerability to 3rd Party Problems
Many web teams will throw up their hands on days like this and say "it's a google problem - what can we do?" as if is so big that no one be protected from such significant failure but you control this learn yesterday latency and lost sales prepared the next time major 3rd party application impacts experience on your site take steps now to put in place processes technology Yottaa ecommerce acceleration platform which govern these applications before 3 hour outage puts business red.
Bob is currently the Co-founder and CTO of Yottaa. Before Yottaa, Bob was Chief Architect at Nexaweb. Through his work at Nexaweb, Bob became an industry leader in web performance and has been invited to many industry conferences such as JavaOne, the Server-Side Symposium, EclipseCon, ApacheCon, AjaxWorld and the Ajax Experience to speak on web performance. Before he joined Nexaweb in 2003, Bob was with Trakus, a technology company focused on tracking sports athletes in real time. At Trakus Bob designed a real-time distributed control system and many of its front-end applications. Before Trakus, Bob was at Cabletron designing network communications related software (FTP, TCP/IP, SMNP etc.).