Manifest position 398 · CrUX rank bucket 1000
https://bbs.animanch.com
Coverage complete
All 58 atomic checks received conclusive outcomes. Category, settings, contact, sitemap, and search blocks are recorded as site findings rather than audit blockers because homepage and thread templates remained inspectable.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The prefers-color-scheme: dark screenshot is pixel-identical to the light screenshot; the page instead exposes a manual toggle. F01 medium: System dark-mode preference is ignored |
respect-user-preferencesrespects-reduced-motion | pass | high | No animations or non-zero transitions were present while prefers-reduced-motion: reduce matched. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse measured link contrast as low as 3.46:1 on the green notice and 4.19:1 for dark-theme tabs, below 4.5:1. F02 medium: Some controls and links do not preserve sufficient contrast |
implement-natural-interactionsview-transitions | issues | high | The structure probe found no view-transition CSS and the page uses ordinary MPA navigation and Bootstrap tab swaps. F03 low: Navigation and tab state swaps are abrupt |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation, parallax, reveal, or scrollytelling surface exists on the representative pages. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No custom gesture-driven interaction exists; forum navigation uses native links and controls. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The mobile layout is 28,788px tall, while screenshots show static header/navigation and the DOM contains no scroll-state/container-query feature. F04 low: Very long listing pages provide no scroll-position feedback |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or viewport-edge menu requiring anchored positioning was found. |
provide-guided-navigationdirects-attention | pass | high | Thread pages provide TOP and category breadcrumbs, and the homepage labels each list state with visible tabs. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Initial desktop and mobile captures showed content immediately with no modal, consent wall, or interstitial obscuring it. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No modal, disclosure, tooltip, or transient overlay was present on the representative successful pages. |
maximize-content-reduce-noisereduced-chrome | pass | high | The first viewport is dominated by recommended threads, notice text, and listing navigation rather than decorative application framing. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, scrollWidth and clientWidth were both 360, horizontal overflow was 0, and a viewport meta tag was present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The live CSS probe found zero @container rules despite cards/navigation being reused in narrow and wide contexts. F05 low: Repeated components adapt only at page level |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found 18 of the first 30 focusable controls below 44px in one dimension; the category link reported outline-style:none and no box shadow. F06 medium: Many controls are too small and one menu loses visible keyboard focus |
support-core-task-successclear-purpose-and-primary-action | pass | high | The title, recommended threads, category/list tabs, search control, and thread cards make the forum purpose and next actions apparent. |
support-core-task-successprimary-flow-completion | issues | high | Submitting the visible search for ドラゴンボール redirected to /search/... and produced “Sorry, you have been blocked” rather than results. F07 high: The primary search journey is blocked by Cloudflare |
support-core-task-successclear-system-state-and-recovery | issues | high | The search result is a generic Cloudflare block whose only recovery is to email the site owner; it does not preserve the query or offer retry/back-to-results. F08 high: Blocked search offers no in-product recovery |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 3.3s, TBT 320ms, Speed Index 13.6s, and time-to-interactive 33.6s; the trace also measured FCP/LCP 4.50s. F09 high: Load responsiveness misses the good performance range |
be-fast-and-stablevisual-stability | pass | high | Observed CLS was 0 in the mobile layout primitive and approximately 0.00008 in Lighthouse. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 320ms TBT and 33.6s time-to-interactive, despite the shorter native trace observing only 2.08ms TBT in its window. F10 medium: Third-party work blocks interactivity |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR recorded 663 requests and 4.19MB transferred, including 557 image requests and 545 HTTP 403 responses; parser-inserted jQuery/Bootstrap and four stylesheets are candidate blockers. F11 high: The listing performs hundreds of wasteful requests |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 529KiB unused JavaScript and 22KiB unused CSS, including 93% of Bootstrap CSS and substantial ad/analytics code. F12 medium: Large unused third-party bundles dominate the page |
be-inclusivenames-roles-labels | issues | high | The image audit found 100/100 images without alt; Lighthouse also failed image-alt and found an unlabeled upload input, while DOM probes found unlabeled search controls. F13 high: Images and form controls lack accessible names |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured 3.46:1 for notice links and 4.19:1 for dark-theme tab links, below the 4.5:1 text minimum. F14 medium: Link and tab colors fail WCAG contrast |
be-inclusivestructure-and-focus | issues | high | The homepage probe found no headings and no <main>; the category control computed outline:none and box-shadow:none when focused. F15 high: The homepage lacks a heading/main structure and one menu has no focus indicator |
be-inclusivelegible-text | issues | high | The 360px screenshot shows 更新順 and シャッフル split vertically into individual characters, making navigation slow to scan. F16 medium: Mobile tab labels wrap one character per line |
be-inclusivezoom-reflow-targets-and-media | issues | high | The focus/geometry probe found 18 of 30 sampled controls below 44px in one dimension, including 17px-high utility links. F17 medium: Small touch targets undermine reflow usability |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed errors-in-console with repeated CORS failures from Geniee and GMO advertising endpoints. F18 medium: Advertising code emits repeated console errors |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 100 images without dimensions; screenshots show the logo broken, and the HAR contains 545 HTTP 403 responses, mostly thumbnails. F19 medium: Image assets are broken and unsized |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported four deprecation warnings, inspector cookie issues, and five BFCache failure reasons including cache-control:no-store. F20 medium: Deprecated APIs and BFCache blockers remain |
be-discoverabletitle-and-description | pass | high | Homepage and thread pages expose descriptive titles and meta descriptions in server-rendered HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found an <a onclick="location.reload()"> without href, and the page declares meta robots index,nofollow despite a public forum; viewport metadata is present. F21 medium: Some navigation is not crawlable and all page links are marked nofollow |
be-discoverablecanonical-and-indexing-signals | issues | high | The homepage has no canonical URL, declares index,nofollow, and /sitemap.xml returned a Cloudflare block, although robots.txt allows general search crawling. F22 medium: Homepage indexing signals are inconsistent |
be-discoverablestructured-and-shareable-metadata | issues | high | Open Graph metadata exists, but the homepage probe found no JSON-LD and the thread exposes no DiscussionForumPosting schema. F23 low: Forum threads lack structured discussion metadata |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but PHPSESSID lacks Secure and HttpOnly; seven other cookies lack Secure. CSP and nosniff are missing, and HSTS is effectively disabled with max-age=0. F24 critical: Session and analytics cookies are insecure and core security headers are absent |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe found 41 third-party origins and 12 known tracker domains; the HAR measured 99 third-party requests and 1.19MB transferred. F25 high: The page contacts an excessive tracking ecosystem |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No authentication surface or browser permission request was present on the representative public forum pages. |
be-private-and-securedefensive-browser-policies | issues | high | The header probe found no CSP/frame-ancestors or X-Frame-Options, no Referrer-Policy, no Permissions-Policy, and HSTS max-age=0. F26 high: Browser-enforced defensive policies are mostly absent |
be-resilientprogressive-enhancement | pass | high | Raw server HTML contained 100% of rendered content tokens, with title and description intact; the page is not a JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Successful homepage and thread loads use ordinary links/forms and showed no cut-off overlay or fragile custom top-layer UI. |
be-resilientoffline-and-installable | not-applicable | high | This public MPA discussion forum is not presented as an installable app; no offline editing or app-like promise was identified. |
be-resilientnetwork-and-http-failure-states | issues | high | Category, settings, contact, sitemap, and an ordinary search were intermittently replaced by Cloudflare “Sorry, you have been blocked” pages. F27 high: Network/security failures replace the site with an unrecoverable generic page |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | The site is deliberately Japanese-language and Japan-locale community content with no locale switch, currency, scheduling, or cross-time-zone workflow in the audited scope. |
be-internationalisedlocale-aware-data | not-applicable | high | The site is deliberately Japanese-language and Japan-locale community content with no locale switch, currency, scheduling, or cross-time-zone workflow in the audited scope. |
be-internationalisedtime-zone-correctness | not-applicable | high | The site is deliberately Japanese-language and Japan-locale community content with no locale switch, currency, scheduling, or cross-time-zone workflow in the audited scope. |
be-trustworthyno-dark-patterns | pass | high | No forced continuity, confirmshaming, disguised action, subscription pressure, or nagging consent wall appeared in the audited public flows. |
be-trustworthyhumane-error-handling | pass | high | The visible search input uses native required validation; no premature custom invalid state appeared before interaction. |
be-trustworthytrustworthy-input-assistance | issues | high | The DOM probe found empty autocomplete values and no labels on search and upload controls. F28 low: Form controls omit useful input metadata |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication, account-management, or payment flow exists in the audited public scope. |
be-sustainableoptimised-assets | issues | high | The image audit found 99 below-fold images without lazy loading and all 100 sampled images without dimensions; the HAR recorded 557 image requests and 2.96MB transferred. F29 high: Hundreds of thumbnails are fetched eagerly without intrinsic sizing |
be-sustainableno-wasteful-work | issues | high | The HAR recorded 663 requests with 545 HTTP 403 responses, while Lighthouse reported repeated advertising CORS failures. F30 high: Failed advertising and thumbnail work consumes resources without user value |
be-sustainablethird-party-and-media-budget | issues | high | The HAR attributes 1.19MB and 99 requests to third parties; tracker evidence lists 41 third-party origins and 12 known trackers. F31 high: Third-party cost is disproportionate to a text forum |
be-agent-readystructured-agent-capabilities | not-applicable | high | No developer intent for agent-executed forum capabilities is evident; robots.txt explicitly restricts several AI crawlers, so absence of WebMCP is not penalised. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model task is promised by this conventional public forum, so built-in inference is optional rather than required. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 dark-mode/tab interaction cycles, heap nodes decreased from 509,665 to 507,687 and self size decreased from 27,511,079 to 27,456,329 bytes. |
be-memory-efficientbounded-footprint | pass | high | The loaded long listing used about 27.5MB heap self-size with 3,347 DOM elements; substantial but bounded for the 21k-28k px feed and ad integrations. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | No Detached* constructor appeared in either heap summary and repeated interaction reduced total nodes/edges rather than accumulating them. |
Provenance
Canonical report: results/atomic/reports/0398-bbs_animanch_com.json
Report SHA-256: c69c9c312767ba9f8f4710051235db74189dc83f8d983a4d965d5465d1ffa175
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/bbs_animanch_com/2026-07-26T08-19-26-105Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/bbs_animanch_com/2026-07-26T08-19-26-105Z
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.