Below is a record of all code versions introduced by Commversion since inception. The purpose of this document is to maintain clear tracking and reference of the different types of codes deployed for our clients over time.
Legacy Code
This was the original code generated through Live Chat. It relied entirely on Live Chat instructions for deployment and did not support SmartChat. It was a basic implementation used solely to add the chat widget to a website.
CDN Code
The CDN Code introduced SmartChat functionality. It allowed multiple micro-codes to be added within the main code, reducing the need for frequent back-and-forth with clients whenever privacy policy updates or code changes were required.
Code Launch Date: 24th April 2024
Example: <script src="https://cht-srvc.net/api/lc.js?client=cv_commversion"></script>
Guide: https://commversioncom.freshdesk.com/a/solutions/articles/88000042212
Optimised Code
This code was introduced with page speed optimization in mind. Clients reported that the widget was slowing down their websites. To address this, the tech team developed a modified version of the CDN Code that delays loading the widget until after the client’s website has fully loaded.
In addition to improving page speed, this code also enhanced SEO performance by reducing render-blocking behavior and improving overall page load metrics.
Code Launch Date: 07th July, 2025
CLS Optimised Code
This version was introduced to address CLS (Cumulative Layout Shift) issues reported by clients. CLS measures how much visible content on a web page shifts while loading.
For example, when a user attempts to click a button and a late-loading image or ad causes the page to shift contents, resulting in a mis-click, that’s layout shift. CLS quantifies how disruptive this experience is.
Causes of a Poor CLS Score:
Images or ads loading late and pushing content down
Fonts loading late and changing text size
New elements being inserted above existing content
CLS is important because it directly impacts user experience and Google search rankings. Pages with poor CLS scores feel unstable and may be penalized in search results.
To maintain a stable layout and improve CLS scores, this code defers loading the chat widget until the user scrolls or interacts with the page.
Code Launch Date: 29th Oct, 25
Guide: https://commversioncom.freshdesk.com/a/solutions/articles/88000062890
CLS Performance Code
After the CLS Optimised Code was rolled out, the Performance Team observed a drop in client engagement. The issue occurred when users navigated between pages—the widget only loaded after a scroll or click on each new page.
This behavior conflicted with Commversion’s service expectations, where the widget should appear on the intended pages without requiring additional user interaction. The CLS Performance Code was introduced to resolve this issue by removing the dependency on scroll or click triggers while maintaining CLS improvements.
Code Launch Date: 26th Dec, 25
Guide:
CLS (Performance Impact) Updated Code - [Mobile] - https://commversioncom.freshdesk.com/a/solutions/articles/88000063082
CLS (Performance Impact) Updated Code - [Desktop + Mobile] -
https://commversioncom.freshdesk.com/a/solutions/articles/88000063081
CLS Overlay Code
The previous CLS performance code proved to be ineffective. While it resolved the CLS issue, it negatively impacted the widget’s behaviour. To address this, the team updated the widget implementation to ensure it no longer affects the website’s Cumulative Layout Shift (CLS). This was achieved by introducing a dummy chat overlay identical to the actual chat widget, which delays layout changes caused by the real widget and switches visibility using modifiers once the page layout has stabilized. Through this approach, the chat widget no longer contributes to CLS.
From a user experience perspective, the impact is minimal as most functionality and behaviour remain consistent with the previous implementation. The only noticeable change is that the chat widget appears with a slight delay on page reload. This updated implementation has been named the CLS Overlay Code.
Code Launch Date: 10th Feb, 26
Guide: https://commversioncom.freshdesk.com/a/solutions/articles/88000063198ring
Current Status:
The CLS Overlay Code will be implemented on a request basis, specifically for clients who have reported or flagged CLS-related issues. All other clients will continue to run on the Optimised Code referenced in the logs above
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article