Manifest position 268 · CrUX rank bucket 1000
https://www.amazon.com
Coverage complete
58/58 atomic checks judged across four representative public commerce paths.
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 prefers-color-scheme: dark, matchMedia was true but body remained rgb(255,255,255), color-scheme was normal, and the capture remained light. F-01 medium: The storefront ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce active, three 2,000 ms animations remained running. F-02 medium: Animations continue when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | medium | The prefers-contrast: more capture retained readable navigation, controls, promotional text, and visible boundaries. |
implement-natural-interactionsview-transitions | issues | high | Platform probe found zero authored view-transition rules; page/search/product changes are full-document abrupt swaps in the captured journey. F-03 low: Route changes do not provide visual continuity. |
implement-natural-interactionsscroll-driven-animations | pass | medium | CSS probe found no scroll timelines and the inspected pages showed no scroll-linked decorative motion, so no main-thread scroll-animation anti-pattern was present. |
implement-natural-interactionsphysical-gestures | pass | medium | Screenshots and DOM show platform scrolling and conventional links/controls; no custom pointer-driven gesture surface was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long homepage uses static two-row navigation; CSS probe found no scroll timeline/container-query behavior or progress affordance. F-04 low: Long shopping pages provide no scroll-state-aware navigation chrome. |
provide-guided-navigationanchored-positioning | issues | high | The location callout is an ad-hoc overlay and the CSS probe found no anchor-positioning/container rules; it occupies the header/content boundary. F-05 medium: Header overlays are not positioned with resilient anchored primitives. |
provide-guided-navigationdirects-attention | pass | high | The pages expose skip links and explicit keyboard shortcuts for main content, search, cart, home, orders, and product summary. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | A delivery-location callout appears on load over the hero/header on mobile and obscures page content until dismissed. F-06 medium: A location interruption obscures the initial shopping surface. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM probe found zero dialog, popover, or details elements despite the visible dismissible location overlay. F-07 medium: Transient overlays are built without semantic top-layer primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | The first viewport devotes two dense nav rows plus a large promotional hero and overlapping country notice before core product browsing content. F-08 low: Dense chrome and promotions compete with shopping content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360px, layout measured 1,000px wide with 640px horizontal overflow and no viewport meta; the screenshot visibly clips the desktop canvas. F-09 critical: The homepage does not reflow to a 360px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS probe found zero @container rules; reusable cards remain arranged on the 1,000px canvas in the narrow capture. F-10 medium: Reusable cards do not adapt to their available container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse failed target-size; focus probe found many controls with no computed outline and 8x4px disclosure buttons. F-11 high: Several controls have undersized targets or no visible focus treatment. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, search results, product detail, and cart titles/content clearly state their purpose; search is prominent and product/cart actions are labelled. |
support-core-task-successprimary-flow-completion | pass | medium | The unauthenticated journey exposes crawlable search, product, cart, and checkout form endpoints without an account wall before cart; the sampled product explains its delivery limitation and offers alternatives. |
support-core-task-successclear-system-state-and-recovery | pass | high | The unavailable product states that it cannot ship to the selected location and offers Change Address/See Similar Items; the 500 sitemap response supplies home/search recovery. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 18.7s, FCP 5.6s, interactive 19.1s, and CLS 0.093; performance score was 0.55. F-12 critical: Largest content paint and interactivity are far outside good ranges. |
be-fast-and-stablevisual-stability | pass | high | Lighthouse CLS was 0.093, inside the good threshold below 0.1; the layout primitive observed no shifts in its post-load window. |
be-fast-and-stableefficient-main-thread | pass | high | Trace found zero long tasks and 0ms TBT; Lighthouse TBT was about 10ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 65 requests/1.32MB and ten render-blocking candidates, including six very-high-priority stylesheets; trace LCP was 3.84s and Lighthouse cold-run LCP 18.7s. F-13 high: Render-blocking chains and resource delivery delay primary content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse failed unused CSS and unused JavaScript audits; HAR attributes 388KB transferred to 17 scripts and 109KB to eight stylesheets. F-14 high: The homepage ships avoidable unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed aria-allowed-attr and label-content-name-mismatch; the DOM probe also found unnamed image-only links and one image without alt. F-15 high: Some controls and image links lack reliable accessible names/ARIA semantics. |
be-inclusivesufficient-contrast | pass | high | Lighthouse accessibility remained 0.93 without a color-contrast failure, and both normal and increased-contrast screenshots remain legible. |
be-inclusivestructure-and-focus | issues | high | Homepage has no h1, jumps from h3 to h5, and the focus probe found many focusable controls with outline style none. F-16 high: Heading hierarchy and keyboard focus visibility are inconsistent. |
be-inclusivelegible-text | pass | medium | Desktop and product captures show readable type, adequate line spacing, and no text clipping at the desktop viewport. |
be-inclusivezoom-reflow-targets-and-media | issues | high | No viewport meta was present, 360px layout overflowed by 640px, and Lighthouse failed target-size. F-17 critical: Zoom/reflow and touch-target support fail on the sampled narrow viewport. |
follow-best-practicesno-console-errors | issues | high | Lighthouse explicitly failed the errors-in-console audit. F-18 medium: The homepage emits console errors during load. |
follow-best-practicessound-document-and-assets | issues | high | Although doctype and UTF-8 are valid, Lighthouse failed image-aspect-ratio and unsized-images; image probe found 19/20 missing dimensions. F-19 high: Most images lack intrinsic dimensions and some render at incorrect aspect ratios. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported deprecations and inspector issues, alongside a best-practices score of 0.50. F-20 medium: Deprecated APIs and DevTools inspector issues remain in production. |
be-discoverabletitle-and-description | pass | high | Homepage, search, product, and cart have descriptive titles; homepage and product include descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable-anchors, the DOM includes javascript:void(0) navigation links, and the page lacks viewport meta. F-21 high: Some navigation is not crawlable and the page lacks mobile indexing basics. |
be-discoverablecanonical-and-indexing-signals | issues | high | Canonical is present, but /sitemap.xml returned HTTP 500 while robots.txt contains extensive blocks; raw non-JS fetch returned 202. F-22 high: Sitemap and HTTP indexing signals are inconsistent. |
be-discoverablestructured-and-shareable-metadata | issues | high | The sampled product had canonical/description but zero JSON-LD and zero Open Graph tags; homepage had only two OG tags. F-23 medium: Product entities lack structured and complete share metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but headers probe found no CSP, HSTS, or nosniff; cookie audit found eight flagged cookies, including session-id without HttpOnly and several without Secure. F-24 critical: Transport defenses and cookie attributes are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR recorded 55 third-party-origin requests and 947,519 third-party bytes; tracking endpoints included fls-na.amazon.com and unagi.amazon.com. F-25 high: Third-party and telemetry traffic dominates the sampled load. |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No geolocation/notification prompt appeared on load, secrets scan found no credentials, and auth is only entered through explicit sign-in links. |
be-private-and-securedefensive-browser-policies | issues | high | Headers probe found no frame protection, Referrer-Policy, Permissions-Policy, HSTS, CSP, or X-Content-Type-Options. F-26 critical: Browser-enforced defensive policies are absent on the main response. |
be-resilientprogressive-enhancement | issues | high | Discoverability fetch returned only 1% content coverage and classified the raw response as a JS shell; title, h1, and description were absent from raw HTML. F-27 critical: Core storefront content is unavailable to no-JavaScript clients. |
be-resilientresilient-runtime-behaviour | pass | medium | The location callout remained within the viewport and supplied Dismiss/Change Address; product unavailability retained state and alternatives. |
be-resilientoffline-and-installable | not-applicable | high | No manifest link was present; this was judged contextual rather than a failure. |
be-resilientnetwork-and-http-failure-states | pass | high | The sampled HTTP 500 response presented a clear apology, home link, search form, and retry route instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang is en-us, but dir is absent and CSS probe found zero logical-property rules despite the global language/country surface. F-28 medium: Global storefront layout is not demonstrably bidi/logical-property ready. |
be-internationalisedlocale-aware-data | pass | medium | The storefront detects delivery country, exposes language/country preferences, and adjusts shipping availability to the selected locale. |
be-internationalisedtime-zone-correctness | not-applicable | high | The sampled pages contain no time-zone-sensitive flow to test. |
be-trustworthyno-dark-patterns | issues | high | The first viewport combines a large Prime promotion with an automatically displayed location callout, adding nagging promotional/interruption pressure before product discovery. F-29 medium: Promotional and location prompts compete with neutral shopping choices on arrival. |
be-trustworthyhumane-error-handling | pass | high | The unavailable product explains the cause in plain language and offers Change Address, Similar Items, and delivery-location controls. |
be-trustworthytrustworthy-input-assistance | pass | medium | Search is correctly labelled and the cart’s checkout action uses a native form; no paste prevention or hostile input handling was observed. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | The sampled product makes availability explicit before checkout, cart is separately named, and sign-in is an explicit user action rather than an on-load wall. |
be-sustainableoptimised-assets | issues | high | Image probe found 15 legacy-format images, no modern-format images, eight without srcset, four oversized, and 19 without dimensions. F-30 high: Image delivery wastes bytes and misses responsive/modern formats. |
be-sustainableno-wasteful-work | issues | high | HAR loaded 65 requests and 1.32MB on the initial storefront, including telemetry and modules below the primary task; Lighthouse found unused CSS/JS. F-31 high: Initial load includes avoidable background and unused work. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party origins accounted for 947,519 bytes, about 72% of transfer, while images used 407KB and scripts 388KB. F-32 high: Third-party and media transfer is disproportionate on initial load. |
be-agent-readystructured-agent-capabilities | issues | high | Robots.txt explicitly disallows GPTBot, ClaudeBot, GoogleAgent-Mariner/Shopping and many other agents; Lighthouse agentic-browsing score was 0.46, despite agent-action attributes in search. F-33 medium: Agent-facing shopping capability is fragmented and broadly blocked. |
be-agent-readyon-device-inference | not-applicable | high | No user-benefiting on-device inference use case was established during recon. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After ten top-to-bottom scroll cycles, used JS heap rose from 16.49MB to 23.80MB (44%) while DOM nodes rose only 2,132 to 2,151; separate heap summaries also increased after exercised loading. This is a leak-risk signal, not a confirmed retained-path diagnosis. F-34 medium: Repeated scrolling shows substantial heap growth requiring retained-object investigation. |
be-memory-efficientbounded-footprint | pass | medium | Exercised heap summary was about 32.1MB with 468,588 snapshot nodes; this is substantial but proportionate to a dense commerce homepage and did not approach an obvious crash-risk footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Repeated scrolling added only 19 live DOM nodes; available summary evidence did not show runaway DOM accumulation. Raw retained-path analysis was not used, so confidence is medium. |
Provenance
Canonical report: results/atomic/reports/0268-www_amazon_com.json
Report SHA-256: 5651e5fd82e3cd4c936faa15537cc45ac184f1b45718ee769b77770d8e2438be
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_com/2026-07-26T02-25-52-988Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_com/2026-07-26T02-25-52-988Z
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.