Don't Let Third Parties Slow You Down

Slides uploaded now, thanks for your patience!

@Daniel Lamb: It’s certainly true that iframe creation takes some time, though our real-world experimental data shows it’s certainly faster than the ~10ms reported by Steve’s blog post. But for publishers that aren’t going to change their pages, the alternative to an iframe is a blocking script fetch; here the iframe wins hands-down.

That’s great news Arvind, thanks!

Actually I would love to hear a little bit more about the synchonisation problems you talked about. We use adsense in iframes, but when I made our site “even faster” it went to fast for adsense and the communication about how many ads were already shown went screwed.

Another thin I want to ask. On Google IO Ajax for Adsense war presented and got in closed Beta. Since then I’m trying to get in or at least get a look in the documentation. Because what I saw on the demonstration site, it quite looks like what I want to have Adsense…

@Benedikt, You are right. We’d like to add an advanced adsense code in future for publishers who can make a change on their side. Our current solution is meant to help all publishers instantly. We’ll keep you all posted on the progress.

Great presentation. I ran into the document.write issue last night while trying to optimize out ad loading. Can you post your slides?

Great session!

Nice that you think about all those people which would have a hard time implementing a new code. We had a BoF session yesterday evening, actually talking about third party impact. Mostly brawling about bad code, but some ideas surfaced.

One idea bears a question for you. Why don’t you have a second, more advanced adsense code, which people can use which do care and which have the skills to implement?

Great session thank you! You mentioned that you use iframes because you do not want to force websites to update the html markup. I understand that is necessary, and I think the solution you’ve been playing with is brilliant, but since iframes are:

“1-2 orders of magnitude more expensive to create than any other type of DOM element – Steve Souders”

Do you have any plans for a more efficient “opt-in” solution? You already check for global variables for the ad meta data (google_ad_width) why not add another such as:

google_ad_id = “element_id”; google_ad_ids = [“element_id1”,”element_id1”];

Just a thought…

wow. Michael Kleber… mathematician with superior mental capacity, undoubtedly. So much useful info so fast in such a short period of time… Thank you, Michael!

nice presentation, would you mind sharing slides?

It’s awesome to hear Arvind talk about the very techniques we used in late 2008 to mitigate 3rd party impact on our page performance for the insideline.com redesign :-) I’ll be talking more about what we did in my session tomorrow at 6:00 pm.

imho, one of the best if not the best session

I talk about the growing performance impact of third-party content in my P3PC series . It’ll be great to hear some stats on this from Google and esp. nice to hear their tips on making ads faster. This is a super critical talk to hear.