Manifest position 866 · CrUX rank bucket 1000
https://www.amazon.it
Coverage complete
Coverage-complete audit across six representative public surfaces. Purchase submission and authenticated account pages were intentionally not exercised.
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 | Under prefers-color-scheme: dark, computed body background remains rgb(255,255,255), root color-scheme remains normal, and the dark screenshot is visually unchanged. F01 medium: The site does not follow the user’s dark colour preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe matched the reduce preference but still found three running leftToRight animations with 2000 ms duration. F02 medium: Animations continue when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | high | All controls and text remained visible; Lighthouse color-contrast scored 1. |
implement-natural-interactionsview-transitions | issues | high | The feature probe found only the browser root view-transition name and no authored transition names across homepage, product, cart, help, and sign-in surfaces. F03 low: Page and state changes do not expose meaningful View Transition treatment. |
implement-natural-interactionsscroll-driven-animations | issues | high | The DOM probe found zero ScrollTimeline animations on the long homepage and product page. F04 low: Scroll-related presentation does not use declarative scroll timelines. |
implement-natural-interactionsphysical-gestures | issues | high | Across probes, only the homepage exposed one scroll-snap container; product, cart and help exposed none, while no declarative gesture affordance was found. F05 low: Long product and listing surfaces offer little platform-native gesture support. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The 4,376 px homepage and 9,003 px product screenshot show static chrome; probes found no scroll timelines or scroll-state behavior. F06 low: Navigation chrome does not react to the user’s position on very long pages. |
provide-guided-navigationanchored-positioning | issues | high | The DOM contains many role=dialog navigation flyouts but the computed-style probe found zero anchored elements and no popovers. F07 low: Flyouts and menus use custom positioning rather than resilient CSS anchoring. |
provide-guided-navigationdirects-attention | pass | medium | Skip links, descriptive navigation, persistent cart state, and strong orange/blue focus rings guide attention across pages. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile load screenshots show a fixed consent panel covering the centre of the first viewport before interaction. F08 high: A large cookie consent panel obscures the primary content on every fresh visit. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The consent surface is a FORM role=dialog; axe reports that dialog is not allowed on that element. The site has no dialog, popover, or details elements. F09 medium: The consent modal and navigation overlays are custom ARIA widgets rather than native primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | The full homepage screenshot is 4,376 px tall and gives substantial space to two navigation rows, repetitive promotional tiles, and a multi-column footer. F10 low: Dense navigation, repeated cards, and a very large footer compete with shopping content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360x800 the homepage layout primitive reports no viewport meta, a 1000 px layout viewport, and 640 px overflow. The product page is scaled to 0.36, making text tiny. F11 high: Pages omit the viewport meta tag and render as a desktop canvas on phones. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Homepage exposed 23 container-query containers and product/cart/help each exposed a component container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse fails target-size with two affected groups; the mobile screenshot also shows dense header and card controls. F12 medium: Several controls and links are too small or too tightly spaced for touch. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Search, product Add to basket, cart checkout, sign-in Continue, and help search each present an obvious next action. |
support-core-task-successprimary-flow-completion | pass | medium | Search results link to products with visible price and Add to basket; cart exposes checkout and sign-in continuity. No purchase was placed. |
support-core-task-successclear-system-state-and-recovery | pass | medium | The empty cart offers deals/sign-in, help offers task-based recovery, and malformed direct auth routes show a clear Home recovery link. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse reports FCP 6.9 s and LCP 16.3 s, with performance score 0.58. The separate desktop trace still records LCP 4.09 s. F13 high: The homepage is slow to become useful on the Lighthouse mobile profile. |
be-fast-and-stablevisual-stability | pass | high | Desktop and mobile layout observers recorded CLS 0; Lighthouse also reports CLS 0. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded no long tasks and 0 ms TBT; Lighthouse reports 110 ms TBT, within a good range. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR summary records 2.43 MB over 99 requests, 21 fonts using 729 KB, ten render-blocking candidates, and a 591 KB WAF script that took 3.02 s. F14 high: Critical delivery is heavy and contains long blocking chains. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 661 KiB unused JavaScript and 190 KiB unused CSS across the tested load. F15 medium: The homepage ships substantial code that Lighthouse does not use. |
be-inclusivenames-roles-labels | issues | high | axe reports critical aria-allowed-attr failures on search controls, an invalid dialog role on the consent form, and a select labeled only by title. Lighthouse also fails ARIA audits. F16 high: Critical controls contain invalid ARIA and incomplete visible labeling. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast scored 1 and the prefers-contrast screenshot retained visible text and controls. |
be-inclusivestructure-and-focus | issues | high | The homepage has no h1, begins visible content at h3/h4, and axe reports heading-order and region violations. F17 medium: Heading and landmark structure is inconsistent. |
be-inclusivelegible-text | issues | high | The product mobile screenshot shows a 1000 px desktop layout scaled to 0.36 on a 360 px device because the viewport meta tag is absent. F18 high: Mobile text is rendered at desktop scale and becomes difficult to read. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Both mobile layout captures lack viewport metadata; Lighthouse fails target-size and the homepage reports 640 px horizontal overflow. F19 high: The page fails mobile reflow and touch-target expectations. |
follow-best-practicesno-console-errors | issues | high | Lighthouse fails errors-in-console and records one console error item. F20 medium: The homepage logs a browser error during load. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive finds 38 of 39 images missing dimensions; Lighthouse identifies six incorrect-aspect-ratio images. F21 medium: Numerous images lack stable dimensions and some render at the wrong aspect ratio. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports one deprecation warning on the homepage. F22 low: A deprecated browser API is still used. |
be-discoverabletitle-and-description | pass | high | Homepage and product have unique descriptive titles and meta descriptions; cart/help/auth utility pages have descriptive titles. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse fails crawlable-anchors; probes show javascript:void(0) navigation links, and mobile evidence confirms no viewport meta. F23 medium: Some navigation links are not crawlable and the page is not mobile friendly. |
be-discoverablecanonical-and-indexing-signals | issues | high | Homepage and product canonical URLs exist and robots.txt returns 200, but probes expose no hreflang links and /sitemap.xml returns 404. F24 low: Localized indexing signals are incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | high | The product probe found no JSON-LD and no Open Graph tags despite visible product name, price, availability, ratings, and imagery. F25 medium: The product page lacks structured product and social-preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers evidence reports no CSP, HSTS, nosniff, frame protection, Referrer-Policy, or Permissions-Policy. Cookie evidence finds four cookies without Secure and auth-like session cookies without HttpOnly. F26 high: Transport is HTTPS, but baseline security headers and cookie flags are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence sees 10 third-party origins and the HAR attributes 90 requests and 2.10 MB to origins other than www.amazon.it, including advertising and session telemetry endpoints. F27 medium: The initial page load has a broad telemetry and cross-origin footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; the sign-in page loads IdentityWebAuthnAssets and presents a passkey error state in its DOM. |
be-private-and-securedefensive-browser-policies | issues | high | The main document has no clickjacking policy, Referrer-Policy, Permissions-Policy, CSP, or HSTS according to the headers primitive. F28 high: Browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | issues | high | Discoverability fetch received HTTP 202 with only 2,007 bytes; just 1% of rendered content tokens were present and the primitive classified the response as a JS shell. F29 high: Core content is effectively unavailable to a generic non-JavaScript crawler. |
be-resilientresilient-runtime-behaviour | pass | medium | The tested menus, consent controls, cart state, product details, and help page rendered without clipped active content or blank application shells. |
be-resilientoffline-and-installable | not-applicable | high | Amazon commerce requires live inventory, price, account, and payment services; an offline checkout or installable app was not treated as a requirement. |
be-resilientnetwork-and-http-failure-states | pass | medium | Malformed direct sign-in paths render a concise recovery page with a Home link instead of a blank shell; cart and help provide actionable empty/recovery states. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The English Italian-market page sets lang=en-gb, but dir is absent, hreflang is absent, and the style probe counts 658 rules using physical left/right properties. F30 medium: Localized pages rely heavily on physical CSS and do not publish direction metadata. |
be-internationalisedlocale-aware-data | pass | medium | English content consistently uses euro currency and localized commercial labels on the Italian market surface. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event time, schedule, recurring interval, or time-zone-sensitive task appears in the audited shopping, cart, sign-in, or help surfaces. |
be-trustworthyno-dark-patterns | pass | medium | Consent offers Accept and Decline side by side; pricing, basket actions, sign-in terms, returns, and cancellation help links are plainly disclosed. |
be-trustworthyhumane-error-handling | pass | medium | The sign-in field is an email control with a visible label and the account flow provides Need help; recovery pages provide a direct Home action. |
be-trustworthytrustworthy-input-assistance | pass | high | The sign-in identity field uses autocomplete=username and an email input type; search and help controls have explicit labels. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | Prices and Add to basket are visible before commitment; checkout is separated; account terms and Help are visible; cancellation and returns links are discoverable in help. |
be-sustainableoptimised-assets | issues | high | The image primitive finds 37 legacy-format images, 29 without srcset, 24 below-fold images not lazy loaded, and 38 without both dimensions. F31 medium: Image delivery misses several basic efficiency controls. |
be-sustainableno-wasteful-work | pass | medium | Trace found no long tasks and no autoplay media; the page has no video and no known third-party tracker match, despite the separately reported transfer budget issue. |
be-sustainablethird-party-and-media-budget | issues | high | HAR records 729 KB across 21 fonts and 2.10 MB across non-main origins; the WAF challenge alone is 591 KB. F32 medium: Fonts, WAF, and third-party scripts consume a disproportionate initial-load budget. |
be-agent-readystructured-agent-capabilities | issues | high | Product and homepage probes found no agent tool registration or structured action interface; product JSON-LD is also absent, leaving agents to infer controls from a large DOM. F33 low: The commerce experience exposes no structured agent action surface. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or generative task in the audited commerce flow requires on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | Heap samples were 21.96 MB, 24.66 MB, 16.90 MB, and 19.03 MB across three batches, showing collection rather than monotonic retained growth; DOM nodes stayed at 2,009. |
be-memory-efficientbounded-footprint | pass | medium | Baseline snapshot was 32.48 MB self size and runtime used heap about 22 MB, proportionate to the large commerce page though optimization remains desirable. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | DOM count remained 2,009 through 30 cycles; no Detached constructor appeared in either top-constructor summary and heap fell after collection. |
Provenance
Canonical report: results/atomic/reports/0866-www_amazon_it.json
Report SHA-256: f2816ee040e86f6dadedb933b41c764a400657bb06b7350a06aac9dda9da9307
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_it/2026-07-23T12-35-37-103Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_it/2026-07-23T12-35-37-103Z
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.