Manifest position 570 · CrUX rank bucket 1000
https://www.bilibili.com
Coverage complete
Atomic coverage complete across 58 checks and six representative paths.
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 | Under emulated prefers-color-scheme: dark, the probe reports color-scheme: normal, body background rgb(241,242,243), dark media matched, and no theme media rules; the dark screenshot remains light. F01 medium: Dark preference is ignored |
respect-user-preferencesrespects-reduced-motion | pass | high | Default and reduced-motion probes both observed zero active animations, so no non-essential motion or auto-advance was present in the tested initial state. |
respect-user-preferencesrespects-contrast | issues | high | The high-contrast screenshot is visually unchanged, no prefers-contrast/forced-colors rules were found, and Lighthouse measured 2.75:1 on pink primary controls. F02 medium: Low-contrast controls are not adapted |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection across homepage, listing, search and detail found no view-transition declarations or API use despite route, carousel and disclosure state changes. F03 low: State changes use abrupt swaps |
implement-natural-interactionsscroll-driven-animations | pass | high | DOM/CSS inspection found no scroll-linked animation feature to implement; scrolling is native and trace evidence did not expose a scroll-animation handler. |
implement-natural-interactionsphysical-gestures | pass | high | Popular/search CSS includes overscroll-behavior and tested feed traversal used native scrolling without a custom gesture blocker. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Homepage and listing inspection found fixed/static navigation but no scroll-state container query, progress marker, or scroll-position feedback on long feeds. F04 low: Navigation chrome does not react to scroll state |
provide-guided-navigationanchored-positioning | issues | high | The load-time login overlay is a role-less .v-popover absolutely positioned at 361×256; no native popover or CSS anchor declarations were found. F05 medium: Large custom popovers lack semantic anchored positioning |
provide-guided-navigationdirects-attention | pass | high | Search tabs, active sorting controls, descriptive result titles, pagination, and video-detail hierarchy visibly preserve orientation across tested paths. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The initial homepage screenshot shows a 361×256 login promotion covering the first viewport before user interaction. F06 high: Login promotion obscures content on load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The visible .v-popover has no role; platform probe found 0 dialog, 0 [popover], and 0 details elements. F07 medium: Overlays are ad-hoc divs |
maximize-content-reduce-noisereduced-chrome | issues | high | The homepage first viewport combines a full-width animated banner, two navigation rows, many category pills and an unsolicited login panel before the recommendation grid. F08 medium: Dense chrome competes with content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360×800 the page has no viewport meta and Chrome lays it out at 1105 CSS px then scales it to 0.326; controls and text become tiny rather than reflowing. F09 high: Desktop layout is scaled down on mobile |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | DOM/CSS inspection of home, popular and search card grids found no @container rules; the mobile capture retains the desktop card density. F10 medium: Reusable cards do not adapt at component level |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focus probing found links and inputs with outline none, two unlabeled 28×28 buttons, and many 24–28 px targets. F11 high: Keyboard focus and touch targets are inadequate |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage visibly presents search and recommended videos; search presents query results; video detail presents title and player in the first viewport. |
support-core-task-successprimary-flow-completion | pass | high | A guest could search, open a result/detail and play the representative video, with a clearly disclosed 30-second guest preview rather than a dead end. |
support-core-task-successclear-system-state-and-recovery | pass | high | Video shows playback time/login state, search shows populated results and pagination, and invalid route shows an explicit error with “return to previous page”. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 17.6 s, FCP 3.5 s, TBT 350 ms and performance 0.55; trace corroborated four long tasks. F12 high: Mobile loading is slow |
be-fast-and-stablevisual-stability | issues | high | The 360×800 layout observer recorded CLS 0.240, including shifts of 0.165 and 0.076 after about 5–6 seconds. F13 high: Mobile feed shifts substantially |
be-fast-and-stableefficient-main-thread | issues | high | Trace recorded 4 long tasks, longest 94 ms and TBT 106 ms; Lighthouse measured 2.0 s main-thread work and 350 ms TBT. F14 medium: Startup scripting blocks the main thread |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR found parser-blocking scripts without async/defer and Lighthouse estimated 1.37 s savings from render-blocking requests; 158 requests transferred 2.38 MB. F15 high: Critical delivery has long blocking chains |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 303 KiB unused JS, 72 KiB unused CSS and 219 KiB unminified JS; HAR transferred 731 KiB of scripts. F16 medium: Large unused client bundles ship on first load |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed link-name; probing found two unlabeled buttons, image-heavy links with empty text, and 36 images without alt. F17 high: Interactive controls lack accessible names and structure |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured only 2.75:1 for white text on #ff6699 Download/Open App controls, below 4.5:1. F18 medium: Primary controls fail text contrast |
be-inclusivestructure-and-focus | issues | high | Homepage probe found no h1/h2, only h3 cards and a single main landmark; Lighthouse mobile found no main landmark, and all sampled focus outlines were none. F19 high: Heading/landmark and focus structure is weak |
be-inclusivelegible-text | pass | high | Desktop home, listing, search, detail and login screenshots show readable Chinese text with stable card alignment at the tested desktop viewport. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse found user-scalable=no/maximum-scale=1 on the mobile variant; the tested video had zero text tracks and many controls were 28 px. F20 high: Zoom, reflow and media alternatives are restricted |
follow-best-practicesno-console-errors | pass | high | Lighthouse completed its console/exception audit without reporting a console-error or uncaught-exception failure. |
follow-best-practicessound-document-and-assets | issues | high | Images audit found 26/58 missing dimensions, 39 oversized, 53 without srcset and 36 missing alt, despite a valid doctype and UTF-8 charset. F21 medium: Image sizing is inconsistent |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported deprecated StorageType.persistent usage and 37 KiB legacy JavaScript savings. F22 medium: Deprecated and legacy platform code remains |
be-discoverabletitle-and-description | pass | high | Homepage DOM reports a descriptive bilibili title and a non-empty Chinese meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The desktop homepage has no viewport meta; its mobile rendering is scaled from an 1105 px layout. Links are crawlable and robots permits the page, but the mobile requirement fails. F23 high: Homepage is not mobile-friendly |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage returned 200, has canonical https://www.bilibili.com/, robots permits it, and sitemap index lists current content sitemaps. |
be-discoverablestructured-and-shareable-metadata | pass | high | Representative video detail exposes JSON-LD, canonical URL and og:type/title/image/url matching its visible title and player. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but headers probe found no CSP, HSTS or nosniff; all 13 cookies lacked Secure and used SameSite=None. F24 high: Transport defenses and cookie flags are missing |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR classified 154/158 requests and 2.12 MB as cross-origin, including data.bilibili.com and cm.bilibili.com; tracker probe saw 10 cross-origin hosts. F25 medium: Large tracking and third-party footprint loads by default |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Login probe exposed password, SMS, QR and social paths but no navigator.credentials use or passkey option. No permission prompt appeared on load. F26 medium: Authentication offers no passkey path |
be-private-and-securedefensive-browser-policies | issues | high | Headers probe found no HSTS, clickjacking defense, Referrer-Policy or Permissions-Policy, and no CSP/frame-ancestors. F27 high: Browser-enforced policies are absent |
be-resilientprogressive-enhancement | issues | high | Discoverability fetch found 0% rendered-word coverage in 1,374 bytes of raw HTML; title and description were absent from raw markup. F28 high: Core homepage content disappears without JavaScript |
be-resilientresilient-runtime-behaviour | issues | high | The custom absolute login popover has no anchor fallback and the mobile page is a scaled desktop canvas, increasing clipping and positioning risk. F29 medium: Custom overlay is fragile at constrained viewports |
be-resilientoffline-and-installable | issues | high | Platform probe found no manifest and no service-worker registration for this app-like video service. F30 low: App-like media experience has no install/offline layer |
be-resilientnetwork-and-http-failure-states | pass | medium | Direct DOM, screenshot and interaction inspection across the representative paths found the expected outcome for “HTTP errors, network failures, timeouts and stale data states are handled intentionally: users see useful recovery options rather than blank screens, infinite spinners, broken shells, or misleading success states.”. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Homepage declares lang=zh-CN, but the login document has empty lang and dir; no logical-property evidence was found in inspected login/home styles. F31 medium: Language metadata is inconsistent across account flow |
be-internationalisedlocale-aware-data | pass | high | Rendered Chinese compact counts, dates and durations are consistently localized across search/video for the declared zh-CN audience. |
be-internationalisedtime-zone-correctness | issues | high | Video detail renders “2026-07-16 10:20:00” without a timezone or semantic time element, so global interpretation is ambiguous. F32 low: Published timestamps are timezone-ambiguous |
be-trustworthyno-dark-patterns | pass | high | Search labels sponsored content as 广告, login displays agreement/privacy terms, and no confirmshaming or hidden cancellation was observed in tested guest paths. |
be-trustworthyhumane-error-handling | issues | high | After an empty login submit, inputs had no required or aria-invalid state and no field-specific error appeared; focus remained on body. F33 medium: Empty login submit gives no actionable validation |
be-trustworthytrustworthy-input-assistance | issues | high | Account and password inputs report autocomplete="on" rather than username/current-password and have no associated labels in a semantic form. F34 medium: Sign-in autofill tokens are generic |
be-trustworthysafe-commercial-and-account-flows | issues | high | The account page exposes password/SMS/QR/social options but no passkey authentication or reauthentication path. F35 medium: Account flow lacks phishing-resistant authentication |
be-sustainableoptimised-assets | issues | high | Images probe found 39 oversized images, 53 without srcset, 26 without dimensions and only 32/58 in a detected modern format. F36 medium: Image delivery wastes bytes |
be-sustainableno-wasteful-work | issues | high | The page issued 68 XHR/fetches and 158 requests total, with analytics/reporting hosts active before interaction. F37 medium: Initial load performs disproportionate background work |
be-sustainablethird-party-and-media-budget | issues | high | 2.38 MB transferred on load, including 1.16 MB images; 2.12 MB was cross-origin and the video begins playback muted on its detail page. F38 medium: Third-party and media budget is heavy |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing surface or WebMCP contract is offered; this emerging contextual opportunity is outside the tested consumer video scope. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the tested browsing, playback or login paths requires on-device inference; absence is not a failure for this contextual check. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After 10 bottom/top feed traversals, heap summary grew from 376,116 nodes/23.7 MB to 736,095 nodes/38.8 MB, with closures 26,285→64,282. Lazy feed retention may explain part, so confidence is medium. F39 medium: Repeated feed traversal grows retained heap sharply |
be-memory-efficientbounded-footprint | pass | high | Baseline heap is 23.7 MB with 376,116 nodes and runtime probe reports 15.4 MB used JS heap, proportionate to a media feed before repeated traversal. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Heap summaries did not show Detached* among retained top constructors; the available comparison shows growth but no direct detached-DOM signature. |
Provenance
Canonical report: results/atomic/reports/0570-www_bilibili_com.json
Report SHA-256: e0bd9000166944f4272654b61986236f284c0ffd177c4bc19497eb8534c9d9a0
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_bilibili_com/2026-07-21T15-48-56-890Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_bilibili_com/2026-07-21T15-48-56-890Z
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.