Forum Moderators: martinibuster

Message Too Old, No Replies

Google DFP / GPT tags are the last items visualized on the page

         

Marfola

7:07 am on Mar 30, 2012 (gmt 0)

10+ Year Member



We use the DFP-small business platform to serve adsense with GPT (Google Publisher Tag) async in single request mode. The new GPT tag loads the ads in async and reduces the number of http. That said, the ads are always the last elements on the page to be visualized. We’ve determined that its neither a traditional loading or rendering problem but rather a slow loading of the iframe content. The latency is greatest on Safari (mac) and ie9 and oftentimes the ads are visualized several seconds after the next to last item visualized.

We’ve tested the page in firebug, pingdom, webpagetest and google console.

All show that the adds load when called and render properly, they aren’t blocking the onload event, nor is an other element blocking the onload event or any other element.

We’ve tried placing the GPT tags at the top of the page, calling the GPT js in the header, setting a timeout for both the header and body, loading everything else but our html and css files after the onload event.

In all cases, ads loaded with GPT tags in async and single reguest mode are the last items visualized on the page.

levo

7:21 am on Mar 30, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Asynchronous loading just prevents blocking, if an asynchronous script inserts a iframe/image etc. before the onload event, the browser delays the onload event until those resources are loaded too. DFP async tag waits for onload probably by design. Check other 3rd party scripts (social buttons etc. - event if they use async method) and try to move them after onload event.

Marfola

2:29 pm on Mar 30, 2012 (gmt 0)

10+ Year Member



Hi Levo,

Thanks for the response.

Per my initial post 'we’ve tried loading everything - social network bottons, other third party, ecc - but our html and css files after the onload event.' but the 'ads loaded with GPT tags in async and single reguest mode are still the last items visualized on the page' and 'oftentimes the ads are visualized several seconds after the next to last item visualized'.

I agree that DFP async tag probably waits for onload by design however users don't wait for DFP async tags to load before interacting with the page. Many users have moved beyond the ads before they load and as a result we are seeing a decrease in ad revenue per ad impression.