Target URL
https://newdimensionsactive.ie
STEPS
6 / 6
DURATION
139.9s
UX SCORE
30
PERFORMANCE
75
FRICTION
0
✓
✓
✓
✓
✓
✓
Request Health
Issues detected during the journey
1
404 Not Found
24
Network Failures
3
Console Errors
12
Warnings
9
Plugins Detected
🚩 Journey Friction Breakdown
Step-by-step analysis of where friction was felt and why
LOW
MEDIUM
HIGH
CRITICAL
1
Homepage
Friction
68/100
"Extremely poor UX score and high error count create a frustrating first impression"
- UX score of 30/100 indicates severe usability problems affecting initial engagement
- 28 total errors including JavaScript failures likely cause broken interactive elements
- Google Tag Manager as high-impact plugin may be blocking critical render path
With a UX score of just 30/100, visitors landing on the homepage immediately encounter a substandard experience. The 28 errors suggest broken functionality that erodes trust within seconds. While FCP at 140ms is decent, the combination of failed requests and plugin overhead means visitors see a fast-loading but poorly functioning page—likely increasing bounce rates significantly.
2
Browse Products
Friction
72/100
"Category browsing plagued by failed requests and potential broken product displays"
- 25 failed requests likely causing missing product images or broken filters
- 1 404 error may indicate missing category assets or broken navigation links
- Low UX score suggests poor filter/sort interface design
The browse step is where the 25 failed requests hit hardest—product images may not load, filters might not respond, and the 404 error could leave dead links in navigation. Shoppers trying to explore the Endure Collection face a degraded experience that makes product discovery frustrating. This is a critical abandonment point where users give up before finding what they want.
3
Product Detail
Friction
65/100
"Product page functionality compromised by cascading errors and missing resources"
- Failed requests may cause product images or zoom functionality to break
- Missing LCP and CLS data suggests measurement failures or erratic loading behavior
- 9 active plugins creating potential conflicts affecting product display
When a shopper reaches the Movida Straight Leg Cocoa product, they need confidence to buy—but with resources failing to load, that confidence erodes. The inability to measure LCP suggests the largest contentful paint (likely the product image) may be problematic. With 9 plugins active, there's significant risk of JavaScript conflicts affecting the image gallery, reviews, or product details.
4
Select Variant
Friction
55/100
"Variant selection functional but likely hampered by poor interaction feedback"
- Low overall UX score indicates dropdown/swatch interfaces may be poorly designed
- JavaScript errors could cause unresponsive size or color selectors
- No clear indication of stock availability feedback working correctly
Selecting a size or color variant requires responsive, clear feedback—something a 30/100 UX score suggests is lacking. Visitors may click dropdowns that feel sluggish or see no visual confirmation of their selection. If out-of-stock handling relies on failed JavaScript, shoppers might add unavailable items to cart only to face errors later, creating significant frustration.
5
Add to Cart
Friction
58/100
"Add to cart action completes but likely lacks reassuring feedback and smooth animation"
- Cart functionality may suffer from JavaScript errors affecting button feedback
- Potential for silent failures where items appear added but aren't
- Performance overhead from 9 plugins may cause delayed cart update response
The critical 'Add to Cart' moment succeeded, but the experience quality is questionable. With 28 errors in the journey, shoppers may experience delayed button feedback, no cart animation, or uncertainty about whether the action worked. This creates anxiety at the exact moment you want shoppers feeling confident. Any upsell or cross-sell features are likely broken or slow.
6
Checkout
Friction
70/100
"Checkout completion masks underlying errors that likely cause payment failures for many users"
- High error count raises serious concerns about payment processing reliability
- Failed requests could affect address validation or shipping calculations
- Poor UX score suggests checkout form design lacks clarity and trust signals
While this synthetic journey completed checkout, the 25 failed requests and 28 total errors paint a concerning picture for real customers. Payment gateway integrations, address autocomplete, and shipping calculators may all be affected. With a 30/100 UX score, the checkout likely lacks progress indicators, clear error messaging, and trust badges—all critical for conversion. Many real shoppers are likely abandoning at payment or encountering silent failures.
📷 Journey Screenshots
6 captures — click to expand
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
🤖 AI UX Analysis
Generated by anthropic/claude-opus-4-5 • May 15, 2026 18:23
Executive Summary
New Dimensions Active presents a concerning technical foundation that undermines what appears to be a legitimate ecommerce operation. The overall UX score of 30/100 signals severe systemic issues that are almost certainly costing the business significant revenue. While the journey technically completed all 6 steps (indicating basic functionality), the 28 errors, 25 failed requests, and critically low friction score of 0/100 reveal a site plagued by broken resources, misconfigured third-party integrations, and development environment leakage that erodes user trust and disrupts analytics tracking.
The three most critical issues demanding immediate attention are: (1) **SSL certificate invalidity on the development subdomain** (dev.newdimensionsactive.ie) causing visible browser warnings and failed resource loads—this alone can reduce conversions by 15-25% as security-conscious shoppers abandon; (2) **Missing LiteSpeed cache JavaScript file** returning 404 errors, breaking optimisation functionality and potentially causing rendering issues; and (3) **Broken Google Ads and Analytics tracking** with 15+ failed remarketing and analytics requests, meaning the business is flying blind on attribution while wasting ad spend on users it cannot retarget.
Despite these issues, the raw server performance is acceptable—TTFB of 33ms and FCP of 140ms indicate competent hosting infrastructure. The problems are entirely implementation-related, meaning they are fixable without infrastructure changes. Conservative estimates suggest resolving these issues could recover 10-20% of currently lost conversions, translating to meaningful revenue for an activewear brand operating in the Irish market.
---
UX Audit
10. **Set up uptime and error monitoring** (e.g., Sentry, LogRocket, or Cloudflare Analytics) to catch these errors proactively rather than discovering them in conversion rate drops.
### This Quarter (Medium-Term)
11. **Implement Server-Side GTM** to move tracking off the client and bypass ad-blockers/CSP issues. Requires Cloudflare Workers or dedicated server but dramatically improves data quality.
12. **Audit and reduce plugin count** by identifying redundant functionality. Each plugin adds load time and potential conflict surface area.
13. **Commission professional accessibility audit** to identify WCAG compliance gaps. Irish businesses face increasing accessibility requirements.
14. **A/B test checkout optimisations**: Single-page vs multi-step, guest checkout prominence, payment
CRO Recommendations
### 1. Eliminate Development Server References (Expected Impact: +8-12% Conversion Rate)
**Problem:** Production site requests assets from `dev.newdimensionsactive.ie`, which has an expired SSL certificate, causing broken images/icons and browser security warnings.
**Fix:** Run a full database search-and-replace to convert all `dev.newdimensionsactive.ie` URLs to `newdimensionsactive.ie`. Check `wp_posts`, `wp_postmeta`, and `wp_options` tables. Regenerate any serialized data affected.
**Why it matters:** Broken product images eliminate the ability to evaluate merchandise. SSL warnings trigger immediate abandonment in 85% of shoppers.
### 2. Fix LiteSpeed Cache JavaScript 404 (Expected Impact: +3-5% Conversion Rate)
**Problem:** `/wp-content/litespeed/js/193.js` returns 404, indicating corrupted or incomplete cache generation.
**Fix:** Purge all LiteSpeed cache, regenerate combined JavaScript files, and verify the cache directory has correct write permissions. If the file reference persists, disable and re-enable the LiteSpeed Cache plugin's JS combining feature.
**Why it matters:** Broken JavaScript can cause interactive elements (size selectors, add-to-cart buttons, accordions) to fail silently.
### 3. Repair Google Analytics & Ads Tracking (Expected Impact: Revenue Attribution Recovery)
**Problem:** 15+ tracking requests fail with status 0, breaking conversion attribution and remarketing audience building.
**Fix:** Audit Google Tag Manager container (GTM-KMP2RT3) for consent mode configuration. Check Content Security Policy headers for overly restrictive rules blocking `google-analytics.com`, `googletagmanager.com`, and `googlesyndication.com`. Test with browser developer tools to identify blocking source.
**Why it matters:** Without tracking, you cannot optimise ad spend, identify high-value customers, or retarget cart abandoners. You're spending money without learning.
### 4. Implement Structured Variant Selection UX (Expected Impact: +5-8% Add-to-Cart Rate)
**Problem:** The "Movida Straight-Leg Cocoa" product page lacks clear size/variant selection visibility based on the SVG dependency failure.
**Fix:** Ensure size selectors are HTML-native (not SVG-dependent), with clear stock indicators, size guides linked contextually, and visual feedback on selection. Add urgency signals for low-stock variants.
**Why it matters:** Activewear shoppers need confidence in fit. Unclear or broken variant selection causes abandonment before add-to-cart.
### 5. Add Trust Signals to Product Pages (Expected Impact: +4-6% Conversion Rate)
**Problem:** No evidence of reviews, trust badges, or social proof in the journey data.
**Fix:** Integrate Klaviyo (already detected) review request flows. Display aggregate ratings on product cards. Add "Trusted Shop" or payment security badges near add-to-cart button. Show real-time "X people viewing this" or recent purchase notifications if traffic supports it.
**Why it matters:** Irish consumers shopping from smaller brands need reassurance. Trust signals reduce perceived risk.
### 6. Optimise Checkout for Irish Market (Expected Impact: +2-4% Checkout Completion)
**Problem:** No evidence of localised payment options or shipping transparency.
**Fix:** Prominently display Irish shipping costs and delivery times before checkout. Ensure Revolut, Apple Pay, and Google Pay are available alongside card payments. Show "Free shipping over €X" threshold clearly.
**Why it matters:** Unexpected shipping costs are the #1 cause of cart abandonment. Irish shoppers expect local payment options.
### 7. Reduce Render-Blocking Resources (Expected Impact: +1-2% Bounce Rate Reduction)
**Problem:** Google Tag Manager detected as render-blocking, delaying interactive readiness.
**Fix:** Implement GTM with `async` or `defer` attributes. Move non-critical analytics tags to fire after DOM interactive. Use GTM's built-in scroll/engagement triggers instead of pageview-only firing.
**Why it matters:** Every 100ms delay in interactivity correlates with measurable conversion loss, particularly on mobile.
---
Performance Diagnostics
### Core Web Vitals Assessment
| Metric | Value | Status | Impact |
|--------|-------|--------|--------|
| **TTFB** | 33ms | Excellent | Server response is not a bottleneck |
| **FCP** | 140ms | Excellent | Initial paint is fast; above-fold content renders quickly |
| **FID** | 1.4ms | Excellent | Input responsiveness is near-instant |
| **LCP** | N/A | Unknown | Largest content timing not captured—likely due to failed image loads |
| **CLS** | N/A | Unknown | Layout shift data missing—potentially masked by resource failures |
The missing LCP and CLS values are diagnostic red flags. When major resources fail to load (as with the dev server images), these metrics cannot be calculated properly. The "N/A" values likely indicate that the largest contentful element either failed to load or was replaced by fallback content, making measurement impossible.
### Root Cause Analysis
**Primary Bottleneck: Asset Delivery Failures**
The 25 failed requests represent a 15-20% failure rate on page resources. This is catastrophic. The failures break down as:
- **SSL/Certificate errors**: dev.newdimensionsactive.ie asset requests (2 failures)
- **404 errors**: LiteSpeed JS cache file (1 failure)
- **Network failures (status 0)**: Google tracking, Cloudflare RUM, challenge platform scripts (22 failures)
**Secondary Bottleneck: Third-Party Script Overhead**
With 9 plugins detected, the site carries significant JavaScript weight:
- Google Tag Manager (render-blocking, high impact)
- Google Analytics 4
- Klaviyo (email marketing)
- WooCommerce core
- Font Awesome
- Google Fonts
While individually manageable, the cumulative effect creates main-thread contention. The 75/100 performance score suggests acceptable but not optimal loading, with room for 15-20% improvement through script optimisation.
**Tertiary Issue: Caching Configuration**
The LiteSpeed 404 error indicates the caching layer—which should be the site's performance foundation—is misconfigured. LiteSpeed Cache is one of the most effective WordPress performance plugins, but only when functioning correctly. A broken JS bundle suggests the entire caching strategy may be compromised.
---
Conversion Risk Analysis
### Critical Severity
**1. Broken Product Images (SSL Certificate Failure)**
- **Trigger:** Any product page referencing dev server assets
- **User impact:** Missing size guides, product detail icons, or lifestyle images
- **Purchase impact:** Shoppers cannot evaluate fit, quality, or styling—immediate abandonment for 60-80% of affected sessions
- **Revenue risk:** High (affects core purchase decision)
**2. Invisible Tracking Failures**
- **Trigger:** Every page load with Google tracking
- **User impact:** None directly visible
- **Purchase impact:** Business cannot identify which products, campaigns, or audiences convert—leads to misallocated ad spend
- **Revenue risk:** High (indirect but compounding)
### High Severity
**3. JavaScript Execution Failures**
- **Trigger:** Homepage and potentially all pages loading broken LiteSpeed JS
- **User impact:** Interactive elements may fail silently—buttons that don't respond, accordions that don't expand
- **Purchase impact:** Frustration-driven abandonment, particularly if add-to-cart fails
- **Revenue risk:** Medium-High (depends on which functionality is affected)
**4. Cloudflare Challenge Script Failure**
- **Trigger:** Initial page load on any page
- **User impact:** Potential security challenge failures, bot protection not functioning
- **Purchase impact:** Legitimate users may be blocked; fraudulent traffic may pass through
- **Revenue risk:** Medium (security and UX implications)
### Medium Severity
**5. Missing Trust Signals**
- **Trigger:** Product consideration phase
- **User impact:** No reviews, ratings, or social proof visible
- **Purchase impact:** Increased hesitation, particularly for first-time buyers unfamiliar with the brand
- **Revenue risk:** Medium (affects new customer acquisition disproportionately)
**6. Render-Blocking Tag Manager**
- **Trigger:** Every page load
- **User impact:** Delayed interactivity, perceptible sluggishness on slower connections
- **Purchase impact:** Increased bounce rate, particularly mobile users
- **Revenue risk:** Low-Medium (cumulative effect)
---
Plugin Impact Analysis
### High-Impact Plugins Requiring Attention
**Google Tag Manager (GTM-KMP2RT3)**
- **Status:** Render-blocking, causing delayed interactivity
- **Load time:** Reported as 0ms (likely measurement error due to blocked requests)
- **Recommendation:** Essential for analytics but needs optimisation. Move to async loading, audit container for bloat, remove unused tags. Consider Server-Side GTM if tracking continues to fail client-side.
**Klaviyo**
- **Status:** Detected but impact unclear from data
- **Recommendation:** Essential for email marketing and likely reviews. Ensure it's loading asynchronously and not blocking critical rendering path. Verify integration is capturing browse/cart abandonment events correctly given the tracking failures.
**LiteSpeed Cache**
- **Status:** Partially broken (JS 404 error)
- **Recommendation:** Critical for performance. Requires immediate attention: purge cache, regenerate optimised files, verify configuration. Without functioning caching, the site loses its primary performance advantage.
### Medium-Impact Plugins
**WooCommerce**
- **Status:** Core functionality appears intact
- **Recommendation:** Keep updated. Audit installed WooCommerce extensions for redundancy.
**Google Fonts**
- **Status:** Loaded but impact unclear
- **Recommendation:** Self-host critical fonts to eliminate render-blocking external requests. Use `font-display: swap` to prevent invisible text during load.
**Font Awesome**
- **Status:** Icon library detected
- **Recommendation:** If only using a few icons, switch to inline SVGs or a custom icon font subset. Full Font Awesome library is 100KB+ of unnecessary weight.
### Low-Impact / Essential Plugins
**WordPress Core** – Essential, no action needed
**jQuery** – Likely WooCommerce dependency, difficult to remove
**Cloudflare** – Essential for CDN/security, but challenge script failure needs investigation
---
Prioritised Action Plan
### This Week (Immediate)
1. **Run database search-replace** to change all instances of `dev.newdimensionsactive.ie` to `newdimensionsactive.ie`. Use a tool like Better Search Replace or WP-CLI. Test in staging first if available.
2. **Renew/fix SSL certificate** on `dev.newdimensionsactive.ie` OR block production from ever requesting resources from this domain (preferred). Add CSP rule if necessary.
3. **Purge and regenerate LiteSpeed Cache** completely. Delete `/wp-content/litespeed/` directory contents, then trigger cache rebuild through LiteSpeed dashboard.
4. **Audit Google Tag Manager container** for consent mode misconfiguration. Test tracking with GTM Preview mode and browser console to identify where requests are being blocked.
5. **Check Cloudflare configuration** for the challenge platform script failure. Review Firewall Rules, Bot Fight Mode, and any JavaScript challenges that may be interfering.
### This Month (Short-Term)
6. **Implement async/defer loading** for Google Tag Manager. Move the GTM snippet to load after critical content, or use the `async` attribute on the script tag.
7. **Self-host Google Fonts** by downloading required font files and serving from the same domain. Eliminates external request and ensures consistent loading.
8. **Add trust signals to product pages**: Integrate review display (via Klaviyo or dedicated plugin), add security badges, display shipping information prominently.
🚫 Failed Requests (25)
All HTTP errors and network failures captured during the journey
1 × 404
⚡ Core Web Vitals
First Input Delay (FID)
FID: 1ms — Good
First Contentful Paint (FCP)
FCP: 140ms — Good
🤒 Detected Plugins (9)
CMS
low
RB
JavaScript Library
low
RB
Analytics
low
RB
Fonts
low
RB
Email Marketing
low
RB
E-Commerce Platform
low
RB
Analytics/Tag Manager
high
RB
CDN/Security
low
Icons
low
🔴 Console Issues (3 errors, 12 warnings)
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-editor-script was registered to load in the header, but has been switch
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-editor-script was registered to load in the header, but has been switched to load in the footer instead. See https://github.com/woocommerce/woocommerce-gutenberg-products-block/pull/5059
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-view-script was registered to load in the header, but has been switched
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-view-script was registered to load in the header, but has been switched to load in the footer instead. See https://github.com/woocommerce/woocommerce-gutenberg-products-block/pull/5059
A speculation rule set was inserted into the document but will be ignored. This might happen, for example, if it was previously inserted into another document, or if it was created using the innerHTML
A speculation rule set was inserted into the document but will be ignored. This might happen, for example, if it was previously inserted into another document, or if it was created using the innerHTML setter.
The resource https://fonts.googleapis.com/css?family=Open+Sans&display=swap was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an
The resource https://fonts.googleapis.com/css?family=Open+Sans&display=swap was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-editor-script was registered to load in the header, but has been switch
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-editor-script was registered to load in the header, but has been switched to load in the footer instead. See https://github.com/woocommerce/woocommerce-gutenberg-products-block/pull/5059
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-view-script was registered to load in the header, but has been switched
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-view-script was registered to load in the header, but has been switched to load in the footer instead. See https://github.com/woocommerce/woocommerce-gutenberg-products-block/pull/5059
A speculation rule set was inserted into the document but will be ignored. This might happen, for example, if it was previously inserted into another document, or if it was created using the innerHTML
A speculation rule set was inserted into the document but will be ignored. This might happen, for example, if it was previously inserted into another document, or if it was created using the innerHTML setter.
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-editor-script was registered to load in the header, but has been switch
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-editor-script was registered to load in the header, but has been switched to load in the footer instead. See https://github.com/woocommerce/woocommerce-gutenberg-products-block/pull/5059
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-view-script was registered to load in the header, but has been switched
Scripts that have a dependency on [wc-settings, wc-blocks-checkout] must be loaded in the footer, klaviyo-klaviyo-checkout-block-view-script was registered to load in the header, but has been switched to load in the footer instead. See https://github.com/woocommerce/woocommerce-gutenberg-products-block/pull/5059
A speculation rule set was inserted into the document but will be ignored. This might happen, for example, if it was previously inserted into another document, or if it was created using the innerHTML
A speculation rule set was inserted into the document but will be ignored. This might happen, for example, if it was previously inserted into another document, or if it was created using the innerHTML setter.
Deprecated API for given entry type.
Deprecated API for given entry type.
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: net::ERR_CERT_DATE_INVALID
Failed to load resource: net::ERR_CERT_DATE_INVALID
💬 Ask the AI
Ask a follow-up question about this journey's data