This document discusses Google's implementation of ads on web pages using Doubleclick for Publishers (DFP). It describes how DFP ads were previously implemented using multiple HTTP requests and scripts that blocked page loading. The new implementation uses a small script to asynchronously create an iframe that then loads the ad content, allowing ads to load in parallel with the page and be refreshed asynchronously as well. This friendly iframe approach offers performance benefits over previous methods by reducing blocking scripts and HTTP requests for improved page loads.

1. Example of implementation with Google ads

2. • Pages are complex: lots of resources from
various domains
• A lot of what's loaded is third party content
We need unobstrusive loading
techniques to get better perfs.

3.  On TGU FR Homepage, we have 3 DFP
(Doubleclick for Publishers) ads
Impact:
 15 HTTP requests, 78KB total
 Scripts block the page’s content from downloading

4. Concept
iframe on the same origin that serves remote content
How is it possible?
 The previous heavy script is replaced with a very small
script that only creates the iframe
 Inside this iframe, it executes the heavy time-
consuming script that will get the ads
 It creates another friendly iframe that contains the ad

5. Why is a friendly iframe that
awesome?
 Ads can be loaded in parallel with the rest of the page
 Start of loading ads can be delayed, regardless of tag
placement (not possible with either standard method)
 Ads may be loaded using AJAX or other dynamic
coding frameworks, without introducing compatibility
issues due to ads using document.write() etc.
 Gives the ad access to the DOM of the page, allowing
interstitials, expanding ads, resizing the iframe…

6. With his new DFP ads, Google offers the
best current solution
 The script that creates the iframe is asynchronous
 The single request mode : 1 HTTP request for all ads
slots
 Asynchronously refreshing ad slots
 Support for expanding ads