Manifest position 249 · CrUX rank bucket 1000
https://gamewith.jp
Coverage complete
Atomic coverage complete: all 58 catalog checks have conclusive outcomes.
Attempts
2 / 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-condition screenshot remains the same light page and the stylesheet probe found no prefers-color-scheme handling. F-001 medium: No system-driven dark theme |
respect-user-preferencesrespects-reduced-motion | pass | medium | Under prefers-reduced-motion: reduce, document.getAnimations() returned no active animations, so no non-essential motion persisted. |
respect-user-preferencesrespects-contrast | issues | high | No prefers-contrast/forced-colors CSS was found, and Lighthouse found 248 insufficient-contrast nodes. F-002 high: Contrast preferences and baseline contrast are not supported |
implement-natural-interactionsview-transitions | issues | medium | No view-transition CSS or API usage was present; navigation between the sampled MPA routes is an abrupt full-document swap. F-003 low: Route changes are abrupt |
implement-natural-interactionsscroll-driven-animations | pass | medium | No scroll-linked animation surface or scroll-driven animation was observed, so the page does not use a main-thread scroll animation anti-pattern. |
implement-natural-interactionsphysical-gestures | pass | medium | The sampled core controls use ordinary links, buttons and scrolling; no custom gesture interaction that fights platform behavior was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The long home and article templates have static chrome and no scroll-state query, progress indicator, or position-aware header behavior. F-004 low: Long pages provide no scroll-position feedback |
provide-guided-navigationanchored-positioning | pass | medium | No tooltip/menu requiring anchor positioning was found on sampled core paths; the consent surface is viewport-modal rather than anchored UI. |
provide-guided-navigationdirects-attention | pass | high | The article and detail pages expose breadcrumbs, ordered headings, and clear related-content navigation that preserve orientation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | A consent interstitial blocks all content on every fresh page load before interaction. F-005 high: Consent interstitial blocks every fresh visit |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The blocking consent surface is a custom div with role=dialog rather than a native dialog; rejection requires opening Manage options. F-006 medium: Consent UI is a custom dialog implementation |
maximize-content-reduce-noisereduced-chrome | issues | high | Ads, fixed-width sidebars, dense navigation, rankings and banners dominate the viewport and visually compete with editorial content. F-007 high: Advertising and dense chrome crowd out content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The page declares viewport width=1580; Chrome renders a 1440 CSS-pixel layout scaled to 25%, with 140px horizontal overflow and unreadably tiny content. F-008 critical: Mobile receives a scaled desktop canvas |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | No @container/container-type usage was found and sampled templates hard-code viewport widths of 1000 or 1580 instead of adapting components. F-009 high: Components do not adapt to available space |
adapt-to-the-form-factorinput-modality-aware | issues | high | The first focusable link computed outline-style none and zero width; many visible header links are only 16–24px high, below comfortable touch size. F-010 high: Keyboard focus and touch target support are weak |
support-core-task-successclear-purpose-and-primary-action | pass | high | The home, article, game detail, search and login pages have descriptive Japanese titles/headings and recognizable navigation to core content. |
support-core-task-successprimary-flow-completion | pass | medium | Game discovery links lead to detail/article pages and the login path provides email/password plus social sign-in controls; no auth wall blocks public content. |
support-core-task-successclear-system-state-and-recovery | issues | medium | The login fields are not required and expose no aria-invalid or browser validation message on blank submission, weakening actionable recovery. F-011 medium: Login errors are not surfaced early or accessibly |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse mobile reports LCP 5.7s, TBT 420ms, Speed Index 12.1s and TTI 20.1s; the independent trace reports LCP 4.15s. F-012 high: Loading performance misses user-centric targets |
be-fast-and-stablevisual-stability | pass | high | Observed CLS was 0.0001 in the layout capture and 0.042 in Lighthouse, both in the good range. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reports 4.9s main-thread work, 1.6s JavaScript execution and 420ms TBT; the trace recorded long tasks. F-013 high: Main-thread work is excessive |
be-fast-and-stableefficient-resource-delivery | issues | high | The load transferred 3.62MB over 192 requests; parser-inserted jQuery/ad/basic scripts and CSS are render-blocking candidates, with 2.56s estimated render-blocking savings. F-014 high: The critical delivery path is heavy and blocking |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 660KiB unused JavaScript and 44KiB unused CSS, while ad/analytics bundles dominate script transfer. F-015 high: Large amounts of unused code ship on first load |
be-inclusivenames-roles-labels | issues | high | The header information image lacks alt text, and the email/password controls have no associated labels or ARIA labels. F-016 high: Some content and login controls lack accessible names |
be-inclusivesufficient-contrast | issues | high | Lighthouse found 248 contrast failures, including 12px #929292 text on white at 3.11:1. F-017 high: Widespread text contrast failures |
be-inclusivestructure-and-focus | issues | high | The consent manager injects several additional H1 elements and the focused logo link has no visible outline or box shadow. F-018 high: Focus visibility and heading structure are disrupted |
be-inclusivelegible-text | issues | high | The forced desktop canvas is scaled to 25% on a 360px device, making navigation and article text too small to read comfortably. F-008 critical: Mobile receives a scaled desktop canvas |
be-inclusivezoom-reflow-targets-and-media | issues | high | Fixed width viewport metadata prevents normal mobile reflow, and numerous navigation targets are only 16–30px high. F-008 critical: Mobile receives a scaled desktop canvas F-010 high: Keyboard focus and touch target support are weak |
follow-best-practicesno-console-errors | issues | medium | Lighthouse captured SyntaxError: Identifier tabSelector has already been declared on the home page. F-019 medium: A production JavaScript syntax error is logged |
follow-best-practicessound-document-and-assets | issues | high | Although doctype/charset are valid, 99 of 100 images lack explicit dimensions, 99 use legacy formats, and Lighthouse reports an unsized image. F-020 high: Images lack robust sizing and modern delivery |
follow-best-practicesbrowser-platform-hygiene | issues | medium | Lighthouse reports a deprecated API warning, third-party-cookie issues and a DevTools inspector issue. F-021 medium: Deprecated and inspector issues remain |
be-discoverabletitle-and-description | pass | high | Home, article, game detail, search and login pages expose descriptive titles; public content pages include meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found 19 non-crawlable anchors and the viewport meta uses fixed widths rather than device-width. F-022 high: Interactive tabs use non-crawlable JavaScript URLs |
be-discoverablecanonical-and-indexing-signals | pass | high | Public pages return 200, expose canonical URLs, robots.txt and sitemap.xml are reachable, and no accidental noindex signal was observed. |
be-discoverablestructured-and-shareable-metadata | pass | high | The article provides NewsArticle and BreadcrumbList JSON-LD plus complete Open Graph title, URL, image and description matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and HSTS are present, but CSP only declares frame-ancestors; 12 cookies lack Secure and many use SameSite=None. F-023 high: Cookie and CSP protections are weak |
be-private-and-securedata-minimisation-and-third-parties | issues | high | A fresh load contacted 34 third-party origins and 8 known tracker domains; 190 of 192 HAR requests were classified cross-origin and 3.47MB was transferred cross-origin. F-024 high: Tracking begins with an extensive third-party footprint |
be-private-and-securein-context-permissions-and-modern-auth | issues | medium | The sampled login supports password and social providers but exposes no site passkey/WebAuthn flow; no permission prompt fired on load. F-025 medium: Login offers no phishing-resistant passkey option |
be-private-and-securedefensive-browser-policies | issues | high | X-Content-Type-Options, Referrer-Policy and Permissions-Policy are absent; HSTS max-age is only one day, and cookie posture is weak. F-026 high: Defensive response policies are incomplete |
be-resilientprogressive-enhancement | pass | high | Raw server HTML is 2.25MB, is not a JS shell, retains title/H1/description, and contains 81% of rendered content tokens. |
be-resilientresilient-runtime-behaviour | pass | medium | Sampled MPA routes loaded usable server-rendered content, the consent manager remained in viewport, and no blank runtime shell occurred. |
be-resilientoffline-and-installable | not-applicable | high | GameWith is a public editorial/content website rather than an installed app; no manifest/offline app promise is needed for its primary reading task. |
be-resilientnetwork-and-http-failure-states | pass | medium | An invalid representative URL returns an intentional HTTP 404 response rather than a misleading 200 shell. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | The audited site is deliberately Japanese-language and Japan-market focused; no locale switcher, multi-currency, cross-zone scheduling, or international audience promise was observed. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited site is deliberately Japanese-language and Japan-market focused; no locale switcher, multi-currency, cross-zone scheduling, or international audience promise was observed. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited site is deliberately Japanese-language and Japan-market focused; no locale switcher, multi-currency, cross-zone scheduling, or international audience promise was observed. |
be-trustworthyno-dark-patterns | issues | high | The consent wall offers a one-click Consent action but no equivalent one-click Reject action, while a fresh load already contacts extensive ad/tracker infrastructure. F-027 high: Consent choices are asymmetrical |
be-trustworthyhumane-error-handling | issues | medium | Email/password inputs are not required and blank submission produced no browser validation message or aria-invalid state. F-011 medium: Login errors are not surfaced early or accessibly |
be-trustworthytrustworthy-input-assistance | issues | high | Email and password fields omit autocomplete=username/current-password tokens and lack explicit labels. F-028 high: Sign-in fields omit autofill semantics |
be-trustworthysafe-commercial-and-account-flows | issues | medium | The account flow relies on passwords/social providers and presents no passkey option; form controls also lack modern autofill tokens. F-025 medium: Login offers no phishing-resistant passkey option F-028 high: Sign-in fields omit autofill semantics |
be-sustainableoptimised-assets | issues | high | 99/100 images are legacy formats, 24 lack srcset, 9 are oversized, and Lighthouse estimates 733KiB image-delivery savings. F-029 high: The image pipeline wastes bytes |
be-sustainableno-wasteful-work | issues | high | The page performs 192 requests, ships 660KiB estimated-unused JavaScript and executes large advertising/analytics bundles before a core task. F-030 high: Background and unused work is excessive |
be-sustainablethird-party-and-media-budget | issues | high | Third-party/cross-origin delivery accounts for 190 requests and 3.47MB, including ad-tech, analytics and consent infrastructure disproportionate to a text-heavy homepage. F-031 high: Third-party cost is disproportionate to content value |
be-agent-readystructured-agent-capabilities | issues | low | The site is content-rich and agent-relevant, but exposes no WebMCP/agentic tool interface for search or game discovery; agents must scrape links/forms. F-032 low: Game search is not exposed as a structured agent capability |
be-agent-readyon-device-inference | not-applicable | high | No user task observed in the sampled pages requires on-device generation or summarisation; omitting built-in AI is not a quality failure here. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 cycles self size rose about 0.90MB (1.2%) and closures rose by only 3; this single comparison does not show unbounded retained growth. |
be-memory-efficientbounded-footprint | issues | medium | A text-heavy homepage retains about 76.7MB self size across 1.29M heap nodes, a large footprint consistent with extensive ad/analytics machinery. F-033 medium: Homepage memory footprint is large |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appears among the top retained constructors, closures remained effectively flat (34,836 to 34,839), and the repeated cycle did not show listener-like growth. |
Provenance
Canonical report: results/atomic/reports/0249-gamewith_jp.json
Report SHA-256: 1cf9ab0c32d76529f5e217a14b397cad093af27ad0505e8d4045b676c0e1ad46
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/gamewith_jp/2026-07-26T01-04-39-064Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/gamewith_jp/2026-07-26T01-04-39-064Z
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.