Manifest position 678 · CrUX rank bucket 1000
https://search.rakuten.co.jp
Coverage complete
Atomic coverage complete across four representative commerce templates plus login and failure-state probes.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-mode screenshot is pixel-identical in appearance to the default capture; the reduced-motion/media probe reports color-scheme: normal and a light body background rgb(247,247,247), with no prefers-color-scheme rules. F01 medium: The shopping surfaces ignore the user’s dark-theme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Computed animation probe under prefers-reduced-motion: reduce found zero active animations; no reduced-motion-dependent motion remained to suppress. |
respect-user-preferencesrespects-contrast | issues | high | The preference probe found no prefers-contrast or forced-colors rules, while Lighthouse found multiple essential text contrast failures on both search and product templates. F02 medium: No preference-specific high-contrast treatment is provided. |
implement-natural-interactionsview-transitions | issues | high | The CSS/media feature probe found no view-transition rules and the MPA search-to-product journey performs a full abrupt navigation. F03 low: Route changes are abrupt and do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | The audited templates contain no parallax, scrollytelling, reveal, or other scroll-linked motion to implement. |
implement-natural-interactionsphysical-gestures | pass | high | The result pages retain native browser scrolling and the DOM/CSS probe found no custom gesture surface fighting platform scrolling. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The search template is 10,403 CSS px tall, but the CSS feature probe found no scroll-state query or progress treatment and the captured header remains static. F04 low: Long result pages provide no scroll-state feedback. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, transient popover, or viewport-edge menu was present in the exercised shopping path. |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs, explicit query/result text, visible filters and descriptive product links preserve location and next-action context. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots across four templates showed no modal, consent wall or full-viewport interstitial obscuring core content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No modal or transient overlay was presented during the exercised search and product journey. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop and mobile captures show multiple bright campaign banners, utility rows, notices and dense controls before or around the first product; the product capture devotes several viewports to store graphics. F05 medium: Promotional chrome competes with the primary shopping content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x800 viewport, search and category layouts report scrollWidth 1024 versus clientWidth 360, or 664 px overflow; index and product omit viewport metadata and are scaled-down desktop pages. F06 high: Core templates render a fixed desktop canvas on mobile. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The search DOM reports body width 1024px and container-type: normal; the feature probe found no @container usage, and the narrow screenshot clips the product region. F07 high: Components do not adapt to their available container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The active DOM probe measured 436 of the first 500 visible links, buttons, and fields below 44px in at least one dimension; Lighthouse also failed target-size. F08 high: Most interactive targets are too small for touch. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The entry identifies a category index; the search page shows the query, result count, filters and product links; the product page exposes price/product content. |
support-core-task-successprimary-flow-completion | pass | high | A GET search for 米 returned product results and a result link successfully opened the representative product detail without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | A deliberately invalid route returned a clear 404 title, explanation, reload/back advice and a service-list recovery link. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured search LCP 10.3s, CLS 0.158 and TBT 1,400ms; product LCP was 21.9s, CLS 0.545 and TBT 870ms. CDP traces corroborated LCP of 6.34s and 19.27s. F09 high: Representative pages miss the Core Web Vitals performance bar by a wide margin. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse measured CLS 0.545 on the product page and 0.158 on search; the index layout observer recorded CLS 0.459. Image evidence found 46 dimensionless search images and 62 on product. F10 high: Late content causes severe layout movement. |
be-fast-and-stableefficient-main-thread | issues | high | Search Lighthouse reported 1,400ms TBT and the trace found three long tasks up to 377ms; the page loads 100 scripts. Product loads 167 scripts. F11 high: Heavy scripting blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 372 requests/5.71MB for search and 499 requests/9.58MB for product, including parser-inserted high-priority styles/scripts; the product document took about 10.9s in the HAR. F12 high: Resource delivery is extremely heavy and has long critical chains. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Search transfers 4.15MB across 100 scripts; product transfers 4.18MB across 167. Search downloads repeated ~154KB Google tags and multiple ~151KB Facebook configurations. F13 high: Third-party and duplicate script payload dominates the load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility scores were 0.62/0.69. Search failed aria-command-name with 54 nodes and invalid ARIA on 21; product images audit found 63 images without alt and Lighthouse found unlabeled controls. F14 high: Interactive controls and media lack accessible names and valid roles. |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed color-contrast on both templates; product has 12 groups including #f2ab00 on white at 1.98:1 and #8f8f8f on white at 3.23:1. F15 high: Essential text fails WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | Search, category and product probes found no h1; search had only one landmark and product had none. Lighthouse failed landmark-one-main and found focusable descendants inside aria-hidden search carousel slides. F16 high: Document structure and focus semantics are incomplete. |
be-inclusivelegible-text | issues | high | The 360px index and product screenshots shrink 1024–1244px canvases into the viewport; search body text is 12px and clipped horizontally. F17 medium: Scaled desktop layouts make text cramped and illegible on narrow screens. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Search/category retain 664px horizontal overflow at 360px; index/product have no viewport meta, and Lighthouse failed meta-viewport/target-size checks. F18 high: The experience fails mobile reflow and target-size requirements. |
follow-best-practicesno-console-errors | issues | high | Lighthouse recorded 17 console errors on search and 22 on product, dominated by failed/CORS-blocked Yahoo analytics calls. F19 medium: Third-party integrations log many browser errors. |
follow-best-practicessound-document-and-assets | issues | high | Image probes found 46 search and 62 product images without dimensions; product Lighthouse failed image-aspect-ratio and 85 of 87 inspected images use legacy formats. F20 medium: Images are frequently unsized, unlabeled, or use problematic aspect handling. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Both Lighthouse runs report deprecated Attribution Reporting use from Google tags and fail BFCache/inspector checks; product also has a broken source-map warning. F21 medium: Deprecated APIs and browser lifecycle blockers remain. |
be-discoverabletitle-and-description | pass | high | All four templates returned descriptive titles and meta descriptions; search title is “【楽天市場】米の通販”. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Although links are mostly real hrefs and raw HTML is strong, the entry/product pages omit viewport metadata and representative narrow layouts fail reflow. F22 high: Public pages are not consistently mobile friendly. |
be-discoverablecanonical-and-indexing-signals | pass | high | Representative public pages returned HTTP 200 with canonical URLs and no accidental noindex; robots.txt allows the audited search route. |
be-discoverablestructured-and-shareable-metadata | issues | high | The inspected product exposes BreadcrumbList JSON-LD and complete Open Graph tags but no Product JSON-LD, despite being a commercial product entity. Search exposes only og:image among OG tags. F23 medium: Product structured data is incomplete. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS and nosniff are present, but CSP only contains frame-ancestors; 18 first-party cookies were flagged, with many not Secure and SameSite=None. F24 high: Cookie and CSP protections are weaker than the HTTPS transport suggests. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 58 third-party origins and 14 known tracker domains on search; HAR attributes 370 of 372 requests and 5.62MB to non-main-origin hosts. Product reaches 77 third-party origins. F25 high: The page sends a very large tracking footprint on first load. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load. The central login form uses autocomplete=username and its source contains passkey affordances. |
be-private-and-securedefensive-browser-policies | issues | high | Permissions-Policy is missing, CSP lacks script/style/default restrictions, and Lighthouse observed 54–55 third-party cookies across the representative pages. F26 medium: Defensive policy coverage is incomplete and third-party cookie dependence is high. |
be-resilientprogressive-enhancement | pass | high | Raw-HTML coverage was 63% on the entry and 80–91% on search/category/product; all were non-shell pages with core text present without JS. |
be-resilientresilient-runtime-behaviour | pass | high | The exercised listing/product pages loaded usable content despite several failed tracker requests; no clipped transient overlay blocked the path. |
be-resilientoffline-and-installable | not-applicable | high | This transaction/search marketplace intrinsically depends on live inventory, pricing and account services; installability/offline transaction support is not expected. |
be-resilientnetwork-and-http-failure-states | pass | high | The invalid route rendered a useful 404 with explanation and recovery links rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Representative documents declare lang=ja; Japanese left-to-right content and reading order render consistently on inspected pages. |
be-internationalisedlocale-aware-data | pass | high | Prices render as Japanese yen and delivery/calendar dates use Japanese locale conventions throughout the representative commerce path. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited search and product path contains local delivery dates but no user-created global event or recurring time-zone-sensitive schedule. |
be-trustworthyno-dark-patterns | pass | high | The inspected pages disclose product prices, shipping caveats, result ordering and deadlines; no consent wall, confirmshaming or forced continuity appeared. |
be-trustworthyhumane-error-handling | pass | high | Search inputs are optional and the tested invalid route gives neutral, actionable recovery guidance without blaming the user. |
be-trustworthytrustworthy-input-assistance | pass | high | The relevant account identifier field uses autocomplete=username and is programmatically labelled; search fields do not collect address/payment credentials. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The product/search surfaces visibly disclose price, shipping variability and delivery caveats; account sign-in is delegated to a clearly labelled central flow with passkey strings present. |
be-sustainableoptimised-assets | issues | high | Product transfers 5.08MB of images; 85 of 87 inspected product images use legacy formats, 78 below-fold images are not lazy, 51 lack srcset, and 62 lack dimensions. F27 high: Image delivery wastes bandwidth. |
be-sustainableno-wasteful-work | issues | high | Search makes 372 requests including 72 fetch/XHR and 100 scripts; trackers include multiple repeated pixels/tags and failed requests that still consume CPU/network. F28 high: Background advertising and analytics perform disproportionate work. |
be-sustainablethird-party-and-media-budget | issues | high | Search transfers 5.71MB with 5.62MB attributed outside the main origin; product transfers 9.58MB and loads 498 of 499 requests from other origins, including 5.08MB images. F29 high: Third-party and media weight is disproportionate to the shopping task. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared intent indicates an agent-facing surface; this emerging capability is not required for the current human shopping scope. |
be-agent-readyon-device-inference | not-applicable | high | No declared product intent calls for summarisation or on-device inference in the audited shopping path. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll down/up cycles, same-session DOM nodes remained 6,501 and used JS heap fell from 130.7MB to 97.4MB; separate heap summaries differed only 1.31%. |
be-memory-efficientbounded-footprint | issues | high | The heap summary reported about 115.5MB self size, 2.21M heap nodes and 11.75M edges after load. Repeated scrolling did not indicate a leak, but the cold footprint is disproportionate and aligns with 100 scripts. F30 medium: The initial heap footprint is high for a result listing. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The repeated scroll probe kept DOM node count fixed at 6,501 and showed no monotonic used-heap growth; no leak signal was established. |
Provenance
Canonical report: results/atomic/reports/0678-search_rakuten_co_jp.json
Report SHA-256: 2041c10d926a5d6f40dc4df50abfd71a31e283963bb006d2d93a5b3e17e74a05
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/search_rakuten_co_jp/2026-07-22T08-31-18-464Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/search_rakuten_co_jp/2026-07-22T08-31-18-464Z
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.