Short answer: NO
Initial page rendering is not affected at all. Overall experience might be affected, like it is with any Javascript running on the page, depending also on client device.
Below it’s the explanation of how the integration works like any other Javascript code added to your webpage. It’s comparable with Google Analytics JS, Facebook Pixel JS, TagManager or any other tracking services you definitely use. Everything it’s done asynchronous. Asynchronous means it waits for main program (page load) flow, without disturbing anything.
One 100% safe solution is that you can load our integration code at the end of the page html, meaning it will wait for absolutely everything else to load before it. The only disadvantage of this is that A/B testing and other campaigns triggered on page load will be delayed a bit.
If your hosting/infrastructure provider suggests that using our service will affect it’s servers, than you should ask him or yourself the following questions:
- how is the their server affected by including a piece of javascript code on the page? Can you explain?
- how is the integration done that asks for more server resources? This is because some systems are old/not modernly built, don’t use cache or make various useless internal requests to always display our code.
- how is it comparable to displaying Facebook pixel? Isn’t that slowing down the website as well?
If you keep receiving this story, please get in touch with us or introduce our account manager to him to discuss over email. Our solution it’s really easy to implement/integrate also through TagManager if you want to use our service.