Great article! I was wondering why you needed to load 3rd party JavaScript before the window.onload event. Is this a business or technical requirement/decision? We load a number of pixel trackers on bizrate.com and I'm trying to create a system of intelligently loading all of them and actually ran into issues when attempting to attach my loaded to the onload event. When I dropped that requirement everything consistently worked as expected.
I'm trying to grok the nature of the partnership with Google here. It seems like everything in this article could have been done without talking to Google.
Jon: We are able to determine the type of the 3rd-party component in our CMS. So if it is an ad in a JavaScript format, we load it before the onload event. This is due to the fact that ads use document.write, which has to be executed before the onload event is fired otherwise bad things happen. More on that is discussed in our blog post.
Courier: If the banner is called in an iFrame, we lazy loaded like the rest of the page components. Otherwise, we call it at the bottom of the page and then relocate it to its original position. I hope this answers your question :-)
Christopher: Google has been a leader in promoting and evangelizing web performance and so is Edmunds. Our shared interest and passion for making the web faster makes all of us natural partners by default.
Estoy de acuerdo con Ismael. El interes de todos es hacer assecible y rapida la rendicion de la web. Gracias por tu explicacion Edmunds.Lo intentare.Carin, caridadtovar@hot
Interesting article, but why the misleading title? Following Google's guidelines doesn't make you a partner with Google, by any normal interpretation of the word "partner".
This comment has been removed by the author.
ReplyDeleteGreat article! I was wondering why you needed to load 3rd party JavaScript before the window.onload event. Is this a business or technical requirement/decision? We load a number of pixel trackers on bizrate.com and I'm trying to create a system of intelligently loading all of them and actually ran into issues when attempting to attach my loaded to the onload event. When I dropped that requirement everything consistently worked as expected.
ReplyDeleteRendering third party banners can impact your website performance, how did you address this?
ReplyDeleteI'm trying to grok the nature of the partnership with Google here. It seems like everything in this article could have been done without talking to Google.
ReplyDeletedafdfad
ReplyDeleteI wrote a response earlier that seems to have vanished. Four attempts to publish and it still disappears.
ReplyDeleteJon: We are able to determine the type of the 3rd-party component in our CMS. So if it is an ad in a JavaScript format, we load it before the onload event. This is due to the fact that ads use document.write, which has to be executed before the onload event is fired otherwise bad things happen. More on that is discussed in our blog post.
ReplyDeleteCourier: If the banner is called in an iFrame, we lazy loaded like the rest of the page components. Otherwise, we call it at the bottom of the page and then relocate it to its original position. I hope this answers your question :-)
ReplyDeleteChristopher: Google has been a leader in promoting and evangelizing web performance and so is Edmunds. Our shared interest and passion for making the web faster makes all of us natural partners by default.
ReplyDeleteEstoy de acuerdo con Ismael. El interes de todos es hacer assecible y rapida la rendicion de la web. Gracias por tu explicacion Edmunds.Lo intentare.Carin,
ReplyDeletecaridadtovar@hot
Interesting article, but why the misleading title? Following Google's guidelines doesn't make you a partner with Google, by any normal interpretation of the word "partner".
ReplyDelete