TrafficGuard’s Site tag javascript framework is distributed asynchronously via a high-performance and ultra-low-latency global network. The library is constantly optimised to balance capability and transfer/evaluation time and is minified to ensure lower byte size without decompression overhead.

The Site tag will have a minimal impact on your page loading speed and end-user experience.

Through numerous performance analyses sampled on an array of devices and browsers, the TrafficGuard Site tag has performed far better than common advertising tags, such as the Facebook pixel.

Page Rendering and Interactivity
​

We will not allow the script to delay the rendering or interactivity of your page.
tg.js is very small ~20 KB, gzipped. This is much smaller than most scripts.

The script is fetched from Google's Cloud CDN and typically takes under 20ms.

The tg.js script is loaded asynchronously, ensuring that it’s requested only after any static resources such as CSS and images.

For cases where a site needs to prioritise page speed over fraud detection the tag can be loaded with <script defer> in order to ensure it is not evaluated until after the full page load. The downside of this may be a discrepancy in reporting for short clicks.

UI Thread Utilisation
​

After a page is loaded, we have taken careful steps to optimise the TrafficGuard script to avoid using precious CPU time.
We ensure we only conduct the minimum possible work required to verify the client device and we restrict the most intensive processes to only a single execution per user session, where possible.

Outgoing Event Processing

Events are sent to TrafficGuard over the same Google Edge network. In the majority of cases, these take very little time and run asynchronously.

Continued optimisation

While we are continually optimising the script for detection and behavioural analysis, we closely monitor the performance of the script and make any possible optimisations.

Read more about why the site tag is important.