Manifest position 263 · CrUX rank bucket 1000
https://www.amazon.com.br
Coverage complete
Coverage-complete report-mode audit across five representative public commerce paths. Authenticated account, order history and final payment confirmation were not covered because they require credentials/payment; the accessible pre-auth boundary was covered.
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 html color-scheme remained normal and body stayed white (#fff) with dark text; the screenshot is unchanged from light mode. F01 medium: Honours prefers-color-scheme: a usable dark mode exists and is driven by the user's preference (color-scheme / prefers-color-scheme / light-dark()), not hard-coded light only. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned none; only 0.1s control transitions remained and the CSS inventory includes a reduced-motion branch. |
respect-user-preferencesrespects-contrast | pass | high | The forced-colors/prefers-contrast screenshot keeps navigation, search, hero copy and card content visible with system high-contrast colors. |
implement-natural-interactionsview-transitions | issues | medium | Homepage CSS exposes view-transition text, but search and product templates expose no View Transition CSS and cross-document navigation remains an abrupt full load. F02 medium: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, entry reveal, or other scroll-linked motion was observed on the representative templates, so there is no scroll-driven motion implementation to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The audited desktop commerce paths expose conventional links, buttons and carousels; no pull, swipe-to-remove or gesture-only control was present. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | After scrolling 1,200px, the main navbar moved to top -1200px with position:static; it provides no persistent location/progress cue or scroll-state adaptation. F03 medium: Sticky/affixed UI reacts to scroll state and position (e.g. the new scroll-state(scrolled) query, shrinking headers, progress indicators) so chrome responds to position instead of static or JS-driven toggling. |
provide-guided-navigationanchored-positioning | issues | medium | Across product/cart/home there are 22-35 custom role=dialog nodes, no popover elements, and product/search CSS exposed no anchor positioning; overlays use legacy custom positioning. F04 medium: Tooltips, popovers and menus use CSS anchor positioning (with fallback positions) so they stay attached and reposition correctly rather than being manually positioned. |
provide-guided-navigationdirects-attention | pass | high | Skip links target main content, search results, product details, buying options and reviews; keyboard focus is visibly outlined. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Initial homepage, listing and product captures expose the core content without a blocking load-time interstitial. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM contains no native dialog/popover/details elements but 22 custom role=dialog nodes on home and 35 on product; the add-to-cart insurance overlay is custom chrome rather than a native dialog. F05 medium: Overlays and rich controls use the right primitive: popover (with declarative light-dismiss) for transient UI, dialog for modal flows, details for disclosure, native-but-branded selects and pickers, rather than ad-hoc divs. |
maximize-content-reduce-noisereduced-chrome | pass | medium | Despite dense merchandising, the first viewport devotes the majority of space to the current offer/product content and global chrome remains confined to the top navigation. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | All audited templates omit meta viewport. At a requested 360px viewport the homepage retained a 1000px layout and layout evidence reported 640px overflow; product and search were scaled-down desktop pages with tiny text. F06 critical: Layout adapts to narrow viewports with no horizontal overflow and no fixed pixel widths forcing a desktop layout on mobile; viewport meta present; fluid scaling and intrinsic sizing rather than brittle breakpoints. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Search/product probes found no container-query signals and their 360px captures simply shrink a desktop grid; the product three-column composition is still present at mobile width. F07 high: Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The first 100 controls include 8x4px buttons, 12-20px-high links, and 13px checkboxes; several common targets are below comfortable touch sizing even though focused controls do receive a visible outline. F08 medium: Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Search communicates the result query, the product page presents title, price and prominent add/buy actions, and the cart presents a clear checkout action. |
support-core-task-successprimary-flow-completion | issues | high | Adding the product does not proceed directly to cart; it inserts a full-page insurance upsell dialog, adding an avoidable modal detour before the primary flow can continue. F09 medium: The representative primary flow can be completed end-to-end with predictable steps, no avoidable dead ends, no hidden required information, and no needless detours through modals, account walls, or upsells. |
support-core-task-successclear-system-state-and-recovery | pass | high | The empty cart clearly states that it is empty and offers shopping/sign-in recovery; the missing URL page explains the failure and links back home. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured homepage LCP 26.6s, TBT 1,210ms and performance 31; product LCP was 27.9s with CLS 0.444 and performance 38. F10 critical: Core Web Vitals are in the good range: LCP is fast, interaction latency (INP) is low, and CLS is minimal; work is prioritised and deferred sensibly. |
be-fast-and-stablevisual-stability | issues | high | Product Lighthouse measured CLS 0.444 with two large layout shifts; the 360px layout observer also recorded late shifts. F11 high: No cumulative layout shift from late content (images, banners, fonts) that arrives without reserved space. |
be-fast-and-stableefficient-main-thread | issues | high | Homepage Lighthouse reports 5.0s main-thread work, 2.9s JavaScript execution and 1,210ms TBT; the trace corroborates long tasks. F12 high: The main thread is not blocked by long tasks or heavy scripting; work is deferred, chunked, prioritised, or moved off-thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | Home transferred 5.66MB in 365 requests and product 6.99MB in 277; summaries identify many VeryHigh-priority parser stylesheets and product Lighthouse estimates 890ms render-blocking savings. F13 high: Critical resources are delivered efficiently: cache headers are useful, render-blocking chains are short, fonts do not block or shift text, HTTP delivery is modern, and network dependency trees do not delay the main content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 645KiB unused JavaScript on home and 1,007KiB on product, plus 255KiB/183KiB unused CSS. F14 high: The page does not ship large unused or duplicated JavaScript/CSS, avoidable legacy bundles, or third-party code that dominates the load without user value. |
be-inclusivenames-roles-labels | issues | high | axe found critical invalid/required ARIA on both templates, an unnamed product dialog, invalid list relationships, and a select labelled only by title. F15 critical: Interactive elements have accessible names, correct roles, and form fields have labels; images have alt text where meaningful; canvas/expressive content is exposed to assistive technology. |
be-inclusivesufficient-contrast | issues | high | axe measured the footer contact link at only 2.09:1 against surrounding text and found no non-color distinction. F16 high: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | Home has no H1 and duplicate/nested banner landmarks; product starts with H2/H3 before H1 and axe reports broken heading/list/landmark structures. Focus styling itself is visible. F17 high: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves. |
be-inclusivelegible-text | issues | high | Without a viewport declaration, 360px captures scale 1000px desktop layouts down; product and search text is visibly too small for comfortable reading. F18 high: Text is legible and inclusively rendered: comfortable line layout, precise alignment, stable rendering across mixed fonts, no clipping or cramped wrapping that harms comprehension. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The missing viewport meta prevents true mobile reflow and the target probe found numerous controls below 24px, including 8x4px buttons and 13px inputs. F19 high: The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling. |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed errors-in-console on both home and product. F20 medium: The page loads without console errors or uncaught exceptions. |
follow-best-practicessound-document-and-assets | issues | high | Although doctype/charset are valid, Lighthouse found six incorrectly proportioned images on home; image audit found 61/80 missing dimensions and 18/9 oversized images. F21 medium: Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.) |
follow-best-practicesbrowser-platform-hygiene | issues | high | Both Lighthouse runs report two deprecated-API warnings and DevTools inspector issues; product also ships legacy JavaScript with an estimated 41KiB saving. F22 medium: The page uses the platform cleanly: no deprecated APIs, no avoidable BFCache blockers, no broken source maps or inspector issues, no stale vulnerable libraries, no paste-prevention on inputs, and no notification/geolocation prompts on load. |
be-discoverabletitle-and-description | issues | high | Homepage/product metadata is descriptive, but the representative search results page has no meta description. F23 medium: The page has a unique, descriptive <title> and a meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | All audited pages omit viewport meta; home/product expose javascript: hrefs (5 and 67), and Lighthouse fails crawlable anchors. F24 medium: Links are crawlable (real href), there is a viewport meta tag, robots does not block indexing, and link text is descriptive. |
be-discoverablecanonical-and-indexing-signals | pass | medium | Home and product returned successful browser responses and expose appropriate canonical URLs; robots.txt and sitemap.xml were reachable, while dynamic search intentionally has no canonical. |
be-discoverablestructured-and-shareable-metadata | issues | high | The product probe found no JSON-LD and no Open Graph tags despite representing a rich product entity. F25 medium: Where the page represents an article, product, organization, event, place or other rich entity, structured data and share-preview metadata accurately describe the visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but the homepage response lacked CSP, HSTS, nosniff, clickjacking, referrer and permissions headers; six of eight home cookies lacked Secure and auth-like session cookies lacked HttpOnly. F26 high: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Home made 357 third-party requests transferring 5.40MB; product made 249 transferring 6.66MB, including advertising/reporting origins. F27 high: No over-collection of user data, no leaky third parties, and analytics/background data collection is minimised and batched rather than chatty or session-wide by default. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission request code was found on load, and the sign-in experience contains passkey support plus username autocomplete. |
be-private-and-securedefensive-browser-policies | issues | high | Homepage lacks HSTS, clickjacking protection, Referrer-Policy and Permissions-Policy; product adds HSTS/XFO but still lacks the latter two. F28 high: Browser-enforced defenses are configured where appropriate: HSTS, clickjacking protection (frame-ancestors / X-Frame-Options), Trusted Types for XSS-sensitive apps, origin isolation, privacy-preserving third-party cookie posture, and sensible Referrer-Policy / Permissions-Policy. |
be-resilientprogressive-enhancement | issues | high | Non-JS crawler evidence saw 0% rendered-word coverage on home and search; raw responses lacked title/H1/description and crawler screenshots are effectively empty, while product alone is server-rendered. F29 high: Core content and primary flows are reachable and usable without JavaScript and on older or non-Baseline browsers; modern features layer on as enhancements with fallbacks, and reactive/transition state stabilises rather than flickering before it settles. |
be-resilientresilient-runtime-behaviour | pass | high | The exercised insurance overlay remains fully inside the viewport, presents an explicit close and neutral decline action, and the inspected paths remained operational. |
be-resilientoffline-and-installable | issues | high | A service worker is registered, but no web app manifest is linked, so this app-like commerce site is not installable from the audited surface. F30 medium: Where the site is an app, it is installable (web app manifest) and offers an offline fallback and works on flaky networks. (Contextual: a brochure or intrinsically-online site may reasonably not need this.) |
be-resilientnetwork-and-http-failure-states | pass | high | A representative missing URL presents a branded, understandable recovery page with search and a link home instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | medium | lang=pt-br is correct, but product/search expose no logical-property signal; the product stylesheet probe counted 178 physical left/right declarations, creating writing-mode and translation-layout risk. F31 medium: Correct lang and dir attributes, logical CSS properties (inline/block) rather than physical left/right, and translation-ready markup so the layout and reading order survive other languages and writing modes. |
be-internationalisedlocale-aware-data | pass | medium | Visible prices use Brazilian currency notation and the interface/content uses Brazilian Portuguese consistently. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public shopping paths expose no scheduled event, recurring time, or user-editable date/time concept requiring a time-zone correctness judgement. |
be-trustworthyno-dark-patterns | pass | medium | The insurance offer is an interruption, but it is unchecked by default and gives “Não, obrigado” equal visual weight; no confirmshaming or forced continuity was observed. |
be-trustworthyhumane-error-handling | pass | medium | The sign-in form has a visible label and the DOM includes specific invalid email/phone, generic retry, and passkey recovery messages. |
be-trustworthytrustworthy-input-assistance | issues | high | Sign-in email correctly uses autocomplete=username, but the password field has no autocomplete token instead of current-password and/or webauthn assistance. F32 medium: Input is assisted, not obstructed: correct autocomplete tokens so address, payment, sign-in and sign-up fields autofill, and inputs are highlighted/sized to help the user rather than trip them up. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | Product price and insurance cost are explicit, the add-to-cart upsell can be declined, and sign-in supports passkeys; no concealed commitment was observed before the authenticated boundary. |
be-sustainableoptimised-assets | issues | high | Home image audit found 99/100 legacy-format images, 96 missing srcset, 18 oversized and 83 below-fold images not lazy; images alone transferred 3.52MB. F33 medium: Images and decorative assets are optimised and served at appropriate resolutions; decorative pseudo-element imagery and heavy decorative images are resolution-optimised rather than oversized. |
be-sustainableno-wasteful-work | issues | high | The audited first loads make 277-365 requests and ship 645KiB-1,007KiB estimated unused JavaScript, indicating substantial work without first-view value. F34 medium: Background work and fetching are not wasteful: background processing is efficient and de-prioritised, and the lightest technique that achieves the result is preferred over heavy or redundant work. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party infrastructure accounts for 5.40MB on home and 6.66MB on product; product begins fetching multiple 197-306KB video segments during initial load. F35 high: Third-party scripts, fonts, video, audio, animation and heavy media are proportionate to the user value they provide; autoplay or background media is avoided unless essential and resource use is cached or deferred where possible. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agentic commerce would be plausible, but the site exposes no declared WebMCP/agent-facing surface and this emerging capability is not assumed to be an intended public contract. |
be-agent-readyon-device-inference | not-applicable | high | No user-facing summarisation, generation or translation task was exposed on the representative paths; absence of built-in AI usage is therefore not a failure. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten carousel advances in one session, live DOM nodes changed from 3479 to 3478 and animations stayed at zero. Heap grew about 4.1MB, but no monotonic DOM retention was observed in this bounded exercise. |
be-memory-efficientbounded-footprint | issues | medium | The homepage heap summary contains 452,638 heap nodes and 28.7MB self size at baseline, rising to 469,091 and 32.0MB after a short interaction window; this is heavy for a storefront landing page. F36 medium: Heap size and DOM node count are reasonable for what the page is; the footprint is proportionate rather than bloated. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Top constructor summaries contain no Detached* population, closures stayed essentially flat (21,460 to 21,419), and live DOM count did not grow after ten carousel actions. |
Provenance
Canonical report: results/atomic/reports/0263-www_amazon_com_br.json
Report SHA-256: 986493ef0c2663c8833a305328939fba563ff05a51057f29d9a14b366ac13fe3
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_com_br/2026-07-26T02-00-28-658Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_amazon_com_br/2026-07-26T02-00-28-658Z
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.