The State of Web Vitals

Tag managers on page

Tag managers present on the page.

Field data PhoneDesktopAll Scope All sites Q1 2026 edition · Phone field outcomes
Metric LCP INP CLS
1

At a glance the headline numbers for Tag managers on page

Tag managers present on the page.

8
Categories
In the distribution
87.3%
Fleet share
Top: google_tag_manager
45.7%
Sites with any
Of google_tag_manager

87.3% of sites load Google Tag Manager.

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv
2

The tag managers on page mix who uses what, and how stable each group is

Median CLS (sites using feature)
0
0.10
0.20
0.30
0.40
0.50
Google tag manager0.0087% of sites
Matomo tag manager0.009% of sites
Tealium iq0.012% of sites
Segment tag manager0.001% of sites
Piwik pro tag manager0.001% of sites
Adobe launch0.031% of sites
Tagcommander0.030% of sites
Ensighten0.020% of sites
VariantShare of sitesMedian
Google tag manager
87%
0.00
Matomo tag manager
9%
0.00
Tealium iq
2%
0.01
Segment tag manager
1%
0.00
Piwik pro tag manager
1%
0.00
Adobe launch
1%
0.03
Tagcommander
0%
0.03
Ensighten
0%
0.02

Tag managers on page. On the fleet: 87.3% google tag manager, 8.6% matomo tag manager, 1.7% tealium iq. 45.7% of sites use at least one google_tag_manager.

The State of Web Vitals · Q1 2026 · 94,910 sites · phone field datacorewebvitals.io/state-of-cwv
3

Why this matters for the Core Web Vitals, and where to start fixing it

A tag manager is remote code execution for the marketing team. It loads first, then injects whatever the container holds: more scripts, more pixels, more vendors. None of it passes through your build or your code review, and all of it runs on your visitor's main thread.

The manager itself is not the cost. The contents are, and containers only ever grow. Audit the container like a dependency list: every tag has an owner, a purpose and an expiry date, or it goes.

How does this affect the Core Web Vitals?

Tag managers on page correlates with the INP. With Matomo tag manager, 94% of sites pass the INP. With Segment tag manager, 76% do. The causal link is weak: the choice mostly marks what kind of site made it.

Go fix it The case for limiting analytics and tracking scripts → The dataLayer INP yield pattern → Defer scripts until needed →
Related signals Third-party categories → Optimization plugins → Consent platforms → CMS → Chrome field data from 94,910 sites, representing millions of real page loads · How we measured