Manifest position 334 · CrUX rank bucket 1000
https://www.bestbuy.com
Coverage complete
All 58 atomic checks received conclusive outcomes. Representative product and cart failures are recorded as site issues, not omitted work.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The prefers-color-scheme: dark screenshot retains the same white page surfaces as the default capture, and the computed page color-scheme is normal. F01 medium: The storefront does not provide a user-preference-driven dark theme. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found six running animations with 3000 ms duration and infinite iterations while prefers-reduced-motion: reduce matched. F02 medium: Animations continue when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | high | The loaded CSS probe found no prefers-contrast or forced-colors rule, while controls depend heavily on blue/white styling. F03 low: No high-contrast or forced-colors adaptation was found. |
implement-natural-interactionsview-transitions | pass | high | Loaded CSS contains view-transition declarations, providing declarative state/route transition support. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, entry/exit reveal, or other scroll-linked motion was observed on the representative paths, so there is no scroll handler to modernise. |
implement-natural-interactionsphysical-gestures | pass | high | Loaded CSS contains scroll-snap and overscroll-behavior declarations, and no conflicting gesture surface was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Desktop and mobile screenshots show a fixed-height two-row header, and CSS inspection found no scroll-state(scrolled) query or progress treatment. F04 low: The large two-row navigation chrome does not respond to scroll state. |
provide-guided-navigationanchored-positioning | pass | high | Loaded CSS contains anchor-name and position-anchor declarations for attached overlay positioning. |
provide-guided-navigationdirects-attention | pass | high | Skip links, clearly grouped global navigation, visible selected search query and view-transition CSS preserve orientation. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No load-time interstitial or content-obscuring consent wall appeared in desktop or mobile captures. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Opening Shop sets body overflow:hidden, while the DOM probe found zero popover, dialog, details, or role=dialog elements. F05 medium: Global menus use custom body-locking behavior rather than semantic overlay primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | Desktop marketing/search views devote the main region to offers/products and use a consistent global header without decorative borders around every item. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The mobile layout primitive measured scrollWidth 1069 px against clientWidth 360 px, 709 px horizontal overflow; screenshots show clipped headers, clipped cards and large blank regions. F06 critical: Core commerce pages break at a 360 px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Loaded CSS contains multiple @container rules, direct evidence of component-level container responsiveness despite the separate viewport failure. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe measured multiple navigation links at 16 px high and the international selector CSS explicitly sets .language-menu button:focus { outline: 0 }. F07 medium: Several navigation targets are too short and one control loses focus indication. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Entry, home, search and sign-in surfaces use clear labels and prominent next actions such as country selection, Search, Shop now and Continue. |
support-core-task-successprimary-flow-completion | issues | high | Search rendered results, but direct product navigation returned ERR_HTTP2_PROTOCOL_ERROR on desktop and mobile; cart captures remained an empty shell after seven seconds. F08 high: The representative browse-to-cart flow does not complete reliably. |
support-core-task-successclear-system-state-and-recovery | issues | high | The failed product capture shows a browser protocol error and the cart capture shows only global chrome with a blank content region, no loading, empty, retry, or back-to-shopping state. F09 high: Blank product/cart states offer no status or recovery. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 8.9 s, TBT 3,150 ms and Speed Index 13.1 s (performance 31); the independent trace measured FCP/LCP 9.38 s. F10 critical: Loading performance is far outside the good Core Web Vitals range. |
be-fast-and-stablevisual-stability | issues | high | The mobile layout observer recorded CLS 0.186 with a largest individual shift of 0.115, above the good threshold. F11 high: The mobile layout shifts materially during load. |
be-fast-and-stableefficient-main-thread | issues | high | The trace found seven long tasks, a 659 ms longest task and 1,323 ms TBT; Lighthouse measured 3,150 ms TBT, 7.2 s JS execution and 9.9 s main-thread work. F12 critical: Heavy scripting blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 275 requests and 6.66 MB transferred, including ten parser-inserted VeryHigh-priority stylesheets; Lighthouse estimates 900 ms render-blocking and 844 KiB cache savings. F13 high: Resource delivery contains a large render-blocking and weak-cache burden. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR recorded 150 scripts transferring 6.06 MB, including a 1.06 MB chunk; Lighthouse estimates 3,156 KiB unused JavaScript and 54 KiB unused CSS. F14 critical: The page ships several megabytes of unnecessary JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility scored 84 and failed link-name and aria-allowed-attr; the image audit also reported 15 images without alt attributes. F15 high: Some links and ARIA attributes are not accessible. |
be-inclusivesufficient-contrast | pass | high | Lighthouse did not flag color-contrast among automated accessibility audits, and visible white/blue and black/white text is legible in captures. |
be-inclusivestructure-and-focus | issues | high | The US homepage rendered no h1, Lighthouse flagged positive tabindex, and the international language buttons explicitly suppress their focus outline. F16 high: Heading/focus structure is not consistently logical. |
be-inclusivelegible-text | pass | high | Desktop content uses readable font sizes, line lengths and hierarchy; no text clipping is visible at the supported desktop condition. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse failed meta-viewport because user scaling is disabled or maximum-scale is below 5; mobile evidence shows 709 px overflow and 16 px-high links. F17 critical: The page restricts zoom and fails narrow reflow. |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed errors-in-console during the audited load. F18 medium: The page logs browser console errors. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse found unsized images and two deprecated API warnings; the image audit found 17 images without responsive sources and two oversized images. F19 medium: Document assets include sizing and deprecated-platform defects. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found three BFCache failure reasons, missing source maps for large first-party JS, inspector issues, deprecated APIs and console errors. F20 medium: Browser-platform hygiene is weak. |
be-discoverabletitle-and-description | pass | high | The homepage has a descriptive title and meta description, confirmed by DOM probes and Lighthouse. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse SEO scored 85, reported an invalid robots.txt and two links without descriptive text. F21 medium: Robots and link-text signals are defective. |
be-discoverablecanonical-and-indexing-signals | issues | high | The canonical URL is present, but Lighthouse reports invalid robots.txt; the raw crawler fetch also failed, preventing reliable non-JS retrieval in this run. F22 medium: Indexing signals are inconsistent. |
be-discoverablestructured-and-shareable-metadata | issues | high | The holistic DOM probe found zero JSON-LD blocks and no og:title on a public retail homepage. F23 medium: The commerce homepage lacks structured and share-preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | The HTTPS document lacked CSP, HSTS, nosniff, frame protection, Referrer-Policy and Permissions-Policy; 26 cookies were flagged insecure and many used SameSite=None. F24 critical: Core transport defenses and cookie flags are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe found 24 third-party origins and eight known advertising trackers; HAR recorded 78 third-party requests transferring 1.26 MB. F25 high: Tracking and third-party activity are disproportionate. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Notification permission remained default with no load-time prompt; sign-in uses autocomplete="username webauthn" and its source contains WebAuthn/passkey support. |
be-private-and-securedefensive-browser-policies | issues | high | Header inspection found no HSTS, clickjacking protection, Referrer-Policy, Permissions-Policy or CSP/frame-ancestors. F26 critical: Browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | issues | high | The discoverability run produced a blank crawler screenshot and 0% raw-content coverage while the rendered view contained 170 content tokens; the raw fetch failed. F27 high: Core storefront content is not reliably available to a non-JavaScript crawler. |
be-resilientresilient-runtime-behaviour | issues | high | Product navigation produced ERR_HTTP2_PROTOCOL_ERROR and the cart rendered global chrome over an empty content region with no in-page fallback. F28 high: Runtime route failures degrade to blank or browser-error states. |
be-resilientoffline-and-installable | not-applicable | high | The audited retail purchase flow depends on live price, inventory, fulfillment and payment state; an offline/installable mode is not necessary for truthful completion, while progressive enhancement is judged separately. |
be-resilientnetwork-and-http-failure-states | issues | high | Repeated product and cart captures exposed a browser protocol error or blank shell without Retry, Continue shopping, status copy or preserved context. F29 high: Network/HTTP failures do not provide actionable recovery. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The entry document declares lang="en" and exposes English, French and Spanish variants with language-scoped content and country routing. |
be-internationalisedlocale-aware-data | pass | high | The entry localizes complete headings/actions into English, French and Spanish and routes Canadian shoppers to the localized Canadian storefront. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event scheduling, user-entered time, recurring interval or cross-zone coordination surface was present in the representative public paths. |
be-trustworthyno-dark-patterns | pass | high | Observed entry, offers and sign-in present direct choices, visible terms/privacy links and no confirmshaming or preselected paid commitment. |
be-trustworthyhumane-error-handling | pass | high | Submitting empty sign-in focuses the email input and invokes the clear native message “Please fill in this field.” after interaction. |
be-trustworthytrustworthy-input-assistance | pass | high | Sign-in labels the email field and uses autocomplete="username webauthn"; browser and passkey assistance are enabled rather than obstructed. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Search results are visible but the product route failed and cart body remained blank; pricing/commitment and checkout controls therefore could not be reviewed or reversed in the primary path. F30 high: The commercial journey cannot reliably reach a usable cart state. |
be-sustainableoptimised-assets | issues | high | The image audit found 17 of 25 images without srcset, two oversized assets and one below-fold image loaded eagerly; Lighthouse estimates 165 KiB image savings. F31 medium: Image delivery is not consistently responsive or right-sized. |
be-sustainableno-wasteful-work | issues | high | HAR recorded 275 requests, 150 scripts and 6.66 MB; trace LCP was 9.38 s with 1.32 s TBT, while many analytics/chat endpoints remained active. F32 critical: The homepage performs substantial non-essential work before usefulness. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties made 78 requests and transferred 1.26 MB; known advertising trackers included DoubleClick, Google Ads and Tag Manager. F33 high: Third-party scripts exceed a proportionate homepage budget. |
be-agent-readystructured-agent-capabilities | issues | high | Lighthouse agentic-browsing scored 33 and failed accessibility-tree and llms.txt recommendations; discoverability produced a blank crawler view. F34 medium: A high-value commerce site exposes weak agent-facing structure. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, language-model or other inference task was exposed where on-device AI would clearly improve these retail browsing paths. |
be-memory-efficientno-leak-under-repeated-interaction | issues | high | Baseline-to-post heap snapshots after ten Shop open/Escape cycles grew from 135.4 MB/2,127,297 nodes to 152.5 MB/2,333,939 nodes (12.6% bytes, 9.7% nodes). Separate page loads can add noise, so confidence is medium. F35 medium: Repeated menu interaction showed material retained-heap growth. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap snapshot contained 2,127,297 heap nodes and 135.4 MB self size; the independent performance probe reported about 118.6 MB used JS heap for 858 DOM elements. F36 high: The homepage memory footprint is disproportionate. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | issues | high | Ten open/close cycles were followed by 206,642 additional heap nodes and 17.1 MB additional self size. Constructor-level detached-node data and listener enumeration were unavailable, so confidence is low. F37 medium: Heap-node growth after repeated menu cycles warrants detached-node/listener investigation. |
Provenance
Canonical report: results/atomic/reports/0334-www_bestbuy_com.json
Report SHA-256: 1e5cfe0d2b263068203de4c478932c3c1f84be0b3d807731523457c084d3e389
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_bestbuy_com/2026-07-20T00-30-11-366Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_bestbuy_com/2026-07-20T00-30-11-366Z
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.