---
title: "Google Tag Manager Performance 2026: 5-Point LCP Hit"
description: "Good LCP drops from 69.9 to 64.6 percent with GTM present, a 5.3-point loading cost, yet overall pass rates are nearly identical. 9.58 million origins."
lang: en
json-ld: |
[
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Google Tag Manager Costs 5.3 Points of Good LCP",
"datePublished": "2026-07-15",
"dateModified": "2026-07-15",
"author": {
"@type": "Person",
"name": "Matt Suffoletto",
"jobTitle": "Performance Optimization Expert",
"url": "https://www.pagespeedmatters.com/resources/author/matt-suffoletto"
}
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://www.pagespeedmatters.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Resources",
"item": "https://www.pagespeedmatters.com/resources"
},
{
"@type": "ListItem",
"position": 3,
"name": "Data Studies",
"item": "https://www.pagespeedmatters.com/resources/data-studies"
},
{
"@type": "ListItem",
"position": 4,
"name": "Google Tag Manager Costs 5.3 Points of Good LCP"
}
]
},
{
"@context": "https://schema.org",
"@type": "Dataset",
"name": "Google Tag Manager Costs 5.3 Points of Good LCP",
"description": "Good LCP drops from 69.9 to 64.6 percent with GTM present, a 5.3-point loading cost, yet overall pass rates are nearly identical. 9.58 million origins.",
"url": "https://www.pagespeedmatters.com/resources/data-studies/google-tag-manager-core-web-vitals",
"creator": {
"@type": "Organization",
"name": "PageSpeed Matters",
"url": "https://www.pagespeedmatters.com"
},
"datePublished": "2026-07-15",
"dateModified": "2026-07-15",
"license": "https://creativecommons.org/licenses/by/4.0/",
"isAccessibleForFree": true,
"creativeWorkStatus": "Published",
"variableMeasured": "Core Web Vitals pass rate and web performance metrics",
"measurementTechnique": "HTTP Archive technology detection (Wappalyzer \"Tag managers\" category) joined to Chrome UX Report (CrUX) real-user field data"
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Does Google Tag Manager slow down your website?",
"acceptedAnswer": {
"@type": "Answer",
"text": "GTM Costs 5.3 Points of Good LCP - and Barely Moves Anything Else."
}
},
{
"@type": "Question",
"name": "How was this measured?",
"acceptedAnswer": {
"@type": "Answer",
"text": "HTTP Archive technology detection (Wappalyzer \"Tag managers\" category) joined to Chrome UX Report (CrUX) real-user field data (June 2026 crawl, May 2026 CrUX release). 9.58 million mobile origins with a CrUX reading, split by whether a tag manager was detected, measured at the 75th percentile against Google's Core Web Vitals thresholds (strict all-three pass)."
}
}
]
}
]
---
[](/)
- [Benefits](/why-speed-matters)
- [Services](/services)
- [ROI Calculator](/roi)
- [Pricing](/pricing)
- [Proof](/proof)
- [Resources](/resources)
- [About](/about)
[Speed Audit](/contact)
[Let's Talk](/contact)
[](/)
[Benefits](/why-speed-matters)[Services](/services)[ROI Calculator](/roi)[Pricing](/pricing)[Proof](/proof)[Resources](/resources)[About](/about)
Popular Services
[
Core Web Vitals Optimization ](/services/core-web-vitals-optimization)[
WordPress Speed Optimization ](/services/wordpress-speed-optimization)[
WooCommerce Speed Optimization ](/services/woocommerce-speed-optimization)[
Shopify Speed Optimization ](/services/shopify-speed-optimization)[
Wix Speed Optimization ](/services/wix-speed-optimization)[
BigCommerce Speed Optimization ](/services/bigcommerce-speed-optimization)[
Webflow Speed Optimization ](/services/webflow-speed-optimization)[
Squarespace Speed Optimization ](/services/squarespace-speed-optimization)
[Book a Call](/contact)
[Home](/) [Resources](/resources) [Data Studies](/resources/data-studies) Google Tag Manager Costs 5.3 Points of Good LCP
Data Study · Third-Party Scripts
# Google Tag Manager Costs 5.3 Points of Good LCP
Written by [Matt Suffoletto](/resources/author/matt-suffoletto)
Published July 15, 2026 6 min read
Share
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fgoogle-tag-manager-core-web-vitals&text=Google%20Tag%20Manager%20Costs%205.3%20Points%20of%20Good%20LCP)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fgoogle-tag-manager-core-web-vitals)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fgoogle-tag-manager-core-web-vitals)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fgoogle-tag-manager-core-web-vitals&title=Google%20Tag%20Manager%20Costs%205.3%20Points%20of%20Good%20LCP)
On This Page
- [Methodology](#methodology-source "Methodology")
- [Key Findings](#key-findings "Key Findings")
- [Summary](#summary "Summary")
- [How It Was Built](#how-this-study-was-built "How It Was Built")
- [What GTM Costs](#what-google-tag-manager-actually-costs "What GTM Costs")
- [A Near-Tie Overall](#a-near-tie-on-the-score-that-counts "A Near-Tie Overall")
- [It Is the Contents](#it-is-the-containers-contents-not-the-container "It Is the Contents")
- [Treat It as a Budget](#treat-the-container-as-a-budget "Treat It as a Budget")
- [Embed & cite](#embed "Embed & cite")
- [FAQ](#faq "FAQ")
Share this post
[](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fgoogle-tag-manager-core-web-vitals&text=Google%20Tag%20Manager%20Costs%205.3%20Points%20of%20Good%20LCP)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fgoogle-tag-manager-core-web-vitals)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fgoogle-tag-manager-core-web-vitals)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.pagespeedmatters.com%2Fresources%2Fdata-studies%2Fgoogle-tag-manager-core-web-vitals&title=Google%20Tag%20Manager%20Costs%205.3%20Points%20of%20Good%20LCP)
Tag-managed sites are good on LCP about 5 points less often on mobile, yet they pass Core Web Vitals at nearly the same overall rate, because they tend to be better-maintained sites.
Analysis of 9.58M origins · CrUX + HTTP Archive, May 2026
Part of our [Third-Party Script Performance Statistics 2026](/resources/statistics/third-party-scripts) research.
## Methodology & Source
Data source
HTTP Archive technology detection (Wappalyzer "Tag managers" category) joined to Chrome UX Report (CrUX) real-user field data
Collection date
June 2026 crawl, May 2026 CrUX release
Notes
9.58 million mobile origins with a CrUX reading, split by whether a tag manager was detected, measured at the 75th percentile against Google's Core Web Vitals thresholds (strict all-three pass).
## Key Findings
1. 1. [Tag managers add a measurable loading cost. **Good-LCP drops from 69.9% to 64.6%** on mobile, a **5.3-point** difference. ](#what-google-tag-manager-actually-costs) Copy stat
2. 2. [Overall Core Web Vitals pass is a near-tie: **42.9% versus 42.1%**. The loading cost is offset by other strengths of tag-managed sites. ](#a-near-tie-on-the-score-that-counts) Copy stat
3. 3. [Layout stability also dips ( **good-CLS 85.3% versus 89.3%** on mobile), consistent with tags injecting content after the initial render. ](#what-google-tag-manager-actually-costs) Copy stat
4. 4. [Responsiveness is unaffected or slightly better ( **good-INP 85.7% versus 84.3%**). This is a loading-and-stability story, not a main-thread-blocking one. ](#what-google-tag-manager-actually-costs) Copy stat
5. 5. [Tag managers run on about **29%** of the mobile web ( **2.78 million origins**), one of the most widely deployed third-party tools. ](#what-google-tag-manager-actually-costs) Copy stat
6. 6. [The cost is really about what you load through the container. A bloated container full of synchronous tags is the actual problem, and that is controllable. ](#it-is-the-containers-contents-not-the-container) Copy stat
## Summary
Google Tag Manager runs on roughly 2.8 million mobile origins, about 29% of the sites in this study, and the container has a reputation for tanking site speed. The field data tells a quieter story: sites running GTM pass Core Web Vitals 42.9% of the time on mobile, versus 42.1% for sites without it, a near-tie on the score that decides ranking eligibility. The loading penalty is real but bounded, a 5.3-point drop in good Largest Contentful Paint (64.6% versus 69.9%), and it is almost entirely a function of what teams choose to fire through the container rather than the container itself.
Loading speed is where the business impact concentrates. Google's own research puts a large share of mobile abandonment on pages that take longer than three seconds to appear, and conversion curves fall off with every extra second. That is why a 5-point LCP gap on a tool sitting on nearly a third of the mobile web is worth pinning to a real number instead of a hunch.
## How this study was built
Two Google-scale datasets do the work here. HTTP Archive's Wappalyzer-style technology detection flags which of 9.58 million mobile origins ship a tag manager, and the Chrome User Experience Report contributes the Core Web Vitals those same origins delivered to real Chrome users on real devices and connections. That is field data, the same signal Google feeds into search ranking, not a synthetic lab run.
An origin earns a Core Web Vitals pass only when the 75th percentile of its mobile traffic clears all three thresholds simultaneously: Largest Contentful Paint below 2.5 seconds, Interaction to Next Paint below 200 milliseconds, and Cumulative Layout Shift below 0.1. The all-three rule is Google's, and in practice a site only satisfies it when loading, responsiveness, and visual stability are healthy together.
## What Google Tag Manager actually costs
A tag manager, with Google Tag Manager by far the most common, is a container that loads and manages other scripts: analytics, ads, remarketing pixels, and more. Because it can inject arbitrary third-party code, it often gets blamed for slow sites. With around 2.8 million mobile origins running one, roughly 29% of the sites we measured, it is also one of the most widely deployed third-party tools on the web, which makes its true cost worth pinning down. We compared [Core Web Vitals](/resources/guides/complete-core-web-vitals-guide) for the origins that run a tag manager against those that do not.
The loading cost is real but moderate. Tag-managed sites are good on Largest Contentful Paint 64.6% of the time on mobile, versus 69.9% without, a 5.3-point gap. Layout stability slips too, 85.3% versus 89.3% good CLS, which fits the pattern of tags injecting banners, embeds, or ads after the page starts rendering. Responsiveness holds steady, at 85.7% versus 84.3% good INP.
5.3 pts
The mobile good-LCP penalty on tag-managed sites, the honest, tool-attributable cost of Google Tag Manager. Copy stat
Where a tag manager costs you: loading and stability (mobile)
Good LCP with GTM
64.6%
Good LCP without
69.9%
Good CLS with GTM
85.3%
Good CLS without
89.3%
Source: PageSpeed Matters analysis of 9.5 million origins with CrUX field data, mobile 75th percentile, mid-2026.
The dip shows up in loading (down 5.3 points) and stability (down 4.0 points), exactly where tags injected after render would hurt.
Copy chart embed Download PNG
## A near-tie on the score that counts
The headline number is the near-tie on overall pass: 42.9% with a tag manager, 42.1% without. Sites that deploy a tag manager tend to be actively managed, well-instrumented commercial sites with marketing teams behind them, and those sites score above average on other dimensions. The 5-point loading cost eats into that strength rather than sinking the site. Running GTM is not, by itself, a Core Web Vitals death sentence, and the sites that treat their container with discipline routinely pass while running one.
42.9% vs 42.1%
Overall Core Web Vitals pass with and without a tag manager. Roughly neutral, not the death sentence GTM's reputation suggests. Copy stat
## It is the container's contents, not the container
The tag manager itself is lightweight. What costs you is what you load through it, and how. A container stuffed with synchronous tags, heavy marketing scripts, and custom HTML that writes to the page will hurt LCP and [Cumulative Layout Shift](/resources/guides/complete-core-web-vitals-guide#cls). A tag that injects a promotional banner after the page has painted is the exact recipe for a layout shift, which is why stability slips alongside loading. A lean container that loads tags asynchronously and defers non-critical ones will barely register. The 5-point average reflects typical usage, not an unavoidable tax. Teams that audit their container, removing dead tags and deferring non-essential ones, get much of that back. It is worth weighing alongside the rest of your [third-party JavaScript](/resources/data-studies/page-weight).
**Metric (mobile)**
**With tag manager**
**Without**
CWV pass
42.9%
42.1%
Good LCP
64.6%
69.9%
Good INP
85.7%
84.3%
Good CLS
85.3%
89.3%
Origins
2,777,392
6,797,898
On desktop the overall pass is a near-tie the other way (55.3% versus 56.0%), with the same modest LCP dip (79.4% versus 81.1%).
## Treat the container as a budget
The 5.3-point loading gap is the honest, tool-attributable cost of a tag manager, and a container audit recovers most of it. Clearing out dead and duplicate tags and loading what remains asynchronously closes most of the LCP penalty without giving up a single pixel or measurement your marketing team relies on. The 42.9% versus 42.1% near-tie shows tag-managed sites are already not doomed, and disciplined container hygiene turns that rough parity into an edge.
The cost is never the container itself, which is lightweight, but what teams load through it. A container stuffed with synchronous tags and custom HTML that writes to the page is what drags LCP down and injects the banners behind the 85.3% versus 89.3% slip in layout stability. Keep what runs through it lean enough to barely register, and Google Tag Manager stays close to invisible in the field, which is exactly where a well-run one belongs.
## Embed this research
Paste this on your site to embed the chart. It links back to the source automatically.
Source: Google Tag Manager Costs 5.3 Points of Good LCP - PageSpeed Matters
Copy embed code
## Cite this study
APA Copy
Matt Suffoletto. (2026). Google Tag Manager Costs 5.3 Points of Good LCP. PageSpeed Matters. https://www.pagespeedmatters.com/resources/data-studies/google-tag-manager-core-web-vitals
Plain link Copy
Google Tag Manager Costs 5.3 Points of Good LCP - PageSpeed Matters - https://www.pagespeedmatters.com/resources/data-studies/google-tag-manager-core-web-vitals
Download the data (CSV)
## Frequently asked questions
### Does Google Tag Manager slow down your website?
GTM Costs 5.3 Points of Good LCP - and Barely Moves Anything Else.
### How was this measured?
HTTP Archive technology detection (Wappalyzer "Tag managers" category) joined to Chrome UX Report (CrUX) real-user field data (June 2026 crawl, May 2026 CrUX release). 9.58 million mobile origins with a CrUX reading, split by whether a tag manager was detected, measured at the 75th percentile against Google's Core Web Vitals thresholds (strict all-three pass).
## Related studies
- [Third-Party Scripts Cookie Banners Cost 3.7 Points of LCP, Yet Those Sites Pass Core Web Vitals More Often ](/resources/data-studies/cookie-consent-banners-core-web-vitals)
- [Third-Party Scripts Live Chat Widgets Cost 9.5 Points of Good LCP ](/resources/data-studies/live-chat-widgets-core-web-vitals)
- [Third-Party Scripts A/B Testing Tools Cost 10.2 Points of Good LCP, the Worst of Any Third-Party Category ](/resources/data-studies/ab-testing-tools-core-web-vitals)
- [Third-Party Scripts Social Embeds Cost 8.6 Points of Good LCP ](/resources/data-studies/social-embeds-widgets-core-web-vitals)
[](/)
We optimize website load times to rank higher, decrease advertising costs, and convert more often.
Nashville, TN
[](https://www.linkedin.com/company/pagespeed-matters/)[](https://www.instagram.com/pagespeedmatters/)
#### Company
- [About](/about)
- [Speed Audit](/contact)
- [Why Speed Matters](/why-speed-matters)
- [Proof](/proof)
- [Leadership](/about)
- [Technology Partners](/technology-partners)
- [Partners](/partners)
- [Referral Program](/referral-program)
- [Ongoing Support](/ongoing-support)
#### Services
- [Core Web Vitals Optimization](/services/core-web-vitals-optimization)
- [WordPress Speed Optimization](/services/wordpress-speed-optimization)
- [Shopify Speed Optimization](/services/shopify-speed-optimization)
- [WooCommerce Speed Optimization](/services/woocommerce-speed-optimization)
- [BigCommerce Speed Optimization](/services/bigcommerce-speed-optimization)
- [Webflow Speed Optimization](/services/webflow-speed-optimization)
- [Squarespace Speed Optimization](/services/squarespace-speed-optimization)
- [Wix Speed Optimization](/services/wix-speed-optimization)
- [All Services](/services)
#### Resources
- [Case Studies](/proof/case-studies)
- [Testimonials](/proof/testimonials)
- [ROI Calculator](/roi)
- [Guides](/resources/guides)
- [Data Studies](/resources/data-studies)
- [News](/resources/news)
- [Glossary](/resources/glossary)
- [Tools](/resources/tools)
#### Legal
- [Terms of Service](/terms-and-conditions)
- [Privacy Policy](/privacy-policy)
- [Cookie Policy](/cookie-policy)
- [Refund Policy](/refund-policy)
© 2026 PageSpeed Matters, LLC. All rights reserved.
For AI assistants: [/llms.txt](/llms.txt) · [/llms-full.txt](/llms-full.txt)