Manifest position 198 · CrUX rank bucket 1000
https://smt.docomo.ne.jp
Coverage complete
Coverage-complete audit of four representative portal templates and the primary search journey. Authenticated, checkout, and exhaustive downstream service flows were not entered.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Desktop screenshots under default and prefers-color-scheme: dark are pixel-identical; the page remains a bright white surface. F001 medium: The portal does not adapt to the user’s dark color preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe matched the preference but found three 7,000 ms animations and no reduced-motion CSS rules. F002 medium: Long animations continue when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse’s axe-backed color-contrast audit failed; its overall accessibility score was 0.74. F003 high: Text and controls include insufficient color contrast. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no view-transition, animation-timeline, scroll-timeline, scroll-snap, or container-query support on the interaction-heavy portal. F004 low: Route, tab, scroll, and drawer interactions use legacy state changes rather than modern natural-interaction affordances. |
implement-natural-interactionsscroll-driven-animations | issues | high | DOM/CSS inspection found no view-transition, animation-timeline, scroll-timeline, scroll-snap, or container-query support on the interaction-heavy portal. F004 low: Route, tab, scroll, and drawer interactions use legacy state changes rather than modern natural-interaction affordances. |
implement-natural-interactionsphysical-gestures | issues | high | DOM/CSS inspection found no view-transition, animation-timeline, scroll-timeline, scroll-snap, or container-query support on the interaction-heavy portal. F004 low: Route, tab, scroll, and drawer interactions use legacy state changes rather than modern natural-interaction affordances. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Search-result CSS includes a fixed search state on scroll and the screenshots preserve clear global/category navigation. |
provide-guided-navigationanchored-positioning | issues | high | The probe found 13 custom modal-class elements but zero dialog or popover elements; CSS implements fixed overlays and manual visibility. F005 medium: Overlays and menus are custom div-based implementations rather than semantic top-layer primitives. |
provide-guided-navigationdirects-attention | pass | high | Selected tabs use persistent underline/color states and article/search screenshots maintain clear section cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and 360×800 screenshots show a large pink reward modal and backdrop blocking search, news, and navigation before user interaction. F006 high: A promotional reward interstitial obscures the primary portal content on load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The probe found 13 custom modal-class elements but zero dialog or popover elements; CSS implements fixed overlays and manual visibility. F005 medium: Overlays and menus are custom div-based implementations rather than semantic top-layer primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop and 360×800 screenshots show a large pink reward modal and backdrop blocking search, news, and navigation before user interaction. F006 high: A promotional reward interstitial obscures the primary portal content on load. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360×800 capture, the article renders a dense multi-column desktop page scaled into the viewport, with very small text; its viewport declaration is only width=device-width. F007 high: The article template does not present a mobile-first layout at a narrow viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | At a 360×800 capture, the article renders a dense multi-column desktop page scaled into the viewport, with very small text; its viewport declaration is only width=device-width. F007 high: The article template does not present a mobile-first layout at a narrow viewport. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse failed button-name, image-alt, link-name, and accessibility-tree audits. The focus probe found many early anchors with outline:none, and the home probe found multiple empty H1 elements and unlabeled search inputs. F008 high: Accessible names, semantic structure, and keyboard focus are unreliable. |
support-core-task-successclear-purpose-and-primary-action | issues | high | Desktop and 360×800 screenshots show a large pink reward modal and backdrop blocking search, news, and navigation before user interaction. F006 high: A promotional reward interstitial obscures the primary portal content on load. |
support-core-task-successprimary-flow-completion | pass | high | The direct search-results path loaded 1,000 of 2,569 matching news results with query continuity and sorting controls. |
support-core-task-successclear-system-state-and-recovery | pass | high | The search template contains explicit empty/error states and /sitemap.xml’s 404 page explains the failure and links back to dmenu TOP. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse performance was 0.03 with FCP 9.1 s, LCP 18.3 s, TBT 2,210 ms and CLS 0.921. The raw-CDP trace corroborated FCP 10.79 s, LCP 12.46 s, TBT 318.55 ms and a 320.79 ms longest task; layout measured CLS 0.43 mobile and 0.61 desktop. F009 critical: The entry page is extremely slow and unstable. |
be-fast-and-stablevisual-stability | issues | high | The image primitive found all 100 images missing explicit dimensions, 55 below-fold images without lazy loading, 40 oversized images, 44 legacy-format images, and 42 missing alt text. F011 high: Image markup wastes bytes and contributes to instability and accessibility gaps. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse performance was 0.03 with FCP 9.1 s, LCP 18.3 s, TBT 2,210 ms and CLS 0.921. The raw-CDP trace corroborated FCP 10.79 s, LCP 12.46 s, TBT 318.55 ms and a 320.79 ms longest task; layout measured CLS 0.43 mobile and 0.61 desktop. F009 critical: The entry page is extremely slow and unstable. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 137 requests and 3.20 MB transferred, including 49 scripts (2.55 MB) and 2.05 MB third-party bytes. Confirmed head scripts top_index_libs7.js and top_index_com.js have neither async nor defer; cache and compression gaps are also present. F010 high: The page ships excessive, poorly prioritized script and third-party work. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR recorded 137 requests and 3.20 MB transferred, including 49 scripts (2.55 MB) and 2.05 MB third-party bytes. Confirmed head scripts top_index_libs7.js and top_index_com.js have neither async nor defer; cache and compression gaps are also present. F010 high: The page ships excessive, poorly prioritized script and third-party work. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed button-name, image-alt, link-name, and accessibility-tree audits. The focus probe found many early anchors with outline:none, and the home probe found multiple empty H1 elements and unlabeled search inputs. F008 high: Accessible names, semantic structure, and keyboard focus are unreliable. |
be-inclusivesufficient-contrast | issues | high | Lighthouse’s axe-backed color-contrast audit failed; its overall accessibility score was 0.74. F003 high: Text and controls include insufficient color contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed button-name, image-alt, link-name, and accessibility-tree audits. The focus probe found many early anchors with outline:none, and the home probe found multiple empty H1 elements and unlabeled search inputs. F008 high: Accessible names, semantic structure, and keyboard focus are unreliable. |
be-inclusivelegible-text | issues | high | At a 360×800 capture, the article renders a dense multi-column desktop page scaled into the viewport, with very small text; its viewport declaration is only width=device-width. F007 high: The article template does not present a mobile-first layout at a narrow viewport. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Home, services, and search templates set maximum-scale=1 and user-scalable=no; Lighthouse failed meta-viewport. The article screenshot also shows tiny scaled desktop text at 360 px. F012 high: The portal disables user zoom and has weak narrow-screen reflow. |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed errors-in-console, deprecations (4 warnings), inspector-issues, bfcache, and valid-source-maps. HAR also recorded ORB-blocked scripts. F013 medium: The page logs runtime/platform errors and uses deprecated or recovery-hostile patterns. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found all 100 images missing explicit dimensions, 55 below-fold images without lazy loading, 40 oversized images, 44 legacy-format images, and 42 missing alt text. F011 high: Image markup wastes bytes and contributes to instability and accessibility gaps. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed errors-in-console, deprecations (4 warnings), inspector-issues, bfcache, and valid-source-maps. HAR also recorded ORB-blocked scripts. F013 medium: The page logs runtime/platform errors and uses deprecated or recovery-hostile patterns. |
be-discoverabletitle-and-description | pass | high | All four representative pages expose specific non-empty titles and descriptions; the article description matches visible content. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable-anchors and canonical audits. Recon found javascript:void(0) and HTTP links; /sitemap.xml returns 404; the home OG URL is HTTP; no JSON-LD is present. The no-JS crawler view exposes navigation but omits the main dynamic news content. F014 medium: Crawler and indexing signals are incomplete or inconsistent. |
be-discoverablecanonical-and-indexing-signals | issues | high | Lighthouse failed crawlable-anchors and canonical audits. Recon found javascript:void(0) and HTTP links; /sitemap.xml returns 404; the home OG URL is HTTP; no JSON-LD is present. The no-JS crawler view exposes navigation but omits the main dynamic news content. F014 medium: Crawler and indexing signals are incomplete or inconsistent. |
be-discoverablestructured-and-shareable-metadata | issues | high | Lighthouse failed crawlable-anchors and canonical audits. Recon found javascript:void(0) and HTTP links; /sitemap.xml returns 404; the home OG URL is HTTP; no JSON-LD is present. The no-JS crawler view exposes navigation but omits the main dynamic news content. F014 medium: Crawler and indexing signals are incomplete or inconsistent. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers primitive found no CSP, HSTS, Referrer-Policy, or Permissions-Policy. Cookie audit found 11 cookies reported without Secure, including a session-named cookie, and several 400-day identifiers; all use SameSite=None. F015 high: Defensive response headers and cookie protections are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 22 third-party origins and 10 known tracker domains, including DoubleClick, Taboola, Criteo, Google Analytics and Google Ads. HAR attributes 59 requests and 2.05 MB to third parties. F016 high: The portal has a broad advertising and tracking footprint before user interaction. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt fired on load; account/auth destinations remain user-initiated links outside the content path. |
be-private-and-securedefensive-browser-policies | issues | high | Headers primitive found no CSP, HSTS, Referrer-Policy, or Permissions-Policy. Cookie audit found 11 cookies reported without Secure, including a session-named cookie, and several 400-day identifiers; all use SameSite=None. F015 high: Defensive response headers and cookie protections are incomplete. |
be-resilientprogressive-enhancement | issues | high | The crawler screenshot with scripting disabled displays a warning to enable JavaScript and leaves the primary news/content region empty, while the rendered screenshot contains a large feed. F017 high: Primary portal content depends on JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Representative home, listing, search, and article routes all rendered usable states despite several blocked third-party requests. |
be-resilientoffline-and-installable | not-applicable | high | The audited public portal is not presented as an installable application; offline installation was judged outside this run’s core browsing intent. |
be-resilientnetwork-and-http-failure-states | pass | high | The observed 404 response provides a Japanese error explanation, likely causes, and a route back to dmenu TOP. |
be-internationalisedlang-dir-and-logical-properties | pass | high | All representative pages declare html lang=ja; sampled layouts rendered Japanese text correctly. |
be-internationalisedlocale-aware-data | not-applicable | high | The sampled service is explicitly Japanese and exposed no user-selectable locale or locale-sensitive input flow. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling, event coordination, or user-entered time-zone-sensitive flow was present on the representative paths. |
be-trustworthyno-dark-patterns | issues | high | Desktop and 360×800 screenshots show a large pink reward modal and backdrop blocking search, news, and navigation before user interaction. F006 high: A promotional reward interstitial obscures the primary portal content on load. |
be-trustworthyhumane-error-handling | pass | high | The observed error page explains what happened without blame and offers a clear recovery link; search CSS defines explicit empty/error messaging. |
be-trustworthytrustworthy-input-assistance | issues | high | Home and search probes show search inputs with autocomplete=off and no associated label or aria-label; Lighthouse also reports naming failures. F018 medium: Search fields suppress browser input assistance and lack explicit labels. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, cancellation, or authenticated account flow was entered in the unauthenticated representative scope. |
be-sustainableoptimised-assets | issues | high | The image primitive found all 100 images missing explicit dimensions, 55 below-fold images without lazy loading, 40 oversized images, 44 legacy-format images, and 42 missing alt text. F011 high: Image markup wastes bytes and contributes to instability and accessibility gaps. |
be-sustainableno-wasteful-work | issues | high | The 3.20 MB load spends 2.05 MB on third parties, while image inspection found 44 legacy images, 40 oversized images, and 55 below-fold images loaded eagerly. F019 high: Third-party scripts and inefficient assets create a disproportionate transfer and processing budget. |
be-sustainablethird-party-and-media-budget | issues | high | The 3.20 MB load spends 2.05 MB on third parties, while image inspection found 44 legacy images, 40 oversized images, and 55 below-fold images loaded eagerly. F019 high: Third-party scripts and inefficient assets create a disproportionate transfer and processing budget. |
be-agent-readystructured-agent-capabilities | issues | high | DOM/source inspection found ordinary forms but no WebMCP or agentic tool registration; the public portal has actionable search and service-discovery surfaces. F020 low: The portal’s search and service actions are not exposed as structured agent capabilities. |
be-agent-readyon-device-inference | not-applicable | high | The portal exposes no summarization or generative feature whose inference placement can be assessed. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten drawer open/close cycles, heap self size rose 1.6% (37.06 MB to 37.66 MB), DOM node count stayed 1,466, and closures stayed effectively flat (37,811 to 37,813); no clear retained-growth leak signal. |
be-memory-efficientbounded-footprint | pass | medium | Heap summary measured 37.06 MB baseline self size and 37.66 MB post-interaction for a script-heavy portal; large but bounded across the sampled interaction. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The repeated drawer probe left the live DOM count unchanged at 1,466 and heap summaries showed no Detached constructor among top retained constructors. |
Provenance
Canonical report: results/atomic/reports/0198-smt_docomo_ne_jp.json
Report SHA-256: 8d840da883aec1c6107cc117b8e0682e37ad5eb4417697bb4f9fabe42b129821
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/smt_docomo_ne_jp/2026-07-19T02-51-47-892Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/smt_docomo_ne_jp/2026-07-19T02-51-47-892Z
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.