When you implement the tracking code into your website you may want to know how that will affect the loading time.
When you implement the synchronous code in the <head> tag, the changes are applied before the content loads. Which means that the time load of the website has minimal increase.
- Website pages load slowly or do not render properly
When you type in an URL and a page loads, there is a complex delivery system built around data packets ( images, CSS files, plugins etc. ).
If the internet connection is slow our tracking code has a security time load checker that will skip it and it will not apply the changes in order to not influence at all, the time load and the user experience.
- Flickering effect
This happens when the original content is loading first and after that the changes are applied. This can distract the users from the CTA experiment and the results to not be accurate.
When you install the tracking code please consider the following:
- Position: place it to be the first in the <head> tag, if possible. We highly recommend this position for the changes to be applied before the content load in order for the user to have the best experience.
- Type of code: with asynchronous code the loading time will not be affected, but for the A/B test experiments the flickering effect will be visible. With synchronous code the loading time will be affected with 60 – 200 milliseconds top, but it provides the best user experience.
- Tag Manager: place our tracking code to load first. This helps the changes to be applied before the original page loads.
Click here to read more about integration with other plugins.
- JQuery: we recommend to use the ‘jQuery bundled in Omniconvert code’ option, due to the fact that if the version used by you differs from the version used by our platform, the experiments will be affected.