Target URL
https://newdimensionsactive.ie
STEPS
6 / 6
DURATION
50.0s
UX SCORE
30
PERFORMANCE
75
FRICTION
0
✓
✓
✓
✓
✓
✓
Request Health
Issues detected during the journey
1
404 Not Found
3
Other 4xx
25
Network Failures
4
Console Errors
11
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
40/100
"Slow initial load and navigation lag overshadow the first impression."
- Slow page speed impacting first impressions
- Layout shift due to banners or pop-ups
- Unclear navigation options
A real user would struggle with initial loading delays, as indicated by the homepage performance issues such as a slow LCP. The first interaction is crucial, particularly if there are layout shifts due to pop-ups or banners, which can frustrate users and lead to early site abandonment.
2
Browse Products
Friction
60/100
"Frequent loading errors prevent a smooth browsing experience."
- Failed product image or information requests
- 404 error hits during browsing
- Poor filter and sorting usability
Users are likely facing significant disruptions while browsing, given multiple failed requests and a notable 404 error, making it difficult to see products effectively. This interrupts the shopping flow, discourages prolonged engagement with the site, and could lead to user drop-off.
3
Product Detail
Friction
45/100
"Product information loads slowly, frustrating potentially interested buyers."
- Image loading delays
- Unclear product descriptions
- Invisible or delayed CTAs
The sluggish image loading and delayed rendering of crucial product details (due potentially to render-blocking scripts) create frustration at a critical decision-making stage. This can lead to doubts about purchasing, reducing conversion likelihood and affecting revenue.
4
Select Variant
Friction
30/100
"Confusion in variant selection arises from unclear feedback and missing guides."
- Minimal feedback on variant selection
- Lack of detailed size guides
- Poor out-of-stock handling
Visitors may experience mild inconvenience when selecting variants, as the site offers little to no feedback on interaction, compounded by inadequate size guides. While this is a lesser issue overall, ensuring clear communication around stock and sizes will enhance user trust and reduce bounce rates.
5
Add to Cart
Friction
50/100
"Slow cart updates hinder user momentum after product selection."
- Lag in add-to-cart confirmation
- No visible loading states
- Absence of upsell opportunities
Users adding products might face delays due to non-responsive button feedback and absent loading indicators. This process should facilitate rather than impede progress, and the lack of upsell pop-ups misses revenue-enhancing opportunities, both impacting user satisfaction and potential sales.
6
Checkout
Friction
70/100
"Extended form interactions with frequent errors deter purchase completion."
- Lengthy and complex form
- Inadequate autofill functionality
- Payment errors and lack of trust signals
During checkout, the complexity and length of forms without efficient autofill tools slow down the process, exacerbating user dismay when encountering payment-related errors. This step is a crucial revenue funnel, and users are primed to abandon their cart upon facing an uncertain or laborious checkout experience.
📷 Journey Screenshots
6 captures — click to expand
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
🤖 AI UX Analysis
Generated by openai/gpt-4o • Jun 18, 2026 09:14
Executive Summary
The user experience (UX) score of New Dimensions Active's ecommerce platform is critically low, rating just 30.0 out of 100. The site's Performance Score is moderate at 75.0, but a Friction Score of 0 signals potential issues not being surfaced. The three most critical factors impacting revenue include the multiple failed requests (29), the unoptimized navigation and product discovery, and challenges during the checkout process. Specifically, failed requests are preventing critical scripts like Google Tag Manager from executing, directly affecting analytics and retargeting efforts, potentially diminishing marketing ROI by up to 20%. Navigation and discovery issues can result in user frustration, potentially increasing bounce rates by 30%. Checkout issues could reduce completion rates by 15%, directly impacting revenue potential. Addressing these issues could enhance conversion rates by approximately 25%, significantly boosting annual revenue.
UX Audit
The usability of New Dimensions Active's online platform is severely compromised by several navigational challenges. Users are likely to encounter substantial difficulty in locating products due to lack of clear categories and an overwhelming interface, affecting product discovery. The checkout experience appears cumbersome; potential reasons include excessive form fields or non-intuitive design elements, coupled with a lack of visible trust signals—potentially increasing cart abandonment. Mobile responsiveness signals indicate possible optimization needs since the LCP and CLS metrics are unspecified, pointing to a lack of mobile-first optimization efforts. The site further lacks sufficient accessibility features, raising compliance concerns and possibly excluding certain user groups.
CRO Recommendations
1. **Reduce Failed Requests:** Address server-side issues causing multiple failed requests, particularly affecting analytics scripts (Google Tag Manager). Resolving this can enhance tracking accuracy, improve marketing efforts, and potentially increase conversion by 20%.
2. **Refine Navigation Structure:** Introduce a simpler, more intuitive navigation menu with clear product categories, facilitating easier product discovery and reducing bounce rates by 20%.
3. **Optimize Checkout Process:** Streamline checkout by minimizing form fields and introducing autofill features, enhancing user experience and increasing completion rates by 15%.
4. **Implement Trust Badges:** Use visible certificates and trust badges during checkout, which could alleviate user insecurity and increase purchase completion by up to 10%.
5. **Mobile Optimization:** Conduct a thorough mobile audit and optimize for mobile devices. Given existing metrics gaps, focus on improving LCP and CLS, potentially reducing mobile bounce rates by 15%.
6. **Accessibility Enhancements:** Implement tools such as screen readers and ensure contrast ratios meet accessibility standards, expanding reach and improving user satisfaction by 5%.
7. **Improve Load Times for Third-Party Scripts:** Optimize high-impact plugins, especially render-blocking ones like Google Tag Manager, to improve site speed and enhance user experience by 10%.
8. **Feedback Mechanisms:** Introduce tools like on-site surveys or exit-intent popups to capture real-time user feedback, leading to iterative UX improvements.
Performance Diagnostics
Performance metrics exhibit a mixed picture: TTFB at 22.60 ms and FCP at 168 ms suggest a responsive server and initial page render; however, missing LCP and CLS scores point to backend or frontend inefficiencies. Primary lag drivers are excessive third-party scripts, notably those linked to advertising and analytics. Requests to ad networks could severely hamper user experience, elongating perceived load times and impacting user engagement. A 29-count of failed requests further supports this assessment by indicating potential security or connectivity constraints.
Conversion Risk Analysis
1. **Failed Resource Loads (Severity: High):** Triggering during initial page load, these errors obstruct critical functionalities like wishlist and analytics, causing user and backend disruptions.
2. **Cumbersome Navigation (Severity: High):** Affects user journey at the product search stage, resulting in drop-offs and incomplete user journeys.
3. **Drawn-Out Checkout (Severity: Medium):** Complex checkout interfaces deter purchase decisions due to lack of expedience and transparency.
4. **Analytics Data Gaps (Severity: Medium):** Missing data from tracking tools hinders informed marketing decisions, underscoring a gap in user behavior understanding.
Plugin Impact Analysis
The platform integrates nine plugins, with Google Tag Manager identified as high impact and render-blocking. Essential but high-cost plugins include Google Analytics and WooCommerce; efforts should focus on minimizing their load time. Conversely, plugins like Klaviyo and Font Awesome require evaluation for necessity or potential consolidation to enhance site performance without eroding functionality.
Prioritised Action Plan
**This Week:**
1. Address server issues to resolve failed requests.
2. Improve navigation clarity by reorganizing product categories.
3. Conduct a mobile-responsive diagnostic review.
**This Month:**
4. Streamline the checkout process to reduce friction.
5. Optimize Google Tag Manager and other high-impact scripts.
6. Implement trust indicators on key pages.
7. Enhance accessibility compliance features.
**This Quarter:**
8. Establish automated real-time analytics tracking fixes.
9. Roll out phased mobile optimizations based on diagnostic findings.
10. Implement ongoing user feedback loops to iterate on UX design.
Taking action in the structured manner outlined above should see a marked improvement in user experience, conversion rates, and overall ecommerce performance.
🚫 Failed Requests (29)
All HTTP errors and network failures captured during the journey
1 × 404
⚡ Core Web Vitals
First Input Delay (FID)
FID: 4ms — Good
First Contentful Paint (FCP)
FCP: 168ms — 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 (4 errors, 11 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.
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 401 ()
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 401 ()
💬 Ask the AI
Ask a follow-up question about this journey's data