---
slug: ladezeit
title: "Does Metrunio slow down my shop?"
category: installation
locale: en
updated: 2026-10-18
keywords: ["load time","slow","PageSpeed","Core Web Vitals","file size","async","performance"]
questions: ["How much does the tracking script slow down my page?","Does Metrunio slow down my shop?","Will tracking make my website slower?","How large is the tracking script?","Does Metrunio affect PageSpeed?","Does the script hurt Core Web Vitals?","Does the script load asynchronously?"]
url: https://bench.metrunio.com/en/help/ladezeit
---

# Does Metrunio slow down my shop?

**How much does the tracking script slow down my page?**

The tracking script loads asynchronously, alongside your page, and does not hold up its rendering. About 10.4 KB are transferred with Brotli or 11.6 KB with gzip, after which it sits in the browser cache. The consent bridge, another 10 KB or so, loads only if you connected a consent tool through it, and before the decision in the cookie banner the script sends nothing.

| File | Uncompressed | Transferred (Brotli / gzip) | When it loads |
| --- | --- | --- | --- |
| Tracking script (t.js) | 34.4 KB | 10.4 KB / 11.6 KB | on every page |
| Consent bridge (consent-bridge.js) | 31.4 KB | 9.5 KB / 10.6 KB | only if you chose a consent bridge in the embed code |

Measured on 17.10.2026 on the built files, compressed the way Metrunio serves them. Modern browsers get the Brotli version, older ones gzip.

## What “asynchronous” means here

The embed code adds the script with the async attribute. The browser loads it on the side while it renders text, images and the cart, and waits for Metrunio with none of it. What the script measures it sends in batches in the background. If the measurement address is unreachable for a moment, your customer notices nothing: the events wait in the browser and go out later.

After the first load the browser keeps the script for an hour and then fetches the new version in the background, while it goes on using the old one for up to a day. On the second page of a visit, as a rule, nothing is transferred any more.

## With the Shopify app

The app embed loads the same script asynchronously and the consent bridge not at all: the app reads consent through Shopify. In checkout, the pixel the app creates on connecting measures inside the sandbox Shopify provides for pixels, and Shopify reports the order itself to Metrunio without anything happening in the browser.

> **Note:** An automated test keeps the tracking script at no more than 12.25 KB with gzip; if it grows beyond that, the test fails. We have not measured a before-and-after value in PageSpeed Insights. If you want to know for your shop, measure the home page there once with and once without Metrunio.

## Also asked

- Does Metrunio slow down my shop?
- Will tracking make my website slower?
- How large is the tracking script?
- Does Metrunio affect PageSpeed?
- Does the script hurt Core Web Vitals?
- Does the script load asynchronously?

## Related

- https://bench.metrunio.com/en/help/snippet-einbauen
- https://bench.metrunio.com/en/help/shopify-app
- https://bench.metrunio.com/en/help/consent-bridge
- https://bench.metrunio.com/en/help/sdk-api
- https://bench.metrunio.com/en/help/consent-grundsatz