A-90%
Quality Score
4
Pages
56
Issues
7.3
Avg Confidence
7.5
Avg Priority
13 Critical31 High12 Medium
>_ Testers.AI
AI Analysis
Selfridges scored B (85%) with 56 issues across 6 tested pages, ranking #1 of 22 UK retail sites. That's 68 fewer than the 123.7 category average (95th percentile).
Top issues to fix immediately: "Multiple 403 Errors Prevent Content Loading" — Investigate and resolve the 403 authentication/authorization errors in the backend API calls; "Unresolved DNS Error Breaks Resource Loading" — Verify that all external resource URLs are correctly configured and that DNS records are properly set up; "DNS Resolution Failure - ERR_NAME_NOT_RESOLVED" — Identify which domain/endpoint is failing DNS resolution.
Weakest area — accessibility (5/10): Several accessibility concerns: unclear alt text potential, color contrast issues in some areas, limited keyboard navigation in...
Quick wins: Implement ARIA labels and improve semantic HTML structure for screen reader users. Increase font sizes and padding on interactive elements to improve mobile accessibility.
Qualitative Quality
Selfridges
Category Avg
Best in Category
Pages Tested · 4 screenshots
Homepage
selfridges.com
selfridges.com
selfridges.com
Detected Issues · 56 total
1
Multiple 403 Errors Prevent Content Loading
CRIT P10
Prompt to Fix
The application is returning 403 Forbidden errors when loading critical resources from the API. Investigate all endpoints that are returning 403 status codes. Check the authentication headers, CORS configuration, and user permissions to ensure that legitimate requests are being properly authorized. Add appropriate authentication tokens/credentials to all API calls and verify that the backend is not incorrectly rejecting valid requests.
Why it's a bug
The console shows multiple 'Failed to load resource: the server responded with a status of 403' errors, indicating that critical resources are being blocked. This directly impacts user experience as content may fail to load or display properly. The presence of these errors suggests backend functionality is broken and users cannot access expected features or content.
Why it might not be a bug
The page appears to render visually, so some content is displayed. However, the 403 errors indicate actual functionality failures that would prevent features from working.
Suggested Fix
Investigate and resolve the 403 authentication/authorization errors in the backend API calls. Ensure proper credentials, permissions, and CORS configuration are in place for all resource requests.
Why Fix
Users may be unable to access key features, load personalized content, or complete important tasks if resources are being blocked with 403 errors. This creates a broken experience.
Route To
Backend Engineer / DevOps
Page
Tester
Mia · Usability TesterTechnical Evidence
Elements:
Multiple resource endpointsConsole:
Failed to load resource: the server responded with a status of 403 ()Network:
403 Forbidden responses on multiple resource requests2
Unresolved DNS Error Breaks Resource Loading
CRIT P10
Prompt to Fix
There is a DNS resolution error (net::ERR_NAME_NOT_RESOLVED) preventing a resource from loading. Identify which domain or URL is failing to resolve by checking the Network tab. Verify the domain name is spelled correctly and that DNS records are properly configured. If this is a third-party service, check that the endpoint is still active and accessible. Update the URL if needed and test that the resource loads successfully.
Why it's a bug
The console shows 'Failed to load resource: net::ERR_NAME_NOT_RESOLVED', which indicates a DNS resolution failure. This prevents a resource from loading entirely and is a critical infrastructure issue that blocks user-facing functionality.
Why it might not be a bug
Could be a temporary network issue, but the presence in console logs indicates it's reproducible in the test environment.
Suggested Fix
Verify that all external resource URLs are correctly configured and that DNS records are properly set up. Check for typos in domain names in the resource URLs. Ensure all third-party service endpoints are accessible and properly resolved.
Why Fix
DNS resolution failures prevent resources from loading, breaking features and creating a broken user experience. Users cannot access content they expect to see.
Route To
DevOps / Infrastructure Engineer
Page
Tester
Mia · Usability TesterTechnical Evidence
Elements:
External resource with unresolved domainConsole:
Failed to load resource: net::ERR_NAME_NOT_RESOLVEDNetwork:
DNS resolution failure on resource request3
DNS Resolution Failure - ERR_NAME_NOT_RESOLVED
CRIT P9
Prompt to Fix
A network request is failing with 'net::ERR_NAME_NOT_RESOLVED' error. This means the domain name cannot be resolved by DNS. Please identify which API endpoint or resource URL is causing this error, verify the domain name is correctly spelled in the code, check that all DNS records are properly configured for production, and ensure the service is accessible. Add retry logic and user-facing error handling for network failures.
Why it's a bug
A network request failed with ERR_NAME_NOT_RESOLVED, indicating the application cannot resolve a domain name. This is a critical network connectivity issue that will completely prevent the affected feature from working. Users will experience broken functionality without understanding why.
Why it might not be a bug
This could be an external third-party service that is temporarily down, but if it's a first-party service, this is a critical infrastructure issue.
Suggested Fix
Identify which domain/endpoint is failing DNS resolution. Verify the domain name is spelled correctly in the code. Check DNS records and ensure the service is properly deployed and accessible. Add retry logic and graceful degradation for failed network requests. Implement user-facing error messaging.
Why Fix
DNS resolution failures prevent entire features from loading. This breaks core functionality and creates a poor user experience. Identifying and fixing the unresolvable domain is essential for application stability.
Route To
DevOps/Infrastructure Engineer
Page
Tester
Sharon · Security TesterTechnical Evidence
Console:
[ERROR] Failed to load resource: net::ERR_NAME_NOT_RESOLVEDNetwork:
net::ERR_NAME_NOT_RESOLVED