B86%
Quality Score
6
Pages
122
Issues
7.5
Avg Confidence
7.7
Avg Priority
33 Critical70 High19 Medium
>_ Testers.AI
AI Analysis
Superdrug scored B (86%) with 122 issues across 6 tested pages, ranking #9 of 20 UK retail sites. That's 8 fewer than the 130.2 category average (50th percentile).
Top issues to fix immediately: "Multiple Resource Load Failures - DNS Resolution Error" — 1) Verify all resource URLs in the application are correctly configured and using valid domain names; "Resource loading failures affecting product display and functionality" — Investigate and resolve the DNS resolution errors for the failed resources; "Missing alt text on informative images throughout the page" — Add descriptive alt text to all informative images on the page.
Weakest area — accessibility (5/10): Low contrast in some areas, small text on product cards, and limited alt text visibility for images.
Quick wins: Improve color contrast ratios to meet WCAG AA standards, especially for text over backgrounds. Add skip navigation links and improve keyboard navigation for users with mobility issues.
Qualitative Quality
Superdrug
Category Avg
Best in Category
Pages Tested · 6 screenshots
Homepage
superdrug.com
superdrug.com
superdrug.com
superdrug.com
superdrug.com
Detected Issues · 122 total
1
Unexplained POST request to encrypted endpoint suggests data exfiltration
CRIT P9
Prompt to Fix
There is a POST request to an encrypted/obfuscated endpoint (V0k7s/GmJW_ pattern) that appears to be exfiltrating data. Please: (1) Identify the source code making this POST request, (2) Document what data is being sent in the request body, (3) Explain the legitimate business purpose for this endpoint, (4) Replace the encrypted endpoint name with a clear, documented URL if legitimate, (5) Ensure the user has provided explicit consent for any data transmission, (6) Verify compliance with GDPR/CCPA requirements. If this is generated code from an AI tool, review all AI-generated code for similar obfuscated data transmission patterns and remove any undocumented data collection.
Why it's a bug
Network analysis shows a POST request to an encrypted/obfuscated endpoint (https://www.superdrug.com/V0k7s/GmJW_/c-/SUWD/mn_0/tiuEQGffbtrbmfEu/RDU6OHkC/NzgsP1tR/BnQB) returning status N/A. This pattern is suspicious and suggests AI-generated code may be exfiltrating user data to an unclear destination. The endpoint name is encrypted/obfuscated, the purpose is unclear, and this appears to be generated code without clear business logic explanation.
Why it might not be a bug
This could be a legitimate analytics or tracking endpoint that uses encoded URLs for security. However, the obfuscation combined with POST data transmission warrants investigation.
Suggested Fix
Audit all POST requests to identify their purpose and destination. Document what data is being sent and why. Replace encrypted/obfuscated endpoint names with clear, documented URLs. Ensure data transmission complies with privacy regulations and has proper user consent. Remove any undocumented data exfiltration.
Why Fix
Obscured POST requests to unclear endpoints create serious security and privacy risks. Users cannot understand what data is being collected or where it's being sent. This may violate privacy laws and expose the company to legal liability.
Route To
Security Engineer / Privacy Officer
Page
Tester
Jason · GenAI Code AnalyzerTechnical Evidence
Console:
[ERROR] Failed to load resource: net::ERR_NAME_NOT_RESOLVEDNetwork:
POST https://www.superdrug.com/V0k7s/GmJW_/c-/SUWD/mn_0/tiuEQGffbtrbmfEu/RDU6OHkC/NzgsP1tR/BnQB - Status: N/A2
Multiple Resource Load Failures - DNS Resolution Error
CRIT P9
Prompt to Fix
I'm seeing multiple 'Failed to load resource: net::ERR_NAME_NOT_RESOLVED' errors in the browser console. This indicates DNS resolution failures for resources being loaded by the application. Please: 1) Identify which resources are failing to load by checking the network tab. 2) Verify all resource URLs use valid, resolvable domain names. 3) Check that any CDN or external service endpoints are correctly configured. 4) Ensure DNS records are set up correctly for all referenced domains. 5) Add error handling to gracefully handle failed resource loads instead of breaking the page.
Why it's a bug
Multiple resources are failing to load with net::ERR_NAME_NOT_RESOLVED errors (4 occurrences). This indicates DNS resolution failures that prevent critical resources from loading. Users will experience broken functionality, missing images, stylesheets, scripts, or API calls. This directly impacts user experience and feature availability.
Why it might not be a bug
Could potentially be a temporary network issue on the user's end or local DNS misconfiguration, but the repeated pattern suggests a systematic problem with the application's resource URLs or server configuration.
Suggested Fix
1) Verify all resource URLs in the application are correctly configured and using valid domain names. 2) Check DNS records for any referenced domains. 3) Review network requests in browser DevTools to identify which specific resources are failing. 4) Ensure CDN or external service endpoints are correctly configured and accessible. 5) Add error handling and fallback mechanisms for failed resource loads.
Why Fix
Resource load failures degrade the user experience significantly. Users may see broken layouts, missing images, or non-functional features. This could lead to task failures and user abandonment.
Route To
Backend/DevOps Engineer or Full Stack Engineer
Page
Tester
Sharon · Security TesterTechnical Evidence
Console:
[ERROR] Failed to load resource: net::ERR_NAME_NOT_RESOLVED (appears 4 times)Network:
net::ERR_NAME_NOT_RESOLVED3
Multiple Failed Resource Loads - DNS Resolution Errors
CRIT P9
Prompt to Fix
I'm seeing 'Failed to load resource: net::ERR_NAME_NOT_RESOLVED' errors in the browser console appearing 3 times. This indicates DNS resolution failures for critical resources. Please: 1) Identify all external resource URLs in the HTML/CSS/JS that are failing to load, 2) Verify these domain names are correctly spelled and configured, 3) Test that DNS can resolve these domains, 4) Check CDN/hosting configurations are correct, 5) Add proper error handling and logging to identify which specific resources are failing, 6) Implement fallback mechanisms for critical resources.
Why it's a bug
The application is failing to load resources due to net::ERR_NAME_NOT_RESOLVED errors, which indicates DNS resolution failures. This error appears 3 times in the logs, suggesting critical dependencies are not loading. This directly impacts functionality as resources required for the application to work properly are unavailable. Users will experience broken features or incomplete application state.
Why it might not be a bug
Could be a temporary DNS issue on the user's network or test environment, but the repetition suggests a consistent problem with resource URLs or CDN configuration.
Suggested Fix
1) Verify all resource URLs are correctly configured and point to valid domains. 2) Check that CDN/external service domains are correctly spelled and accessible. 3) Ensure DNS records for these domains are properly configured. 4) Test resource loading in multiple network environments. 5) Add fallback resources or error handling if critical resources fail to load.
Why Fix
Failed resource loads prevent the application from functioning properly. This directly impacts user experience and may cause critical features to be unavailable. Fixing DNS/URL issues ensures all dependencies load correctly.
Route To
Backend/DevOps Engineer or Full Stack Engineer
Page
Tester
Sharon · Security TesterTechnical Evidence
Console:
[ERROR] Failed to load resource: net::ERR_NAME_NOT_RESOLVEDNetwork:
net::ERR_NAME_NOT_RESOLVED (appears 3 times)