Frequently Asked Questions (FAQ)

Does Catch.js load synchronously by default?

Yes, Catch.js loads synchronously by default.

Can I load Catch.js asynchronously?

Yes, you can use Catch's NPM package to do so. Refer to the documentation for additional details on how to do so.

Does Catch.js initialize synchronously?

No, Catch.js initalizes asynchronously.

Does Catch cache Catch.js?

Yes, Catch makes use of caching in order to load Catch UI elements as quickly as possible for the highest percentage of consumers as possible. Specifically, Catch caches Catch.js both on the customer’s browser and using a CDN (Content Delivery Network).

How does Catch affect page performance?

Catch designs our SDKs to minimally impact consumer-facing latency and your site's score on Google PageSpeed Insights while providing you with the functionality you need to integrate with Catch. Catch serves three JavaScript files on page load: catch.js (~72 kB) to display and manage UI widgets, index.js (~3.1 kB) to manage lazy loading, and vendor.js (~26.0 kB) for error logging. Catch makes use of code splitting and lazy loading to optimize performance: we defer loading additional JavaScript and images required to render informational modals until the consumer interacts with the site. Further, Catch continuously looks for ways to decrease the size of our JavaScript files and other assets.