Web SDK - Performance Impact

Learn how the Web SDK impacts the performance of your webpage

The SDK has the smallest possible impact on your page’s performance. Here is why:

• The integrated <script> snippet loads the SDK asynchronously. The browser’s rendering process is not blocked. If you value perfect bug reports over optimizing performance for internal testing deployments, it is possible to remove the async attribute from the code snippet to ensure that a larger part of the page load process can be recorded.
• SDK only loads and executes the specific code required to provide the requested functionality. At page load, the SDK loads single digit kilobytes of script and styles required for bootstrapping the SDK and for showing the bug reporting button. In the default settings, only when the end-user starts to interact with the SDK, the code required to record and report sessions is loaded. This code only runs when a user records and reports an issue (enabling the optional instant replay feature causes recording to start after SDK initialization).