Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
The audit of your website's home page reveals several issues with your tracking setup. The Google Tag Manager (GTM) container is present but did not load successfully, which means none of the expected tags fired. Additionally, your Google Analytics 4 (GA4) setup is present but did not record any hits, indicating a potential issue with data collection. There are also warnings about the lack of a <noscript> fallback and the dataLayer not being initialized correctly, which could affect tracking reliability. Since your site is not on Shopify, there's no need to worry about Trekkie or Web Pixels API. However, the current setup's failure to load GTM and GA4 properly is a significant gap that needs addressing. I recommend auditing other key pages like product, cart, checkout, and order-confirmation to ensure comprehensive tracking across your site. Given these issues, consider connecting your store to PayHelm AI for a more detailed analysis and guidance on resolving these tracking problems.
Tag setup present but not confirmed loading.
GA4 configured but no hits observed (may be consent-gated).
Not an ecommerce store — scored on basic analytics coverage.
No data-quality issues found in tracked events.
Consent Mode present but incomplete (v2 signals missing).
Tag load timing not measured.
No conflicting analytics IDs.
The v2 consent signals were seen, but the default consent state was not observed. Consent Mode v2 needs both a gtag('consent','default',…) call before tags load and a gtag('consent','update',…) call once the visitor responds (CMP: CookieYes).
No tag load timing was captured (the container may not have loaded, or timing was unavailable).
No cross-domain (linker) tracking was detected. If your checkout or other steps live on a different domain, set up linker tracking so visits aren't split into separate sessions.
Google Ads Enhanced Conversions were not detected. They send hashed first-party data (email/phone) to recover conversions lost to cookie restrictions — worth enabling if you run Google Ads.
GA4 User-ID tracking was not detected. If you have logged-in users, setting a User-ID lets GA4 join their activity across devices and sessions.
SEO fundamentals look solid across all checks.
Title is 39 characters — within the ideal 30–70 character range.
Home Care Services in the UK | Caremark (39 chars)Meta description is 137 characters — within the ideal 70–160 character range.
Caremark provides high-quality home care across the UK. Our domiciliary care services include live-i… (137 chars)One H1 heading found — the recommended structure for every page.
Looking for excellent home care near you?No noindex directive — the page is eligible to be indexed.
robots: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1Canonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://www.caremark.co.uk/All core Open Graph tags found — links display richly when shared on social media.
og:title ✓ og:description ✓ og:image ✓Structured data found — search engines can use it to generate rich results (star ratings, FAQs, products, breadcrumbs, etc.).
JSON-LD script foundViewport meta tag found — the page is set up for mobile-friendly rendering.
viewport meta tag presentNo tags were observed sending data. They may be gated behind cookie consent, or none are configured.
— none observed —
Every dataLayer push observed during page load — with full payload and configuration analysis.
›GTM lifecycle events (1)— gtm.js, gtm.dom, gtm.load, etc.
Data points present in the dataLayer that your tags can read (the values pushed alongside each event).
The actual tracking requests your browser sent — the ground-truth proof that a tag fired.
GTM-P9JBW9F
A Google Tag Manager container is installed on this page.
0/1 container(s) returned a successful gtm.js response.
The container script did not load (blocked, unpublished, or wrong ID), so no tags will fire.
Fix this issueNo <noscript> fallback found in the HTML source.
The recommended <noscript> fallback is missing. It's minor, but Google's standard install includes it.
Fix this issueGTM snippet appears inside <head>.
The container is loaded early, as Google recommends, so tags fire as soon as possible.
dataLayer was not clearly initialised before the container snippet.
If the container loads before dataLayer is ready, early values (like ecommerce data) can be lost.
Fix this issueG-T4PMMRRMJ8 — no /g/collect hit observed.
GA4 is configured but we did not see it send data on this page — it may be gated behind cookie consent or misconfigured.
Fix this issuedefault=false, update=true, signals=[ad_storage, ad_user_data, ad_personalization, analytics_storage, functionality_storage, personalization_storage, security_storage], CMP=CookieYes
The v2 consent signals were seen, but the default consent state was not observed. Consent Mode v2 needs both a gtag('consent','default',…) call before tags load and a gtag('consent','update',…) call once the visitor responds (CMP: CookieYes).
Fix this issueDOMContentLoaded 1021ms
No tag load timing was captured (the container may not have loaded, or timing was unavailable).
No linker configuration observed
No cross-domain (linker) tracking was detected. If your checkout or other steps live on a different domain, set up linker tracking so visits aren't split into separate sessions.
Not detected
Google Ads Enhanced Conversions were not detected. They send hashed first-party data (email/phone) to recover conversions lost to cookie restrictions — worth enabling if you run Google Ads.
Not detected
GA4 User-ID tracking was not detected. If you have logged-in users, setting a User-ID lets GA4 join their activity across devices and sessions.
Ecommerce Funnel — Not Applicable
This site doesn't appear to be an online store, so the ecommerce funnel report has been skipped. GTM tag coverage, triggers, variables, and on-page scripts are still audited above.
If this site does sell products, try re-running the audit on a product page URL — that will surface add-to-cart, checkout, and purchase event coverage.
These tracking scripts are hardcoded directly in your page HTML. Moving them into GTM makes them easier to update, pause, version, and conditionally fire — without touching your code.
Meta Pixel script (fbevents.js) found hardcoded directly in the page HTML.
Fix: Remove the hardcoded snippet and use a GTM 'Facebook Pixel' or 'Custom HTML' tag instead.
Risk: If GTM also fires Meta Pixel, you'll double-count conversions and inflate ROAS. Centralising in GTM also lets you pause, version, and conditionally fire without a code deploy.
GA4 gtag.js snippet installed directly in the page HTML (outside GTM).
Fix: Remove the hardcoded GA4 snippet and manage it via a GTM 'Google Analytics: GA4 Configuration' tag.
Risk: Running GA4 both directly and via GTM sends duplicate pageviews and inflates every metric in your reports.
Your tracking has gaps — PayHelm can fix this.
Broken tags mean lost attribution and bad decisions. PayHelm unifies your ecommerce, ad, and analytics data so every number is trustworthy — no guesswork.