Manifest position 410 · CrUX rank bucket 1000
https://item.rakuten.co.jp
Coverage complete
Requested bare item host redirects to www.rakuten.co.jp; audit covers the resulting homepage plus representative search and product templates. Account, payment, order submission and localized external Rakuten properties 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 | Dark-mode capture is pixel-identical to the light capture and computed color-scheme is "normal"; no prefers-color-scheme CSS was found. F-001 medium: Honours prefers-color-scheme: a usable dark mode exists and is driven by the user's preference (color-scheme / prefers-color-scheme / light-dark()), not hard-coded light only. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, a running 800 ms spin animation remained and no reduced-motion CSS rule was found. F-002 medium: Honours prefers-reduced-motion: non-essential animations and auto-advance are reduced or removed when the user asks for less motion. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse failed color-contrast, and the high-contrast capture retains low-emphasis gray text and dense controls. F-003 high: Honours prefers-contrast / forced-colors: controls, text and scrollbars remain visible under high-contrast preferences. |
implement-natural-interactionsview-transitions | issues | high | The page exposes the API but CSS/DOM inspection found no view-transition usage; navigation and carousel state changes are abrupt. F-004 low: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps. |
implement-natural-interactionsscroll-driven-animations | issues | high | No animation-timeline CSS was found; the page uses legacy slideshow and scroll JavaScript patterns. F-005 low: Scroll-linked motion (parallax, scrollytelling, entry/exit reveals) uses declarative CSS scroll-driven animations (off main thread) instead of scroll event listeners. |
implement-natural-interactionsphysical-gestures | pass | high | DOM/CSS evidence shows carousels use overflow scrolling, scroll-snap-type and overscroll-behavior rather than pointermove gesture emulation. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long commerce pages use static/fixed chrome; CSS inspection found no scroll-state container queries or progress affordance. F-006 low: Sticky/affixed UI reacts to scroll state and position (e.g. the new scroll-state(scrolled) query, shrinking headers, progress indicators) so chrome responds to position instead of static or JS-driven toggling. |
provide-guided-navigationanchored-positioning | issues | high | Transient UI is implemented with absolute/fixed custom wrappers and role=dialog; no anchor positioning or position-try CSS was found. F-007 medium: Tooltips, popovers and menus use CSS anchor positioning (with fallback positions) so they stay attached and reposition correctly rather than being manually positioned. |
provide-guided-navigationdirects-attention | issues | high | Neither homepage nor product page has an h1, while screenshots show many competing promotions and no clear focus cue after navigation. F-008 medium: Navigation and in-page jumps guide attention (highlight effects, scroll/carousel markers, directional transitions, drill-down and drawer navigation) so the user can follow where focus moved. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Desktop and mobile load screenshots show content immediately with no full-viewport interstitial obscuring it. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection found no dialog element but found custom role=dialog and bookmark popup wrappers with manual positioning/dismiss behavior. F-009 medium: Overlays and rich controls use the right primitive: popover (with declarative light-dismiss) for transient UI, dialog for modal flows, details for disclosure, native-but-branded selects and pickers, rather than ad-hoc divs. |
maximize-content-reduce-noisereduced-chrome | issues | high | Mobile captures show desktop-scale, promotion-heavy layouts with banners, fixed shop chrome, side navigation, carousels and ads competing with products. F-010 high: Minimise non-content chrome and borders so the content is the focus, not the application frame; expressive/decorative visuals serve the content rather than crowd it. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | No viewport meta exists. At a 360x800 emulation Chrome laid out a 1024 px page; desktop layout measured 244 px overflow, and mobile screenshots are scaled-down desktop pages. F-011 critical: Layout adapts to narrow viewports with no horizontal overflow and no fixed pixel widths forcing a desktop layout on mobile; viewport meta present; fluid scaling and intrinsic sizing rather than brittle breakpoints. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found no @container rules; reused commerce modules retain fixed widths such as 1020 px and 950 px across narrow captures. F-012 high: Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse failed target-size, and component CSS explicitly removes focus outlines on .rex-button. F-013 high: Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike. |
support-core-task-successclear-purpose-and-primary-action | issues | high | The product mobile capture opens on shop promotions and product grids; the actual umbrella title, price and purchase action are not visible in the first viewport. F-014 high: The page communicates what it is for and exposes the primary next action without requiring users to hunt through decorative content, generic copy, or competing calls to action. |
support-core-task-successprimary-flow-completion | issues | high | The product page is a 76,483 px desktop-layout document on mobile with 40+ variant/acknowledgement choices; the purchase controls require extensive scanning in a scaled view. F-015 high: The representative primary flow can be completed end-to-end with predictable steps, no avoidable dead ends, no hidden required information, and no needless detours through modals, account walls, or upsells. |
support-core-task-successclear-system-state-and-recovery | pass | high | The product probe exposes explicit unselected, required and sold-out variant states plus cart and checkout actions. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 13.9 s, CLS 0.219 and TBT 1,530 ms; all are outside the good range. F-016 critical: Core Web Vitals are in the good range: LCP is fast, interaction latency (INP) is low, and CLS is minimal; work is prioritised and deferred sensibly. |
be-fast-and-stablevisual-stability | issues | high | The layout primitive observed CLS 0.266 on mobile and 0.863 at the default desktop viewport; 90 of 100 sampled images lacked dimensions. F-017 high: No cumulative layout shift from late content (images, banners, fonts) that arrives without reserved space. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 21.1 s main-thread work and 1,530 ms TBT; trace corroborated long tasks. F-018 high: The main thread is not blocked by long tasks or heavy scripting; work is deferred, chunked, prioritised, or moved off-thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 731 requests and 8.04 MB, including parser-inserted high-priority scripts/styles and missing cache headers; Lighthouse estimated 1.78 s render-blocking savings. F-019 high: Critical resources are delivered efficiently: cache headers are useful, render-blocking chains are short, fonts do not block or shift text, HTTP delivery is modern, and network dependency trees do not delay the main content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | 146 scripts transferred 2.49 MB; Lighthouse estimated 2.99 MB unused JavaScript and 101 KiB unused CSS. F-020 high: The page does not ship large unused or duplicated JavaScript/CSS, avoidable legacy bundles, or third-party code that dominates the load without user value. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed aria-allowed-attr, aria-command-name, image-alt and link-name; the image probe found 87 of 100 sampled images missing alt. F-021 high: Interactive elements have accessible names, correct roles, and form fields have labels; images have alt text where meaningful; canvas/expressive content is exposed to assistive technology. |
be-inclusivesufficient-contrast | issues | high | Lighthouse color-contrast audit failed on the homepage. F-022 high: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | Homepage and product probes found zero h1 elements, Lighthouse found no main landmark, and CSS removes button outlines. F-023 high: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves. |
be-inclusivelegible-text | issues | high | Without a viewport meta, the 1024/980 px desktop pages are scaled into 360 px, producing tiny text and dense controls. F-024 high: Text is legible and inclusively rendered: comfortable line layout, precise alignment, stable rendering across mixed fonts, no clipping or cramped wrapping that harms comprehension. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse failed meta-viewport and target-size; narrow captures re-scale rather than reflow. F-025 high: The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling. |
follow-best-practicesno-console-errors | issues | high | Lighthouse errors-in-console audit failed during load. F-026 medium: The page loads without console errors or uncaught exceptions. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found 90/100 missing dimensions, 8 oversized and 89 legacy-format images. F-027 high: Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.) |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported a deprecation warning and inspector issues. F-028 medium: The page uses the platform cleanly: no deprecated APIs, no avoidable BFCache blockers, no broken source maps or inspector issues, no stale vulnerable libraries, no paste-prevention on inputs, and no notification/geolocation prompts on load. |
be-discoverabletitle-and-description | pass | high | Homepage and product probes show descriptive titles and non-empty meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Links are real hrefs and raw content is crawlable, but there is no viewport meta and Lighthouse robots.txt audit failed. F-029 high: Links are crawlable (real href), there is a viewport meta tag, robots does not block indexing, and link text is descriptive. |
be-discoverablecanonical-and-indexing-signals | pass | high | Both representative public pages returned 200; canonical URLs are present and discoverability fetches succeeded. |
be-discoverablestructured-and-shareable-metadata | issues | high | Open Graph metadata exists, but the representative product exposes VideoObject and BreadcrumbList JSON-LD without Product/Offer structured data matching price and availability. F-030 medium: Where the page represents an article, product, organization, event, place or other rich entity, structured data and share-preview metadata accurately describe the visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS and nosniff are absent; two cookies are not Secure and all seven use SameSite=None. F-031 high: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR recorded 643 third-party-origin requests and 7.91 MB; multiple Google advertising/tag scripts and sync endpoints loaded before interaction. F-032 high: No over-collection of user data, no leaky third parties, and analytics/background data collection is minimised and batched rather than chatty or session-wide by default. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Notification permission remained default with no on-load prompt; authentication is linked to a dedicated Rakuten identity origin. |
be-private-and-securedefensive-browser-policies | issues | high | CSP/frame-ancestors or X-Frame-Options, HSTS, Referrer-Policy and Permissions-Policy are all absent. F-033 high: Browser-enforced defenses are configured where appropriate: HSTS, clickjacking protection (frame-ancestors / X-Frame-Options), Trusted Types for XSS-sensitive apps, origin isolation, privacy-preserving third-party cookie posture, and sensible Referrer-Policy / Permissions-Policy. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 85% raw-HTML coverage on home and 96% on product; neither is a JavaScript shell. |
be-resilientresilient-runtime-behaviour | issues | high | Custom fixed/absolute overlays and 950-1020 px layout modules are clipped or scaled on narrow screens; no anchor fallback positioning was found. F-034 medium: The page behaves robustly at runtime: overlays and menus never get cut off, DOM state survives moves, background work and async dependencies are sequenced and conditional rather than fragile, and initial visibility state is detected correctly. |
be-resilientoffline-and-installable | not-applicable | high | This marketplace depends on live inventory, pricing, identity and checkout; installability/offline operation was judged out of scope, while other resilience checks remain applicable. |
be-resilientnetwork-and-http-failure-states | pass | high | Despite several aborted optional ad/analytics requests in HAR, primary storefront content and navigation rendered in screenshots. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares html lang="ja" and Japanese reading order is correctly rendered. |
be-internationalisedlocale-aware-data | pass | high | Visible prices use yen formatting and campaign/ranking dates use Japanese locale conventions. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited storefront paths do not schedule user events or expose user-entered times; displayed campaign dates are locale labels rather than a cross-zone workflow. |
be-trustworthyno-dark-patterns | pass | high | Load and product evidence shows pricing and sold-out states directly; no consent wall, forced continuity or confirmshaming was observed on covered paths. |
be-trustworthyhumane-error-handling | pass | high | Product selection state explicitly labels required selections, unselected values and sold-out variants before checkout. |
be-trustworthytrustworthy-input-assistance | issues | high | The representative search field explicitly sets autocomplete="off" and has no associated visible label in the probe. F-035 low: Input is assisted, not obstructed: correct autocomplete tokens so address, payment, sign-in and sign-up fields autofill, and inputs are highlighted/sized to help the user rather than trip them up. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The product probe exposes the price range, shipping state, variant availability, cart and checkout as separate explicit actions. |
be-sustainableoptimised-assets | issues | high | HAR transferred 5.28 MB of images; 89/100 sampled images were legacy formats, 8 oversized and 14 lacked responsive sources. F-036 high: Images and decorative assets are optimised and served at appropriate resolutions; decorative pseudo-element imagery and heavy decorative images are resolution-optimised rather than oversized. |
be-sustainableno-wasteful-work | issues | high | The homepage made 731 requests with 146 scripts, including numerous advertising and analytics requests before interaction. F-037 high: Background work and fetching are not wasteful: background processing is efficient and de-prioritised, and the lightest technique that achieves the result is preferred over heavy or redundant work. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party-origin traffic accounted for 643 requests and 7.91 MB of the 8.04 MB load. F-038 high: Third-party scripts, fonts, video, audio, animation and heavy media are proportionate to the user value they provide; autoplay or background media is avoided unless essential and resource use is cached or deferred where possible. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No developer intent to expose agent-facing WebMCP capabilities was declared; this emerging check is contextual and not required for the storefront audit. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the audited paths requires on-device language-model or summarizer inference; this emerging capability is contextual. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After a fresh load plus 10 next/previous carousel cycles, the heap summary was 126.9 MB / 2.26M nodes versus a 71.7 MB / 1.19M-node baseline; separate-session timing makes this medium-confidence but warrants same-session leak tracing. F-039 medium: Repeating a representative interaction (open/close a modal, navigate a route and back, infinite-scroll a list) about 10 times does not grow retained heap without bound; what is allocated during the interaction is released when it ends. |
be-memory-efficientbounded-footprint | issues | high | A post-interaction snapshot contained 2.26M heap nodes and 126.9 MB self size for the homepage, disproportionate to the visible catalog landing page. F-040 high: Heap size and DOM node count are reasonable for what the page is; the footprint is proportionate rather than bloated. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary surfaced Detached* constructors among its reported top constructors; no direct detached-DOM signal was observed. |
Provenance
Canonical report: results/atomic/reports/0410-item_rakuten_co_jp.json
Report SHA-256: a800a7a614b652634991769e6380be4575bb85a8b0090bfb3df8f6df749ff303
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/item_rakuten_co_jp/2026-07-20T14-46-56-970Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/item_rakuten_co_jp/2026-07-20T14-46-56-970Z
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.