View Categories

Impact on page latency

< 1 min read

Blockthrough’s ad serving script has two components:

  • Detection script: Used for adblock and Acceptable Ads consent detection, payload: ~2-5kb
  • Recovery script: Used for initiating and running an action, payload: ~260-530kb

The detection script runs each time a user requests a web page on the publisher’s site. Due to its small payload, the detection process contributes virtually no additional page latency. If consent for Acceptable Ads is not detected in the session, the recovery script is never called and the process ends here.

In case consent for Acceptable Ads is detected in the user session, the recovery script is called and an auction is initiated for available impressions. In controlled test with 4 different publisher sites, the average time for auction completion (call-to-render) was determined to be ~800ms. This is on the lower end of the 500-4000ms timeout range that most publishers typically to set for auction timeouts.

To sum up, Blockthrough contributes virtually no page latency for your regular (non-adblock) inventory. Further, the page latency added by Blockthrough’s recovery script should be less than or comparable to the page latency contributed by the ad serving scripts running on your standard (non-adblock) inventory.