Manifest position 265 · CrUX rank bucket 1000
https://www.amazon.com.mx
Coverage complete
Atomic coverage complete. Search/product/deals route failures were executed and recorded as observed issues, not untested blockers.
Attempts
1 / 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 | Computed and screenshot comparison under dark emulation shows the same white cards/light content surfaces; html reports color-scheme normal. F01 medium: Dark preference is ignored |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, the active hero image changed after seven seconds even though zero CSS animations were reported, so auto-advance continues. F02 medium: Hero auto-advances despite reduced-motion |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot keeps navigation, search, headings, links and product imagery visible with strong system contrast. |
implement-natural-interactionsview-transitions | issues | medium | CSS inspection found zero view-transition rules; search/product navigation uses full document changes and exposed abrupt challenge-state swaps. F03 low: Route/state changes lack View Transitions |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, reveal animation, animation-timeline or scroll-timeline behavior was present on the exercised templates. |
implement-natural-interactionsphysical-gestures | issues | medium | The homepage uses script-driven carousels with no scroll-snap or overscroll rules found; movement is controlled by legacy carousel controls rather than platform gesture primitives. F04 low: Legacy carousel interaction bypasses native gesture primitives |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | Long storefront chrome remains static while scrolling; CSS inspection found no scroll-state query, timeline or progress affordance. F05 low: Long-page chrome is not scroll-state aware |
provide-guided-navigationanchored-positioning | issues | high | DOM inspection found 22 role=dialog overlays but no dialog/popover primitives and no effective anchor positioning or position-try rules. F06 medium: Custom overlays lack robust anchored positioning |
provide-guided-navigationdirects-attention | pass | medium | Visible carousel arrows, section headings, skip links and a strong 3px keyboard outline cue movement and focus on the accessible routes. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Fresh-load homepage, cart and sign-in screenshots show core content immediately with no modal or consent interstitial covering it. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The homepage exposes 22 custom role=dialog elements but zero dialog, popover or details elements, indicating manual overlay semantics/dismissal. F07 medium: Overlays use custom role dialogs instead of native primitives |
maximize-content-reduce-noisereduced-chrome | issues | high | The first viewport is dominated by two navigation bars, a large rotating ad and dense competing promotional cards rather than a clear content hierarchy. F08 medium: First viewport is crowded with competing chrome and promotions |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360px visual viewport the layout primitive reported no viewport meta, 1000px inner/scroll width and 640px horizontal overflow. F09 high: Homepage does not reflow at 360px |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Live CSS contains multiple @container width rules that change reusable grid-card spans and ordering. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focus is visible, but the first viewport probe found 4 of 61 controls below 24px in one dimension and the fixed 1000px mobile layout harms touch use. F10 medium: Touch ergonomics are weakened by small targets and desktop scaling |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage search/navigation, deals headings, cart state and sign-in form each state their purpose and expose a clear next action. |
support-core-task-successprimary-flow-completion | issues | high | Fresh-profile search and product-detail routes both stop at a “Continuar a Compras” anti-bot gate; the deals route also returned “Algo falló”, preventing a dependable browse-to-buy journey. F11 high: Anti-bot and server gates break product discovery |
support-core-task-successclear-system-state-and-recovery | pass | high | Empty cart, invalid sign-in and unknown-route states explain the state and provide sign-in, retry/home or corrective actions. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured FCP 7.6s, LCP 20.5s and performance 0.56; a separate trace still measured LCP 2.74s, showing materially variable load performance. F12 high: LCP is slow and highly variable |
be-fast-and-stablevisual-stability | pass | high | Both desktop and mobile layout observers recorded CLS 0 with no shift entries; Lighthouse also reported CLS 0. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded only 2 long tasks, longest 71.29ms, with 40.77ms total blocking time; Lighthouse TBT was 121ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 315 requests and 5.74MB transferred, including five parser-inserted VeryHigh-priority stylesheets and 21 font requests. F13 high: Initial delivery is request-heavy and render-blocked |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 465KiB unused JavaScript and 155KiB unused CSS, including 328KiB wasted in the WAF challenge script. F14 medium: Large unused JS and CSS payloads ship on first load |
be-inclusivenames-roles-labels | issues | high | Lighthouse found invalid ARIA on the searchbox/carousel and a cart visible-label/accessibility-name mismatch; the image probe found 14 missing alt values. F15 medium: ARIA/name and image-alt defects remain |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed and forced-colors screenshot preserved text/control visibility. |
be-inclusivestructure-and-focus | issues | high | Keyboard focus has a clear 3px outline, but the homepage has no H1 and Lighthouse found an accessibility tree/ARIA structure failure. F16 medium: Homepage lacks a coherent top-level heading/ARIA structure |
be-inclusivelegible-text | pass | medium | Desktop, forced-colors, cart and sign-in screenshots show readable body text, headings and controls without clipping on their intended layout. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Homepage and cart omit viewport meta; 360px capture renders a 1000px desktop layout and the probe found four sub-24px controls. F17 high: Zoom/reflow support is broken by missing viewport metadata |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured repeated console.error entries for late-loading modules and MIX rendering errors. F18 medium: Production page logs rendering errors |
follow-best-practicessound-document-and-assets | issues | high | Doctype/UTF-8 are valid, but 87 of 100 images lack dimensions, 98 lack srcset and 99 use legacy formats. F19 medium: Image markup and delivery are structurally weak |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported deprecated Shared Storage usage and DevTools inspector issues. F20 low: Deprecated APIs and inspector issues are present |
be-discoverabletitle-and-description | pass | high | Homepage and deals have descriptive titles and meta descriptions; title/description Lighthouse audits pass. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found javascript:void(0) anchors, and the homepage lacks viewport meta and overflows by 640px at a 360px visual viewport. F21 high: Mobile and crawlability fundamentals fail |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage returns over HTTPS with a self-canonical; deals provides a canonical; robots permits ordinary crawling of these public routes. |
be-discoverablestructured-and-shareable-metadata | issues | medium | No JSON-LD was present on the homepage or cart despite organization/store/entity content, reducing machine-readable rich-result context. F22 low: Store/entity metadata lacks JSON-LD |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS and nosniff are absent; 6 of 7 cookies were flagged insecure and session-like cookies were not HttpOnly. F23 high: Security headers and cookie flags are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR attributed 307 requests and 5.53MB to non-main origins, while runtime evidence shows continuous detailed performance telemetry endpoints. F24 medium: Third-party-like delivery and telemetry footprint is excessive |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; the real sign-in surface contains WebAuthn/passkey code and uses username autocomplete. |
be-private-and-securedefensive-browser-policies | issues | high | Headers primitive found no clickjacking defense, Referrer-Policy or Permissions-Policy in addition to missing HSTS/CSP. F25 high: Browser-enforced defensive policies are absent |
be-resilientprogressive-enhancement | pass | high | Browser screenshots with JavaScript disabled retain the homepage navigation, hero and promotional content, closely matching the rendered view. |
be-resilientresilient-runtime-behaviour | issues | high | Fresh browser sessions produce inconsistent route behavior: home/cart work, search/product show a challenge gate, and deals can render a generic server failure. F26 high: Runtime behavior is inconsistent across core routes |
be-resilientoffline-and-installable | not-applicable | high | This commerce storefront is intrinsically online for live inventory, pricing and checkout; no installable/offline intent is declared and no manifest is linked. |
be-resilientnetwork-and-http-failure-states | pass | high | The 404/server-failure surfaces clearly say what happened and offer retry, search or a homepage route rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | html lang is es-mx, content is localized Spanish, controls use dir=auto where needed, and LTR reading order remains coherent. |
be-internationalisedlocale-aware-data | pass | medium | Rendered prices use Mexican peso notation and Spanish offer/countdown labels appropriate to the es-MX storefront. |
be-internationalisedtime-zone-correctness | not-applicable | medium | Representative public paths exposed countdown durations but no absolute user-entered or cross-time-zone event timestamps to validate. |
be-trustworthyno-dark-patterns | pass | medium | Pricing/promotions are visibly labelled, sign-in states terms before continuation, and cart/account actions are explicitly named; no confirmshaming or forced continuity was observed. |
be-trustworthyhumane-error-handling | pass | high | Submitting the empty sign-in form shows a specific Spanish alert asking for mobile number or email without losing context. |
be-trustworthytrustworthy-input-assistance | issues | high | The username field uses autocomplete=username, but the password input exists with an empty autocomplete attribute instead of current-password. F27 low: Password field omits autofill semantics |
be-trustworthysafe-commercial-and-account-flows | issues | high | Cart and sign-in are clear, but the representative search/product routes are gated, so pricing-to-product-to-checkout continuity could not be completed reliably. F28 high: Commercial flow cannot reliably reach product and checkout |
be-sustainableoptimised-assets | issues | high | Of 100 images, 99 are legacy formats, 98 lack srcset, 87 lack dimensions and 86 below-fold images are not lazy-loaded. F29 high: Homepage assets are not sustainably optimized |
be-sustainableno-wasteful-work | issues | high | The homepage makes 315 requests and emits detailed telemetry while idle; Lighthouse reports 465KiB unused JS and 155KiB unused CSS. F30 medium: Idle page performs wasteful delivery and telemetry work |
be-sustainablethird-party-and-media-budget | issues | high | The 5.74MB load includes 5.53MB from non-main origins, 248 image requests and 21 font requests, disproportionate for the initial storefront viewport. F31 high: Initial media and cross-origin budget is excessive |
be-agent-readystructured-agent-capabilities | issues | high | No WebMCP/agentic tool registration was found and robots.txt explicitly disallows major agent user-agents, despite the site being an agentic-commerce candidate. F32 medium: Agentic commerce capabilities are unavailable by policy and structure |
be-agent-readyon-device-inference | not-applicable | medium | No public summarisation or language-model task on the exercised storefront paths clearly requires on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten carousel-next interactions, heap grew from 25.20MB/407,012 nodes to 27.42MB/413,845 nodes; the modest one-pass increase was concentrated in native/code rather than an obvious runaway constructor. |
be-memory-efficientbounded-footprint | pass | medium | Runtime JS heap was 20.74MB with 2,595 DOM elements; snapshot self-size was 25-27MB, proportionate to a large commerce homepage. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Before/after heap summaries show no Detached* constructor among retained leaders and closure count changed only 20,546 to 20,587 after ten interactions. |
Provenance
Canonical report: results/atomic/reports/0265-www_amazon_com_mx.json
Report SHA-256: 27d9fdb7eae69ad15dc93eab3c21c0ad313c8cbd9696c45827baf54b3cb687ff
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_com_mx/2026-07-19T13-39-22-743Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_com_mx/2026-07-19T13-39-22-743Z
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.