After adding chat, the page started opening more slowly. The timing alone does not prove the cause: images or site code may also have changed in the same release. Compare the same page with chat and without loading it. Look separately at file download time and JavaScript execution time.
What is slowing things down: loading, clicks, or chat
Chat JavaScript downloads additional files and runs in the browser. While the main thread is busy with heavy code, the page may respond late to clicks. Official documentation.
Chat may delay the interface from appearing, create heavy work after loading, or slow down only when its panel opens. Record the specific action and visible symptom. Don’t treat a lower overall score as an explanation of the cause. Keep a copy of the page version from before chat was added and the current release build. If the initial viewport, fonts, and code all changed at the same time, comparing two dates does not isolate the widget. Compare the same build. In your DevTools, temporarily block the chat’s initial file while keeping all other resources available.
Which conditions to keep the same
| Mode | What changes | How to compare | What to check in the profile |
|---|---|---|---|
| Widget enabled | Original mode | Save a profile | Requests and execution |
| Widget blocked in a test | Control mode | Repeat the conditions | Don’t change the build |
| Two integrations | Duplicate startup | Remove the extra one | Function remains available |
| Async only | Loading behavior changes | Check the browser’s main thread | Check JavaScript execution time |
In the table, note the mode with the widget, the control mode without it, the startup moment, and whether consent is present if it affects loading. Include opening the panel after the initial viewport. A third-party service’s resources may change between runs, so save the actual URLs and timings. Keep cold and warm cache runs separate. If chat is needed for an important user action, disabling it is not a final optimization without a product decision. Blocking helps identify the cause. For a permanent solution, agree with the site owner on loading chat later or replacing it while retaining the needed contact method.
Check network activity and code execution
In Network, group the provider’s requests and check the initiator. One initial file may load additional code files, fonts, and embedded iframe windows. In Performance, find their code execution and related main-thread work. A script that downloads quickly can still take a long time to process; a large response does not necessarily block the main content. Compare when the needed element appears and how responsive the control action is. Don’t add up parallel request durations as though they were the delay for the whole page. Check whether chat delayed the main text from appearing or a button’s response. A large downloaded file without such a connection does not yet explain the slowdown.
Disable only chat in the test browser
Compare several page loads with the same network and CPU throttling, window width, and cache state. For each mode, record when the main text appears, the delay before the control click responds, and the chat requests. The profiles will show whether the heavy task disappeared along with the widget. If results vary widely, repeat the series before changing how the widget is integrated.
In Network, find the chat’s initial JS file. Use the context menu to select Block request URL and enable Request blocking. Reload the test page with the same network profile and record Performance. After comparing, remove the block. If the main site also breaks, this test changes more than just the loading of an independent chat widget.
Choose when to load chat
If the widget is not needed for the initial viewport, consider starting it later or loading it when the user expresses intent, while keeping the function clearly accessible. Async helps avoid waiting for downloads in the previous order, but execution still uses browser resources. Defer also has specific mechanics and does not eliminate a heavy handler. Choose an option based on the stage where you found the delay. Check the provider’s readiness event so the button does not look active before the panel can open. If changing the loading time affects analytics, separately preserve any event tracking you need.
Remove duplicate integrations
Look for duplicate integrations through the theme and tag manager. Two instances can create extra requests, handlers, and panels. Check behavior when the provider is unavailable: the main interface should not wait indefinitely for chat if chat is not an essential part of the action. Diagnose this on a test copy using controlled blocking or delay. To test a failure, block the provider only in your own browser or on a test copy. If the service requires a particular loading method, check its current official provider instructions before rewriting the initial file yourself.
Repeat the load and open chat
The profile shows that the identified work has decreased; the main interface works. Open the chat panel without sending a real message and check that the button is ready. After user consent, if required, the widget connects once.
Read also: JavaScript performance optimization: a complete guide for web developers and Site speed and conversion: how much each extra second of loading costs. Site checks are available on the reChecker technical audit page.