Manifest position 543 · CrUX rank bucket 1000
https://bakusai.com
Coverage complete
Atomic coverage complete across 58 checks and six representative paths. No local source was supplied; report mode only.
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 white surface, and the CSS probe found no prefers-color-scheme, light-dark(), or color-scheme implementation. F-01 medium: The public forum is light-only. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, the probe still found a running 6.5-second animation and no reduced-motion media rule. F-02 medium: Motion continues when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | high | The CSS probe found no prefers-contrast or forced-colors rule; the high-contrast capture retains the same dense, low-emphasis styling. F-03 medium: The interface has no high-contrast adaptation. |
implement-natural-interactionsview-transitions | issues | medium | The CSS probe found no view-transition usage across MPA navigation or the stamp modal state change. F-04 low: Route and state changes are abrupt. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation, parallax, carousel, or scrollytelling interaction is present to implement. |
implement-natural-interactionsphysical-gestures | pass | medium | The inspected surfaces rely on native scrolling and links; no custom pointermove or gesture layer was observed fighting platform behavior. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The listing and thread are several screens long, but screenshots and CSS inspection show no progress indicator or scroll-reactive chrome. F-05 low: Long pages provide no scroll-state guidance. |
provide-guided-navigationanchored-positioning | issues | medium | The stamp overlay is custom DOM, while the CSS probe found no anchor positioning, popover, or dialog primitives. F-06 low: Transient UI is manually positioned rather than anchored. |
provide-guided-navigationdirects-attention | pass | medium | Breadcrumbs, selected area styling, descriptive thread links, and back-to-list controls give direct location cues across the exercised read journey. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | medium | Load screenshots show banners and inline ads but no full-screen interstitial or content-blocking consent wall. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The thread exposes custom .js-stampmodal-open/.close controls, while the probe found zero dialog, popover, or details elements. F-07 medium: The stamp overlay is an ad-hoc control. |
maximize-content-reduce-noisereduced-chrome | issues | high | At 360px the desktop page is scaled to fit; the listing is dominated by banners, a dense image grid and side rail, while the thread places multiple ads before and beside the core discussion. F-08 high: Advertising and chrome overwhelm the content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360x800 viewport, listing/thread layout metrics report innerWidth 1100 and a scale of about 0.327; screenshots show tiny desktop text and controls. F-09 critical: Core forum templates render as shrunken desktop pages on mobile. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no container queries; the listing grid and side rail are merely scaled down at 360px. F-10 high: Dense components do not adapt to their available width. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focused forum links report outline: none; many navigation targets are only 25px high, and Lighthouse fails target-size. F-11 high: Forum controls are too small and keyboard focus is not visible. |
support-core-task-successclear-purpose-and-primary-action | issues | high | The mobile listing first viewport contains dense navigation, banners, tabs, a search strip, a large image grid and a side rail before a clear thread-reading action. F-12 medium: The next useful action is buried in competing content. |
support-core-task-successprimary-flow-completion | pass | medium | The public read journey completed from region selection to listing to a thread, with thread/list/home return controls available. |
support-core-task-successclear-system-state-and-recovery | issues | high | The unknown-route page says “ika error! click” and instructs users to use the browser Back button rather than offering a clear home/search/retry action. F-13 medium: The error state is cryptic and lacks a direct recovery action. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse reports LCP 4.2s, TBT 990ms, CLS 0.12, and performance 0.45. F-14 high: The representative thread is slow and unstable. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse reports CLS 0.12 and the image audit finds 90 of 100 images without both dimensions. F-15 medium: Late assets shift the page. |
be-fast-and-stableefficient-main-thread | issues | high | The trace records a 541.82ms long task and 503.94ms TBT; Lighthouse records 990ms TBT and a 22.5s time to interactive. F-16 high: Third-party scripting blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR records 249 requests and 2,357,529 transferred bytes, including 55 scripts and 153 images; Lighthouse flags cache, font, HTTP, dependency-tree and render-blocking insights. F-17 high: The thread has an excessive dependency and transfer footprint. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse flags unused CSS, unused JavaScript, unminified CSS/JS, legacy JavaScript and heavy main-thread work. F-18 high: The page ships avoidable unused and legacy code. |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility is 0.56 and fails image-alt, label, link-name, select-name, list/listitem, definition-list and frame-title; the runtime probe finds several untitled third-party iframes and 21 empty-name links. F-19 high: Accessible names and semantics are incomplete. |
be-inclusivesufficient-contrast | issues | high | Lighthouse fails the color-contrast audit on the thread, and the site has no contrast-preference adaptation. F-20 high: Text contrast fails WCAG checks. |
be-inclusivestructure-and-focus | issues | high | Lighthouse fails heading-order and tabindex; direct focus probes show outline: none on forum links. F-21 high: Heading structure and focus treatment are unreliable. |
be-inclusivelegible-text | issues | high | The 1100px desktop layout is scaled to roughly 32.7% at 360px, producing tiny body and control text in the listing and thread captures. F-22 critical: The core forum is unreadably small on mobile. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse fails meta-viewport and target-size, while the 360px captures preserve a desktop canvas rather than reflowing. F-23 high: Reflow and target sizing fail on the core templates. |
follow-best-practicesno-console-errors | pass | medium | Lighthouse did not report a console-error audit failure and the resource probe observed no HTTP >=400 resource entries on the representative thread. |
follow-best-practicessound-document-and-assets | issues | high | The image audit finds 90 missing dimensions, 43 oversized assets and 82 legacy-format images; Lighthouse fails unsized-images. F-24 high: Asset markup is unsized and inefficient. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse flags deprecations, inspector issues, BFCache blockers, third-party cookies, and missing source-map quality. F-25 medium: The page triggers platform hygiene diagnostics. |
be-discoverabletitle-and-description | pass | medium | Home and thread have descriptive, content-specific titles and meta descriptions; the raw HTML preserves both. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse fails meta-viewport and crawlable-anchors; the runtime probe reports 7 anchors without href and 21 linked elements with no discernible text. F-26 high: Mobile and link crawlability signals are incomplete. |
be-discoverablecanonical-and-indexing-signals | pass | medium | The thread returned 200, exposed a canonical without the tracking/back parameter, robots.txt did not broadly block indexing, and no accidental noindex was observed. |
be-discoverablestructured-and-shareable-metadata | issues | high | The thread exposes zero JSON-LD blocks; og:description contains HTML-like “<div><imgsrc=...>” text rather than a clean summary. F-27 medium: The article template lacks structured data and has malformed social description content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP and HSTS are absent; all 13 observed first-party cookies lack Secure, including bakusai_session. F-28 critical: Secure transport is undermined by missing defenses and insecure cookies. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe sees 30 third-party origins and known Google Analytics, DoubleClick and Rubicon trackers; HAR records 249 requests. F-29 high: The thread has an extensive tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | No permission prompt fired on load, but the delegated login probe finds password/OAuth options and no WebAuthn/passkey implementation. F-30 medium: Authentication does not offer a phishing-resistant passkey path. |
be-private-and-securedefensive-browser-policies | issues | high | Headers are missing clickjacking protection, Referrer-Policy, Permissions-Policy, CSP and HSTS. F-31 high: Browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | pass | medium | Discoverability reports 100% home and 89% thread raw/rendered content overlap with non-empty server HTML, so core reading survives without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | medium | Core menus, links, search and thread content loaded and remained operable in the exercised states; no blank shell or cut-off required overlay was observed. |
be-resilientoffline-and-installable | not-applicable | high | The audited public forum is a content MPA rather than an install-oriented app; no offline promise or app intent was found. |
be-resilientnetwork-and-http-failure-states | issues | high | The exercised 404 route renders “ika error! click” and relies on the browser back button instead of direct recovery choices. F-32 medium: Unknown-route recovery is not actionable. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | Bakusai is deliberately a Japanese-language local forum; the audited pages declare lang=ja and no multilingual or bidi product surface was identified. |
be-internationalisedlocale-aware-data | not-applicable | high | The scoped public read/login journey is single-locale Japanese and no user-selectable locale, currency, or cross-locale data flow was identified. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling, recurring-event, or cross-time-zone workflow appears in the exercised forum and authentication surfaces. |
be-trustworthyno-dark-patterns | pass | medium | The exercised browsing and login states showed no confirmshaming, forced continuity, preselected paid option, or consent wall; promotional recommendations were labelled PR where inspected. |
be-trustworthyhumane-error-handling | pass | medium | Empty login submission uses required native validation, moves focus to email, and prevents submission without clearing context. |
be-trustworthytrustworthy-input-assistance | pass | medium | The login email and password controls expose autocomplete=email and autocomplete=current-password, with visible recovery links. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | The login surface clearly separates OAuth and email methods, offers password/email recovery, account creation, privacy policy and terms, and makes no paid commitment. |
be-sustainableoptimised-assets | issues | high | Of 100 listing images, 82 use legacy formats, 43 are oversized, 40 lack srcset and 70 below-fold images are not lazy-loaded. F-33 high: Image delivery wastes bytes and decoding work. |
be-sustainableno-wasteful-work | issues | high | The thread loads 249 requests from 33 origins and later executes a 541.82ms long task, despite a simple text/article-and-comments core task. F-34 high: Background and third-party work is disproportionate. |
be-sustainablethird-party-and-media-budget | issues | high | HAR transfers 2.36MB, with 1.17MB of images and 882KB of scripts; 30 third-party origins participate. F-35 high: Third-party and media weight exceeds the value of the text thread. |
be-agent-readystructured-agent-capabilities | issues | medium | The public content is crawler-visible (89% raw/rendered overlap), but no WebMCP/agentic tool surface was found despite a visible “生成AI企業パートナー募集” link on the error template. F-36 low: Forum capabilities are not exposed as structured agent tools. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model feature is offered, and on-device inference is not required for the core browse/read/post journey. |
be-memory-efficientno-leak-under-repeated-interaction | issues | high | After 10 open/close cycles, heap nodes rise from 508,125 to 733,629 and self size from 29.22MB to 36.05MB; m.fn.init objects rise from 134 to 20,954 and closures from 24,540 to 64,725. Same-session used heap rises about 4.18MB while DOM elements stay at 3,076. F-37 high: Repeated stamp-modal use retains a large amount of JavaScript state. |
be-memory-efficientbounded-footprint | issues | medium | A fresh loaded thread heap contains 508,125 snapshot nodes and 29.22MB self size alongside 249 network requests and 55 scripts. F-38 medium: The baseline client footprint is heavy for a text thread. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | issues | medium | Across 10 open/close cycles the live DOM count stays 3,076, yet closures add 40,185 and m.fn.init wrappers add 20,820, consistent with retained listeners/wrappers rather than visible DOM growth. F-39 high: The modal interaction appears to accumulate handlers or retained wrappers. |
Provenance
Canonical report: results/atomic/reports/0543-bakusai_com.json
Report SHA-256: fc85643c5b4997c81065995de2bf433ccda4aa8aa76912508722d74b62ba6cfb
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/bakusai_com/2026-07-21T11-33-55-751Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/bakusai_com/2026-07-21T11-33-55-751Z
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.