Manifest position 818 · CrUX rank bucket 1000

https://dmarket.docomo.ne.jp

Coverage complete

Coverage-complete report-only audit of six representative paths. Not covered: authenticated account/history and actual third-party merchant checkout, because credentials and purchases were out of scope.

Attempts

1 / 3

Judged checks

58 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	The preferences screenshot is pixel-identical in appearance to the default light capture, and the CSS probe found no prefers-color-scheme rule. F01 medium: The site remains light when the user requests a dark color scheme.
respect-user-preferences `respects-reduced-motion`	pass	high	Under the combined reduced-motion emulation, the page exposed no active Web Animations and no autoplay media; the preference capture remained usable.
respect-user-preferences `respects-contrast`	issues	high	The CSS probe found no prefers-contrast or forced-colors rules; the emulated high-contrast capture remained unchanged. F02 low: The stylesheet does not adapt to contrast or forced-colors preferences.
implement-natural-interactions `view-transitions`	issues	high	CSS inspection across the loaded page found no view-transition declarations; representative routes are conventional MPA navigations. F03 low: Navigation uses abrupt cross-document swaps rather than progressive View Transitions.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	No scroll-linked animation was present on the representative routes, so there is no scroll animation implementation to classify.
implement-natural-interactions `physical-gestures`	pass	high	CSS inspection found native scroll-snap support and the representative pages scroll with the platform; no custom pointer-drag handler was observed.
provide-guided-navigation `scroll-state-aware-chrome`	issues	high	Mobile captures and CSS inspection show a fixed header but no scroll-state container query or progress indicator. F04 low: The persistent mobile chrome does not communicate scroll state.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No tooltip, non-modal popover, or edge-positioned menu was exposed on the representative unauthenticated paths.
provide-guided-navigation `directs-attention`	pass	high	The listing screenshot clearly marks the selected shop category in red and keeps the page title and filtering controls adjacent to the results.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	Desktop and mobile initial-load screenshots show a modal covering the primary content before any user action. The message is important, but the interruption occupies most of the viewport. F05 high: A large service-closure notice blocks the marketplace on every homepage load.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	The live DOM probe found visible .c-modal-* divs with no role=dialog, aria-modal, or native dialog element. F06 high: The blocking notice is an ad-hoc div modal without dialog semantics.
maximize-content-reduce-noise `reduced-chrome`	pass	high	After the closure notice, listing and detail screenshots devote the viewport to shop cards, point rates, merchant description, and a clear merchant CTA rather than ornamental framing.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	At 360px, the layout primitive measured only a 1px rounding difference (376px scroll width vs 375px visual viewport), with no clipped content; viewport metadata is present.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	The loaded stylesheet probe found no @container rules even though cards and navigation components recur in narrow and wide contexts. F07 low: Responsive behavior is viewport-centric rather than component-aware.
adapt-to-the-form-factor `input-modality-aware`	issues	high	The interaction probe found 12 visible controls below 24 CSS px in one dimension, including a 16x16 modal close button and 16-18px-high links. F08 medium: Several interactive targets are too small for reliable touch use.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	The listing states ショップ一覧 and exposes categories; the shop detail states the merchant, point rate, and a prominent サイトへ進む action.
support-core-task-success `primary-flow-completion`	pass	high	The representative browse flow reaches a populated shop list, a detailed merchant offer, and a prominent outbound merchant CTA without an account wall.
support-core-task-success `clear-system-state-and-recovery`	pass	high	A nonexistent route returns a branded Japanese 404 with an explanation, reload advice, cache/cookie recovery steps, and a top-page link.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured performance 40, FCP 4.5s, LCP 8.0s, Speed Index 7.3s, and TTI 10.8s. A less-throttled trace measured LCP 2.28s, confirming network/CPU sensitivity. F09 high: Mobile load performance is poor.
be-fast-and-stable `visual-stability`	issues	high	Lighthouse reported CLS 0.403 with three shifts; the mobile layout primitive independently observed CLS 0.317 from shifts at about 3.26s and 4.89s. The image audit found 95/100 images without explicit dimensions. F10 high: Late content causes severe layout movement.
be-fast-and-stable `efficient-main-thread`	pass	high	The trace recorded zero tasks over 50ms and 0ms total blocking time in its 8.8s capture; Lighthouse TBT was 110ms.
be-fast-and-stable `efficient-resource-delivery`	issues	high	The HAR identified parser-inserted styles and multiple classic scripts; the DOM confirmed the first-party scripts have neither async nor defer. Lighthouse estimated 2.13s render-blocking savings and 581KiB cache-lifetime savings. F11 high: Render-blocking and poorly cached resources delay the initial page.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	Lighthouse estimated 278KiB unused JavaScript and 34KiB unused CSS. Four Google tag loader requests alone transferred about 578KiB. F12 medium: The page ships substantial unused and duplicated script work.
be-inclusive `names-roles-labels`	issues	high	Lighthouse failed link-name; the DOM probe listed at least 20 visible unnamed interactive elements, and the image audit found 21 images without alt text. F13 high: Many links and images lack accessible names.
be-inclusive `sufficient-contrast`	issues	high	Lighthouse accessibility failed the color-contrast audit on the homepage. F14 high: Some text and UI colors fail WCAG contrast.
be-inclusive `structure-and-focus`	issues	high	Lighthouse failed heading-order; the DOM has an empty H1 followed by H3 navigation headings. The modal is not exposed as a dialog, although the sampled keyboard focus outline was visible. F15 medium: Heading structure and modal focus semantics are inconsistent.
be-inclusive `legible-text`	pass	high	Mobile listing, detail, notice, and 404 captures show readable Japanese body text with stable line wrapping and no clipping at 360px.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	The interaction probe found 12 visible controls below 24 CSS px in one dimension, including a 16x16 modal close button and 16-18px-high links. F08 medium: Several interactive targets are too small for reliable touch use.
follow-best-practices `no-console-errors`	pass	high	Lighthouse did not report its errors-in-console audit as failing during the measured homepage load.
follow-best-practices `sound-document-and-assets`	issues	high	Lighthouse reported unsized images and one deprecated API warning; the image primitive found 95 of 100 images without width and height. F16 medium: Asset markup does not consistently reserve image geometry and uses a deprecated API.
follow-best-practices `browser-platform-hygiene`	issues	high	Lighthouse reported a BFCache blocker and missing source maps for large first-party JavaScript in addition to the deprecation warning. F17 medium: The page has avoidable browser-platform hygiene failures.
be-discoverable `title-and-description`	pass	high	The homepage exposes a descriptive Japanese title and a specific meta description in both raw and rendered HTML.
be-discoverable `crawlable-and-mobile-friendly`	issues	high	The DOM probe found at least 20 visible unnamed links and Lighthouse failed link-name. URLs are real hrefs and a viewport meta exists, but link purpose is not exposed reliably. F18 medium: Many prominent card links have no descriptive link text.
be-discoverable `canonical-and-indexing-signals`	issues	high	robots.txt returned 200 and allows primary content, while /sitemap.xml returned HTTP 404. Canonical URLs are present. F19 medium: The site does not expose a sitemap at the conventional location.
be-discoverable `structured-and-shareable-metadata`	issues	high	The homepage has Open Graph tags but the DOM probe found no JSON-LD for the Organization/WebSite or marketplace entities. F20 low: Share metadata exists, but rich entity metadata is absent.
be-private-and-secure `secure-transport-and-headers`	issues	high	HTTPS is used, but the headers primitive found no CSP, HSTS, X-Content-Type-Options, Referrer-Policy, or Permissions-Policy. All eight observed cookies were flagged, including three Google Analytics cookies without Secure and with SameSite=None. F21 high: Core browser security headers are missing and analytics cookies are not Secure.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	The HAR recorded 71/79 requests and 1.318MB/1.435MB as cross-origin by host classification; tracker evidence found two known tracker origins. Four tag-manager/gtag files transferred about 578KiB before user interaction. F22 high: Tracking and third-party delivery dominate the page load.
be-private-and-secure `in-context-permissions-and-modern-auth`	issues	high	No permission prompt was triggered on load, but the d Account redirect presented ID-first sign-in and the rendered/auth source probe found no WebAuthn or PublicKeyCredential signal. F23 medium: The observed sign-in entry does not advertise phishing-resistant authentication.
be-private-and-secure `defensive-browser-policies`	issues	high	HTTPS is used, but the headers primitive found no CSP, HSTS, X-Content-Type-Options, Referrer-Policy, or Permissions-Policy. All eight observed cookies were flagged, including three Google Analytics cookies without Secure and with SameSite=None. F21 high: Core browser security headers are missing and analytics cookies are not Secure.
be-resilient `progressive-enhancement`	pass	high	The discoverability fetch received 200 and 379,566 bytes of substantive server HTML; the site is not an empty JS shell and title/description survive without scripting.
be-resilient `resilient-runtime-behaviour`	pass	high	The blocking notice remains fully contained and dismissible at both desktop and narrow mobile sizes; listing/detail content also remains usable at 360px.
be-resilient `offline-and-installable`	not-applicable	high	This commerce directory redirects transactions to online merchant sites and is intrinsically network-dependent; an installable offline app is not necessary for its core task.
be-resilient `network-and-http-failure-states`	pass	high	The tested 404 route gives a clear failure explanation and concrete recovery routes rather than a blank shell or infinite spinner.
be-internationalised `lang-dir-and-logical-properties`	not-applicable	high	The service is explicitly a Japan-only, Japanese-language marketplace; alternate writing modes are outside the observed product scope.
be-internationalised `locale-aware-data`	not-applicable	high	No user-selectable locale or cross-locale date, number, or currency workflow is offered; displayed dates and point rates are for the single Japanese locale.
be-internationalised `time-zone-correctness`	not-applicable	high	No cross-time-zone scheduling or event coordination flow exists on the audited Japanese marketplace paths.
be-trustworthy `no-dark-patterns`	pass	high	The service end date and implications are stated plainly, no consent wall or disguised advertisement appeared, and the detail page labels point rates and outbound action clearly.
be-trustworthy `humane-error-handling`	not-applicable	high	No editable validation form was present on the representative marketplace, listing, detail, notice, or 404 paths.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	No address, payment, registration, or password form is owned by the audited host on the representative paths; sign-in redirects to the separate d Account service.
be-trustworthy `safe-commercial-and-account-flows`	pass	high	The merchant detail shows the reward rate before the outbound action and labels that action as leaving for the merchant; no hidden subscription or continuity commitment appears.
be-sustainable `optimised-assets`	issues	high	Lighthouse estimated 316KiB image-delivery savings; the image probe found missing intrinsic dimensions on 95 images and no responsive source on the raster image it flagged. F24 medium: Image delivery leaves meaningful byte and stability savings.
be-sustainable `no-wasteful-work`	issues	high	The HAR recorded 71/79 requests and 1.318MB/1.435MB as cross-origin by host classification; tracker evidence found two known tracker origins. Four tag-manager/gtag files transferred about 578KiB before user interaction. F22 high: Tracking and third-party delivery dominate the page load.
be-sustainable `third-party-and-media-budget`	issues	high	The HAR recorded 71/79 requests and 1.318MB/1.435MB as cross-origin by host classification; tracker evidence found two known tracker origins. Four tag-manager/gtag files transferred about 578KiB before user interaction. F22 high: Tracking and third-party delivery dominate the page load.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	The retiring marketplace exposes no declared agent-facing surface; the emerging WebMCP capability is treated as an opportunity, not an obligation.
be-agent-ready `on-device-inference`	not-applicable	high	No summarisation or generative task is part of the observed marketplace journey, so on-device inference would not clearly improve the core task.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	medium	After ten full-page down/up scroll cycles, heap self size increased only 293,503 bytes (1.5%) and node count 1.1%; this bounded single-run delta does not indicate unbounded retention.
be-memory-efficient `bounded-footprint`	pass	medium	The representative merchant page heap was about 19.2MB at baseline, proportionate to the image-rich detail page and its scripts.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	medium	Neither heap summary surfaced Detached* constructors among retained top constructors; closure count changed from 15,492 to 15,510 after repeated scrolling, not an accumulating pattern.

Provenance

Canonical report: results/atomic/reports/0818-dmarket_docomo_ne_jp.json
Report SHA-256: 3fcfdd5bcb7a4433afedabc7301b776356e3b03f0d005ade1e206b4baa47b018
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/dmarket_docomo_ne_jp/2026-07-23T05-29-30-870Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/dmarket_docomo_ne_jp/2026-07-23T05-29-30-870Z
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.