Manifest position 607 · CrUX rank bucket 1000
https://www.target.com
Coverage complete
Coverage-complete external audit. A persistent loading overlay blocked visual interaction, but rendered DOM and independent evidence primitives permitted all atomic checks to be judged.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-emulated screenshot is visually identical to the light capture, and the computed root color-scheme is normal with a white body background. F01 medium: The site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe matched reduce but still found a 550 ms animation with an indefinite iteration count on the persistent loader. F02 medium: An indefinite loading animation remains active under reduced motion. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot showed text, controls, focus rings, and modal boundaries remaining visible. |
implement-natural-interactionsview-transitions | pass | high | Live CSS inspection found five rules containing view-transition usage. |
implement-natural-interactionsscroll-driven-animations | pass | high | Live CSS inspection found three rules using animation-timeline or scroll-timeline. |
implement-natural-interactionsphysical-gestures | not-applicable | high | Representative paths expose conventional links, buttons, scrolling, and form controls rather than a custom gesture surface. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The rendered site provided sticky header/navigation and CSS scroll-timeline rules without horizontal instability. |
provide-guided-navigationanchored-positioning | pass | high | Live CSS inspection found two anchor-positioning rules, and header account chrome stayed attached at the viewport edge. |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs, descriptive cards, skip links, and clear search/product hierarchy provide directional context. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop, mobile, search, product, category, and cart screenshots show a modal “Almost there…” overlay; after 15 seconds it remained display:flex and visible. F03 critical: A modal loading screen obscures every audited commerce surface indefinitely. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM evidence identifies a DIV role=dialog/aria-modal=true; the persistent overlay has no visible close, cancel, or retry action. F04 high: The blocking overlay is an ad-hoc role=dialog with no user dismissal. |
maximize-content-reduce-noisereduced-chrome | pass | high | Underlying content uses large imagery and card groupings with limited framing; chrome is compact when overlays are excluded. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360×800, scrollWidth equaled clientWidth (360 px), horizontal overflow was 0, and viewport meta was present. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Live stylesheet inspection found three container-query/container-type rules and mobile content reflowed to one column. |
adapt-to-the-form-factorinput-modality-aware | pass | high | Focus walk found 44–48 px primary controls and visible dashed focus treatment on most controls; mobile targets were touch-sized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, search, and product DOM expose clear headings, descriptive product links, price, and Add to cart action. |
support-core-task-successprimary-flow-completion | issues | high | Search results and product details were present in the DOM, but all journey screenshots remained covered by the loader, preventing pointer completion of selection and add-to-cart. F05 critical: The representative search-to-product-to-cart journey is visually blocked. |
support-core-task-successclear-system-state-and-recovery | issues | high | After 15 seconds the only message remained “Almost there… Thank you for your patience,” with no timeout, retry, cancel, or fallback. F06 high: The loading state provides no recovery action or useful progress. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 8.7 s and TBT about 2,000 ms, with a performance score of 0.35; the independent trace was faster but still recorded blocking work. F07 high: Lab load performance misses the good Core Web Vitals bar. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observer measured CLS 0.000008 and Lighthouse measured CLS 0.00003, both effectively zero. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reported about 2,000 ms TBT; the trace recorded five long tasks, a 248.73 ms maximum task, and 303.95 ms TBT. F08 high: Heavy JavaScript blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR evidence recorded 208 requests and 5.75 MB transferred, including 19 stylesheets and at least ten parser-inserted VeryHigh-priority stylesheet candidates; 2.91 MB was one media resource. F09 high: The homepage delivers a large, fragmented critical path. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 634 KiB of unused JavaScript; HAR recorded 87 scripts and 2.08 MB of script transfer. F10 high: Substantial unused JavaScript is shipped on initial load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse’s label-content-name-mismatch audit failed, despite an otherwise strong 0.99 accessibility score. F11 medium: Some visible labels do not match their accessible names. |
be-inclusivesufficient-contrast | pass | high | Lighthouse accessibility score was 0.99 with no contrast failure; forced-colors capture retained visible text and UI. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed heading-order; the DOM starts with an H2 sign-in prompt before H1, then jumps from H1 to H3 cards. F12 medium: The heading hierarchy is not sequential. |
be-inclusivelegible-text | pass | high | Desktop/mobile screenshots show readable line lengths, unclipped headings, and clear product/card copy. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Viewport allows normal scaling, mobile reflow had no overflow, primary header targets measured 44–48 px, and no essential autoplay media was present. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit scored 1 with no items. |
follow-best-practicessound-document-and-assets | pass | high | Lighthouse passed doctype, charset, image aspect-ratio and responsive-image audits; DOM confirmed HTML5 doctype and UTF-8. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed the inspector-issues audit and recorded third-party-cookie concerns; the HAR also contained eight 403 responses. F13 medium: Chrome reports unresolved inspector issues. |
be-discoverabletitle-and-description | pass | high | Homepage, search, and product probes each found descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Real href links, viewport meta, index/follow robots, and descriptive navigation text were present; Lighthouse SEO scored 1.0. |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage/product canonicals were present, HTTP fetch returned 200, robots allowed public pages, and robots listed dedicated sitemap indexes. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage contained two structured metadata scripts and product title/description/canonical accurately matched visible product content. |
be-private-and-securesecure-transport-and-headers | issues | high | The cookie primitive counted 24 insecure/problematic cookies, including ffsession, TealeafAkaSid, AMCV cookies and sddStore without Secure; idToken lacked HttpOnly. F14 high: Multiple cookies are not marked Secure and an auth-like token is script-readable. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Trackers found 33 third-party origins and five known tracker hosts; HAR attributed 187/208 requests and 5.67 MB to non-www.target.com origins. F15 high: The homepage has a broad tracking and third-party footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Lighthouse passed geolocation/notification-on-start audits; no permission prompt appeared on load. Authentication UI was present but not entered. |
be-private-and-securedefensive-browser-policies | issues | high | Headers showed no Permissions-Policy; Referrer-Policy was no-referrer-when-downgrade. CSP only declared frame-ancestors, leaving script/style policy unenforced in this header. F16 medium: Browser policy headers are incomplete and referrer policy is permissive. |
be-resilientprogressive-enhancement | pass | high | Raw HTML returned 200, was not a JS shell, retained title/H1/description, and contained 86% of rendered content tokens. |
be-resilientresilient-runtime-behaviour | issues | high | The same loading dialog stayed visible after 15 seconds across independent loads, while underlying content had rendered. F17 high: Runtime initialization does not converge to a usable state. |
be-resilientoffline-and-installable | issues | high | Recon found no manifest link. A service-worker-capable runtime exists, but no install metadata or tested offline fallback was exposed. F18 medium: No web app manifest or offline fallback was evident for this app-like commerce experience. |
be-resilientnetwork-and-http-failure-states | issues | high | HAR recorded eight HTTP 403 responses and all tested paths remained under the loading modal with no retry or fallback. F19 high: Failed dependencies lead to an indefinite loader rather than recovery. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | html lang is en-US and no locale selector or localized variant was found in representative navigation. |
be-internationalisedlocale-aware-data | not-applicable | high | Visible monetary values are US dollars; no multi-locale formatting surface was present. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative retail flow showed delivery dates but no time-zone-editable event model. |
be-trustworthyno-dark-patterns | pass | high | Visible prices and sale labels were explicit; sign-in prompt was dismissible; no preselected purchase or consent coercion was observed. |
be-trustworthyhumane-error-handling | pass | high | No required-data form was part of the anonymous search/product path; search accepted a query without premature error behavior. |
be-trustworthytrustworthy-input-assistance | issues | high | The recon probe found the email-address field using autocomplete="on" rather than the specific email token; the search input deliberately uses off. F20 low: Input autocomplete semantics are too generic. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Product price and Add to cart were present in DOM evidence, but product and cart screenshots remained blocked by the indefinite modal. F21 high: Commercial actions cannot be completed reliably in the observed state. |
be-sustainableoptimised-assets | issues | high | The images primitive found five oversized images, 18 without srcset, and all 38 missing at least one explicit dimension; the page does use WebP query delivery. F22 medium: Images are not consistently responsive or dimensioned. |
be-sustainableno-wasteful-work | issues | high | HAR measured 208 requests, 87 scripts, 187 cross-origin requests, and a 2.91 MB media transfer while an indefinite loader continued animating. F23 high: Large background and third-party work is disproportionate to the initial retail task. |
be-sustainablethird-party-and-media-budget | issues | high | 5.67 MB of 5.75 MB was from origins other than www.target.com; one media asset was 2.91 MB and known ad/session-replay trackers loaded. F24 high: Third-party and media transfer dominates the homepage. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No WebMCP runtime capability was exposed and no target-site web-uplift config declared agent intent. |
be-agent-readyon-device-inference | not-applicable | high | Browser AI globals existed, but the audited retail tasks did not invoke an inference feature. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten bottom/top search-result scroll cycles, nodes grew only 0.22% and heap self size 0.61%; object, closure, and Promise counts decreased or stayed effectively flat. |
be-memory-efficientbounded-footprint | issues | high | The search baseline heap contained 1,455,397 nodes, 6,810,817 edges, and 69.7 MB self size, including 117,103 closures. F25 medium: The search results page has a large baseline heap footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after summaries showed closures decreasing from 117,103 to 116,913 and Promises from 2,335 to 2,295; no Detached constructor appeared among retained top constructors. |
Provenance
Canonical report: results/atomic/reports/0607-www_target_com.json
Report SHA-256: 89c5e695b98bd91d0cce5c2a1cd4deaee2d2a45513315d2071f32a71f92f1e2e
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_target_com/2026-07-21T21-59-31-609Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_target_com/2026-07-21T21-59-31-609Z
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.