C75%
Quality Score
6
Pages
160
Issues
7.4
Avg Confidence
7.5
Avg Priority
36 Critical90 High32 Medium2 Low
>_ Testers.AI
AI Analysis
eBay UK scored B (85%) with 160 issues across 7 tested pages, ranking #21 of 22 UK retail sites. That's 36 more than the 123.7 category average (5th percentile).
Top issues to fix immediately: "Multiple images with empty alt text lack meaningful descriptions" — Provide meaningful, descriptive alt text for each image; "Missing skip navigation link prevents keyboard users from bypassing re" — Add a skip navigation link as the first focusable element on the page; "Render-Blocking JavaScript Resources Delaying Initial Page Render" — 1) Add 'async' or 'defer' attributes to non-critical JavaScript tags.
Weakest area — accessibility (6/10): The page lacks clear focus indicators, alt text visibility for images is uncertain, and color contrast in some sections may be ...
Quick wins: Consolidate promotional sections to reduce visual clutter and improve focus hierarchy. Implement consistent design language across all sections with unified typography and spacing.
Qualitative Quality
eBay UK
Category Avg
Best in Category
Pages Tested · 6 screenshots
Homepage
ebay.co.uk
ebay.co.uk
ebay.co.uk
ebay.co.uk
ebay.co.uk
Detected Issues · 160 total
1
Multiple images with empty alt text lack meaningful descriptions
CRIT P9
Prompt to Fix
Review all images on the eBay homepage with empty alt attributes. For informative images (product listings, event promotions), add descriptive alt text that conveys the image content, including product/event names and key details. For truly decorative images, add role='presentation' or aria-hidden='true' to hide them from screen readers. Ensure compliance with WCAG 2.1 SC 1.1.1 (Non-text Content) by providing text alternatives for all non-text content that conveys information or purpose.
Why it's a bug
The page contains multiple images with empty alt attributes (hasAlt: false) that appear to be decorative placeholders but are placed in content areas where they may convey information. Four images show empty alt text: 'TGkAAeSwTKRpnwP-', 'OHIAAeSwWpdplD6q', 'piEAAeSwWflpoB6i', and 'YJcAAeSwu6hpsvc0'. Without proper alt text, screen reader users cannot understand the purpose or content of these images, violating WCAG 2.1 Level A success criterion 1.1.1 (Non-text Content). This creates a significant barrier for users with visual impairments trying to understand the eBay Live section content.
Why it might not be a bug
If these images are truly decorative and serve no informational purpose, empty alt text may be acceptable with proper img role='presentation' or aria-hidden='true'. However, their placement in prominent content sections suggests they likely convey information about listings or events.
Suggested Fix
Provide meaningful, descriptive alt text for each image. For product/listing images, include product name and key details. For event images, describe the event title and key information. If images are truly decorative, explicitly mark them with role='presentation' or aria-hidden='true'. Example: <img src='...' alt='Clearance Electronics - Tablets and Laptops at Warehouse Prices'> for informative images.
Why Fix
Screen reader users rely on alt text to understand image content. Meaningful alt text allows users with visual impairments to fully participate in browsing products and events, understand listings, and make informed purchasing decisions. This is critical for accessibility and legal WCAG 2.1 compliance.
Route To
Frontend Engineer / Accessibility Engineer
Page
Tester
Alejandro · Accessibility SpecialistTechnical Evidence
Console:
N/A - issue detected from static content analysis2
Missing skip navigation link prevents keyboard users from bypassing repetitive content
CRIT P9
Prompt to Fix
Add a skip navigation link as the first interactive element on every page. The link should be visually hidden by default and become visible when focused (on keyboard focus). It should link to the main content area using a fragment identifier (e.g., #main-content). Ensure the main content section has a corresponding id attribute. This satisfies WCAG 2.1 SC 2.4.1 (Bypass Blocks) and improves keyboard navigation experience.
Why it's a bug
The page lacks a visible or properly implemented skip navigation link that would allow keyboard users to jump directly to main content, bypassing the navigation bar and repetitive elements. This violates WCAG 2.1 Level A success criterion 2.4.1 (Bypass Blocks). Keyboard users must tab through all navigation elements before reaching the main content area, creating unnecessary friction and making the page tedious to navigate, especially on pages with extensive navigation menus.
Why it might not be a bug
Skip links are considered best practice rather than strictly required by WCAG 2.1, though criterion 2.4.1 does require a mechanism to bypass repetitive content. Some might argue that proper heading hierarchy could substitute for skip links.
Suggested Fix
Add a skip navigation link as the first focusable element on the page. Make it visually hidden by default but visible on focus. Link to the main content area (typically a main landmark or the first h1). Example: <a href='#main-content' class='skip-link'>Skip to main content</a> with CSS that shows it on :focus.
Why Fix
Keyboard and screen reader users navigate pages using keyboard only. Without skip links, they must navigate through extensive navigation menus on every page visit, creating significant friction and frustration. Skip links dramatically improve usability for these users and are required for WCAG 2.1 Level A compliance.
Route To
Frontend Engineer / Accessibility Engineer
Page
Tester
Alejandro · Accessibility SpecialistTechnical Evidence
Console:
N/A - structural issue not reflected in console3
Render-Blocking JavaScript Resources Delaying Initial Page Render
CRIT P9
Prompt to Fix
Audit all synchronous JavaScript loading in the eBay homepage. For each render-blocking script (logs.ebb041e86c5338dbe8f6.bundle.js, d.homepage-Cxc8qTiS.js, jquery-3.7.1.min.js, runtime.582565b4.js, index_lcNW.01863ec5.js, ebay-cookies/6.js, and discovery platform scripts), determine if it's critical for initial page render. Convert non-critical scripts to use 'async' attribute or dynamic import() calls. Defer eBay RUM analytics to load after the page reaches interactive state. Implement code-splitting for discovery platform bundles to load only the minimum code needed for initial render, deferring feature-specific code. Ensure jQuery and other vendor libraries are deferred unless absolutely required for above-fold content.
Why it's a bug
Multiple critical JavaScript resources are loaded synchronously and blocking page render: logs.ebb041e86c5338dbe8f6.bundle.js, d.homepage-Cxc8qTiS.js, _DZdCPiVu.js, _TeCbo2dj.js, _DoJxNrA2.js, _3nSyviLC.js, _CLQ2DPen.js, jquery-3.7.1.min.js, runtime.582565b4.js, index_lcNW.01863ec5.js, ebay-cookies/6.js, and multiple other JS files. These resources must complete downloading and parsing before the DOM can render, directly impacting Largest Contentful Paint (LCP) and Time to Interactive (TTI). With 486 total network requests, the cumulative blocking effect is severe.
Why it might not be a bug
Some JavaScript must execute early for critical functionality like cookie consent and analytics initialization. However, the architecture could still defer non-critical JS or load critical code asynchronously with proper prioritization.
Suggested Fix
1) Add 'async' or 'defer' attributes to non-critical JavaScript tags. 2) Implement code-splitting to break large bundles into smaller chunks. 3) Defer eBay RUM analytics (logs.ebb041e86c5338dbe8f6.bundle.js) to load after page interactive. 4) Use dynamic imports for discovery platform scripts that aren't needed for initial render. 5) Move third-party scripts (jQuery, non-critical vendor code) to async loading patterns. 6) Implement a resource priority queue to load critical render-path JS first.
Why Fix
Render-blocking resources directly impact Core Web Vitals, particularly LCP and FID. Reducing render-blocking JS can improve LCP by 1-3 seconds, improving SEO rankings and user experience. This is critical for mobile users on slower connections.
Route To
Frontend Performance Engineer / Build Systems Engineer
Page
Tester
Tariq · Performance SpecialistTechnical Evidence
Network:
GET https://ir.ebaystatic.com/cr/ebay-rum/cdn-assets/logs.ebb041e86c5338dbe8f6.bundle.js, GET https://ir.ebaystatic.com/rs/c/discoveryplatformweb/d.homepage-Cxc8qTiS.js, GET https://ir.ebaystatic.com/cr/v/c01/code.jquery.com_jquery-3.7.1.min.js