Website Tracking & Analytics Audit

axopeptides.co.uk Tracking & SEO Audit — Grade A

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

Works, with issueshttps://axopeptides.co.uk/

Read the full audit summary

Your website's tracking setup is mostly in good shape, with Google Tag Manager (GTM) and Google Analytics 4 (GA4) both successfully firing on your homepage. However, there are a couple of areas that need attention. The tag load performance is slower than optimal, which could impact data accuracy and user experience. Additionally, there's a gap in tracking the 'view_item_list' event, which is important for understanding how users interact with product listings. Since your site is not using Shopify, there's no risk of duplicate pixel firing from Shopify's Trekkie or Web Pixels API. Next, I recommend auditing your product pages, cart, and checkout process to ensure all critical events are captured accurately. If you want to address these issues efficiently, consider connecting your store to PayHelm AI for a more comprehensive analysis.

AI discovery review not included

What to look at first

Priorities below are taken directly from findings in this report.

SEO Review

78out of 100Grade BGood

SEO basics are mostly in place with a few opportunities to improve.

Title tagPass

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

AxoPeptide - Batch-Tested. Traceable. Research-Only (51 chars)

Meta descriptionWarning

No meta description. While not a direct ranking factor, a good description significantly improves click-through from search results.

No meta description found.

H1 headingPass

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

Research Peptides UK —Batch-Tested Materials for Laboratory Research

Robots / indexabilityPass

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

robots: max-image-preview:large

Canonical URLPass

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

https://axopeptides.co.uk/

Open Graph tagsWarning

2 Open Graph tag(s) missing. Complete the set for consistent social link previews.

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.

WooCommercedetected

WooCommerce markup (woocommerce / wc-* classes) in HTML

GTM-P47R8NSFhead

Loaded

Tags(3)

Marketing & analytics tags observed sending data while the page loaded.

Meta PixelPixel

4 hits

Google AdsConversion / Remarketing

3 hits

Google Analytics 4GA4 Event

2 hits

Triggers(9)

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

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

Variables(10)

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

gtm.starteventgtm.uniqueEventIdgtm.scrollThresholdgtm.scrollUnitsgtm.scrollDirectiongtm.triggerscmdtargetparams

Network hits(14)

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

200gtm.jshttps://www.googletagmanager.com/gtm.js?id=GTM-P47R8NSF

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=AW-18339618615

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=GT-KVJ2BBVR

200pixelhttps://connect.facebook.net/en_US/fbevents.js

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=AW-18339618615&cx=c&gtm=4e68a1

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=GT-KVJ2BBVR&cx=c&gtm=4e68a1

204adshttps://stats.g.doubleclick.net/g/collect?v=2&ngs=1&ibt=1&tid=G-YDJM4689XF&cid=1577363621.1786485687&gtm=45Pe68b0h2v9259584254za200zb9260731307zd9260731307&rcb=

beaconadshttps://ad.doubleclick.net/ccm/s/collect?auid=1341549930.1786485686&gtm=45be68a1za200zb9260731307zd9260731307xec&fmt=8

200adshttps://googleads.g.doubleclick.net/pagead/viewthroughconversion/18339618615/?random=1786485686448&cv=11&fst=1786485686448&bg=ffffff&guid=ON&async=1&en=page_vie

beaconga4-collecthttps://analytics.google.com/g/collect?v=2&tid=G-YDJM4689XF&gtm=45Pe68b0h2v9259584254za200zb9260731307zd9260731307&_p=1786485685784&_gaz=1&gcs=G1--&gcd=13l3l3l3

200pixelhttps://connect.facebook.net/signals/plugins/openbridge3.js?v=2.9.373

200pixelhttps://connect.facebook.net/signals/config/976812165414579?v=2.9.373&r=stable&domain=axopeptides.co.uk&optin_meta_enabled_capi=true&hme=6d1ed5deee7eafc01c53d9e

200pixelhttps://www.facebook.com/tr/?id=976812165414579&ev=PageView&dl=https%3A%2F%2Faxopeptides.co.uk%2F&rl=&if=false&ts=1786485687529&iw=false&sw=800&sh=600&v=2.9.373

beaconga4-collecthttps://analytics.google.com/g/collect?v=2&tid=G-YDJM4689XF&gtm=45Pe68b0h2v9259584254za200zb9260731307zd9260731307&_p=1786485685784&gcs=G1--&gcd=13l3l3l3l5l1&np

JavaScript errors (2)

Not signed in with the identity provider.

