Tracking payload

More than 200 KB of tracking payload measurably slows the page and enlarges the compliance surface.

What we check

Sums the size of loaded tracking scripts in KB.

Why it matters

More than 200 KB of tracking payload measurably slows the page and enlarges the compliance surface.

Common causes

Several analytics tools measure the same thing in parallel, GA4 plus heatmap plus session recording plus product analytics.
Tag manager containers grew for years, nobody ever deleted a tag.
Session recording tools load on every page although only the checkout was meant to be studied.
Consent, chat, and personalisation widgets each bring their own library along.

The fix

Run a script audit: remove unused tags, consolidate the rest in a tag manager, lazy-load non-critical scripts.

Check it yourself first

The Tracking Check tests this point along with all the others, in seconds.

Start the Tracking Check →

Related checks

Third-party scripts →Tag manager →

Asked often

What does a failing "Tracking payload" check mean?

More than 200 KB of tracking payload measurably slows the page and enlarges the compliance surface. Run a script audit: remove unused tags, consolidate the rest in a tag manager, lazy-load non-critical scripts.

How do you fix a failing "Tracking payload" check?

Run a script audit: remove unused tags, consolidate the rest in a tag manager, lazy-load non-critical scripts.

The fix, delivered

Wired up in days, not sprints.

Findings from the Tracking Check go into a ranked sequence with effort estimates in the Audit Sprint, every module with an acceptance criterion.

To the service Request an Audit Sprint