Target URL
https://newdimensionsactive.ie
STEPS
6 / 6
DURATION
52.4s
UX SCORE
30
PERFORMANCE
75
FRICTION
0
✓
✓
✓
✓
✓
✓
Request Health
Issues detected during the journey
11
404 Not Found
75
Network Failures
12
Console Errors
22
Warnings
11
Plugins Detected
🚩 Journey Friction Breakdown
Step-by-step analysis of where friction was felt and why
LOW
MEDIUM
HIGH
CRITICAL
1
Homepage
Friction
25/100
"Slow rendering on homepage affects first impressions."
- Potentially slow LCP, although not specifically recorded
- Render-blocking scripts from high-impact plugins
The homepage experience may feel sluggish to users due to delayed rendering, linked to high-impact plugins like Google Tag Manager. This can lead to impatience or frustration, reducing user engagement at critical first impression moments.
2
Browse Products
Friction
65/100
"Broken links disrupt browsing flow."
- Presence of 404 errors
- Navigational disruptions due to failed requests
Users encountering 404 errors while browsing products experience broken journeys, which may lead to frustration and increased bounce rates. The business implication is a potential loss of sales opportunities due to these navigational roadblocks.
3
Product Detail
Friction
40/100
"Failed requests hinder product detail fetching."
- Interrupted load caused by failed requests
- Potential incomplete display of product information
Accessing full product details is vital for purchase decisions. Failed requests can prevent users from viewing necessary data, such as images or descriptions, leading to uncertainty. This hesitation can dramatically decrease conversion rates.
4
Select Variant
Friction
15/100
"Variant selection relatively smooth with minor delays."
While selecting product variants, users may experience some minor latency. However, since these delays do not heavily impact decision-making, the overall friction is minimal, contributing to a satisfactory decision-making process.
5
Add to Cart
Friction
30/100
"Inconsistent cart updates due to site performance issues."
- Occasional lag due to performance metrics
- Moments of TTFB spikes
Although TTFB is generally low, fluctuations can occasionally cause delays in cart updates, leading to possible double clicks or user errors. Disruptions at this stage can plant seeds of doubt, influencing abandonment later in the process.
6
Checkout
Friction
85/100
"Checkout process failure due to structural issues."
- Structural delays introduced by cumulative plugin load
- High number of failed requests interfering with transactions
The checkout experience is plagued by failures and delays, significantly risking transaction completions. With high user stakes at this stage, these interruptions can significantly impact conversion rates, leading to revenue loss and increased customer frustration.
📷 Journey Screenshots
6 captures — click to expand
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
🤖 AI UX Analysis
Generated by gpt-4o • May 13, 2026 21:52
Executive Summary
The user experience health of the New Dimensions Active website is currently inadequate, with an overall UX score of 30.0 out of 100. The performance score stands at a reasonable 75.0, but the friction score at 0.0 indicates significant usability challenges. The most critical issues involve: 1) High volume of 404 errors, especially the failure to load key JavaScript files like `jquery-3.4.1.min.js`, `customs.js`, and `owl.carousel.js`, which could result in a non-functioning or incomplete user interface directly impacting conversion potential by up to 40%. 2) Render-blocking plugins such as Google Tag Manager, Meta Pixel, and TikTok Pixel, which significantly delay page load times, potentially reducing conversion rates by 20-30%. 3) The absence of Largest Contentful Paint (LCP) and Cumulative Layout Shift (CLS) metrics, critical indicators for measuring visual stability and primary content loading speed, may imply poorly rendered pages which can turn users away.
UX Audit
The navigation clarity is significantly hindered by repeated failed resource loads. Critical JavaScript files not loading obscures user interactions and may lead to incomplete page rendering. The absence of LCP and CLS readings suggests potential visual stability issues, making content discovery difficult. The cart and checkout experiences could suffer from broken elements due to missing scripts, leading to a cumbersome checkout — an essential phase where users often abandon carts if processes are not smooth. Despite having a solid First Contentful Paint (FCP) of 340ms suggesting rapid initial rendering, further navigation could be restricted.
Mobile responsiveness cannot be conclusively assessed in the absence of specific mobile data but should be reviewed given the display complexity implied by the plugins and existing issues. Accessibility concerns are expected, with missing resource files possibly leading to non-compliance with screen readers or other assistive technologies, severely affecting a portion of users' ability to interact with the site effectively.
CRO Recommendations
1. **Resolve 404 Errors for JavaScript Files**: Ensure essential scripts like `jquery.min.js` are correctly loaded. This fix will restore core functionalities on user interfaces improving conversions by an estimated 40%.
2. **Optimize and Defer Render-blocking Plugins**: Update Google Tag Manager, Meta Pixel, and TikTok Pixel to load asynchronously, reducing initial page load times and boosting conversions by 25%.
3. **Validate Core Web Vitals**: Address missing LCP and CLS metrics by ensuring pages render important elements first and maintain layout stability. Expected conversion boost: 15-20%.
4. **Improve Checkout Process**: Reinstate complete form and function using accurate script loading; redesign for clarity and efficiency will enhance the shopping experience with a conversion increase by 10-15%.
5. **Increase Accessibility Compliance**: Use tools like Lighthouse audits to ensure the website is accessible, particularly focusing on missing elements and potential screen reader barriers, offering a 10% conversion benefit by reducing user friction.
Performance Diagnostics
Performance, while decent with an FCP of 340ms and TTFB of 33ms, suffers from larger issues primarily due to failing resource requests and blocking plugins. The resource load failures disrupt the complete functioning of the page, inhibiting user interactions. Given that render-blocking plugins are causing delays, these should be loaded asynchronously or removed if not essential. The absence of LCP and CLS data suggests pages with elements that load outside the expected sequence, degrading overall performance.
Conversion Risk Analysis
1. **404 JavaScript Errors**: High severity, blocking core functionalities, noticeable upon initial page interaction. Critical conversion impact reducing user engagement and interaction completeness.
2. **Render-blocking Plugins**: Medium-high severity upon page load. Increases time to interactive threshold, deterring impatient users from proceeding.
3. **Absence of Core Web Vitals**: Medium severity affecting user experience consistency and confidence, compounded by unpredictable load sequences.
Plugin Impact Analysis
Google Tag Manager, Meta Pixel, and TikTok Pixel hold substantial potential for performance hindrance as they are render-blocking. These should either be optimized for non-blocking load patterns or re-evaluated for necessity. Essential plugins like WooCommerce and WordPress remain non-negotiable for site functioning but should still be optimized.
Prioritised Action Plan
### This Week
1. Fix all 404 JavaScript errors.
2. Update and test plugin configurations to load asynchronously.
### This Month
3. Verify and optimize LCP and CLS readings through CSS and script optimization.
4. Conduct a mobile responsiveness and accessibility audit with tools like Lighthouse.
### This Quarter
5. Implement enhanced checkout flow after ensuring the necessary script infrastructure is stable.
6. Comprehensive site audit post-corrective actions to measure improvements.
7. Regularly maintain plugin updates to stay abreast of performance enhancements.
8. Implement a consistent user testing framework to address ongoing user experience developments.
🚫 Failed Requests (86)
All HTTP errors and network failures captured during the journey
11 × 404
⚡ Core Web Vitals
First Input Delay (FID)
FID: 3ms — Good
First Contentful Paint (FCP)
FCP: 340ms — Good
🤒 Detected Plugins (11)
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
Advertising/Tracking
high
RB
Advertising/Tracking
high
RB
🔴 Console Issues (12 errors, 22 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.
Specifying 'overflow: visible' on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/view-transitions/blob/main/debugging_ov
Specifying 'overflow: visible' on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/view-transitions/blob/main/debugging_overflow_on_images.md for details.
[Meta Pixel] - Duplicate Pixel ID: 171218963448322.
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.
[TikTok Pixel] - Missing 'content_id' paramter
Issue: The 'content_id' parameter isn't being received. This is required for Video Shopping Ads (VSA).
Suggestion: Include the 'content_id' parameter in
[TikTok Pixel] - Missing 'content_id' paramter
Issue: The 'content_id' parameter isn't being received. This is required for Video Shopping Ads (VSA).
Suggestion: Include the 'content_id' parameter in your source code. This is required for Video Shopping Ads (VSA). See https://ads.tiktok.com/help/article/standard-events-parameters?redirected=2 for more information.
[TikTok Pixel] - Missing 'content_id' paramter
Issue: The 'content_id' parameter isn't being received. This is required for Video Shopping Ads (VSA).
Suggestion: Include the 'content_id' parameter in
[TikTok Pixel] - Missing 'content_id' paramter
Issue: The 'content_id' parameter isn't being received. This is required for Video Shopping Ads (VSA).
Suggestion: Include the 'content_id' parameter in your source code. This is required for Video Shopping Ads (VSA). See https://ads.tiktok.com/help/article/standard-events-parameters?redirected=2 for more information.
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.
Specifying 'overflow: visible' on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/view-transitions/blob/main/debugging_ov
Specifying 'overflow: visible' on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/view-transitions/blob/main/debugging_overflow_on_images.md for details.
[Meta Pixel] - Duplicate Pixel ID: 171218963448322.
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
[TikTok Pixel] - Missing 'content_id' paramter
Issue: The 'content_id' parameter isn't being received. This is required for Video Shopping Ads (VSA).
Suggestion: Include the 'content_id' parameter in
[TikTok Pixel] - Missing 'content_id' paramter
Issue: The 'content_id' parameter isn't being received. This is required for Video Shopping Ads (VSA).
Suggestion: Include the 'content_id' parameter in your source code. This is required for Video Shopping Ads (VSA). See https://ads.tiktok.com/help/article/standard-events-parameters?redirected=2 for more information.
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.
Specifying 'overflow: visible' on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/view-transitions/blob/main/debugging_ov
Specifying 'overflow: visible' on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/view-transitions/blob/main/debugging_overflow_on_images.md for details.
[Meta Pixel] - Duplicate Pixel ID: 171218963448322.
[TikTok Pixel] - Missing "value" parameter
Issue: Events shared are missing a 'value' parameter'. This is used calculate ROAS for people and the bid for your highest value customers.
Suggestion: Go t
[TikTok Pixel] - Missing "value" parameter
Issue: Events shared are missing a 'value' parameter'. This is used calculate ROAS for people and the bid for your highest value customers.
Suggestion: Go to your source code and include the "value" parameter. See https://ads.tiktok.com/help/article/standard-events-parameters?redirected=2 for more information.
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: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: net::ERR_CERT_DATE_INVALID
💬 Ask the AI
Ask a follow-up question about this journey's data