B+89%
Quality Score
4
Pages
61
Issues
7.3
Avg Confidence
7.6
Avg Priority
17 Critical32 High12 Medium
>_ Testers.AI
AI Analysis
Currys scored B (85%) with 61 issues across 6 tested pages, ranking #2 of 22 UK retail sites. That's 63 fewer than the 123.7 category average (91st percentile).
Top issues to fix immediately: "Multiple Resource Loading Failures Affecting Page Functionality" — Investigate and resolve the failed resource loading issues, particularly the coupon code functionality listeners; "Multiple Resource Load Failures - Unhandled DNS Resolution Errors" — Implement comprehensive error handling for all network requests: (1) Wrap API calls in try-catch blocks, (2) Implemen...; "Missing skip navigation link to main content" — Add a skip navigation link as the first focusable element in the page.
Weakest area — accessibility (5/10): Text contrast ratios on some promotional banners appear insufficient. Missing alt text descriptions visible in screenshot.
Quick wins: Improve color contrast on promotional banners to meet WCAG AA standards for all text elements. Add descriptive alt text to all product images and promotional graphics.
Qualitative Quality
Currys
Category Avg
Best in Category
Pages Tested · 4 screenshots
Homepage
currys.co.uk
currys.co.uk
currys.co.uk
Detected Issues · 61 total
1
Multiple Resource Loading Failures Affecting Page Functionality
CRIT P9
Prompt to Fix
The coupon code functionality is broken - the browser console shows 'unable to apply listener to code input box' and 'unable to apply listener to code submit button' errors. Multiple external resources are failing to load with DNS resolution errors and 403 Forbidden responses. Fix all resource loading failures, ensure all required scripts load successfully, and verify that event listeners for the promotional code input and submit button are properly attached. Test the complete coupon code application flow end-to-end to confirm users can enter and submit codes.
Why it's a bug
The console logs show numerous failed resource loads (ERR_NAME_NOT_RESOLVED, 403 Forbidden, 404 errors) and parser-blocking script failures. While not all failures are visible in the static screenshot, the coupon code functionality appears non-functional based on the log 'unable to apply listener to code input box' and 'unable to apply listener to code submit button'. Users attempting to use promotional codes would experience broken functionality. This directly impacts a key user goal: applying discounts during purchase.
Why it might not be a bug
The visual layout appears intact in the screenshot, and some page elements are rendering. However, the console errors clearly indicate critical functionality is broken, which manifests as a usability failure even if visually the page appears complete.
Suggested Fix
Investigate and resolve the failed resource loading issues, particularly the coupon code functionality listeners. Verify that all required scripts are loading correctly and that DNS resolution works. Implement fallback mechanisms for failed third-party script loads to ensure core functionality remains available.
Why Fix
Users expect promotional code functionality to work seamlessly. Broken code input and submission prevents users from applying discounts, leading to cart abandonment and loss of revenue. This is a critical user path on an e-commerce site.
Route To
Backend/Full Stack Engineer, DevOps Engineer
Page
Tester
Mia · Usability TesterTechnical Evidence
Elements:
<input> for code submission, <button> for code submission, scripts loading from doubleclick.net and other external sourcesConsole:
'unable to apply listener to code input box', 'unable to apply listener to code submit button', multiple 'Failed to load resource' errors, 'net::ERR_NAME_NOT_RESOLVED', 'status of 403', 'status of 404'Network:
Failed DNS resolutions for multiple resources, 403 Forbidden responses from secure ad servers, 404 errors for some endpointsPage Text:
Trade in & How much? Recycling's on us! (promotional messaging visible)2
Multiple Resource Load Failures - Unhandled DNS Resolution Errors
CRIT P9
Prompt to Fix
Review all network API calls in main.js, common.js, and tracking.js. For each fetch/XHR call that's failing with ERR_NAME_NOT_RESOLVED or 403/404 errors: (1) Move hardcoded URLs to environment configuration, (2) Wrap calls in try-catch with specific error handling for DNS failures and 403/404, (3) Implement exponential backoff retry (max 3 attempts, starting at 1s delay), (4) Add user-visible error messages for critical failures, (5) Send errors to error tracking service. Example: Instead of `fetch(hardcodedUrl)`, use `fetchWithRetry(getConfigUrl('endpoint'), {maxRetries: 3, backoffMs: 1000})`.
Why it's a bug
The console logs show 15+ ERR_NAME_NOT_RESOLVED errors and multiple 403/404 failures without any visible error handling or retry logic. This indicates AI-generated code that makes network requests without proper try-catch blocks, fallback mechanisms, or retry logic with exponential backoff. The failures are silent - no user-facing alerts or error messages visible, causing potential feature breakdowns.
Why it might not be a bug
Some failures could be due to environmental/network issues rather than code problems, though persistent DNS failures suggest configuration or hardcoded endpoint issues.
Suggested Fix
Implement comprehensive error handling for all network requests: (1) Wrap API calls in try-catch blocks, (2) Implement exponential backoff retry logic with maximum retry limits (3-5 attempts), (3) Add user-facing error messages for critical failures, (4) Log errors to monitoring service, (5) Use environment variables for all URLs instead of hardcoded endpoints, (6) Implement graceful degradation when APIs fail.
Why Fix
Unhandled network failures cause silent feature breakdowns, poor user experience, and make debugging difficult. Proper error handling ensures resilience and helps identify configuration issues early.
Route To
Backend/Infrastructure Engineer
Page
Tester
Jason · GenAI Code AnalyzerTechnical Evidence
Console:
[ERROR] Failed to load resource: net::ERR_NAME_NOT_RESOLVED (appears 15+ times)
[ERROR] Failed to load resource: the server responded with a status of 403 ()
[ERROR] Failed to load resource: the server responded with a status of 404 ()Network:
Multiple failed GET requests with ERR_NAME_NOT_RESOLVED and 403/404 status codes throughout network activity3
Missing skip navigation link to main content
CRIT P9
Prompt to Fix
Add a skip navigation link to bypass main navigation menu. Create a hidden anchor link positioned before the header that jumps to id='main-content'. Style the skip link to be invisible by default (position: absolute; top: -9999px) but become visible and focused when keyboard users tab to it (outline: visible; position: static). Ensure the main content section has id='main-content'. This satisfies WCAG 2.1 Level A criterion 2.4.1 (Bypass Blocks).
Why it's a bug
The page lacks a skip navigation link that allows keyboard users to bypass repetitive navigation elements and jump directly to main content. This forces keyboard and screen reader users to tab through all header navigation on every page load, creating a significant accessibility barrier and violating WCAG 2.1 Level A (2.4.1 Bypass Blocks).
Why it might not be a bug
Skip links are not always visible in screenshots as they are typically hidden until keyboard focus, but their absence is a clear WCAG violation regardless of visual representation.
Suggested Fix
Add a skip navigation link as the first focusable element in the page. Place it before the header/navigation and link it to the main content area using an anchor. Style it to be hidden by default but visible on keyboard focus. Example: <a href="#main-content" class="skip-link">Skip to main content</a> positioned off-screen until focused.
Why Fix
Keyboard users and screen reader users will be able to navigate directly to main content without having to tab through repetitive navigation menus, significantly improving page usability and reducing cognitive load.
Route To
Frontend Engineer / Accessibility Engineer
Page
Tester
Alejandro · Accessibility SpecialistTechnical Evidence
Console:
No direct console evidence, but this is a structural accessibility requirement