Tag managers on page

Tag managers present on the page.

Field data PhoneDesktopAll Scope All sites Q2 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.2%
Fleet share
Top: google_tag_manager
100.0%
Sites with any
Of google_tag_manager

87.2% of sites load Google Tag Manager.

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
2

The tag managers on page mix who uses what, and how fast each group loads

VariantShare of sitesMedian
Google tag manager
87%
Matomo tag manager
9%
Tealium iq
2%
Segment tag manager
1%
Adobe launch
0%
Piwik pro tag manager
0%
Tagcommander
0%
Ensighten
0%

Tag managers on page. On the fleet: 87.2% google tag manager, 8.7% matomo tag manager, 1.6% tealium iq. 100.0% of sites use at least one google_tag_manager.

The State of Web Vitals · Q2 2026 · 189,915 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.

Related signals Third-party categories → Optimization plugins → Consent platforms → CMS → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured