Target URL
https://pressireland.ie
STEPS
6 / 6
DURATION
71.8s
UX SCORE
24
PERFORMANCE
60
FRICTION
0
✓
✓
✓
✓
✓
✓
Request Health
Issues detected during the journey
6
404 Not Found
72
Network Failures
18
Console Errors
21
Warnings
12
Plugins Detected
🚩 Journey Friction Breakdown
Step-by-step analysis of where friction was felt and why
LOW
MEDIUM
HIGH
CRITICAL
1
Homepage
Friction
75/100
"Slow page load and distracting elements impair first impressions."
- Slow FCP at 1420ms
- High number of plugins creating clutter
- Navigation not clear
The slow First Contentful Paint at 1420ms due to excessive plugins affects the initial user experience negatively, creating a wait before content appears. This delay, combined with cluttered navigation, leads to frustration and potential drop-off. Users may leave before exploring other areas, impacting conversion rates adversely.
2
Browse Products
Friction
90/100
"Severe issues in browsing due to failed requests and slow loads."
- High number of failed requests
- Slow product grid load
- 404 errors encountered
The browsing step suffers from a high number of failed requests and 404 errors disrupting the experience. Slow loading product grids further exacerbate user frustration, potentially leading users to abandon the site without making purchases. These issues critically affect user trust and engagement.
3
Product Detail
Friction
80/100
"Poor loading images and unclear descriptions hinder user decision-making."
- Images load slowly
- Descriptions lack clarity
- CTA buttons not prominently displayed
The delayed image load time paired with unclear descriptions complicate the shopper's evaluation of products. The lack of clear call-to-action buttons keeps users from easily moving forward in their purchase journey, increasing abandonment rates and decreasing conversion.
4
Select Variant
Friction
60/100
"Unintuitive variant selection creates confusion and indecision."
- Dropdowns not intuitive
- Out-of-stock items not clearly marked
- Feedback on selection absent
Confusion is introduced by non-intuitive dropdown menus for selecting variants, combined with a lack of clear feedback when selecting options or when items are unavailable. This can lead to prolonged decision times, decreasing the likelihood of proceeding to checkout.
5
Add to Cart
Friction
30/100
"Minor feedback delays after adding items impact confidence slightly."
- Delayed button feedback
- Cart animation not smooth
Despite minor delays in feedback when adding items to the cart and unsmooth cart animations, this step is mostly efficient. These slight inefficiencies don't significantly deter continued shopping, but optimizing them could improve user satisfaction and confidence.
6
Checkout
Friction
55/100
"Form complexity and insufficient trust signals deter final purchase steps."
- Long forms without autofill
- Limited payment options
- Missing trust indicators
Lengthy checkout forms lacking autofill functionality, coupled with insufficient variety in payment options and lack of visible trust signals, create friction in completing a purchase. Enhancements in these areas could reduce cart abandonment rates and elevate conversion metrics.
📷 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 • Jul 27, 2026 12:28
Executive Summary
The overall UX health of Press Ireland's ecommerce platform is critically low, evidenced by an overall UX score of 24/100. The journey analysis has spotlighted three pressing issues that are negatively impacting revenue potential: First, numerous failed network requests, notably leading to 404 errors, signify serious disruptions in user journeys, potentially forfeiting conversions due to customer frustration. Secondly, the rendering of Google's external services, such as Google Tag Manager, is notably slow, often introducing obstructive delays in user interaction, thereby increasing bounce rates. Lastly, structural permission denials stemming from the “requestStorageAccess” point to a misconfiguration potentially hampering analytics and personalized user experiences. These issues, if unresolved, could significantly suppress conversion rates and affect gross sales margin by an estimated 15-25%.
UX Audit
The user experience journey showcases substantial deficiencies. Navigation lacks clarity, primarily due to missing alt tags and insufficient categorization. Users are likely encountering friction in product discovery due to inconsistent product labels and images, which are further hindered by a limited filtering system. The cart and checkout process suffers from lackluster performance due to redundant form field validations and improper error handling, which aggravates abandonment rates. Signals of mobile responsiveness are weak; resizing issues and CTA (Call To Action) buttons falling below the fold cause accessible usability deficits. Accessibility concerns are omnipresent, especially with frame-embedded elements underperforming owing to failing Content Security Policy directives.
CRO Recommendations
1. **Error-free Network Requests**: Redress 404 and permission-denied errors on crucial user flows. Fix these server issues to ensure uninterrupted shopping journeys. Expect up to 20% conversion lift by reducing friction.
2. **Improved Site Navigation**: Introduce more intuitive navigation with clear labels and integrated breadcrumb trails for easy product discovery. Enhanced categorization can increase user exploration, potentially boosting conversions by 10%.
3. **Optimized Checkout Process**: Streamline checkout by consolidating form fields, adding auto-complete features, and ensuring sticky CTAs are above the fold on mobile. Expect reduced cart abandonment and an overall conversion uplift of up to 15%.
4. **Enhance Product Discovery**: Implement advanced filtering/sorting functions and improve image quality and consistency. A smoother discovery experience can increase product page click-through rates by 12-18%.
5. **Responsive Design Tuning**: Conduct a responsive design overhaul focusing on media queries to fix layout shifts and ensure button accessibility across devices. This can improve mobile user retention by 8-10%.
Performance Diagnostics
Current performance metrics disclose several areas needing improvement. The First Contentful Paint (FCP) is adequate at 1420 ms, suggesting initial user perception of speed is reasonable. However, TTFB at 905 ms indicates latency issues stemming from server configuration or slow backend processing. Unsatisfactory plugin handling, notably Google Tag Manager, destabilizes server timing due to rendering blocks. Image optimization and JS file compression appear inadequate, attributing to suboptimal load times without specific LCP data available.
Conversion Risk Analysis
The primary conversion blockers from the diagnostic data, prioritized by severity, include:
1. **404 Errors (High Severity)**: Triggered primarily during checkout and account login, undermining user trust and leading to drop-offs.
2. **Rendering-blocking Scripts (High Severity)**: Detected primarily during initial load, causing significant wait time and inducing page abandonment.
3. **Permission Denied Errors (Medium Severity)**: Triggered when utilizing external resources, causing interruptions in personalized features and recommendations.
Plugin Impact Analysis
Among the 12 plugins active, Google Tag Manager presents the highest load impact owing to its high payload and render-blocking nature. Essential plugins include WooCommerce and Bootstrap for core functionalities, whereas plugins like reCAPTCHA and Klaviyo should be evaluated for necessity given their performance hits. Google Fonts can be locally hosted to reduce HTTP requests.
Prioritised Action Plan
**This Week:**
1. Fix 404 errors and network request failures—especially in critical paths like checkout.
2. Diagnose and remediate rendering-blocking issues with Google Tag Manager.
**This Month:**
3. Reassess and streamline site navigation, implementing a breadcrumb system.
4. Refactor the checkout process to minimize form fields and errors.
5. Optimize mobile layout and conduct cross-device testing for usability.
**This Quarter:**
6. Conduct a thorough audit of plugin usage; eliminate redundant plugins, and optimize others like Google Fonts for performance.
7. Implement intensified analytics via refined data tracking to better understand user behavior post-improvements.
8. Develop advanced filtering options and consistent imagery for product pages.
9. Explore server-side enhancements for reducing TTFB.
10. Establish a continuous monitoring strategy for catching new or recurring errors.
🚫 Failed Requests (78)
All HTTP errors and network failures captured during the journey
6 × 404
⚡ Core Web Vitals
First Contentful Paint (FCP)
FCP: 1420ms — Good
🤒 Detected Plugins (12)
CMS
low
RB
E-Commerce Platform
low
RB
JavaScript Library
low
RB
Analytics
low
RB
CSS Framework
low
RB
CDN/Security
low
RB
Icons
low
RB
Email Marketing
low
RB
Security
low
RB
Analytics/Tag Manager
high
RB
Fonts
low
E-Commerce Platform
low
RB
🔴 Console Issues (18 errors, 21 warnings)
Time to First Byte (TTFB)
TTFB: 905ms
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
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
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
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
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
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
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
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
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
Deprecated API for given entry type.
Deprecated API for given entry type.
requestStorageAccess: Permission denied.
Failed to load resource: the server responded with a status of 404 ()
requestStorageAccess: Permission denied.
Failed to load resource: the server responded with a status of 404 ()
Framing 'https://www.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestors 'self'". The violation has been logged, but no further action has been taken.
Framing 'https://www.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestors 'self'". The violation has been logged, but no further action has been taken.
Framing 'https://www.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestors 'self'". The violation has been logged, but no further action has been taken.
requestStorageAccess: Permission denied.
requestStorageAccess: Permission denied.
Failed to load resource: the server responded with a status of 404 ()
requestStorageAccess: Permission denied.
Failed to load resource: the server responded with a status of 404 ()
requestStorageAccess: Permission denied.
requestStorageAccess: Permission denied.
Failed to load resource: the server responded with a status of 404 ()
requestStorageAccess: Permission denied.
Failed to load resource: the server responded with a status of 404 ()
requestStorageAccess: Permission denied.
💬 Ask the AI
Ask a follow-up question about this journey's data