Cloudflare Analytics
Cloudflare Analytics is how a site that already routes its traffic through Cloudflare gets visitor numbers back. Part of it is counted at the network edge, and part of it is a small beacon script the page loads, which is the part visible from a browser. If you have opened developer tools on a site behind Cloudflare and seen a request you did not recognise, this is often it. The index found it on 507 of the 5,294 sites measured, 9.6% of them, which makes it the fifth most-encountered company in a field of 88.
Common, and found on the lightest pages in the index
The unusual thing about this entry is not how often it appears but what it appears next to. The median site carrying Cloudflare Analytics reaches 6 outside companies over 27 third-party requests, with 1 classified as tracking. Against the other 87 companies in the index, that median company count ranks 79th and that request count 77th — near the bottom of both tables, meaning these are among the least loaded pages measured.
That follows from what the product is for. A site reaching for Cloudflare's own numbers is often a site that has not installed a separate analytics vendor, an ad stack or a tag manager. The index's vendor catalogue files this entry under Analytics and does not classify it as tracking.
494 of 507 had contact before the banner could be answered
Early contact happened on 494 of the 507 sites, 97.4%. Of the 88 companies here, that share ranks 13th, so it sits well up the table even though the pages themselves sit near the bottom of it.
The timing explains the combination. The median site made its first third-party contact 506 ms into the load, ranking 83rd of the 88 companies here and so sitting near the fast end of that table, and the earliest first contact anywhere in the group was 90 ms. A page with six third parties still has a first one, and on these pages it arrives early.
What a light page looks like up close
medium.com reached 2 outside companies in total, both inside the window, with first contact at 176 ms. roku.com also reached 2, both inside it. openai.com reached 3, all 3 inside it. canva.com reached 3 as well, at 1,254 ms. These are pages an ordinary reader would call clean, and they are still fully described before any banner could have been answered.
At the group's upper end the shape changes but the pattern does not. britannica.com reached 9 companies with all 9 inside the window behind an IAB TCF consent tool, okta.com 8 with all 8 inside it behind OneTrust, tandfonline.com 10 with all 10 inside it. nist.gov reached 5, 4 of them inside the window, with no banner detected. oxylabs.io is a partial exception at 12 companies with only 2 inside the window, and epicgames.com is the clearest counter-example in the set: 6 companies, none inside the window, first contact at 2,087 ms behind a OneTrust banner. name.com and patreon.com fall between.
Google is on three-quarters of the same pages
Across the 507 sites, Google was also present on 376 of them — 74.2%. OneTrust follows at 14%, jsDelivr at 10.1%, Amazon CloudFront at 7.9% and Meta Pixel at 7.5%, with Amazon Ads, Microsoft Clarity, Google Tag Manager, Sentry and Criteo each below 7%.
One very common neighbour and then a fast drop to single-digit percentages is the same story the medians tell. These are pages with few outside parties on them, and the party they most often share is the one nearly everything shares.
Banners, and what comes after them
A consent tool was detected on 235 of the 507 sites. An IAB TCF consent tool was seen on 116 of them and OneTrust on 79, with Cookiebot on 15, CookieYes on 11, and Usercentrics and Osano on 6 each. Those figures count sites where each tool was seen alongside the others rather than dividing the 235 into slices; a site can carry more than one banner.
After the consent window closes, the median site in this group adds no further companies at all. For the typical page here, the third-party set a visitor meets is settled before an answer is possible.
| Site | Companies | Before consent | First contact |
|---|---|---|---|
| openai.com | 3 | 3 | 532 ms |
| epicgames.com | 6 | 0 | 2087 ms |
| medium.com | 2 | 2 | 176 ms |
| nist.gov | 5 | 4 | 611 ms |
| oxylabs.io | 12 | 2 | 857 ms |
| canva.com | 3 | 3 | 1254 ms |
| roku.com | 2 | 2 | 978 ms |
| name.com | 4 | 4 | 420 ms |
| okta.com | 8 | 8 | 658 ms |
| tandfonline.com | 10 | 10 | 869 ms |
| patreon.com | 6 | 4 | 468 ms |
| britannica.com | 9 | 9 | 747 ms |
| Tool | Sites |
|---|---|
| IAB TCF consent tool | 116 |
| OneTrust | 79 |
| Cookiebot | 15 |
| CookieYes | 11 |
| Usercentrics | 6 |
| Osano | 6 |
The six most common are listed. The remaining 2 of 235 sites with a banner carry something outside that six. One tool is recorded per site, so these counts never overlap.
Seen on the same pages
Companies most often contacted by the same sites. Co-presence only — the crawl records what arrived, not who called whom.
- GoogleTogether on 376 of these sites
- OneTrustTogether on 71 of these sites
- jsDelivrTogether on 51 of these sites
- Amazon CloudFrontTogether on 40 of these sites
- Meta PixelTogether on 38 of these sites
- Amazon AdsTogether on 34 of these sites
- Microsoft ClarityTogether on 30 of these sites
- Google Tag ManagerTogether on 26 of these sites
Questions
Is Cloudflare Analytics a tracker?
The vendor catalogue behind this index lists it under Analytics and does not classify it as tracking. That is a classification, not a verdict: it still means the visitor's browser contacts an outside company during the page load, which is what this index counts.
Why does it appear on such lightly loaded pages?
Sites reaching for the analytics that come with their existing network provider often have not installed a separate measurement or advertising stack. The median page carrying it reaches 6 outside companies, which ranks 79th of the 88 companies in this index.
How many sites is it on?
507 of the 5,294 measured, 9.6% of the corpus, making it the fifth most-encountered company of the 88 broken out here.
Does a page with only two or three third parties still contact them before consent?
In this group, generally yes. medium.com and roku.com each reached two companies, both inside the consent window. Across all 507 sites, 494 had at least one company contacted inside that window.
Which company arrived first on these pages?
The index records when the first third-party contact of a page load happened — a median of 506 ms here — and how many companies arrived inside the consent window, but not the order in which named companies were reached. A per-page breakdown is what MurmStack shows live in the browser.