Manifest position 103 · CrUX rank bucket 1000
https://www.alibaba.com
Coverage complete
Representative homepage and category templates completed. Search, manufacturer, and product paths consistently returned a CAPTCHA interception; this was judged as direct evidence of a core-flow issue rather than an audit blocker.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Under prefers-color-scheme: dark, the screenshot remains light and the probe reports colorScheme "normal" with a white body background. F003 medium: The site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found five running shape-flow animations, each with a 20,000 ms duration, while prefers-reduced-motion: reduce matched. F004 medium: Long-running decorative motion continues under reduced motion. |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse color-contrast passed; prefers-contrast emulation matched and the live CSS included contrast rules. |
implement-natural-interactionsview-transitions | issues | high | The platform-feature CSS probe found no view-transition rules across the representative category interface. F005 low: Page and state changes do not use declarative View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation was present on the audited templates, so implementation technique does not apply. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull, carousel gesture, or other gesture-driven core control was present in the audited public paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The 4,991 px category page screenshot and CSS probe show a static desktop header with no scroll-state or scroll progress treatment. F006 low: The long catalog lacks scroll-state-aware navigation cues. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or edge-positioned popover was required in the exercised category and search states. |
provide-guided-navigationdirects-attention | pass | high | The category breadcrumb, selected category, product count, and product headings provide explicit orientation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots after a 5 second wait show a large Accio Work trial modal dimming and blocking the primary Alibaba marketplace content. F001 high: A promotional trial interstitial obscures the homepage on arrival. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | medium | The homepage DOM snapshot taken while the overlay was visible contained no <dialog> or popover element, while the screenshot shows modal behavior. F002 medium: The load-time overlay is not exposed through a native modal primitive in the captured DOM. |
maximize-content-reduce-noisereduced-chrome | issues | high | At 360 px the fixed desktop filter rail occupies most of the visible width, leaving only a clipped product column. F007 medium: Dense persistent filters and navigation crowd the product content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Layout evidence reports scrollWidth 1200, clientWidth 360, and 840 px horizontal overflow; the screenshot shows clipped header, breadcrumb, filters, and products. F008 critical: The category template renders a 1,200 px desktop layout on a 360 px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The category’s filter/product composition remains desktop-sized at 360 px, and the platform CSS probe found no container-query rules. F009 high: Catalog components do not adapt to their available container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse found 35 target-size failures; the focus probe found many anchors with outline-style none and no box shadow. F010 high: Many controls are too small and several links have no visible focus indicator. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The category first viewport clearly names “Solar Panels”, product count, filters, products, prices, MOQ, and search. |
support-core-task-successprimary-flow-completion | issues | high | Fresh search, manufacturer, and product-detail captures all returned “Captcha Interception” and a slide-to-verify challenge instead of results or product content. F011 high: Search, manufacturer, and product-detail navigation can dead-end at an anti-bot challenge. |
support-core-task-successclear-system-state-and-recovery | issues | high | The challenge shows only a slider, QR code, and “Click to feedback”; it does not explain how to resume the search or preserve the query. F012 medium: The traffic challenge provides weak recovery and no path back to the intended task. |
be-fast-and-stablegood-core-web-vitals | issues | high | The raw trace measured homepage LCP at 5,256.64 ms. Category Lighthouse measured 2.1 s, showing a template-specific regression. F013 high: Homepage LCP is slow despite the category template performing well. |
be-fast-and-stablevisual-stability | pass | high | Mobile category layout recorded CLS 0.00015; category Lighthouse CLS was 0.00013. |
be-fast-and-stableefficient-main-thread | pass | high | Homepage trace total blocking time was 80.1 ms and category Lighthouse TBT was 67 ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR evidence records 465 requests and 7,776,049 transferred bytes, including 102 scripts (3.60 MB), 222 images (1.61 MB), and multiple parser-inserted stylesheets. F014 high: The homepage ships a very large request graph. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The HAR shows large messenger/RFQ bundles on homepage load; Lighthouse found 44 KiB unused in one category bundle (72.7% of that resource). F015 medium: Non-critical and partly unused JavaScript is shipped up front. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed button-name and link-name; the DOM probe counted 114 empty links and 78 images without an alt attribute on the category page. F016 high: Important controls and links lack accessible names. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed on the category template. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed landmark-one-main; focus sampling found many anchors with no outline or focus shadow. F017 high: The category page has no main landmark and focus styling is inconsistent. |
be-inclusivelegible-text | pass | high | Desktop/category screenshots show readable type hierarchy and Lighthouse found no contrast failure. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At 360 px the category overflows by 840 px and Lighthouse reports 35 undersized or crowded targets. F018 high: The interface fails narrow reflow and target-size requirements. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured TypeError: Cannot read properties of null (reading “2”) in cdn-seo-ai-category-wap/index.js. F019 medium: A category JavaScript exception is logged. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found all three visible images without width/height, two without srcset, and one 600 px image displayed at 134 px. F020 medium: Image delivery lacks basic sizing and responsive hints in the observed homepage overlay. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports an unload listener and four BFCache failure reasons, plus a deprecated API warning. F021 medium: Deprecated unload behavior prevents BFCache restoration. |
be-discoverabletitle-and-description | pass | high | Homepage and category expose descriptive titles and meta descriptions in raw and rendered HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse SEO scored 1.0; anchors are crawlable and category viewport metadata is valid, notwithstanding the separate reflow failure. |
be-discoverablecanonical-and-indexing-signals | pass | high | Category returned 200 with canonical URL, index/follow robots meta; robots.txt and sitemap.xml returned 200. |
be-discoverablestructured-and-shareable-metadata | issues | high | Metadata evidence shows complete Open Graph tags but no JSON-LD for the product-list/category entity. F022 low: The category has social metadata but no structured entity data. |
be-private-and-securesecure-transport-and-headers | issues | high | The HTTPS response has no CSP, HSTS, nosniff, frame protection, Referrer-Policy, or Permissions-Policy; two 180-day cookies are not Secure and use SameSite=None. F023 high: Baseline security headers and cookie protections are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR reports 461 of 465 requests and 7.74 of 7.78 MB as third-party by origin, while tracker evidence enumerates 12 third-party origins. F024 high: Nearly the entire homepage transfer is attributed to cross-origin infrastructure and telemetry-heavy dependencies. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Login loaded without permission prompts and offered Google, Facebook, LinkedIn, QR, and email routes; passkey-related capability text was present in the document probe. |
be-private-and-securedefensive-browser-policies | issues | high | Header evidence confirms no CSP/frame-ancestors or X-Frame-Options, HSTS, Referrer-Policy, or Permissions-Policy. F025 high: Browser-enforced defense policies are absent. |
be-resilientprogressive-enhancement | issues | high | Discoverability measured 44% homepage and 47% category content coverage without JavaScript. The pages are not empty shells, but substantial product/content detail depends on client rendering. F026 medium: Only about half of rendered catalog vocabulary is available in raw HTML. |
be-resilientresilient-runtime-behaviour | pass | high | The successfully loaded category remained functional and stable with native navigation and no clipped overlay in the desktop state. |
be-resilientoffline-and-installable | not-applicable | high | Alibaba is a transaction marketplace whose current inventory, identity, and ordering require a live connection; an installable/offline app shell was judged non-essential for the audited public web scope. |
be-resilientnetwork-and-http-failure-states | pass | high | The anti-bot response rendered a stable explanatory state and feedback route rather than a blank shell; task recovery limitations are recorded separately. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Category HTML declares lang=en; captured CSS uses inset-inline-start/end and the page exposes region/language selection. |
be-internationalisedlocale-aware-data | pass | high | The page selected delivery region GB and presents explicit currency-valued product prices rather than ambiguous bare numbers. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public pages showed no dates, events, schedules, or time-zone-sensitive data. |
be-trustworthyno-dark-patterns | pass | high | The observed promotion has a visible close control and no confirmshaming; listings expose price and MOQ. |
be-trustworthyhumane-error-handling | pass | high | The only exercised exceptional state explains unusual traffic and offers feedback; its weak recovery is recorded under core task success. |
be-trustworthytrustworthy-input-assistance | pass | high | Search has an accessible label; login identifies the email input and offers QR/social alternatives, though autocomplete is off. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Public listings show price and MOQ; login offers multiple routes without requesting payment or hidden commitment. |
be-sustainableoptimised-assets | issues | high | Image evidence found an oversized 600 px PNG displayed at 134 px and missing responsive sources; the homepage transferred 1.61 MB across 222 images. F027 medium: Image assets are not consistently right-sized or responsive. |
be-sustainableno-wasteful-work | issues | high | The homepage HAR includes 600 KB messenger, 554 KB chat, and 465 KB RFQ bundles during initial load. F028 high: Large messaging and RFQ modules load before user intent. |
be-sustainablethird-party-and-media-budget | issues | high | The homepage transfers 7.78 MB across 465 requests, with 7.74 MB attributed to origins outside www.alibaba.com. F029 high: The initial page budget is disproportionate to the marketplace landing task. |
be-agent-readystructured-agent-capabilities | issues | high | The homepage advertises “AI Mode”, but the platform probe found no WebMCP/agent tool registration; Lighthouse agentic-browsing scored 0.33. F030 low: The marketplace exposes no structured agent tools despite an explicit AI-oriented sourcing surface. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or generative task requiring local inference was exposed in the audited public flow. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten filter toggle cycles, heap self-size decreased from 33,646,286 to 33,549,660 bytes and node count decreased from 444,025 to 443,111. |
be-memory-efficientbounded-footprint | pass | high | The category heap was 33.6 MB self-size for a dense 530-image catalog page, proportionate to the rendered surface. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Post-interaction heap totals did not grow and no Detached* constructor appeared among the largest constructor populations. |
Provenance
Canonical report: results/atomic/reports/0103-www_alibaba_com.json
Report SHA-256: 5427b13f7f5206d9ceec95ffdec9379a31d00b7f7c7490e08575b25c7a5f7a7e
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_alibaba_com/2026-07-18T10-56-13-326Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_alibaba_com/2026-07-18T10-56-13-326Z
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.