For optimal page load performance, place the Web Widget (Classic) script tag at the end of the section of your webpage. This placement prevents the script from blocking the browser's rendering process. Remember, any scripts using the Web Widget (Classic) zE JavaScript API should be placed after this snippet.
The Web Widget (Classic) has a package size of approximately 475 KB when first loaded. This size includes the core assets required for the widget to function. If you enable additional channels like Talk or Chat, the size increases by about 65 KB…
The Web Widget (Classic) requires a significant amount of JavaScript because it is a feature-rich tool designed to enhance customer support on your website. It supports multiple channels like Chat and Talk, allows for customization, and offers…
The Web Widget (Classic) loads asynchronously, meaning it doesn't block the rest of your webpage from loading. However, the JavaScript required can still impact load time as browsers need to download, parse, and execute it. To minimize this impact,…
Yes, the Web Widget (Classic) assets are served from a Content Delivery Network (CDN) using HTTP/2, which helps reduce latency. This setup allows browsers to open a single TCP connection to download the assets, improving load times. For more on…
Yes, the Web Widget (Classic) assets are compressed using Gzip and are cached for up to a year. They are cached both privately on end-user browsers and publicly on CDN edge servers. This caching strategy ensures faster retrieval of assets on…
Google's Lighthouse tool is recommended for monitoring your website's load speed. It is available in the audit tab of developer tools and provides comprehensive coverage of modern web browser features. Lighthouse considers HTTP/2 multiplexing,…