Manifest position 264 · CrUX rank bucket 1000
https://www.amazon.com.be
Coverage complete
Coverage-complete multi-template public-site audit; anonymous checkout beyond basket was not transacted.
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 | The dark-mode screenshot remains a white/light storefront, and the DOM reports color-scheme: normal on html/body. F01 medium: The storefront does not adapt to the user’s dark color preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce matched, the probe found nine animations, including repeating 1.1s spinners, 2s leftToRight animations, and a 1s loading indicator. F02 medium: Continuous animations remain active under reduced-motion. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/contrast emulation matched and computed controls resolved to system black/white/yellow colors with visible borders. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found zero view-transition CSS rules across the loaded stylesheets; representative product/cart changes appear as abrupt page/modal swaps. F03 low: State and route changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, or scroll-linked reveal behavior was present on the audited home, search, product, or cart paths. |
implement-natural-interactionsphysical-gestures | pass | medium | Long home/search pages use native browser scrolling; the screenshots and interaction run showed no custom gesture wall or pointer-only primary action. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The full-page screenshots show fixed, visually unchanged navigation across long home/search pages, while CSS inspection found no scroll-timeline or modern scroll-state mechanism. F04 low: Navigation chrome does not communicate scroll state. |
provide-guided-navigationanchored-positioning | issues | medium | The product probe reports many div-based role=dialog overlays; platform inspection found zero anchor positioning rules and no popover elements. F05 low: Menus and overlays use custom positioning rather than anchor-aware primitives. |
provide-guided-navigationdirects-attention | pass | high | Search results expose clear result/product/add controls, and cart/product states use prominent headings and modal focus cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Home is covered by a cookie panel; the attempted product add-to-cart state is blocked by a language modal layered above the cookie panel. F06 high: Stacked consent and language prompts obstruct the primary commerce journey. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The product probe found 30 role=dialog nodes, almost all DIVs, while platform inspection found no dialog, popover, or details elements. F07 medium: Overlay implementation relies heavily on generic div/form dialogs. |
maximize-content-reduce-noisereduced-chrome | issues | high | The mobile capture is a very long grid of near-identical cards with persistent global/category chrome; the search page contains 1,036 links. F08 medium: Dense repeated merchandising chrome overwhelms content hierarchy. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The mobile layout probe found no viewport meta, an effective 1000px layout width, visual viewport 360px, and 640px horizontal overflow. F09 critical: The page is not reflowable at a 360px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Stylesheet inspection found zero container rules; the 360px capture is a scaled desktop grid rather than components adapting to available space. F10 medium: Reusable cards do not use component-level responsiveness. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus/target probe found 8x4px menu buttons and many 16px-high footer links; Lighthouse failed target-size, while focused search controls had no outline or shadow. F11 high: Multiple interactive targets are too small and some focus states are absent. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Search clearly states results for shoes; product exposes its title, price area, and Add to basket; cart exposes checkout/empty-state next actions. |
support-core-task-successprimary-flow-completion | issues | high | Search and product pages expose Add to basket, but the attempted action ended on a stacked language prompt above consent rather than a basket confirmation. F12 high: The representative browse-to-basket flow is interrupted before the primary action completes. |
support-core-task-successclear-system-state-and-recovery | pass | high | The tested unknown route shows Page Not Found plus a direct home recovery link; the empty basket explains state and offers deals/sign-in actions. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured FCP 8.82s, LCP 9.05s, TBT 286ms and performance 0.50; the independent trace measured LCP 5.24s. CLS was good at 0.014. F13 high: Cold-load paint performance is poor. |
be-fast-and-stablevisual-stability | pass | high | Lighthouse CLS was 0.014 and the layout observer recorded CLS 0 with no shifts during its window. |
be-fast-and-stableefficient-main-thread | pass | high | The independent trace recorded zero >50ms long tasks and 0ms TBT; Lighthouse TBT was 286ms, below a severe-blocking threshold. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 71 requests and 1.60MB transferred; its summary identifies six VeryHigh-priority parser-inserted stylesheets plus parser-inserted scripts. F14 high: The critical path contains many parser-blocking styles and scripts. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The HAR attributes 682KB across 20 script requests, the largest resource-type transfer; Lighthouse also reports a 0.50 performance score. F15 medium: JavaScript dominates the transferred resource budget. |
be-inclusivenames-roles-labels | issues | high | axe found critical aria-allowed-attr failures on the search box and main window plus a serious title-only label on the department select; Lighthouse also failed aria roles/name matching. F16 high: Core controls expose invalid ARIA and weak labeling. |
be-inclusivesufficient-contrast | pass | high | axe reported no color-contrast violation, and forced-colors emulation produced system high-contrast colors and visible control borders. |
be-inclusivestructure-and-focus | issues | high | axe found no h1, invalid heading order and content outside landmarks; focus probing showed focused search controls with no outline/box-shadow. F17 medium: The homepage has an incomplete semantic structure and inconsistent focus visibility. |
be-inclusivelegible-text | pass | high | Desktop captures show readable body/product text with clear basic alignment; no text clipping issue was observed at the desktop condition. |
be-inclusivezoom-reflow-targets-and-media | issues | high | No viewport meta was present and the 360px condition overflowed by 640px; Lighthouse failed target-size and the probe found multiple 8x4px buttons. F18 high: Zoom/reflow and target-size support fail on the audited mobile condition. |
follow-best-practicesno-console-errors | issues | high | Lighthouse’s errors-in-console audit scored 0. F19 medium: Browser errors are logged during page load. |
follow-best-practicessound-document-and-assets | issues | high | Image audit found 18/19 images without width/height and 16 legacy-format images; Lighthouse failed image-aspect-ratio. F20 medium: Image delivery has sizing, aspect-ratio, and format hygiene gaps. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed both deprecations and inspector-issues. F21 medium: Deprecated APIs and DevTools inspector issues are present. |
be-discoverabletitle-and-description | pass | high | Home and product probes contain descriptive titles and meta descriptions; product content matched its title. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Discoverability fetched HTTP 202 with only 1% rendered-word coverage and classified the homepage as a JS shell; Lighthouse failed crawlable-anchors and the DOM contains javascript:void(0) links. F22 high: Homepage content is largely unavailable to non-JavaScript crawlers and some links are non-crawlable. |
be-discoverablecanonical-and-indexing-signals | issues | high | A direct fetch of /sitemap.xml returned a French “Page introuvable” HTML document rather than an XML sitemap, while robots.txt is present. F23 medium: The advertised sitemap endpoint returns a branded not-found page. |
be-discoverablestructured-and-shareable-metadata | issues | high | The product probe found zero JSON-LD and zero Open Graph tags despite a visible product entity; title, description and canonical were present. F24 medium: The product page lacks machine-readable product and social metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers probe found no CSP, HSTS, nosniff, frame protection, Referrer-Policy or Permissions-Policy. Six of seven cookies were flagged insecure; session-id/session-id-time lacked HttpOnly and used SameSite=None. F25 critical: Security headers and cookie attributes are materially weak. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The consent copy states 129 third parties; the tracker probe saw five third-party origins before choice, and six cookies use SameSite=None with roughly year-long expiry. F26 medium: The first-visit privacy footprint is broad and long-lived. |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No permission prompt appeared on load and no permission-requesting code/state was observed on the anonymous audited paths; authentication was not forced for browsing. |
be-private-and-securedefensive-browser-policies | issues | high | No HSTS, clickjacking protection, CSP/frame-ancestors, Referrer-Policy or Permissions-Policy was observed. F27 high: Browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | issues | high | Raw no-JS homepage HTML produced only 1% content coverage and a crawler screenshot that does not represent the rendered storefront, while the product page achieved 91%. F28 high: The homepage does not progressively expose core merchandising content. |
be-resilientresilient-runtime-behaviour | pass | high | Search, product and cart rendered usable content; tested 404 state recovered to home, and no blank runtime shell occurred in browser rendering. |
be-resilientoffline-and-installable | issues | high | A service worker controlled the page, but platform inspection found no web app manifest link. F29 medium: The app-like commerce experience is not installable. |
be-resilientnetwork-and-http-failure-states | pass | high | The intentionally invalid route shows a clear not-found message and a working home recovery link instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Audited pages declare lang=en-gb, expose English/French/Dutch locale choice, and stylesheet inspection found 22 logical-property rules. |
be-internationalisedlocale-aware-data | pass | high | The localized English-Belgium storefront consistently renders euro pricing and offers explicit Belgian language choice across commerce paths. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event time, appointment, recurring schedule, or other time-zone-sensitive value appears in the audited commerce paths. |
be-trustworthyno-dark-patterns | pass | high | The consent panel presents Accept, Decline, and Customise together without confirmshaming; empty basket and pricing/checkout labels are direct. |
be-trustworthyhumane-error-handling | not-applicable | high | The audited anonymous search/product/cart surfaces did not expose a user-editable required-data form with a meaningful invalid-submission state. |
be-trustworthytrustworthy-input-assistance | pass | high | Search input has an accessible Search Amazon.com.be name and cart/search controls use native input/select elements; no paste prevention was observed. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Product action and basket/checkout commitments are plainly labeled; empty basket does not fabricate charges and offers reversible navigation. |
be-sustainableoptimised-assets | issues | high | Image inspection found 16 legacy-format images, no modern-format images, five without srcset, and 18 without width/height. F30 medium: Most homepage imagery uses legacy formats and lacks explicit dimensions. |
be-sustainableno-wasteful-work | pass | high | The trace recorded no long tasks or ongoing blocking work in the measured load window, and no autoplay background media was visible on home. |
be-sustainablethird-party-and-media-budget | issues | high | Initial load transferred 1.60MB; scripts contributed 682KB and the tracker probe saw five third-party origins. F31 medium: Script and external-origin cost is high for the initial storefront view. |
be-agent-readystructured-agent-capabilities | issues | medium | The agent probe found no navigator modelContext/WebMCP surface and no forms carrying tool/agent metadata; the homepage also has no JSON-LD. F32 low: Commerce capabilities are not exposed as structured agent tools. |
be-agent-readyon-device-inference | not-applicable | high | The audited shopping paths do not present a summarisation or generative task whose execution location can be meaningfully judged. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After ten bottom/top scroll cycles, heap self-size was 28.93MB vs 25.66MB baseline (+3.27MB, +12.7%) and node count rose by 6,381. Separate clean browser loads make this a medium-confidence signal, not a proven leak trace. F33 medium: Repeated long-page scrolling retained measurable additional heap. |
be-memory-efficientbounded-footprint | issues | medium | Baseline heap summary contained 416,574 nodes/25.66MB self-size; post-scroll reached 422,955 nodes/28.93MB. This is high for a storefront landing state. F34 medium: The homepage has a large initial DOM/heap footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither baseline nor post-interaction top-constructor summaries contain a Detached* population, and closures increased only 52 across the clean-load comparison. |
Provenance
Canonical report: results/atomic/reports/0264-www_amazon_com_be.json
Report SHA-256: f7bff3e83c5da7ba205ee01bc80d23a08ece03069ed3070f408fd87c319e2706
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_com_be/2026-07-26T02-14-35-985Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_com_be/2026-07-26T02-14-35-985Z
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.