Website Tracking & Analytics Audit

designersduds.com Tracking & SEO Audit — Grade C

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

Works, with issueshttps://www.designersduds.com/

Read the full audit summary

Your website's tracking setup has a few areas that need attention. The Google Tag Manager (GTM) is correctly installed and loads as expected, but the GA4 analytics did not fire on your homepage, which is a concern. Additionally, there is no <noscript> fallback for GTM, and the dataLayer was not initialized before the GTM container, which could affect data accuracy. Since your site is not on Shopify, there's no risk of duplicate pixels from Trekkie or the Web Pixels API. For your next steps, I recommend auditing a product page to ensure 'view_item_list' and other relevant events are firing correctly. Given the issues found, consider connecting your store to PayHelm AI for a more comprehensive analysis and solutions.

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 37 characters — within the ideal 30–70 character range.

DesignersDuds.com | affordable luxury (37 chars)

Meta descriptionPass

Meta description is 151 characters — within the ideal 70–160 character range.

designersduds apparel and footwear for men and women. Contact us on whatsapp 07493426301 - for every… (151 chars)

H1 headingPass

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

Designers Duds Fashion

Robots / indexabilityPass

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

No robots meta tag (defaults to index, follow).

Canonical URLPass

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

https://www.designersduds.com

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.

Wix Storeslikely

Wix Stores markup in HTML

GTM-KTQPSPMGhead

Loaded

Tags(0)

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

— none observed —

Triggers(9)

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

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

Variables(19)

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

eventgtm.uniqueEventIdsite_idgtm.startdeveloper_id.dYzMzMDactiontypeucCategoryInstagram ContentSite Search by Fast SimonUsercentrics for WixVisitor AnalyticsWIXFacebook PixelGoogle Tag ManagerGoogle Tag Servicescmdtargetparams

Network hits(2)

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

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

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

Overall Tracking Health

79out of 100Grade CFair

Tag manager installed20/20

GTM container installed and loading.

GA4 tracking10/20

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

Ecommerce funnel coverage20/20

4 of 4 key funnel stages look healthy.

Data quality15/15

No data-quality issues found in tracked events.

Consent Mode5/10

Consent Mode present but incomplete (v2 signals missing).

Performance4/10

Tag loading is slower than ideal.

No conflicts5/5

No conflicting analytics IDs.

Advanced Tracking Features

Consent Mode v2Warning

The v2 consent signals were seen, but a consent update after the user chooses 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: Usercentrics).

default: yesupdate: no✓ ad_storage✓ ad_user_data✓ ad_personalization✓ analytics_storage✓ functionality_storage✓ personalization_storage✓ security_storageCMP: Usercentrics

Tag PerformanceWarning

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

GTM 2.47sDOM ready 4.17sPage load 5.96s

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-KTQPSPMG

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 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-7FWZF1V8YW — 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

Wix Stores platform detectedInfo

Wix Stores markup in HTML

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

Google Consent Mode v2Warning

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

Fix this issue

Tag load performanceWarning

GTM 2467ms, DOMContentLoaded 4165ms

Google Tag Manager loaded in 2.5s — 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: AddToCart

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_cart

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: Purchase

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.

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.

Multi-page Coverage — 1 additional page checked

The audit automatically visited additional page types discovered on the site to verify tags fire across the full funnel, not just on the entry page.

Collection/category/all-products

GTM: GTM-KTQPSPMGGA4: not firingGoogle (gtag.js)

gtm.domgtm.loadconsent_status

Report ID: 9b855ef1f3

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