container audit

GTM-N5LVW935

19 tags, 2 custom scripts, 2 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).

2 custom HTML tags carrying 1 KB of JavaScript. This runs on every page the container loads on.
2 third-party hosts reachable from its tags.

Tags19

Custom scripts2

Third parties2

Delivered430 KB

Versions21

What we observed

A real browser loaded uncut.co.uk a month ago and recorded every request it made. This is what happened, as distinct from what the container is configured to do. It is one page load — anything that fires only deeper in the site did not fire here.

Container loaded from googletagmanager.com — Google

Measurement sent to google-analytics.com — Google

Consent Quantcast answered its own API. 2 measurement hits left the page before it was granted, carrying a client id (whether that is permitted depends on jurisdiction, and this was not a European visit). no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision. Google recorded gcs=G111 (all granted). 10 advertising hosts were contacted before anything was granted.

Third parties contacted 25 hosts — fonts.googleapis.com, fonts.bunny.net, r1.ddlnk.net, cdn.tagdeliver.com, static.cloudflareinsights.com, s.skimresources.com, squirrels-gen.getsquirrel.co, r1.trackedweb.net, and 17 more

dataLayer events seen gtm.js, sp_consent_ready, gtm.dom, gtm.load, gtm.scrollDepth

Where the data goes

Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on uncut.co.uk More info »

Findings

Ordered by consequence. review has a concrete cost when it bites; info is real but depends on your setup. Seen is how common it is across the containers we have measured — reported separately on purpose, because common and harmless are different claims.

reviewdocument.write (1)

1 piece of custom code call document.write.

Whydocument.write blocks the HTML parser while it runs, and browsers ignore it entirely once the page has finished parsing — so an async-loaded tag using it can silently do nothing.

CheckIf these tags fire on page load they are costing render time; if they fire later they may not be working at all. Worth confirming the tag still does what it was added to do.

Seenseen in 18.4% of 46,522 containers measured

infoConsent configuration detected (2)

The container declares one or more consent signals.

WhyConsent handling is present in the container. This describes what the artifact declares; what actually happened on the page is measured separately, above.

CheckConfirm these settings match the consent policy you intend to enforce, and compare them with the before-and-after observation.

Seenseen in 44.6% of 46,522 containers measured

Third parties it can reach

Each host is a party that can execute code or receive data in a visitor's browser. Follow one to see who else loads it. More info »

www.google-analytics.com ×14edition.pagesuite-professional.co.uk ×1

What the custom templates can do

Custom templates are third-party code shipped inside the container. Injecting scripts and running page globals is ordinary for them — most tag templates need it to work — so this is an inventory, not a warning. It lists the capability each template declares so you can match it against templates you meant to install.

__cvt_171905861_19 private runs page-level globals

__cvt_WR44P gallery injects code from cdn.parsely.com · runs page-level globals

Detected on

Sites observed loading this container. A container used across many hosts is a shared template; one on a single host is a bespoke build. Follow a site to see every container it loads.

uncut.co.uk

What this audit describes

Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.

Container	`GTM-N5LVW935`
Published version	`21` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 17:51:48 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-N5LVW935`
Body checksum	`e3ec64d7bab3f0251575d35855359bc9e3c609222bb120a9eeadfcef20f6d26c` Evidence of the exact bytes we read, not an identity: Google varies the response per request, so re-fetching an unchanged container yields a different checksum. Compare the published version instead.

Re-audit

This reading is from a month ago. A container can be republished at any time, and nothing here updates on its own — a fresh read is the only way to know whether it still says this. Running it again replaces this page in place, so the link keeps working.

Re-audit GTM-N5LVW935

Check another container

Put this container under version control. Tagora exports it to a repository you own, so every change arrives as a pull request. How it works »