How to reduce latency of header bidding
Why do header bidding cause latency? How to reduce it?
Having seen almost all bidders’ header bidding API calls, we’ve observed the few problems listed below:
- Publishers make more money if all bidders are treated fairly. However, bidders that offer asynchronous integrations today (better for the publisher) are given LESS time to respond.
- Blocking ad calls is bad for user experience. Users leave the site if content takes too long to load.
Here’re a few screenshots of websites’ network calls after implemented header bidding. In a later section, there’s a screenshot showing how header bidding is accelerated by prebid.js.
Blocking Call Screenshot 1
- All header bidding requests combined took 4 seconds to load!
- Users have to wait for 4 seconds of blank space in their web browser before any content can load.
Blocking Call Screenshot 2
- All header bidding requests in total took 1 second to load.
- However, if all calls are made asynchrnously, latency can be dramatically reduced.
After prebid.js’s acceleration:
All Pre-bid Calls are made concurrently within 100ms.
Note that AppNexus, Pubmatic, OpenX, Rubicon header bidding calls were all made within the first 100ms.
Timeout at 400ms is respected.
Rotate order of bidders