Short answer: a well-built chat widget loads one small script and waits to load the chat window until a visitor opens it, so it should have almost no effect on how fast your pages appear. Do not take that on trust. Measure your page before and after adding the chat, with the same tool, and keep the change only if the numbers stay where you want them.
Why do people worry that live chat slows a website?
Some third-party scripts do slow pages. A script that loads a large bundle of code at the top of the page, fetches fonts and images straight away, and runs before the page is usable competes with your own content for the same bandwidth and the same browser thread. Visitors then wait longer for the first thing they came to see.
A chat widget is third-party code like any other, so the worry is fair. The question is how it loads, not whether it exists.
What makes a chat widget fast or slow?
Four things decide it:
- Size of the first script. The smaller it is, the less it competes with your page.
- When the chat window loads. A widget that waits until the visitor opens it keeps the heavy part off every page view.
- Whether it blocks rendering. A script loaded with the right attributes does not stop the page from appearing.
- What it does on arrival. Sounds, pop-ups and measuring tools that run at once add work for the browser.
Frosvo's embed script is a small loader. The full chat window loads only when a visitor opens it, so a page where nobody uses the chat pays only for the loader. Visitors who have not agreed to tracking stay private until they click, and the chat can be set to wait for that click.
How do I measure the effect myself?
Use the same tool and the same page before and after, and run each test several times, because single results vary.
- Pick two or three important pages, such as the home page, a product page and the checkout.
- Run each through a speed testing tool and note the loading speed of the main content, how long the page takes to respond to a click, and how much the layout shifts while loading.
- Add the chat and run the same tests again.
- Compare the numbers. A small difference inside normal variation means the chat is not the problem.
Browser developer tools show the same thing in more detail. Look at which scripts load, how big they are and how long the browser spends running them.
Where should I place the chat script?
Place it just before the closing body tag, as the install guide describes, so the content of your page is parsed first. On WordPress, WHMCS, Joomla, PrestaShop and Magento you can install a ready-made package instead of editing templates, which also keeps the script in the right place when your theme updates. The install guide and the platform plugins page show both routes.
Does the chat affect layout shift?
It should not. The chat button is placed over the page in a corner rather than inside the flow of your content, so adding it does not push your text around. Check this on a phone as well: the chat takes over the screen when opened, which is what a small screen needs, but the closed button should stay in its corner.
What about cookies and consent?
A chat that loads before a visitor has agreed to anything should not set tracking cookies. Frosvo's widget respects the consent choice on your site, and you can configure whether visitors are tracked at all before they interact. The live chat GDPR checklist covers what to tell visitors and how to handle requests for their data.
What if I only want the chat on some pages?
Add the script only to the templates where you want it. A common choice is to show the chat on pricing, checkout and help pages, where visitors need answers, and leave it off pages where it only distracts. You can also set office hours so the away message is clear when nobody is available.
Should I keep it if the numbers get worse?
If your tests show a real cost, find the cause before you decide. Check whether another script is the problem, whether the chat is loaded twice, and whether a caching plugin is serving an old copy of your pages. If the chat still costs more than it gives back, remove it. Customers answered quickly are worth something, but never at the price of a page that feels broken.
Frosvo's chat widget and shared inbox are free for one website with no time limit, so you can run this test without paying for anything. Start free, add the chat to a staging page first, and measure. The chat widget page lists everything the widget does, and the live chat best practices guide covers how to run it once it is live.