[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.

Overall Tracking Health

94out of 100Grade AExcellent

Tag manager installed20/20

GTM container installed and loading.

GA4 tracking20/20

GA4 is installed and sending data.

Ecommerce funnel coverage20/20

4 of 4 key funnel stages look healthy.

Data quality15/15

No data-quality issues found in tracked events.

Consent Mode10/10

Consent Mode v2 configured.

Performance4/10

Tag loading is slower than ideal.

No conflicts5/5

No conflicting analytics IDs.

Advanced Tracking Features

Consent Mode v2Pass

Consent Mode v2 is configured. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.

default: yesupdate: yes✓ ad_personalization✓ ad_storage✓ ad_user_data✓ analytics_storage✓ functionality_storage✓ security_storage✓ personalization_storage✓ region✓ wait_for_update

Tag PerformanceWarning

Google Tag Manager loaded in 2.2s — a little slow. Keeping it under ~1.5s helps both tracking accuracy and page speed.

GTM 2.20sGA4 first hit 2.78sDOM ready 4.08sPage load 5.14s

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.

Checkout & Purchase CoverageWarning

We couldn't reach the checkout or order-confirmation page during this audit, so purchase tracking is unverified. Purchase is the single most important event to get right — test it with a real or test order and confirm the 'purchase' event fires once on the thank-you page.

Checks

GTM container detectedPass

GTM-P47R8NSF

A Google Tag Manager container is installed on this page.

Container script loads (gtm.js)Pass

1/1 container(s) returned a successful gtm.js response.

The container's JavaScript downloaded successfully, so GTM can run.

Noscript fallback presentPass

Found <noscript> ns.html iframe.

The fallback for visitors with JavaScript disabled is in place.

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 GTMPass

dataLayer is defined before the container snippet.

Data is available to tags from the very first event.

GA4 firingPass

GA4 — collect hit observed.

Google Analytics 4 is actively sending pageview/event data.

JavaScript errors during loadInfo

2 error(s) logged.

JavaScript errors were logged during page load. These don't necessarily affect tracking — only errors that directly interrupt pixel execution matter. See any vendor-specific errors below for actionable issues.

WooCommerce platform detectedInfo

WooCommerce markup (woocommerce / wc-* classes) in HTML

This site runs on WooCommerce. Tracking setup and common pitfalls differ by platform, which is factored into this audit.

Google Consent Mode v2Pass

default=true, update=true, signals=[ad_personalization, ad_storage, ad_user_data, analytics_storage, functionality_storage, security_storage, personalization_storage, region, wait_for_update]

Consent Mode v2 is configured. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.

Tag load performanceWarning

GTM 2196ms, GA4 first hit 2782ms, DOMContentLoaded 4075ms

Google Tag Manager loaded in 2.2s — a little slow. Keeping it under ~1.5s helps both tracking accuracy and page speed.

Fix this issue

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.

Checkout / purchase coverageWarning

purchase observed=false, checkout page audited=false

Fix this issue

Marketing Funnel Coverage

1 gap to verify0 observed· 10 not auditable on this page

Funnel events are page-specific: purchase only fires on order confirmation, add_to_cart requires a user click. Events shown as are not observable on this page type — audit each page separately for full coverage.

Discovery

Product List / Collection Viewhigh

view_item_listMeta: ViewContent

Not observed on this page. Set up 'view_item_list' on your collection/category/search pages for funnel visibility.

Fix this gap

Product Click from Listmedium

select_item

Not observed during this load — 'select_item' requires user interaction on collection/category pages. Verify by manually testing the action on that page.

Consideration

Product Detail Page Viewcritical

view_itemMeta: ViewContent

Not observable on home pages — 'view_item' only fires on product detail pages. Audit that page type to verify coverage.

Cart Activity

Add to Cartcritical

add_to_cartMeta: AddToCartfound in JS ✓

Not observable on home pages — 'add_to_cart' only fires on product pages and cart. Audit that page type to verify coverage.

Remove from Cartmedium

remove_from_cartfound in JS ✓

Not observable on home pages — 'remove_from_cart' only fires on cart page. Audit that page type to verify coverage.

Cart / Bag Page Viewhigh

view_cart

Not observable on home pages — 'view_cart' only fires on cart page. Audit that page type to verify coverage.

Checkout Funnel

Begin Checkoutcritical

begin_checkoutMeta: InitiateCheckout

Not observable on home pages — 'begin_checkout' only fires on checkout entry page. Audit that page type to verify coverage.

Shipping Info Enteredhigh

add_shipping_info

Not observable on home pages — 'add_shipping_info' only fires on checkout shipping step. Audit that page type to verify coverage.

Payment Info Enteredhigh

add_payment_infoMeta: AddPaymentInfo

Not observable on home pages — 'add_payment_info' only fires on checkout payment step. Audit that page type to verify coverage.

Purchase / Order Confirmationcritical

purchaseMeta: Purchasefound in JS ✓

Not observable on home pages — 'purchase' only fires on order confirmation / thank-you page. Audit that page type to verify coverage.

Post-Purchase

Refund / Order Cancellationlow

refund

This event fires server-side (server-side or order management system) and cannot be observed by a browser-based audit.

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

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.

Report ID: bbe8972627

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