Analytics on page

Analytics scripts 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 Analytics on page

Analytics scripts present on the page.

20
Categories
In the distribution
50.8%
Fleet share
Top: google_analytics_4
100.0%
Sites with any
Of google_analytics_4

50.8% of sites run Google Analytics.

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

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

VariantShare of sitesMedian
Google analytics 4
51%
Universal analytics
38%
Matomo
7%
Snowplow
2%
Plausible
1%
Umami
0%
At internet piano
0%
Adobe analytics
0%
Fathom
0%
Statcounter
0%
Posthog
0%
Clicky
0%
Amplitude
0%
Mixpanel
0%
Pirsch
0%
Simple analytics
0%
Chartbeat
0%
Heap
0%
Goatcounter
0%
Parsely
0%

Analytics on page. On the fleet: 50.8% google analytics 4, 38.1% universal analytics, 6.5% matomo. 100.0% of sites use at least one google_analytics_4.

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

Analytics is script that exists for you, not for the visitor. It still runs on their main thread: listening to events, batching, sending beacons between interactions. Heavy analytics shows up as input delay, the wait before a click handler even starts.

One analytics tool is a cost. The second one is usually a question nobody asked. Count the tools, then ask who actually reads each report. Most stacks shrink fast under that question.

Related signals Third-party categories → Ad networks on page → Cookie wall detected → Third parties per page → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured