We’re taking any possible measure to make sure that our engine will not cause any latency issues:


  1. Our JS engine is written in native (“vanilla”) Javascript (no dependency in any JS framework that needs to be loaded in addition to our main script). The entire engine is written in-house and we regularly test every part of it.
  2. The engine is triggered to run only after the document and all sub-resources have finished loading (document.readyState == “complete”). this means that the engine will not make any calls to ads nor start analyzing the page while the page isn’t fully loaded.
  3. Our JS script is minified, and cacheable. it is also hosted on a content delivery network (CDN). we keep minimizing its size.
  4. In terms of performance, we’re making sure that we access the DOM only when necessary, while keeping references to relevant DOM elements, in order to minimize DOM queries.
  5. We run automated tests on all of our publishers, while measuring latencies and logging time stamps – in order to keep track of any unpredictable change of latency.
  6. We regularly test our product on a range of devices, including slow ones to make sure that the user experience is never harmed.