Typically, I find document complete and onload to be similar, but I’m not sure why there’s such a difference between them in this result. What is actually measured for document complete? The onload event in this case appears to occur shortly after 2s, the document complete occurs later after 11s.
https://www.webpagetest.org/result/161209_TQ_cf2e1af2754065bfcbc8f2571f6dca05/5/details/
Any ideas what could cause this behavior? Thanks for your help!
Looking at the Chrome DevTools Timeline (Performance), there are scripts in http://www.sears.com/ that insert iframes after the onload event: s_code-min.js, utag.js (Tealium tag manager), etc. WebPagetest has reported the onload event for the top site but Document Complete seems to wait for all of these iframes to finish loading.
The initial view doesn’t seem to change visually after onload, except for the “Members earn 20% in points on Sears Marketplace purchases” banner. However, inserting iframes dynamically triggers the busy indicators in Chrome and Firefox - see Browser Busy Indicators | High Performance Web Sites.