Website Tracking & Analytics Audit

caremark.co.uk Tracking & SEO Audit — Grade D

A saved report based on tracking and pages observed during this scan.

Problems foundhttps://www.caremark.co.uk/

Read the full audit summary

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.

AI discovery review not included

What to look at first

Priorities below are taken directly from findings in this report.

SEO Review

100out of 100Grade AExcellent

SEO fundamentals look solid across all checks.

Title tagPass

Title is 39 characters — within the ideal 30–70 character range.

Home Care Services in the UK | Caremark (39 chars)

Meta descriptionPass

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)

H1 headingPass

One H1 heading found — the recommended structure for every page.

Looking for excellent home care near you?

Robots / indexabilityPass

No noindex directive — the page is eligible to be indexed.

robots: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1

Canonical URLPass

Canonical tag points to the page itself — no duplicate-content signals sent to search engines.

https://www.caremark.co.uk/

Open Graph tagsPass

All core Open Graph tags found — links display richly when shared on social media.

og:title ✓ og:description ✓ og:image ✓

Structured data (Schema.org)Pass

Structured data found — search engines can use it to generate rich results (star ratings, FAQs, products, breadcrumbs, etc.).

JSON-LD script found

Mobile viewportPass

Viewport meta tag found — the page is set up for mobile-friendly rendering.

viewport meta tag present

AI discovery review was not included with this saved report.

GTM-P9JBW9Fhead

Not loaded

Tags(0)

No tags were observed sending data. They may be gated behind cookie consent, or none are configured.

— none observed —

Triggers(6)

Every dataLayer push observed during page load — with full payload and configuration analysis.

›GTM lifecycle events (1)— gtm.js, gtm.dom, gtm.load, etc.

Variables(5)

Data points present in the dataLayer that your tags can read (the values pushed alongside each event).

gtm.starteventcmdtargetparams

Network hits(1)

The actual tracking requests your browser sent — the ground-truth proof that a tag fired.

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=G-T4PMMRRMJ8

Overall Tracking Health

64out of 100Grade DNeeds work

Tag manager installed12/20

Tag setup present but not confirmed loading.

GA4 tracking10/20

GA4 configured but no hits observed (may be consent-gated).

Pageview / event coverage10/20

Not an ecommerce store — scored on basic analytics coverage.

Data quality15/15

No data-quality issues found in tracked events.

Consent Mode5/10

Consent Mode present but incomplete (v2 signals missing).

Performance7/10

Tag load timing not measured.

No conflicts5/5

No conflicting analytics IDs.

Advanced Tracking Features

Consent Mode v2Warning

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).

default: noupdate: yes✓ ad_storage✓ ad_user_data✓ ad_personalization✓ analytics_storage✓ functionality_storage✓ personalization_storage✓ security_storageCMP: CookieYes

Tag PerformanceInfo

No tag load timing was captured (the container may not have loaded, or timing was unavailable).

DOM ready 1.02sPage load 1.70s

Cross-domain TrackingInfo

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.

Enhanced ConversionsInfo

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.

User-ID TrackingInfo

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.

Checks

GTM container detectedPass

GTM-P9JBW9F

A Google Tag Manager container is installed on this page.

Container script loads (gtm.js)Fail

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 issue

Noscript fallback presentWarning

No <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 issue

Snippet placement in <head>Pass

GTM snippet appears inside <head>.

The container is loaded early, as Google recommends, so tags fire as soon as possible.

dataLayer initialised before GTMWarning

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 issue

GA4 firingWarning

G-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 issue

Google Consent Mode v2Warning

default=false, update=true, signals=[ad_storage, ad_user_data, ad_personalization, analytics_storage, functionality_storage, personalization_storage, security_storage], CMP=CookieYes

Fix this issue

Tag load performanceInfo

DOMContentLoaded 1021ms

No tag load timing was captured (the container may not have loaded, or timing was unavailable).

Cross-domain trackingInfo

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.

Enhanced Conversions (Google Ads)Info

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.

User-ID tracking (GA4)Info

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.

On-page Scripts — Should Be in GTM (2)

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 (Facebook) Pixel

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.

Google Analytics 4 (direct gtag.js)

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.

Report ID: d846758dc7

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.

Fix this issue Try PayHelm free

Ask a follow-up question