Manifest position 269 · CrUX rank bucket 1000
https://www.amazon.de
Coverage complete
Coverage-complete audit of six representative anonymous/public paths; signed-in checkout and account-management states were out of scope.
Attempts
2 / 3
Judged checks
58 / 58
Blocked
0
Not run
0
This report has no published overall score. Blocked and not-run checks are not passes. A coverage-complete report means every check has a judged outcome; it does not mean every check passed.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Under emulated dark mode the page body remained rgb(255,255,255), text remained dark, color-scheme was normal, and the preference screenshot stayed light. F-001 medium: The storefront ignores the user’s dark-color preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The preference probe reported zero active animations under reduce, and no auto-advancing video was observed. |
respect-user-preferencesrespects-contrast | pass | high | The high-contrast preference capture remained readable and Lighthouse color-contrast scored 1. |
implement-natural-interactionsview-transitions | issues | high | The four-route CSS/DOM probes found no view-transition declarations, while navigation between search, product and basket is a primary journey. F-002 low: Route and state changes are abrupt rather than transition-aware. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked narrative, parallax, reveal, or equivalent interaction was present on the selected templates. |
implement-natural-interactionsphysical-gestures | issues | high | Desktop and mobile screenshots show horizontal card rails and custom overlays; probes found no scroll-snap/modern declarative gesture signal and 26-44 custom role dialogs per route. F-003 low: Carousel-like and overlay interactions rely on legacy custom controls rather than platform-native gesture primitives. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The homepage screenshot shows two persistent navigation rows; CSS probes found no scroll-state or scroll-timeline technique on any representative route. F-004 low: The large site chrome does not adapt to scroll state. |
provide-guided-navigationanchored-positioning | issues | high | Probes found 26-44 role=dialog elements, zero native dialogs/popovers, and no anchor-name, position-anchor or position-try declarations. F-005 medium: Menus and popovers use custom positioned role-dialog structures without CSS anchor positioning. |
provide-guided-navigationdirects-attention | pass | high | Search, product and basket expose contextual headings and skip links; the add-to-cart flow moved to a clearly changed basket state. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The first desktop capture shows a large cookie-consent layer covering the lower half of the viewport while a delivery-address popover covers the hero; the mobile capture also starts with the delivery overlay. F-006 high: Two load-time interruptions obscure shopping content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Across the representative pages probes counted 26-44 role dialogs but zero dialog, popover, or details elements. F-007 medium: Overlays are built from custom role dialogs rather than native dialog or popover primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | The homepage first viewport is dominated by two navigation bars, a campaign banner and four competing promotional cards; the product probe exposed 14 h1 elements and repeated sustainability/error panels. F-008 medium: Dense navigation, promotions, badges and duplicated panels crowd the core content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The mobile layout reported no viewport meta, a 1000 px layout viewport and 640 px horizontal overflow on the homepage; all four page probes reported viewport=null. F-009 critical: The desktop storefront is scaled down instead of reflowing at a 360 px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Representative probes found no @container rules in authored inline styles and mobile screenshots show desktop grids scaled to fit rather than components reorganized for their available space. F-010 medium: Reusable cards and commerce panels do not demonstrate container-level adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The probes counted 45/171 small targets on home, 97/247 on search and 176/409 on product; Lighthouse failed target-size, and several focused shortcut/search controls had no outline or shadow. F-011 high: Many controls are too small for touch and some keyboard focus indicators are absent. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Search is prominent, result cards are clearly labeled, product price and Add to basket are visible, and empty basket actions are explicit. |
support-core-task-successprimary-flow-completion | pass | high | All five flow steps succeeded: consent was declined, Add to basket navigated to smart-wagon, and a basket indicator appeared. |
support-core-task-successclear-system-state-and-recovery | issues | high | The product DOM contains repeated “Sorry, there was a problem” and “Issue loading the information” headings, while the captured product view provides no adjacent retry control. F-012 medium: Partial product failures are exposed without useful recovery actions. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured FCP 6.6 s, LCP 18.1 s, Speed Index 6.6 s and performance 0.56; the independent trace measured LCP 3.05 s under a lighter run. F-013 high: Cold-load performance is well outside the good LCP range. |
be-fast-and-stablevisual-stability | issues | high | The 360 px basket layout observer measured CLS 0.1104 from two shifts, exceeding the good <=0.1 threshold; 39 of 40 homepage images lacked both dimensions. F-014 medium: The basket shifts visibly during load. |
be-fast-and-stableefficient-main-thread | pass | high | Lighthouse TBT was 110 ms and the independent trace reported zero long tasks and 0 ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 289 requests and 4.35 MB transferred, including five parser-inserted VeryHigh-priority stylesheets, 21 fonts and 219 images; Lighthouse LCP was 18.1 s. F-015 high: The initial page has a heavy, render-blocking network dependency shape. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 642 KiB unused JavaScript and 207 KiB unused CSS, including a 590 KiB WAF challenge script and feature bundles with 60-100% waste. F-016 high: Large amounts of shipped JavaScript and CSS are unused on the initial view. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed aria-allowed-attr and label-content-name-mismatch; the product probe found 35 img elements without alt and the search probe found one. F-017 medium: Accessible semantics are inconsistent on complex product and search surfaces. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast scored 1 and the captured core navigation/card text remained visually distinct. |
be-inclusivestructure-and-focus | issues | high | The product page exposed 14 h1 elements, search had no main landmark, and focused search/shortcut controls sometimes had neither outline nor box-shadow. F-018 high: Heading and landmark structure is malformed on key templates. |
be-inclusivelegible-text | issues | high | At 360 px, search and product pages are 1000 px desktop layouts scaled to 0.36; product descriptions and controls are visibly too small for comfortable reading. F-019 high: Narrow-screen text is rendered as tiny desktop content. |
be-inclusivezoom-reflow-targets-and-media | issues | high | All representative page probes lacked a viewport meta declaration; Lighthouse failed target-size and the mobile screenshots show desktop-scale layouts. F-020 high: Mobile reflow and touch-target support fail the inclusive baseline. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured a console.error for a late-loading Mash module from an Amazon JavaScript asset. F-021 medium: The homepage logs a production console error. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found 39/40 images without dimensions, 37 legacy-format images and two oversized images; Lighthouse also failed image aspect ratio and low-resolution image audits. F-022 medium: Image sizing and document assets are not consistently sound. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported one deprecated-API warning and reduced the best-practices score to 0.69. F-023 medium: Deprecated API use remains in production. |
be-discoverabletitle-and-description | issues | high | The route probes found a descriptive title on all pages but description=null on search results and basket. F-024 medium: Search and basket templates omit meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The homepage had five javascript: links, product had 106, Lighthouse failed crawlable-anchors, and every representative template lacked a viewport meta declaration. F-025 high: The site is neither consistently crawlable nor mobile-friendly. |
be-discoverablecanonical-and-indexing-signals | issues | high | Home and product had canonicals, but search had no canonical; no representative page exposed hreflang despite German and English variants. robots.txt itself was valid. F-026 medium: Indexing signals are inconsistent across localized and listing pages. |
be-discoverablestructured-and-shareable-metadata | issues | high | The product probe found no JSON-LD and no Open Graph tags despite a visible price, availability, ratings and product identity. F-027 high: Product pages lack structured product and social-preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but the headers primitive found no CSP, HSTS or nosniff; seven of nine cookies were flagged, including three non-Secure cookies and auth-like session identifiers without HttpOnly. F-028 high: Core transport defenses and cookie attributes are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Before consent, HAR saw 282 cross-origin requests and 4.13 MB cross-origin transfer; the consent text names 129 advertising partners and Amazon telemetry origins were active. F-029 high: The anonymous homepage has a large telemetry and third-party footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The valid sign-in probe found username autocomplete but no passkey text, no WebAuthn signal, and a password field with no autocomplete token; no permission prompt appeared on load. F-030 medium: The sign-in entry point is password-oriented and exposes no passkey option. |
be-private-and-securedefensive-browser-policies | issues | high | The main response exposed no frame protection, Referrer-Policy or Permissions-Policy in addition to missing CSP/HSTS; no frame-ancestors policy could be found. F-031 high: Browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | issues | high | Discoverability fetched HTTP 202 with only 2,007 raw bytes: 1% content coverage, no raw title or description, and isJsShell=true; the product page was materially better at 61% coverage. F-032 high: The public homepage is effectively unavailable to a non-JavaScript generic crawler. |
be-resilientresilient-runtime-behaviour | issues | high | Representative probes found 26-44 role dialogs with no native top-layer primitives, while the product DOM contained repeated issue-loading states. F-033 medium: Custom overlays and asynchronously loaded product modules are fragile. |
be-resilientoffline-and-installable | not-applicable | high | Anonymous product discovery is readable without an install surface, while purchase and account operations are intrinsically online transactions. |
be-resilientnetwork-and-http-failure-states | issues | high | The product page repeatedly rendered “Sorry, there was a problem” and “Issue loading the information” without an adjacent retry control in the captured state. F-034 medium: Network-backed product module failures do not present actionable recovery. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang=en-gb was valid, but probes found hundreds of left/right declarations and almost no logical-property usage; the English product route contains multiple German h1 sections. F-035 medium: Localized pages rely overwhelmingly on physical CSS and mix languages within the product experience. |
be-internationalisedlocale-aware-data | pass | high | The selected en-gb route consistently rendered euro prices and English delivery dates without ambiguous numeric-only formats. |
be-internationalisedtime-zone-correctness | pass | high | Delivery commitments were expressed as named weekdays and dates, with no ambiguous local timestamp or manual time-zone arithmetic exposed. |
be-trustworthyno-dark-patterns | issues | high | The cookie layer gives Accept a filled yellow primary style while Decline is a gray outline, covers half the desktop viewport, and describes sharing with 129 partners. F-036 medium: Consent choices are visually asymmetric and interrupt the task. |
be-trustworthyhumane-error-handling | pass | high | Search and add-to-basket completed without premature validation; visible product failure text was neutral rather than blaming the user. |
be-trustworthytrustworthy-input-assistance | issues | high | The sign-in email uses autocomplete=username, but the password input has an empty autocomplete value and no passkey path is exposed. F-037 medium: Authentication autofill metadata is incomplete. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Price, delivery, stock and Add to basket were visible before commitment; the add flow succeeded and sign-in terms were disclosed before continuation. |
be-sustainableoptimised-assets | issues | high | The image audit found 37/40 legacy formats, 39 missing dimensions, 26 missing srcset and 22 below-fold images without lazy loading. F-038 high: The image estate is dominated by legacy, unreserved and non-responsive assets. |
be-sustainableno-wasteful-work | issues | high | HAR recorded 289 requests and 4.35 MB; Lighthouse found 642 KiB unused JS and 207 KiB unused CSS, while telemetry endpoints made repeated background requests. F-039 high: The initial view performs disproportionate network and code work. |
be-sustainablethird-party-and-media-budget | issues | high | HAR attributed 4.13 MB to cross-origin resources, including 2.25 MB images and 735 KB across 21 fonts; 282 of 289 requests were cross-origin by host. F-040 high: Third-party, font and media costs are not proportionate to the first view. |
be-agent-readystructured-agent-capabilities | issues | high | robots.txt disallows GPTBot, ClaudeBot, OAI-SearchBot, ChatGPT-User and many other agents; probes found no WebMCP, product JSON-LD or agentic tool registration. F-041 high: The commerce surface is deliberately opaque to agents and exposes no structured action interface. |
be-agent-readyon-device-inference | not-applicable | high | The site exposes a server-backed Rufus shopping assistant, but no page claim or tested task established that local inference was an appropriate requirement. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | Post-interaction heap self-size fell from 27,874,900 to 27,077,022 bytes and node count from 447,224 to 416,744; no retained-growth signal appeared. |
be-memory-efficientbounded-footprint | pass | high | Heap self-size was about 27.9 MB on a media-rich commerce homepage; the distribution was dominated by native/code objects and was proportionate to the tested state. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The post-interaction snapshot had fewer total nodes and closures and no Detached* constructor appeared among the retained top constructors. |
Provenance
Canonical report: results/atomic/reports/0269-www_amazon_de.json
Report SHA-256: b8dd8156ee4cc57c294af4ca7428287efe5770e521e61774f21e8abac9458e06
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_de/2026-07-26T02-35-42-431Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_de/2026-07-26T02-35-42-431Z
Catalog SHA-256: sha256:78ccfdb2d483f4c57d9dafed80fd86c6265585a56457c8dcfddc254b80fb44d7
Raw screenshots, HARs, traces, heaps, and other browser artifacts are retained at the local evidence root and intentionally are not committed. Artifact paths in the canonical report are relative to that root.