Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup shows some areas that need attention. Google Tag Manager (GTM) is correctly implemented, but there's a warning due to the absence of a <noscript> fallback, which is a backup for users with JavaScript disabled. Google Analytics 4 (GA4) is firing successfully, but there are two different GA4 IDs in use, which could lead to data inconsistencies. There are no Shopify-native analytics detected, which is expected since Shopify isn't detected on your site. Additionally, the page load performance is slower than ideal, which may affect user experience and data accuracy. On the homepage, no specific e-commerce events like 'view_item_list' were observed, which is a gap that should be addressed. There are also some console errors related to font loading, which could be affecting site performance. For the next steps, consider auditing a product page or cart page to ensure all relevant events are firing correctly. Given the issues found, it would be beneficial to connect your store to PayHelm AI for a more comprehensive analysis and guidance on resolving these gaps.
GTM container installed and loading.
GA4 is installed and sending data.
4 of 4 key funnel stages look healthy.
No data-quality issues found in tracked events.
Consent Mode not detected.
Tag loading is slower than ideal.
Conflicting or deprecated analytics IDs detected.
No Google Consent Mode was detected. This mainly matters if you run Google Ads with EEA/UK traffic — no Google Ads pixel was seen on this site, so it's lower priority for now.
Google Tag Manager took 13.1s to load. Slow tag loading delays tracking and can hurt page performance — consider reducing the number of tags or loading them later.
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.
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.
Multiple GA4 measurement IDs were found (G-G8BTBN8QT0, G-F37RMT2R0J). Sending the same events to more than one GA4 property is sometimes intentional, but is often an accident that doubles event counts or splits data — confirm each ID is meant to be here.
SEO basics are mostly in place with a few opportunities to improve.
Title is 47 characters — within the ideal 30–70 character range.
Medical Spa Boca Raton | Evolution Rejuvenation (47 chars)Meta description is 10 characters. Aim for 70–160 chars to maximise click-through rate.
Boca Raton (10 chars)One H1 heading found — the recommended structure for every page.
Your Body, Transformed From Within.No noindex directive — the page is eligible to be indexed.
robots: max-image-preview:largeCanonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://evolutionrejuvenation.com/1 Open Graph tag(s) missing. Complete the set for consistent social link previews.
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 presentMarketing & analytics tags observed sending data while the page loaded.
Every dataLayer push observed during page load — with full payload and configuration analysis.
›GTM lifecycle events (4)— 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-WP2M6CG7
A Google Tag Manager container is installed on this page.
1/1 container(s) returned a successful gtm.js response.
The container's JavaScript downloaded successfully, so GTM can run.
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 issueG-G8BTBN8QT0, G-F37RMT2R0J — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
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.
No consent API calls observed
No Google Consent Mode was detected. This mainly matters if you run Google Ads with EEA/UK traffic — no Google Ads pixel was seen on this site, so it's lower priority for now.
GTM 13081ms, GA4 first hit 12946ms, DOMContentLoaded 13446ms
Google Tag Manager took 13.1s to load. Slow tag loading delays tracking and can hurt page performance — consider reducing the number of tags or loading them later.
Fix this issueNo 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.
G-G8BTBN8QT0, G-F37RMT2R0J
Multiple GA4 measurement IDs were found (G-G8BTBN8QT0, G-F37RMT2R0J). Sending the same events to more than one GA4 property is sometimes intentional, but is often an accident that doubles event counts or splits data — confirm each ID is meant to be here.
Fix this issuepurchase observed=false, checkout page audited=false
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.
Fix this issueFunnel 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
Not observed on this page. Set up 'view_item_list' on your collection/category/search pages for funnel visibility.
Fix this gapNot observed during this load — 'select_item' requires user interaction on collection/category pages. Verify by manually testing the action on that page.
Consideration
Not observable on home pages — 'view_item' only fires on product detail pages. Audit that page type to verify coverage.
Cart Activity
Not observable on home pages — 'add_to_cart' only fires on product pages and cart. Audit that page type to verify coverage.
Not observable on home pages — 'remove_from_cart' only fires on cart page. Audit that page type to verify coverage.
Not observable on home pages — 'view_cart' only fires on cart page. Audit that page type to verify coverage.
Checkout Funnel
Not observable on home pages — 'begin_checkout' only fires on checkout entry page. Audit that page type to verify coverage.
Not observable on home pages — 'add_shipping_info' only fires on checkout shipping step. Audit that page type to verify coverage.
Not observable on home pages — 'add_payment_info' only fires on checkout payment step. Audit that page type to verify coverage.
Not observable on home pages — 'purchase' only fires on order confirmation / thank-you page. Audit that page type to verify coverage.
Post-Purchase
This event fires server-side (server-side or order management system) and cannot be observed by a browser-based audit.
Access to font at 'https://bodysculptingpros.com/wp-content/uploads/elementor/google-fonts/fonts/montserrat-jtusjig1_i6t8kchkm459wlhyw.woff2' from origin 'https://evolutionrejuvenation.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
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.