Manifest position 422 · CrUX rank bucket 1000
https://sellercentral.amazon.in
Coverage complete
Coverage-complete public-surface audit across the acquisition homepage, sign-in, onboarding handoff, and fee detail archetype. Authenticated seller-dashboard pages and account creation after personal-data entry were not covered.
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 | The dark-mode screenshot remains a light cream surface, and the computed root color-scheme is "normal" under prefers-color-scheme: dark. F01 medium: The public landing page does not honor the system dark theme. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, three autoplay videos were paused, but both 31 MB conveyor GIFs remained present and cannot be paused by the user. F02 medium: Reduced-motion users still receive large animated GIFs. |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse color-contrast passed, and the prefers-contrast: more screenshot retained visible text and controls. |
implement-natural-interactionsview-transitions | issues | medium | The public page is a traditional MPA with ordinary links and custom popup state; no authored transition behavior was observed during route and state inspection. F03 low: Page and state changes do not expose an authored transition treatment. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, reveal, or other scroll-linked motion was present; the probe found zero non-auto animation timelines. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No gesture-driven carousel, swipe action, pull-to-reveal interaction, or custom pointer gesture was present on the representative public paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The page is about 6,651 CSS pixels tall, but visual inspection showed static chrome and no progress or scroll-state affordance. F04 low: The very long landing page has no scroll-position feedback. |
provide-guided-navigationanchored-positioning | issues | high | The DOM contained no dialog or popover elements, while Lighthouse identified custom .popup and .popover containers with close anchors. F05 medium: Popup and popover UI is built from custom div containers. |
provide-guided-navigationdirects-attention | pass | high | The hero establishes a clear reading order, repeated Start selling actions are visually prominent, and focused controls retain visible outlines. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Desktop, mobile, sign-in, and onboarding screenshots loaded without a content-obscuring modal or consent wall. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Lighthouse found multiple anchor elements used as popup close controls, and the DOM probe found no dialog or popover primitives. F06 medium: Dismissible overlays use links and custom containers rather than native primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | The first viewport gives most space to the offer, product image, and primary action; navigation chrome is compact. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | No viewport meta tag is present. At a 390x844 device viewport Chrome laid out a roughly 1001px page and scaled it to 0.39; desktop layout also overflowed by 220px. F07 high: Mobile rendering depends on browser shrink-to-fit instead of a responsive viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The CSS probe found no @container rules even though cards and tabbed content are reused at materially different widths. F08 low: Reused content components do not use component-level containment. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The probe found the Log in and Explore now links at 24px high, numerous footer links at 19 to 22px, and radio inputs at 13px; focus indicators were visible. F09 medium: Many visible interactive targets are substantially shorter than 44px. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The H1 states the fee offer, and Start selling and Log in actions are prominent in both desktop and mobile first viewports. |
support-core-task-successprimary-flow-completion | pass | high | The public acquisition flow provides direct Start selling, Log in, and pricing links; each reached a coherent dedicated entry page without a dead end. |
support-core-task-successclear-system-state-and-recovery | pass | high | Sign-in and onboarding retain Need help and alternate account actions, while the homepage remained usable when an analytics XHR failed. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured 5.7s LCP and 0.199 CLS. The mobile layout observer measured CLS 0.674; trace TBT was low at 19.76ms. F10 high: Lab loading performance and visual stability miss good thresholds. |
be-fast-and-stablevisual-stability | issues | high | Layout observation recorded CLS 0.245 desktop and 0.674 mobile; 24 of 25 images lacked explicit dimensions. F11 high: Late media and layout changes cause visible instability. |
be-fast-and-stableefficient-main-thread | pass | high | The trace found one 69.76ms long task and only 19.76ms total blocking time; Lighthouse TBT was 70ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR recorded 73.65 MB transferred, including two GIFs of about 31 MB each, plus three parser-inserted stylesheets; the page still reached 5.7s Lighthouse LCP. F12 high: Resource delivery is dominated by huge animated and media assets. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 126 KiB unused JavaScript and 49 KiB unused CSS, with assets-Sell.css 91.2% unused. F13 medium: The page ships avoidable unused JavaScript and CSS. |
be-inclusivenames-roles-labels | issues | high | The form probe found required text, email, and phone controls with no associated label and empty autocomplete, plus a visible email field named only by placeholder. F14 high: Several marketing and feedback form controls lack durable programmatic labels. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed and the high-contrast screenshot remained legible. |
be-inclusivestructure-and-focus | issues | high | Lighthouse flagged an H5, "What do you want to learn more about?", that skips the logical heading sequence; focus outlines were otherwise visible. F15 medium: Heading order is invalid in a lower-page learning section. |
be-inclusivelegible-text | pass | high | Screenshots show readable, left-aligned text, strong hierarchy, and no text clipping on the inspected desktop and mobile views. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At a 390px device width the browser rendered a 1001px layout at 0.39 scale. Three autoplay videos also had no caption tracks, although they appeared decorative and muted. F16 high: The missing viewport declaration undermines mobile reflow and zoom behavior. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured a blocked sadobe.sell.amazon.in XMLHttpRequest and net::ERR_FAILED console error. F17 medium: The page logs a CORS failure during a normal load. |
follow-best-practicessound-document-and-assets | issues | high | The document has HTML doctype and UTF-8, but 24 of 25 images lacked explicit dimensions, seven were oversized, and six used legacy formats. F18 medium: Image sizing and document asset hygiene are weak despite valid doctype and charset. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported four BFCache failure reasons, including cache-control:no-store and an unload handler, and 404 source maps. F19 medium: The page is ineligible for BFCache and references missing source maps. |
be-discoverabletitle-and-description | pass | high | The raw and rendered page expose a descriptive title and a detailed meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found multiple anchors without usable href values; the DOM probe counted 11 empty/hash hrefs, and no viewport meta tag exists. Robots permits the homepage. F20 high: The page has uncrawlable controls and lacks a mobile viewport declaration. |
be-discoverablecanonical-and-indexing-signals | issues | high | The page returns 200, declares index/follow and a canonical URL, but /sitemap.xml returns 404 and no hreflang links were observed for the localized en-IN page. F21 medium: Indexing signals are only partially complete. |
be-discoverablestructured-and-shareable-metadata | issues | medium | The probe found six Open Graph tags but zero JSON-LD blocks on a page representing Amazon Seller Central and its commercial offer. F22 low: Share metadata exists but rich structured data is absent. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show HTTPS and HSTS but no CSP. Cookie inspection flagged 14 cookies without Secure and auth-like session-id/session-token cookies without HttpOnly. F23 high: Transport is HTTPS, but CSP and cookie protections are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The HAR found 81 of 86 requests and 73.49 MB on non-page origins; tracker inspection found 14 third-party origins including Demdex and Everest, and long-lived analytics cookies. F24 high: The public landing page has a broad telemetry and third-party footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Lighthouse found no geolocation or notification prompt on load, and the sign-in DOM contains WebAuthn/passkey parameters with autocomplete=webauthn. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS and X-Frame-Options are present, but the headers probe found no CSP, Referrer-Policy, or Permissions-Policy. F25 high: Several browser-enforced defensive policies are missing. |
be-resilientprogressive-enhancement | pass | high | The raw HTML contained 100% of rendered content words, with title, H1, and meta description present without JavaScript; the crawler screenshot remained complete. |
be-resilientresilient-runtime-behaviour | issues | high | The page uses custom .popup/.popover containers and 11 empty/hash hrefs; Lighthouse found multiple href-less close anchors. F26 medium: Custom overlay controls are brittle and some links have no navigation destination. |
be-resilientoffline-and-installable | not-applicable | high | This is a public marketing and authentication entry surface, not an installable application; recon found no manifest or controlling service worker, and offline installation is not required for its core purpose. |
be-resilientnetwork-and-http-failure-states | pass | high | A cross-origin analytics request failed during the audited load, but the complete hero, navigation, forms, and primary actions still rendered and remained usable. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=en-IN and dir=ltr and exposes a visible preferred-language control; the localized page retained coherent reading order. |
be-internationalisedlocale-aware-data | pass | high | Visible commercial data uses India-appropriate crore notation, rupee symbols, and en-IN language conventions. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public pages contain no scheduled event, user-entered time, recurring interval, or time-zone-sensitive workflow. |
be-trustworthyno-dark-patterns | pass | high | Pricing claims, effective date, sign-in, registration, and primary actions are plainly labelled; no consent wall, confirmshaming, or forced continuity appeared. |
be-trustworthyhumane-error-handling | issues | high | Several required controls have no associated labels, and the visible email field relies on a placeholder; no error-announcement relationship was observed in the form probe. F27 medium: Marketing forms lack the semantics needed for humane, accessible validation. |
be-trustworthytrustworthy-input-assistance | issues | high | Required text, email, and phone fields on the landing page all expose an empty autocomplete value; sign-in correctly uses autocomplete=webauthn. F28 medium: Marketing forms omit autocomplete assistance. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Pricing commitments are visible on the fee page, account entry clearly separates sign-in and account creation, and the sign-in markup includes WebAuthn/passkey support. |
be-sustainableoptimised-assets | issues | high | The load transferred 73.65 MB: two animated GIFs alone were 31.1 MB and 31.0 MB. Seven images were oversized, 24 lacked dimensions, and 13 below-fold images were not lazy loaded. F29 high: Asset delivery is grossly disproportionate for a marketing page. |
be-sustainableno-wasteful-work | issues | high | Three muted videos are marked autoplay, two huge animated GIFs load automatically, and 81 third-party requests occurred during the initial page load. F30 high: Large autoplay and telemetry work begins without user intent. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party origins transferred 73.49 MB; images used 65.75 MB and media 6.39 MB before the user requested video playback. F31 high: Third-party and media budgets are far beyond the page value delivered. |
be-agent-readystructured-agent-capabilities | issues | medium | The commerce onboarding surface has standard links and forms but no WebMCP or agentic-tool registration was observed; raw content is crawler-visible. F32 low: Seller registration and support capabilities are not exposed as structured agent tools. |
be-agent-readyon-device-inference | not-applicable | high | No summarization, translation of user content, or other inference-heavy task on these public entry pages would clearly benefit from an on-device model. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After repeated activation of the representative tab/button controls, heap self-size was 14.63 MB versus a 13.85 MB cold baseline; this modest cross-session difference did not show unbounded growth. |
be-memory-efficientbounded-footprint | pass | high | The interacted heap summary reported 235,924 nodes and 14.63 MB self-size for a 1,071-element media-rich page, a proportionate current footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Detached constructors did not appear among the heap summary top constructors, and repeated interaction produced only modest total growth; no strong detached-DOM or accumulation signal was observed. |
Provenance
Canonical report: results/atomic/reports/0422-sellercentral_amazon_in.json
Report SHA-256: 67c766494db1e682e9c44893050ab70d537646a7564bc8529b195bffd98ee57c
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/sellercentral_amazon_in/2026-07-20T17-29-25-692Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/sellercentral_amazon_in/2026-07-20T17-29-25-692Z
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.