Manifest position 867 · CrUX rank bucket 1000
https://www.amazon.ca
Coverage complete
Atomic coverage complete. Search, product, cart, and sign-in failures were observed as direct core-flow issues rather than omitted checks.
Attempts
3 / 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 white/light grey and the computed body color-scheme is normal; no prefers-color-scheme rules were found. AMZ-001 medium: Dark preference is ignored |
respect-user-preferencesrespects-reduced-motion | pass | medium | Reduced-motion emulation matched and document.getAnimations() returned no active animations. |
respect-user-preferencesrespects-contrast | pass | medium | High-contrast screenshot remains legible and Lighthouse color-contrast audit passed. |
implement-natural-interactionsview-transitions | issues | high | Rendered CSS only contains reset-to-unset view-transition declarations; search/product journeys replace the page abruptly with error or challenge screens. AMZ-002 low: Page and state changes do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | pass | medium | CSS/animation probe found no active scroll-linked animation or scroll event-driven visual effect to implement incorrectly. |
implement-natural-interactionsphysical-gestures | issues | high | The homepage hero is an arrow-driven carousel; DOM/CSS inspection found no active scroll-snap or overscroll gesture rules, only reset declarations. AMZ-003 low: Carousel/navigation interactions use legacy controls without platform gesture behaviour |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long homepage keeps a fixed two-row header and no animation-timeline or scroll-state query was found in captured CSS. AMZ-004 low: Navigation chrome does not react to scroll state |
provide-guided-navigationanchored-positioning | issues | high | The platform probe found 27 role=dialog elements, zero native dialogs/popovers, and no active anchor positioning declarations. AMZ-005 low: Overlays are custom-positioned rather than anchored platform popovers |
provide-guided-navigationdirects-attention | pass | medium | Visible carousel arrows, descriptive navigation labels, and a skip-to-main link provide location and movement cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The initial screenshot shows a fixed notice covering the lower page before interaction, including product cards. AMZ-006 medium: Interest-based ads notice interrupts the initial view |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The notice is a form role=dialog; the probe found zero <dialog>, popover, or details elements and 27 custom role=dialog nodes. AMZ-007 medium: Dismissible UI is implemented with custom role-based forms |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop evidence shows two navigation rows, a large hero, four dense merchandising cards, and a fixed notice in one viewport; mobile retains a 1000px desktop canvas. AMZ-008 medium: Dense chrome crowds the shopping content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360x800, layout reported no viewport meta, a 1000px inner layout, and 640px overflow; the screenshot shows clipped desktop content. AMZ-009 critical: Homepage is not mobile-responsive in the captured condition |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | medium | Captured CSS includes container-type:inline-size and @container rules for the Rufus/card layout. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Explicit focus probes reported outline:none/0px on search, cart, hamburger, account, and the privacy Continue Shopping control; tiny 8x4px disclosure buttons were also found. AMZ-010 high: Keyboard focus is invisible on primary controls |
support-core-task-successclear-purpose-and-primary-action | pass | medium | Amazon branding, a dominant labelled search field, category navigation, and product cards make shopping purpose and next actions immediately clear. |
support-core-task-successprimary-flow-completion | issues | high | Search returned “Something went wrong”, product detail returned an automated-access challenge, cart returned the same generic error, and sign-in returned not-found. AMZ-011 critical: Primary discovery and purchase routes fail in fresh sessions |
support-core-task-successclear-system-state-and-recovery | pass | medium | Search/cart error screens are explicit, bilingual, and link back home; the product challenge offers Continue Shopping. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 10.54s, FCP 6.03s, Speed Index 11.04s, TTI 16.42s, and performance 54; trace LCP was 3.40s in a separate desktop-like run. AMZ-012 high: Mobile loading performance misses the LCP bar |
be-fast-and-stablevisual-stability | pass | medium | Layout observer and Lighthouse both measured CLS 0 in captured runs. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 179.5ms TBT and 300ms max potential FID; the trace observed two long tasks up to 66.12ms. AMZ-013 medium: Script work delays interactivity |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 292 requests and 5.39MB transferred, including 223 images, 22 fonts, and multiple VeryHigh parser-blocking stylesheets. AMZ-014 high: The homepage ships a heavy, highly fragmented load |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 438KiB unused JavaScript and 213KiB unused CSS; HAR recorded 882.7KB script transfer. AMZ-015 medium: Large unused JS and CSS payloads are delivered |
be-inclusivenames-roles-labels | issues | high | Lighthouse found disallowed aria-expanded on the searchbox, aria-setsize on a list, and an accessible-name mismatch on Cart. AMZ-016 medium: ARIA semantics are invalid on important controls |
be-inclusivesufficient-contrast | pass | medium | Lighthouse color-contrast audit scored 1 and the contrast-emulated screenshot remained readable. |
be-inclusivestructure-and-focus | issues | high | The rendered homepage has no h1 and explicit probes show most primary controls with no visible outline, despite skip links and landmarks. AMZ-017 high: Heading and focus structure is incomplete |
be-inclusivelegible-text | pass | medium | Visible headings, card labels, navigation, and notice copy are readable with stable alignment in desktop evidence. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At a 360px visual viewport the document still lays out at 1000px and overflows by 640px; the viewport meta is absent in the rendered homepage. AMZ-018 critical: Narrow-screen reflow fails |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured a console error warning that module @m/mash loaded late. AMZ-019 low: The homepage logs a client error |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 86/100 images without dimensions, 86 without srcset, 99 legacy-format images, 18 missing alt values, and Lighthouse found six incorrect aspect ratios. AMZ-020 medium: Image markup and sizing are unsound |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found synchronous main-thread XHR, deprecated Shared Storage usage, third-party cookie inspector issues, and a 50 best-practices score. AMZ-021 medium: Deprecated APIs and browser inspector issues remain |
be-discoverabletitle-and-description | pass | medium | Rendered homepage has a descriptive title and a detailed Canada-specific meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The homepage lacks viewport meta in the rendered state and Lighthouse found a javascript:void(0) anchor; robots.txt blocks GPTBot and several paths. AMZ-022 high: Crawler/mobile signals are inconsistent |
be-discoverablecanonical-and-indexing-signals | pass | medium | Homepage returns public content in browser, declares canonical https://www.amazon.ca/, and serves a detailed robots.txt. |
be-discoverablestructured-and-shareable-metadata | issues | high | The platform probe found Open Graph metadata but zero JSON-LD blocks on a public retail/organization homepage. AMZ-023 low: Homepage lacks structured entity metadata |
be-private-and-securesecure-transport-and-headers | issues | high | Direct response evidence confirms HTTPS/HSTS, but no CSP, nosniff, Referrer-Policy, or Permissions-Policy was present; cookie audit found three non-Secure cookies and auth-like cookies without HttpOnly. AMZ-024 high: Security header and cookie posture is incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Lighthouse found 26 third-party cookies and long identity-sync chains; HAR attributed 283/292 requests and 5.12MB to other origins, while the page shows only a Continue Shopping consent action. AMZ-025 high: Advertising and identity-sync footprint is excessive by default |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The direct /ap/signin route returned a not-found page and its DOM contained no form or passkey/WebAuthn path; no permission prompt appeared on homepage load. AMZ-026 high: Authentication entry is unavailable and modern-auth support cannot be reached |
be-private-and-securedefensive-browser-policies | issues | high | HSTS is present, but CSP/frame-ancestors, nosniff, Referrer-Policy, and Permissions-Policy were absent in captured responses; insecure/SameSite=None cookies remain. AMZ-027 medium: Browser-enforced defence headers are incomplete |
be-resilientprogressive-enhancement | issues | high | Discoverability fetched status 202 with only 2,007 raw bytes and 0% rendered-word coverage; title, h1, and meta description were absent and crawler view lacked retail content. AMZ-028 critical: Core content is invisible to a non-JavaScript crawler |
be-resilientresilient-runtime-behaviour | pass | medium | Navigation drawer survived ten repeated open/close cycles and captured overlays remained within a bounded viewport state. |
be-resilientoffline-and-installable | issues | high | A service worker controls the homepage, but the runtime probe found no web app manifest. For a repeat-use commerce service, this leaves installability and offline intent undefined. AMZ-029 low: No installable app metadata is exposed |
be-resilientnetwork-and-http-failure-states | pass | medium | Synthetic and search failures render explicit bilingual recovery content rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The homepage declares lang=en-ca, offers EN country/language controls, and error states provide English and French recovery copy. |
be-internationalisedlocale-aware-data | pass | medium | The Canada storefront identifies en-CA and presents Canada-specific locale/currency context consistently. |
be-internationalisedtime-zone-correctness | not-applicable | medium | No time-zone-sensitive event, schedule, or stored-time surface was present on the accessible homepage; product/account surfaces were unavailable. |
be-trustworthyno-dark-patterns | issues | high | The initial notice presents a prominent yellow Continue Shopping action while preference adjustment is only an inline text link; no equally prominent reject/manage choice is shown. AMZ-030 high: Privacy choice is visually one-sided |
be-trustworthyhumane-error-handling | pass | medium | Failure pages use plain bilingual language and provide a route back to the homepage rather than blaming the user. |
be-trustworthytrustworthy-input-assistance | pass | medium | Search is explicitly labelled, uses type=text with role=searchbox, and supplies appropriate keyboard/search affordances. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Fresh anonymous product, cart, and sign-in routes returned a challenge, generic error, and not-found page respectively, preventing verification of pricing, checkout, cancellation, or reauthentication. AMZ-031 critical: Commercial and account entry points are not safely completable |
be-sustainableoptimised-assets | issues | high | Of 100 images, 99 used legacy formats, 86 lacked responsive sources, 85 below-fold images were not lazy, and image transfer totalled 3.36MB. AMZ-032 high: Image delivery is materially wasteful |
be-sustainableno-wasteful-work | issues | high | The homepage made 292 requests, including 283 cross-origin requests, and Lighthouse reported 438KiB unused JS plus 213KiB unused CSS. AMZ-033 high: The page performs disproportionate background/network work |
be-sustainablethird-party-and-media-budget | issues | high | HAR recorded 5.12MB cross-origin transfer, 22 font requests (739.7KB), 223 image requests, and 4 media requests for the initial homepage. AMZ-034 high: Third-party and font/media budgets are disproportionate |
be-agent-readystructured-agent-capabilities | issues | high | The homepage contained no WebMCP/agentic tool registration, the raw crawler view had 0% content coverage, and robots.txt explicitly disallows GPTBot. AMZ-035 medium: Commerce capabilities are not exposed safely to agents |
be-agent-readyon-device-inference | not-applicable | medium | No summarisation, language-assistance, or other user-facing inference task was present on the audited surfaces, so on-device inference is not warranted. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten menu open/close cycles, heap node count fell from 511,691 to 472,863 and self size from 35.40MB to 32.29MB; no retained growth signal appeared. |
be-memory-efficientbounded-footprint | pass | medium | Runtime used about 21.6MB JS heap and 4,141 live DOM elements; heap snapshot self size was 35.40MB, proportionate for the content-heavy page though sizable. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Repeated drawer interaction reduced rather than grew heap node/edge populations; top constructor summaries exposed no growing Detached* population. |
Provenance
Canonical report: results/atomic/reports/0867-www_amazon_ca.json
Report SHA-256: a03d83c30c0d9df09d3cf7e95bcd8ceea8e97e057d51047d5dad844d526fe175
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_ca/2026-07-28T09-42-36-188Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_ca/2026-07-28T09-42-36-188Z
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.