GA4 double page views on homepages, by platform (Sept 2026, top 1M)
| Platform | 2+ page_views | 2+ to the same ID | Same ID loaded twice in gtag.js | Homepages with GA4 page_view |
|---|---|---|---|---|
| Shopify | 21.1% | 12.9% | 52.2% | 7,544 |
| Wix | 18.3% | 10.4% | 11.6% | 164 |
| Other/custom | 15.6% | 3.6% | 6.8% | 148,801 |
| Webflow | 14.7% | 2.6% | 5.0% | 536 |
| WordPress | 12.9% | 1.9% | 5.8% | 40,308 |
| Squarespace | 11.0% | 3.7% | 1.5% | 136 |
| All | 15.2% | 3.6% | 8.3% | 197,489 |
Source: PageSpeed Matters, HTTP Archive, Sept 2026. Hits to google-analytics.com only. Wix, Webflow and Squarespace have small samples.
Summary
A GA4 tag that fires twice can double a property's page views and cut its bounce and engagement figures in ways that are hard to spot in reports. We counted how many popular homepages send more than one GA4 page_view on a single load, and where those hits go.
15.2% of top 1M homepages that send a GA4 page_view (30,072 of 197,489) fire it two or more times. Most of those send the hits to two different GA4 properties. Only 3.6% send two page_views to the same measurement ID, which is the case that inflates one property's numbers.
What we measured
We looked at HTTP Archive's Sept 2026 mobile crawl of the top 1M sites by Chrome traffic. For each homepage we counted GA4 collect hits with the page_view event, the measurement ID each hit was sent to, and how many times gtag.js was loaded for each ID.
Counts use hits to google-analytics.com only. The base is the 197,489 homepages that send at least one GA4 page_view there.
Sending page views to more than one GA4 property can be intentional, for example when an agency and the site owner each keep their own property. So only two page_views to the same ID count as true double counting within a property. Core Web Vitals figures use Chrome UX Report field data at the 75th percentile for homepages that have it.
Most double page views go to two different properties
30,072 of 197,489 GA4 homepages (15.2%) fire page_view two or more times on one load. That does not mean 15.2% of sites have inflated analytics.
Of those 30,072, 24,545 (81.6%) send page_view to two or more measurement IDs. Each property then sees one page view. That can be intentional, or it can be an old tag that was never removed.
The problem case is smaller. 7,087 homepages, or 3.6% of the 197,489, send two page_views to the same ID, so that one property records two page views for a single visit. Separately, 8.3% of GA4 homepages (16,458) load gtag.js twice for the same measurement ID. Not every duplicate load sends a second page_view, but it is a likely route to one.
15.2%
Share of top 1M homepages sending a GA4 page_view that fire it two or more times on one load, to the same or different properties.
Shopify stores double-fire most
21.1% of 7,544 Shopify homepages with GA4 send two or more page_views, and 12.9% send two to the same ID. On 40,308 WordPress homepages the figures are 12.9% and 1.9%, and on 148,801 homepages on other platforms they are 15.6% and 3.6%.
Shopify homepages also load gtag.js twice for the same ID far more often: 52.2% do, against 5.8% on WordPress. Not every duplicate load fires a second page_view, but it is the likely source of most same-ID doubles. A store can add GA4 through more than one route, such as a sales channel app and a snippet pasted into the theme, and when both stay active the same tag runs twice.
The smaller platforms in the table have far fewer homepages, so their shares move more from site to site.
Site popularity changes little
Double page views are about as common on big sites as on small ones. 13.8% of 2,026 Top 10K homepages fire page_view twice, against 15.2% of 17,512 Top 100K homepages and 15.2% of 177,951 homepages in the rest of the top 1M.
Large sites may have analytics teams, but they also tend to carry more tags and more vendors, so popularity alone does not seem to protect against a double tag.
Double page views go with lower pass rates
Homepages that fire page_view twice pass Core Web Vitals less often. 37.0% of 25,254 such homepages with CrUX data pass, against 47.2% of 136,267 that fire it once.
This is a correlation, not proof that a second GA4 tag slows a page by that much. A homepage with duplicate tags often has other unreviewed scripts too, and platform mix may play a part. But a duplicate tag is extra JavaScript and extra network requests that the page does not need.
What this means for your site
If your page view counts look high or your engagement rate looks oddly low, check for a double tag before you trust the reports.
- Open your homepage with the browser's network panel, filter for "collect", and count the requests with en=page_view. Note the tid value on each one.
- Two hits with the same tid mean one property is counting each visit twice. Two different tids mean two properties, so confirm both are still wanted.
- Search your theme, plugins, apps and tag manager for every place GA4 is installed. Keep one method, either the hardcoded gtag.js snippet or a tag manager or platform integration, not several.
- In GA4, use DebugView or Tag Assistant to confirm a single page_view per load after the fix.
Sources
- HTTP Archive crawl of the top 1M sites by Chrome traffic, September 2026, mobile
- Chrome UX Report (CrUX) field data, September 2026
- Chrome UX Report (CrUX) documentation, Google: https://developer.chrome.com/docs/crux
Embed this research
Paste this on your site to embed the chart. It links back to the source automatically.
<iframe id="psm-ga4-double-counting" src="https://www.pagespeedmatters.com/embed/data-studies/ga4-double-counting" width="100%" height="600" style="width:100%;border:1px solid #E2E3E1;border-radius:12px" loading="lazy" title="GA4 Double Counting 2026: 15.2% Fire Two Page Views - PageSpeed Matters"></iframe>
<script>window.addEventListener("message",function(e){if(e&&e.data&&e.data.psmEmbed==="ga4-double-counting"&&e.data.height){var f=document.getElementById("psm-ga4-double-counting");if(f){f.style.height=e.data.height+"px";}}});</script>
<p style="font:14px/1.5 system-ui,sans-serif">Source: <a href="https://www.pagespeedmatters.com/resources/data-studies/ga4-double-counting">GA4 Double Counting 2026: 15.2% Fire Two Page Views - PageSpeed Matters</a></p>
Frequently asked questions
How common is GA4 double counting?
15.2% of top 1M homepages that send a GA4 page_view fire it two or more times on one load, but 81.6% of those send the hits to two different properties. Only 3.6% send two page_views to the same measurement ID, which inflates a single property's numbers.
Why does GA4 record two page views for one visit?
Usually because the tag is installed twice, for example a hardcoded gtag.js snippet plus a tag manager or platform integration. In our data, 8.3% of GA4 homepages load gtag.js twice for the same measurement ID.
How do I check if my site sends duplicate GA4 page views?
Open the page with the browser's network panel, filter for collect requests and count those with en=page_view. Two hits with the same tid value mean one property is counting the visit twice.
Does a duplicate GA4 tag slow down my site?
Homepages that fire page_view twice pass Core Web Vitals 37.0% of the time, against 47.2% for those that fire it once. That is a correlation, not proof of cause, but a duplicate tag is extra code the page does not need.
Duplicate analytics tags are usually a quick cleanup, and fixing them gives you reports you can trust and one less script on every page. Need help with this? See our website maintenance services.