Manifest position 906 · CrUX rank bucket 1000
https://rx.sp.mbga.jp
Coverage complete
Atomic coverage complete. Entry URL redirects by client/UA to Mobage portal variants; representative guest homepage, listing, login and missing-route states were inspected.
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 default and dark-emulated 360px screenshots are pixel-identical; the computed root color-scheme is “normal”. F01 medium: The public UI is hard-coded light and does not honor the user’s dark-theme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | No animations were active under reduced-motion emulation, so no non-essential motion persisted. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse measured 2.86:1 for 11px blue footer links against #d0d0d0. F02 high: Essential footer links do not remain sufficiently distinct at normal contrast, so higher-contrast needs are not met. |
implement-natural-interactionsview-transitions | issues | high | DOM/script inspection found no authored View Transition use; navigation is conventional full-document links and no animations were active. F03 low: Route changes are abrupt rather than preserving spatial continuity. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation exists on the representative pages, so there is no implementation technique to evaluate. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No gesture-driven control was present in the guest browsing and login surfaces. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The page is 2,882px tall, while screenshots and DOM show static header/chrome and no active scroll-linked behavior. F04 medium: The long homepage provides no position-aware navigation or scroll progress. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover or anchored menu was exposed on the audited guest paths. |
provide-guided-navigationdirects-attention | pass | high | Direct inspection found the expected outcome on all representative paths without a contradictory signal. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Screenshots show content immediately; the small error toast does not obscure the primary content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No user-triggered overlay or disclosure primitive appeared on the audited paths. |
maximize-content-reduce-noisereduced-chrome | pass | high | The mobile first viewport prioritises game/news content with compact global chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360px viewport the listing had no viewport meta, a 980px layout viewport and 0.367 scale; text and controls are tiny. F05 high: A representative listing is served as a desktop-only 980px canvas and scaled down on phones. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The homepage probe found zero container rules; desktop cards stretch to 780px rows, while the listing falls back to a fixed desktop canvas on mobile. F06 medium: Reusable catalogue components do not adapt cleanly across available space. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus/target probe measured login and registration at 45×31px, primary search links at 38px high, and category links at 32px high. Keyboard outlines were visible. F07 medium: Several common links are below the recommended touch-target size. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The H1 and first viewport clearly identify a games portal and expose new-game, ranking and genre routes. |
support-core-task-successprimary-flow-completion | pass | high | The guest browse journey reached a populated, paginated new-games listing; the separate login journey reached a cancellable form. |
support-core-task-successclear-system-state-and-recovery | issues | high | Both desktop and mobile screenshots show “システムエラーが発生しました。” with no cause, retry, dismissal or recovery action. F08 high: Guest users receive a generic, unactionable system error on the homepage. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 4.8s and FCP 4.1s; the raw trace measured LCP/FCP 3.33s with no blocking tasks. F09 high: Cold-load rendering is slow despite a quiet main thread. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observation measured CLS 0.0000375 and all inspected images declared dimensions. |
be-fast-and-stableefficient-main-thread | pass | high | Trace and layout observers recorded zero long tasks and 0ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR identified three VeryHigh parser-inserted stylesheets and two synchronous parser scripts; its hygiene section flags major sprites, JS, CSS and font responses without useful cache headers. F10 medium: Parser-blocking resources and weak cache delivery delay the first view. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 42KiB unused JS and 35KiB unused CSS; HAR shows near-duplicate 181KiB sprite transfers from sp.mbga.jp and ava-a.sp.mbga.jp. F11 medium: The page ships avoidable unused code and duplicate sprite cost. |
be-inclusivenames-roles-labels | issues | high | The homepage has no landmarks and a visible menu button without text; the login email/password inputs rely on placeholders and have no associated labels; the image probe found 44 images without alt in the rendered DOM, many hidden drawer assets. F12 high: Important controls and form fields lack robust accessible names and labels. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reported 2.86:1 contrast for multiple 11px footer links where 4.5:1 is required. F13 high: Footer text contrast fails WCAG minimums. |
be-inclusivestructure-and-focus | issues | high | The DOM probe found no main/nav/header/footer landmarks; Lighthouse failed landmark-one-main; numerous anchors use javascript:void(0). Focus rings are visible, but structure is weak. F14 high: The homepage lacks navigation/main landmarks and includes many script-only pseudo-links. |
be-inclusivelegible-text | pass | high | Homepage body text is readable at the mobile viewport with clear row separation; listing legibility failures are recorded under reflow/zoom. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Two homepage viewport tags and the login viewport specify maximum-scale=1,user-scalable=no; the listing has no viewport meta and renders at 980 CSS pixels on a 360px device. F15 high: User zoom is disabled and one core template does not reflow. |
follow-best-practicesno-console-errors | pass | high | Lighthouse reported no browser console errors and no deprecated API audit failures on the homepage load. |
follow-best-practicessound-document-and-assets | pass | high | Homepage DOM has an HTML doctype and UTF-8 metadata; image audit found dimensions on all 45 images and layout stayed stable. |
follow-best-practicesbrowser-platform-hygiene | issues | high | The listing loads jQuery 1.7.2 and Modernizr 2.5.3, uses HTTP canonical/assets after redirect, and the homepage contains many javascript:void(0) anchors. F16 medium: Legacy platform choices create fragile navigation and maintenance risk. |
be-discoverabletitle-and-description | pass | high | Homepage and listing DOMs contain descriptive, route-specific titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable-anchors for javascript:void(0) links; the listing has no viewport meta and is scaled from 980px. F17 medium: A substantial set of navigation actions is not crawlable, and the listing is not mobile-friendly. |
be-discoverablecanonical-and-indexing-signals | issues | high | The rendered homepage has no canonical; the listing canonical is HTTP www.mbga.jp; requests to sitemap.xml resolved to generic Mobage HTML rather than a sitemap. F18 medium: Canonical and sitemap signals are inconsistent across hosts and templates. |
be-discoverablestructured-and-shareable-metadata | pass | high | The homepage exposes Open Graph metadata and WebSite semantics consistent with its visible portal content. |
be-private-and-securesecure-transport-and-headers | issues | high | All three guest cookies lack Secure and use SameSite=None; the document lacks CSP, HSTS and X-Content-Type-Options. F19 high: Transport is HTTPS, but cookies and response headers are not safely hardened. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Network evidence includes ad-a.sp.mbga.jp and an analytics JSON-RPC call; the login DOM embeds an analytics endpoint/tracking cookie plus reCAPTCHA/Yahoo tags. F20 medium: Guest loads include advertising/analytics collection without an evident minimisation explanation in the audited path. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login page offers password and social providers; the probe found no authored WebAuthn use, despite browser support. No permission prompt fired on load. F21 medium: Authentication remains password-centric and does not expose a phishing-resistant passkey option. |
be-private-and-securedefensive-browser-policies | issues | high | Header inspection found no frame protection, Referrer-Policy or Permissions-Policy in addition to missing CSP/HSTS/nosniff. F22 high: Browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 86% of rendered content in raw HTML, a raw H1/title/description and no JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | The audited listing and login pages rendered usable server content without cut-off overlays; no fragile async overlay was exposed. |
be-resilientoffline-and-installable | not-applicable | high | This server-rendered games portal is intrinsically online and does not present itself as an installable application; offline installability is contextual. |
be-resilientnetwork-and-http-failure-states | issues | high | A deliberately unknown URL loaded generic Mobage content with no not-found explanation; the homepage also emitted an unactionable system error. F23 medium: Failure routing does not produce a clear recoverable state. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The login probe found an empty html lang value while the visible interface is Japanese; the homepage correctly uses lang=ja. F24 medium: The authentication document does not identify its Japanese language. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative public paths displayed no dates, currencies or locale-sensitive numeric data. |
be-internationalisedtime-zone-correctness | not-applicable | high | No time-zone-sensitive events or times appeared on the representative paths. |
be-trustworthyno-dark-patterns | pass | high | The inspected guest homepage and login show direct labels, visible login cancellation and no consent wall, confirmshaming or forced continuity. |
be-trustworthyhumane-error-handling | issues | high | Email and password fields are not required, have no aria-invalid/aria-describedby relationship, and expose no persistent labels; the homepage error is generic and unrecoverable. F25 medium: The login form lacks client-visible validation semantics before reCAPTCHA submission. |
be-trustworthytrustworthy-input-assistance | issues | high | Email uses autocomplete="on" and password has no autocomplete token; neither uses username/current-password. F26 medium: Login fields do not use purpose-specific autofill tokens. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No purchase/subscription/account-management flow was entered; login cancellation and alternatives were visible, but commercial commitments were outside guest scope. |
be-sustainableoptimised-assets | issues | high | Image inspection found 39 legacy-format images, no modern-format images and 16 below-fold images without lazy loading; images account for 1,001,309 transferred bytes. F27 medium: The page relies heavily on legacy PNG/GIF assets and eagerly loads below-fold images. |
be-sustainableno-wasteful-work | pass | high | The load produced no long tasks and only one XHR/fetch; no autoplay media or continuing animation was present. |
be-sustainablethird-party-and-media-budget | issues | high | HAR recorded 67 requests and 1,160,179 transferred bytes; five large PNG sprites total roughly 767KB and 61 requests were classified off the requested origin. F28 medium: Image sprites and multi-origin delivery dominate a 1.16MB guest load. |
be-agent-readystructured-agent-capabilities | not-applicable | high | This public catalogue exposes crawlable content but no declared agent-facing transactional capability; emerging WebMCP tooling is not required for this scope. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model task is part of the audited guest browsing/login experience. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten representative scroll down/up cycles, DOM nodes fell 812→810; heap self size changed only 4,995,028→5,041,275 bytes (~0.9%). |
be-memory-efficientbounded-footprint | pass | medium | Baseline heap summary was proportionate for the page: 91,409 heap nodes and 4.995MB self size; in-page used heap was 1.31MB. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Repeated scrolling did not increase DOM count (812→810) or heap node count (91,409→89,493); no accumulation signal was observed. |
Provenance
Canonical report: results/atomic/reports/0906-rx_sp_mbga_jp.json
Report SHA-256: e08c41957aa391125864e2dd643d5fed8dfdaf828751b8e10222a7750d54a627
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/rx_sp_mbga_jp/2026-07-23T18-36-51-968Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/rx_sp_mbga_jp/2026-07-23T18-36-51-968Z
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.