What is Turbo Mode?

Burst is automatically configured to receive the most accurate data by adding the script to your header asynchronously, so although it is loaded early, it does not block the loading of other scripts.

The script will acknowledge engagement toward an endpoint and doesn’t have to wait for a response from the server to register the interactions. This endpoint is created in your root directory, so what happens if it’s not there?

Fallback to the REST-API

If you don’t have root access or Burst can’t write to the root automatically, Burst falls back on the REST-API, and you will experience no hindrance other than a possible performance hit.

If the REST API method also fails due to a security plugin, for example, please look at our troubleshooting article for Burst.

So what is Turbo Mode exactly?

No matter what the above configuration is, you can always enable Turbo Mode to improve performance. When enabled, the script is no longer loaded in the header asynchronously but is loaded in the footer and deferred. Defer means the script will only execute if the DOM has been rendered and the page is fully loaded.

This will optimize performance as the page load is not reliant on loading Burst, and you might notice positive feedback on GTMetrix or Web Vitals. However, the impact might be minimal if you have structured your website neatly and have optimized loading and server response. If the latter is the case, we recommend improving data accuracy above a small bump in performance.

If Burst does impact your website, Turbo Mode might be a good way to go. Still, we recommend looking at your entire website and server configuration to improve performance, as Burst should have a minimal impact by default.

Turbo Mode, however, will aggregate data when the page is fully loaded. Any event before a full page load will not count towards engagement. This means potentially missing bounces if one decides to exit the first-page visit before the page is fully loaded.

You can also argue that Turbo Mode will only collect data whereby the page is fully loaded, skips accidental visits, and only counts towards intentional engagement. But this is for you to decide!