Manifest position 492 · CrUX rank bucket 1000
https://www.cmoa.jp
Coverage complete
Coverage complete: all 58 catalog checks have conclusive outcomes. Representative coverage includes home, listing, detail, reader, search, login, registration, and recovery; checkout/payment completion, post-auth account management, adult surfaces, community, and every genre template were not covered because they require credentials/commitment or duplicate the sampled catalog templates.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-condition screenshot is visually identical to the light surface, and the CSS probe reports color-scheme: normal with a white body. F01 medium: The public catalog is light-only. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce the page reports zero active animations and scroll-behavior auto. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse failed color-contrast, while the contrast-preference screenshot remains unchanged from default. F16 high: Text and controls fail minimum contrast. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no authored view-transition rules; representative page changes are full abrupt swaps. F02 low: Navigation and content changes do not use authored view transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | DOM/CSS and runtime probes found no scroll-linked animation or scroll event-driven visual effect, so there is no main-thread scroll animation anti-pattern. |
implement-natural-interactionsphysical-gestures | pass | high | Representative catalog, detail, search, and reader paths use native scrolling/click activation and showed no custom pointer gesture that fights platform behavior. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The homepage is over 11,000 CSS px tall, while DOM/CSS inspection found no scroll-state container query or progress treatment. F03 low: Long pages provide static chrome with no scroll-position feedback. |
provide-guided-navigationanchored-positioning | issues | high | CSS places sideRightMenu absolutely at top:69px/right:14px and the account menu at fixed offsets; no anchor-name/position-anchor/position-try was found. F04 low: Header menus are manually positioned rather than anchored. |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs, explicit section headings, descriptive links, and highlighted genre tabs preserve location and next-step context. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Fresh-load screenshots across home, listing, detail and auth show no content-blocking modal or full-viewport interstitial. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The probe found zero dialog, popover, or details elements while DOM CSS shows class-toggled custom menu overlays and close controls. F05 medium: Custom div menus replace semantic dismissible primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | The first mobile-scaled viewport contains multiple navigation bars, a safety-search block, sidebar calls to action, and several stacked campaign banners before/alongside core books. F06 high: Dense promotional chrome crowds the actual catalog. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x800 emulation, layout metrics report clientWidth/innerWidth 1024 because the viewport is width=1024; screenshots show tiny desktop text and controls. F07 critical: Mobile receives a 1024px desktop layout scaled down to fit. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The probe found zero container rules; authored CSS repeatedly fixes the main shell and common regions at 990px. F08 medium: Reusable catalog components do not adapt at component level. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The probe counted 120 visible targets below 24px in one dimension, Lighthouse failed target-size, and the scaled mobile shell makes controls materially smaller. F09 high: Many controls are too small for touch. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, listing and detail clearly identify comics and expose search, free reading, sample, registration and purchase actions. |
support-core-task-successprimary-flow-completion | pass | high | The catalog-to-detail-to-free-reader journey completed; the reader redirected to a populated speedreader page with the correct title. |
support-core-task-successclear-system-state-and-recovery | pass | high | A deliberately missing route renders a detailed error state with back/retry advice and links to search, rankings, free content, help and top. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 16.3s, CLS 0.662, TBT 230ms and performance 0.33; an unconstrained desktop trace was faster (LCP 1.41s), showing the mobile/throttled risk. F10 critical: Lab Core Web Vitals are poor. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse reported CLS 0.662 and two layout shifts; the image audit found 31 homepage images without dimensions. F11 high: Late content causes major layout shift under mobile lab conditions. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reported 2.6s main-thread work and 1.3s JavaScript execution; the page loads 58 scripts. F12 high: JavaScript startup is heavy. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR confirms parser-inserted blocking jQuery, Axios and cookie scripts plus five stylesheets; Lighthouse estimates 1.03s render-blocking and 2,209KiB cache savings. F13 high: The critical path and caching are inefficient. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 862KiB unused JavaScript and 13KiB unused CSS; DOM inspection shows duplicate Axios, jquery.cookie, Yahoo and LINE/TikTok loaders. F14 high: The page ships substantial unused and duplicate client code. |
be-inclusivenames-roles-labels | issues | high | Lighthouse fails image-alt, input-image-alt and link-name; search inspection found unlabeled text/select fields, and the detail image audit found 74 images without alt. F15 high: Forms, links, and images have incomplete accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed color-contrast, while the contrast-preference screenshot remains unchanged from default. F16 high: Text and controls fail minimum contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse reports non-sequential headings and no main landmark; the page jumps from H2/H3 to H4 and uses many role-bearing fragments without a main region. F17 high: Document structure is incomplete for assistive navigation. |
be-inclusivelegible-text | issues | high | The 360px screenshots render a 1024px canvas at 0.3516 scale, reducing already-small 9px to 13px labels to a few physical pixels. F18 high: The scaled desktop layout makes text illegible on phones. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Homepage uses width=1024; the login viewport includes maximum-scale=1 and user-scalable=0; Lighthouse fails meta-viewport and target-size. F19 high: Viewport policy and fixed layout obstruct zoom and reflow. |
follow-best-practicesno-console-errors | issues | high | Lighthouse explicitly failed errors-in-console; HAR also records blocked/aborted marketing requests. F20 medium: The homepage logs browser errors. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 31 homepage and 42 detail images missing dimensions; Lighthouse also failed unsized-images. F21 medium: Image dimensions and asset structure are inconsistent. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed inspector-issues and BFCache with three failure reasons; the page also loads many legacy scripts and duplicated integrations. F22 medium: Chrome reports platform hygiene problems. |
be-discoverabletitle-and-description | pass | high | Homepage and product have unique descriptive titles and meta descriptions in raw and rendered HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable-anchors. This coexists with 100% raw-content coverage and hundreds of valid href links, so the defect is limited rather than a JS-shell failure. F23 medium: Some links are not crawlable despite strong server rendering. |
be-discoverablecanonical-and-indexing-signals | pass | high | Both tested public pages returned 200, expose matching canonicals, and are present in server-rendered HTML without accidental noindex. |
be-discoverablestructured-and-shareable-metadata | pass | high | Product includes Product, Book and Breadcrumb JSON-LD plus matching Open Graph title, description, URL and image. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and frame-ancestors are present, but HSTS and nosniff are missing; 27 of 29 cookies lack Secure and many use SameSite=None. F24 high: Transport policy and cookie attributes are weak. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker capture sees 42 third-party origins and Google, Facebook, DoubleClick, TikTok, Twitter, LINE, Yahoo and others; HAR records 328 third-party requests and about 5.09MB transferred. F25 high: Tracking and third-party collection are excessive on first load. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login screenshot exposes email/password and six social identity choices; inspected auth markup contains no WebAuthn/passkey signal. No permission prompt fired on load. F26 medium: Authentication offers password and federated identity but no phishing-resistant passkey path. |
be-private-and-securedefensive-browser-policies | issues | high | Headers lack HSTS, Referrer-Policy and nosniff; Permissions-Policy only grants client-hint features and CSP only sets frame-ancestors. F27 high: Browser-enforced defenses are incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 100% homepage and 95% product content coverage without JavaScript; core content is server-rendered. |
be-resilientresilient-runtime-behaviour | issues | high | Header dropdowns are class-toggled absolute boxes with fixed widths/offsets and no anchor fallback; the main site is fixed at 990px. F28 medium: Custom fixed-offset overlays are fragile at viewport edges. |
be-resilientoffline-and-installable | not-applicable | high | This is a public commerce/content site rather than an installed app; an offline catalog/reader was not an evidenced product requirement. |
be-resilientnetwork-and-http-failure-states | pass | high | The deliberately missing route presents a content-rich recovery screen with actionable destination links rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The Japanese pages consistently set html lang=ja and render in the expected LTR reading direction; no alternate locale was declared. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative Japanese pages expose no user-entered or dynamic locale-sensitive date, number, currency, duration, or calendar workflow to test. |
be-internationalisedtime-zone-correctness | not-applicable | high | No events, schedules, or user-facing time-zone-sensitive values occur in the representative paths. |
be-trustworthyno-dark-patterns | pass | high | The sampled pages show explicit free, sale, login and registration actions without confirmshaming, forced continuity, or a blocking consent wall. |
be-trustworthyhumane-error-handling | pass | high | The tested site error state explains likely causes and offers concrete recovery routes in neutral language. |
be-trustworthytrustworthy-input-assistance | issues | high | Search fields have empty autocomplete and no programmatic labels; homepage search explicitly disables autocomplete. F29 medium: Search and sign-in input assistance is incomplete. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Product pricing/free status and login/registration choices are visibly separated; the audit did not trigger a purchase or observe hidden continuity. |
be-sustainableoptimised-assets | issues | high | Of 100 homepage images, 99 use legacy formats, 35 are oversized, 53 lack srcset and 70 below-fold images are not lazy; images transfer 3.31MB. F30 high: Image delivery is wasteful. |
be-sustainableno-wasteful-work | issues | high | The load makes 330 requests and runs repeated vendor loaders, with Lighthouse estimating 862KiB unused JavaScript. F31 high: Background marketing work dominates a page view. |
be-sustainablethird-party-and-media-budget | issues | high | Tag Manager/gtag transfer more than 500KB, TikTok variants over 300KB, Facebook 175KB, amid 42 third-party origins; total load is 5.13MB. F32 high: Third-party script cost is disproportionate to visible user value. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent was available; the emerging WebMCP capability is treated as an opportunity, not a requirement. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model feature is part of the observed product intent, so on-device inference is not required. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten real safe-search state changes, the post heap was smaller than baseline (340,766 vs 497,714 nodes; 18.3MB vs 28.9MB self size), with no retained-growth signal. |
be-memory-efficientbounded-footprint | pass | high | Heap snapshots measured a bounded 18.3MB to 28.9MB self-size range for this image-heavy catalog; no monotonic growth was observed. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The repeated interaction did not increase total heap/node population; this provides no evidence of accumulating detached DOM/listeners, though constructor-level confidence is medium. |
Provenance
Canonical report: results/atomic/reports/0492-www_cmoa_jp.json
Report SHA-256: f384e3fd92b0c9bd9084e740199365386a56c27dd108ace4600e2aba7088a894
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_cmoa_jp/2026-07-21T03-57-38-065Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_cmoa_jp/2026-07-21T03-57-38-065Z
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.