Vampire Vape's GA4 property carries a trust score of 76/100, meaning a meaningful portion of reported data cannot be fully relied upon for strategic decisions. Two high-severity issues — a 147% spike in session_start events and a client-side event failing to reach GA4 — indicate likely tagging regressions or data loss that could be distorting traffic volumes and attribution. With £218,784 in tracked revenue and 6,939 purchases on record, resolving these integrity gaps is critical before using this data to inform budget allocation or funnel optimisation.
Vampire Vape's mobile Core Web Vitals are failing in the field — LCP is hitting 6.70 seconds against Google's 2.5-second pass threshold, which puts organic rankings at direct risk on mobile where the majority of vape shoppers browse; the single biggest revenue-adjacent issue is that two render-blocking files (srverror.com/styles.css and the Google Fonts stylesheet) are wasting over 42,000ms of aggregate load time across 56% of pages, actively delaying when products become visible and purchasable. Fixing the render-blocking resources and taming Google Tag Manager — which alone is burning up to 980ms of blocking time per page and over 10,000ms sitewide — could push mobile performance scores from the current 68–70 range into the high 70s to 80, with projected TBT cuts of roughly 55%. These are not cosmetic score improvements: faster LCP and lower interactivity delay directly correlate with higher add-to-cart rates and lower bounce on product and category pages.
Rank #1 by blocking time on this page. Google Tag Manager transfers 458 KB and keeps the main thread busy for 1683ms, delaying INP and TBT.
Fix: GTM's own weight usually means a lot of tags. Run GTM Preview and look for tags firing on every page that could be scoped to specific events or URLs.
Rank #1 by blocking time on this page. Google Tag Manager transfers 299 KB and keeps the main thread busy for 382ms, delaying INP and TBT. It fires BEFORE consent according to the tracking audit — so it's degrading experience for users who reject cookies too.
Fix: GTM's own weight usually means a lot of tags. Run GTM Preview and look for tags firing on every page that could be scoped to specific events or URLs.
Rank #1 by blocking time on this page. Google Tag Manager transfers 299 KB and keeps the main thread busy for 356ms, delaying INP and TBT. It fires BEFORE consent according to the tracking audit — so it's degrading experience for users who reject cookies too.
Fix: GTM's own weight usually means a lot of tags. Run GTM Preview and look for tags firing on every page that could be scoped to specific events or URLs.
Google's Core Web Vitals threshold for LCP is ≤2.5s at the 75th percentile of real Chrome users. This page is at 6.70s (rated poor). Real-user data — this is what impacts Search rankings.
Vendors firing despite Reject All: GA4. This breaches GDPR/PECR and is incompatible with Consent Mode v2 'denied' signals.
Fix: Add consent-aware GTM triggers (Consent Mode v2 'ad_storage' / 'analytics_storage' = denied) and verify tags wait for an Update signal before firing.
Detected phone in params ['_p', 'cid', 'gtm', 'sid', 'uafvl'] of https://region1.google-analytics.com/g/collect?…
Fix: Hash, redact, or remove PII before sending. Use Enhanced Conversions / CAPI with hashed values where required.
Detected phone in params ['nocache'] of https://consent.Cookiebot.com/logconsent.ashx?…
Fix: Hash, redact, or remove PII before sending. Use Enhanced Conversions / CAPI with hashed values where required.
Went from 41,442 to 102,220. A change this large usually indicates a tagging regression (deploy / theme update) or a data outage.
Fix: Check deploy history and GTM change log around the inflection. Verify the event still fires via DebugView.
The tracking-auditor saw these events fire in the browser, but GA4 has no record of them in the audit window. Common causes: ad-blocker / CMP denial in the real traffic mix, beacon sent to wrong endpoint, Measurement Protocol payload malformed, or a tag filter dropping the event server-side.
Fix: In GTM Preview mode, confirm the event lands in the /g/collect endpoint with the right `tid`. If yes, enable GA4 DebugView and check for a filter/data retention issue. If the gap is large, suspect adblock/CMP denial — consider server-side GTM.
URL: https://www.vampirevape.co.uk/e-liquid/vampire-vape-max-watermelon-10ml-nic-salt-e-liquid — client-side: 1 GA4 events fired client-side (view_item); GA4: 0 page_views in window
Seen on 56/100 audited mobile pages.
Fix: This single file blocks render across most of the site. Defer it (add `defer`), preload it, or inline its critical portion. Biggest sitewide win per line-of-change you'll find.
Seen on 56/100 audited mobile pages.
Fix: This single file blocks render across most of the site. Defer it (add `defer`), preload it, or inline its critical portion. Biggest sitewide win per line-of-change you'll find.
+ 231 more findings — see the detailed dashboards.