We’re excited to announce the release of the
connectOnPageLoad setting in the Web Widget API to give you the option of deferring the Chat connection. With this setting, businesses now have the flexibility to defer the Chat web socket connection until your visitor interacts with the Web Widget, rather than the default behavior of connecting on page load.
Deferring the Chat connection has the following main benefits:
- Improved Chat performance
- Improved Web Widget performance
Improved Chat performance
By deferring the Chat connection on pages where it's not required on page load, the volume of concurrent Chat connections occurring across your website is reduced. This helps ensure that Chat agent and end-user experiences continue seamlessly during periods of high visitor traffic volume.
Improved Web Widget performance
Deferring the Chat connection on page load reduces the processes required as well as the number of assets that need to be delivered to your customer's browser to serve the widget when your web page loads. As a result, this decreases the time it takes before the widget becomes interactive and can improve the scores you receive from web page performance tools such as Google Lighthouse.
Please be aware that there are some important trade-offs and potential impacts to consider when deferring the Chat connection using
- Certain Chat features, such as Conversion Tracking and Proactive Triggers which rely on a visitor’s connection with Chat services, may be impacted.
- Depending on your implementation, certain Web Widget APIs may require some adaptation of your code to avoid any impacts to your customer experience and workflow.
To learn more about the feature, see Optimizing Chat and Web Widget performance.
For further tips on how to use the feature and details on the trade-offs and potential impacts, see ConnectOnPageLoad: Configuration best practices for common use cases.