Manifest position 186 · CrUX rank bucket 1000
https://hiroba.dpoint.docomo.ne.jp
Coverage complete
Coverage-complete audit across five representative public templates/journeys; authenticated post-login and transactional completion were not covered.
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 normal and dark-emulated information screenshots are pixel-equivalent in palette, and the platform probe reports computed colorScheme "normal". F01 medium: The public site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, the probe still found two running 1,200ms badge-balloon animations and an initialized looping Splide carousel. F02 medium: Motion continues when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | high | The forced-colors/high-contrast capture preserves visible text, borders, links and controls across the information template. |
implement-natural-interactionsview-transitions | issues | high | The 4-second navigation recording from an information page to the guide shows a conventional full document replacement, with no authored view-transition treatment detected. F03 low: Cross-document navigation swaps abruptly. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked parallax, scrollytelling or reveal interaction was present on the representative templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull-to-reveal, reorder or other gesture-driven component was present in the audited journeys. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Desktop and narrow captures retain persistent global navigation and location context; no scroll-obscuring chrome was observed. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or edge-positioned transient menu requiring an anchor-positioning judgement was observed. |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs, current navigation context, blue archive arrows and visible focus outlines clearly indicate location and focus movement. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The initial desktop screenshot is dimmed behind a large centered “本日のイチオシ” modal, while a second floating ad also covers the lower-left content. F04 high: A promotion blocks the primary content on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | Both promotional overlays are native DIALOG elements with explicit aria-labelled dismiss buttons. |
maximize-content-reduce-noisereduced-chrome | issues | high | The home and category screenshots show a search header, keyword chips, global navigation, carousel/promotional cards, a fixed bottom navigation and overlapping ad treatments competing simultaneously. F05 medium: Dense promotional chrome overwhelms the content and task hierarchy. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At an outer viewport of 390px, the probe reports innerWidth and visualViewport width of 1,048px because the viewport meta is width=1024; the category screenshot is a tiny desktop canvas rather than reflowed mobile UI. F06 high: Mobile visitors receive a scaled-down 1,024px desktop layout. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The platform probe found zero @container rules, while the 390px category capture preserves multi-column desktop cards and sidebars by shrinking the whole page. F07 medium: Components do not adapt to their available container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The fixed 1,024px canvas is scaled to 37% on a 390px device; although desktop CSS target rectangles can be 32–44px, their effective visual size is substantially smaller in the mobile screenshot. F08 high: Effective mobile controls and text are too small after page-wide scaling. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The guide clearly explains the 1pt=1円 value and exposes registration; category cards state merchant and point reward. |
support-core-task-successprimary-flow-completion | pass | high | Browsing reward categories and opening registration worked; registration handed off predictably to the dアカウント ID step without a dead link. |
support-core-task-successclear-system-state-and-recovery | pass | high | The login Next action is visibly disabled until an ID is entered, with account-help text; an unknown route returns a branded not-found state and top-page recovery link. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.5s, CLS 0.148, TBT 220ms, Speed Index 10.1s and Time to Interactive 31.8s (performance 68). The raw trace was better on an unthrottled pass, so severity uses the throttled mobile result. F09 high: Mobile lab performance misses the Core Web Vitals quality bar. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse recorded CLS 0.148, and the layout primitive observed home shifts totaling 0.060 around 4.3–4.6s. The image audit found 70 images without dimensions. F10 medium: Late content causes visible layout instability. |
be-fast-and-stableefficient-main-thread | pass | high | The raw trace found one 72ms long task and 22ms TBT; Lighthouse TBT was 220ms, still below the 600ms poor threshold. The larger problems are network and TTI. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR captured 153 requests and 6.30MB transferred, including 3.80MB images and 1.40MB fonts. Lighthouse reports undiscoverable, unprioritized LCP and parser-blocking jQuery/CSS chains. F11 high: The critical resource path is heavy and poorly prioritized. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 739,843 bytes of unused JavaScript, led by ad code and multiple Google Tag Manager/gtag payloads; HAR recorded 1.03MB of scripts. F12 medium: Unused third-party JavaScript dominates the script budget. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed image-alt for the homescreen phone image, while the image primitive counted 24 images with no alt value and the app probe found an unlabeled search input. F13 high: Some meaningful images and fields lack accessible text relationships. |
be-inclusivesufficient-contrast | issues | high | Lighthouse/axe found 4.25:1 green text at 12px, 4.47:1 bottom-nav labels, and severely low-contrast campaign/consent states, producing an accessibility score of 92. F14 high: Several text and control states fail minimum contrast. |
be-inclusivestructure-and-focus | issues | high | The platform probe counted two h1 elements on the information template; recon also observed an empty second h1 in the rendered home DOM. Focus outlines were visible, but the document outline is not clean. F15 medium: Heading structure is duplicated and inconsistent across templates. |
be-inclusivelegible-text | pass | high | At the authored desktop layout, article text has comfortable line spacing and readable measure; the mobile scaling failure is recorded separately under reflow. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The page explicitly requests width=1024 even on a 390px device, shrinking the desktop layout and its controls instead of reflowing content. User scaling is allowed, but users must zoom to read and operate the page. F16 high: The mobile viewport does not provide usable reflow. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured “Uncaught SyntaxError: Identifier root has already been declared” in common-js-c-modal-dialog-Bc0k2xk5.js, plus a failed ad resource. F17 medium: The home page logs an uncaught JavaScript exception. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 70 of 100 images without dimensions, 10 oversized images and 22 legacy-format images; Lighthouse also found one distorted and one low-resolution rendered image. F18 medium: Image sizing is inconsistent and frequently omits intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found deprecated Topics API use, three BFCache failure reasons caused by cache-control:no-store behavior, third-party-cookie issues and DevTools inspector issues. F19 medium: Deprecated and cache-hostile platform behavior remains. |
be-discoverabletitle-and-description | pass | high | Home and article expose descriptive unique titles and meta descriptions in both raw HTML and rendered DOM. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Recon found real href links with descriptive Japanese labels, a viewport meta exists, and robots.txt allows public content. |
be-discoverablecanonical-and-indexing-signals | pass | high | Both sampled public pages returned 200 with canonical URLs; robots points to a functioning /sitemap index and does not apply noindex to content. |
be-discoverablestructured-and-shareable-metadata | pass | high | The home page exposes seven Open Graph properties and descriptive visible metadata. No article/product rich-result requirement was established for the sampled portal page. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS, nosniff and SAMEORIGIN are present, but CSP, Referrer-Policy and Permissions-Policy are missing. Cookie evidence reports 12 of 13 cookies without Secure and widespread SameSite=None, including long-lived analytics cookies. F20 high: Security headers and cookie attributes are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 10 third-party origins and Google Analytics, DoubleClick and Tag Manager; Lighthouse listed 13 cross-site cookies, and HAR attributed 146 of 153 requests and 6.25MB to third-party origins. F21 high: The default page load has a broad tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Geolocation remained prompt and Notifications default with no browser prompt on load; authentication is delegated to the first-party dアカウント flow over HTTPS. |
be-private-and-securedefensive-browser-policies | issues | high | The response has HSTS and X-Frame-Options but no CSP/frame-ancestors policy, no Referrer-Policy and no Permissions-Policy; the page also participates in third-party-cookie synchronization. F22 medium: Browser-enforced privacy and XSS defenses are underconfigured. |
be-resilientprogressive-enhancement | pass | high | Both home and article had 100% content-word coverage without JavaScript and were not JS shells. |
be-resilientresilient-runtime-behaviour | pass | high | Native dialogs remain dismissible and the responsive error page provides a recovery link; no clipped menu or blank runtime state appeared in tested paths. |
be-resilientoffline-and-installable | pass | high | The app probe directly found a valid manifest, a registered service worker and a scoped registration for the origin. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately unknown route rendered a branded explanation and a clear “トップへ戻る” recovery action rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=ja and renders Japanese reading order correctly on all sampled templates. |
be-internationalisedlocale-aware-data | issues | high | The Japanese maintenance page displays “2026年7月16日 (Thu) 11:00” and a compact “2026/07/29(水)AM1:00〜AM6:00”, indicating inconsistent formatting rather than one locale-aware pattern. F23 low: Date presentation mixes Japanese content with hard-coded English weekday text. |
be-internationalisedtime-zone-correctness | not-applicable | high | No cross-zone event scheduling or recurring user-managed time data was present; only editorial maintenance timestamps were observed. |
be-trustworthyno-dark-patterns | pass | high | Promotional density is intrusive and reported separately, but registration/login labels and commitments observed were direct; no preselected paid continuity or confirmshaming was found. |
be-trustworthyhumane-error-handling | pass | high | The external login step avoids premature error text, disables continuation until input, and provides an account-ID recovery link and explanatory copy. |
be-trustworthytrustworthy-input-assistance | issues | high | The app probe reports the site search input has no associated label and an empty autocomplete attribute. F24 medium: Search input assistance and labeling are incomplete. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Registration redirects to the recognizable dアカウント service with privacy/terms links, a stay-signed-in choice and no hidden price or subscription commitment in the sampled entry step. |
be-sustainableoptimised-assets | issues | high | The HAR transferred 3.80MB of images and 1.40MB of fonts; the largest single image was 473KB, and the image audit found 10 oversized, 22 legacy-format and 9 non-responsive images. F25 high: Image and font delivery is disproportionate for the page. |
be-sustainableno-wasteful-work | issues | high | The initial HAR recorded 153 requests, six tag-manager/analytics script loads among top offenders, and Lighthouse estimated about 740KB unused JavaScript. F26 medium: The page performs substantial non-core work before user intent. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 146/153 requests and 6.25MB of 6.30MB transferred; active trackers and a 396KB GIF load on the initial page. F27 high: Third-party and campaign media consume nearly the entire transfer budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | This public rewards/content portal exposes no declared agent-facing capability, and the emerging WebMCP check is contextual rather than required. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model task is part of the observed core journey; on-device inference would not add clear value here. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After closing the promotion and repeating menu toggles about 10 times, the fresh post snapshot was smaller: 383,835 vs 403,687 nodes and 23.58MB vs 24.68MB self size. Fresh-session variance limits confidence but there is no growth signal. |
be-memory-efficientbounded-footprint | pass | medium | The loaded promotional portal used about 24.7MB heap self size. This is proportionate to the rendered page and did not increase in the exercised state. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Node, edge, closure and object counts fell after repeated menu interaction; no growing Detached* constructor population appeared among the summary leaders. |
Provenance
Canonical report: results/atomic/reports/0186-hiroba_dpoint_docomo_ne_jp.json
Report SHA-256: 8a74bd2a45006eb01e875b8a9d6c317aa075be18c0d2fc833fb1784f5d95188f
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/hiroba_dpoint_docomo_ne_jp/2026-07-19T00-36-19-518Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/hiroba_dpoint_docomo_ne_jp/2026-07-19T00-36-19-518Z
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.