Manifest position 209 · CrUX rank bucket 1000
https://beauty.hotpepper.jp
Coverage complete
Coverage-complete report across seven representative paths. Real reservation submission was intentionally not performed; the flow was inspected through its coupon/menu entry and four-step structure.
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 dark-mode screenshot is pixel-identical to the light capture; the probe reports colorScheme "normal", light foreground colours, and no prefers-color-scheme CSS. F01 high: Dark preference is ignored |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned no active animations, so no nonessential motion remained. |
respect-user-preferencesrespects-contrast | issues | high | The CSS preference probe found no forced-colors or prefers-contrast rules; Lighthouse also found two ordinary-state controls at only 3.42:1. F02 medium: Contrast preferences are unsupported |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection across the MPA templates found no view-transition-name or @view-transition usage. F03 low: Route and state changes are abrupt |
implement-natural-interactionsscroll-driven-animations | not-applicable | medium | No scroll-linked animation, parallax, scrollytelling, carousel slide effect, or reveal animation was present to implement. |
implement-natural-interactionsphysical-gestures | not-applicable | medium | No swipe, pull, drag, or other gesture-driven control was present on the representative paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The homepage is 4,570 CSS px tall, while CSS inspection found no scroll-state container query, progress indicator, or responsive sticky-header treatment. F04 low: Long pages provide no scroll-state-aware chrome |
provide-guided-navigationanchored-positioning | not-applicable | medium | No tooltip, attached popover, or edge-sensitive context menu was found on the tested paths. |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs on listing/detail pages, explicit four-step booking progress, and repeated labelled reservation links preserve location and next action. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The desktop and mobile first-load screenshots show a gender-selection panel covering the search interface before user interaction. F05 high: A large modal obscures the primary content on arrival |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The overlay is visible in screenshots, but the DOM probe found no dialog or role=dialog element. F06 medium: The blocking overlay is not a semantic dialog |
maximize-content-reduce-noisereduced-chrome | issues | high | The first viewport devotes both side rails to animated campaign creative, adds a centered overlay, dense tab chrome, and a right account rail around a narrow content column. F07 medium: Advertising and dense chrome crowd the content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x800 viewport the layout reports no viewport meta and a 1,311px layout viewport; the screenshot shows the entire desktop page shrunk to unreadable size. F08 critical: Mobile receives a scaled desktop page |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found no @container rules, and every representative mobile screenshot shows desktop components uniformly scaled rather than reorganised. F09 medium: Components do not respond to available container space |
adapt-to-the-form-factorinput-modality-aware | issues | high | The objective probe measured 495 of 511 visible controls below 44px in at least one dimension; many links are 11-18px tall. F10 high: Most controls are smaller than touch guidance |
support-core-task-successclear-purpose-and-primary-action | pass | high | Each representative page has a descriptive Japanese h1/title; salon pages repeat an explicit 空席確認・予約する action. |
support-core-task-successprimary-flow-completion | pass | high | The salon CTA reaches a clearly priced coupon-selection page with a visible STEP1–STEP4 booking sequence and labelled controls, without an account wall at entry. |
support-core-task-successclear-system-state-and-recovery | pass | high | A deliberately invalid route produced a specific not-found title, explanation, top-page recovery link, and alternate service links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 35.5s, TBT 960ms, Speed Index 9.9s, and performance 0.37; the separate trace measured LCP 1.93s under a lighter run, showing condition sensitivity but not negating the throttled result. F11 critical: Measured mobile load performance is poor |
be-fast-and-stablevisual-stability | pass | high | Layout observation reported CLS 0 with no shifts in its window; Lighthouse measured CLS 0.068, within the good range. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 960ms TBT; the trace also recorded two long tasks, while the page loads 94 scripts. F12 high: JavaScript blocks the main thread under mobile conditions |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR identified two VeryHigh parser stylesheets, several parser-inserted classic scripts, 353 requests, missing cache headers, and a 2.14s document request. DOM confirmation shows the core CSS in head. F13 high: Critical delivery is burdened by parser-blocking resources and weak caching |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 1,327 KiB unused JavaScript; the HAR transfers 3.34MB of scripts and shows repeated tag destinations and duplicated vendor loads. F14 high: The page ships large unused and duplicated script payloads |
be-inclusivenames-roles-labels | issues | high | The image primitive reports 71 images without alt and the DOM probe found 29 empty anchors without text, aria-label, or image alt. F15 high: Many image links lack a programmatic name |
be-inclusivesufficient-contrast | issues | high | Lighthouse found two controls at 3.42:1 (#fff on #d36985), below the required 4.5:1 for their text size. F16 high: Key app-install controls fail text contrast |
be-inclusivestructure-and-focus | issues | high | The probe found zero main/nav/header/footer/role landmarks and multiple empty headings; Lighthouse found a skipped heading level. F17 high: Semantic structure is weak despite visible browser focus |
be-inclusivelegible-text | issues | high | The 360px screenshots show desktop text compressed to only a few pixels because the page is scaled instead of reflowed. F18 critical: Text is unreadable at a common mobile viewport |
be-inclusivezoom-reflow-targets-and-media | issues | high | No viewport meta is present; at 360px Chrome creates a 1,311px layout viewport and scales it to 0.275, preventing usable reflow. F19 critical: The page does not reflow for mobile or zoom |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured four CORS/network console errors from Yahoo analytics during load. F20 medium: Third-party analytics generate console errors |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse’s mobile document reported quirks-mode/no doctype, while the desktop probe found HTML doctype, indicating variant inconsistency; 42 images lack dimensions. F21 medium: Document and image asset hygiene is inconsistent |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse recorded a deprecated Attribution Reporting API warning and failed third-party integrations; 28 javascript: links replace normal platform controls. F22 medium: Deprecated and redundant integrations reduce platform hygiene |
be-discoverabletitle-and-description | pass | high | Homepage, listing, salon, style, booking, and login probes all returned specific titles; the homepage has a detailed meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The probe counted 28 javascript: links; Lighthouse listed 11 uncrawlable anchors, and no viewport meta exists. F23 high: Many controls are uncrawlable and the page lacks mobile viewport metadata |
be-discoverablecanonical-and-indexing-signals | pass | high | Public pages return 200, expose self-canonicals, robots allows public templates, and sitemap.xml is a current sitemap index. |
be-discoverablestructured-and-shareable-metadata | issues | high | The metadata probe found no Open Graph, Twitter card, or JSON-LD on the homepage, although salon/detail templates do expose JSON-LD. F24 medium: The homepage lacks share and organization metadata |
be-private-and-securesecure-transport-and-headers | issues | high | The page is HTTPS, but CSP, HSTS, nosniff, frame protection, Referrer-Policy and Permissions-Policy are absent; 44 cookies were flagged insecure and HPB_SESSION_ID is SameSite=None. F25 critical: Transport hardening and cookie policy are unsafe |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe saw 55 third-party origins and eight known tracker domains; 337/353 HAR requests and 4.54MB/4.66MB transferred were classified third-party. F26 critical: Tracking is exceptionally broad on first load |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission request calls were found on load; Recruit login uses username/current-password webauthn autocomplete and a passkey availability field. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive found no HSTS, clickjacking defense, Referrer-Policy, Permissions-Policy, or CSP frame-ancestors. F27 high: Browser-enforced defensive policies are absent |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 93% raw/rendered content overlap, with title, h1 and description present without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | MPA links and forms retained stable server-rendered state across tested listing, detail, style, booking and login paths; no clipped transient menu was observed. |
be-resilientoffline-and-installable | not-applicable | medium | This multi-page marketplace booking service depends on live inventory and is not presented as an installable app; offline booking would be misleading. |
be-resilientnetwork-and-http-failure-states | pass | high | The tested 404 state explains the error and offers direct recovery links to top and service categories. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The homepage correctly declares lang=ja, but the CSS probe found zero logical-property rules versus 25 physical left/right/width/height rules; the Recruit login redirect declares en-GB for Japanese copy. F28 medium: Layout CSS is not writing-mode resilient |
be-internationalisedlocale-aware-data | pass | high | Representative pages render Japanese dates and yen prices with Japanese labels consistently across listing and booking templates. |
be-internationalisedtime-zone-correctness | not-applicable | medium | The audited Japanese salon flow exposes local calendar dates only and no cross-zone event or stored time representation. |
be-trustworthyno-dark-patterns | pass | high | Prices, coupon conditions, membership links and booking commitments are stated directly; no preselected paid option or confirmshaming was observed. |
be-trustworthyhumane-error-handling | pass | high | Search and booking controls use native form elements and labels; no premature validation or blaming language appeared in the tested states. |
be-trustworthytrustworthy-input-assistance | pass | high | Recruit sign-in uses autocomplete="username webauthn" and "current-password webauthn", supporting password managers and passkeys. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Salon/detail/booking pages show price and conditions before selection, a four-step confirmation flow, and passkey-aware sign-in fields. |
be-sustainableoptimised-assets | issues | high | Of 100 images, 86 use legacy formats, none use modern formats, 59 below-fold images are not lazy, and 35 lack srcset. F29 high: Image delivery uses legacy, eager, nonresponsive assets |
be-sustainableno-wasteful-work | issues | high | The page makes 353 requests, including 94 scripts and 70 fetches, with repeated analytics destinations and failed beacon traffic on first load. F30 high: Background marketing work dominates the load |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 4.54MB of 4.66MB transferred; Google Tag Manager alone contributes 2.31MB. F31 critical: Third-party scripts consume nearly the entire transfer budget |
be-agent-readystructured-agent-capabilities | issues | high | The page is 93% visible without JS, but the capability probe found no WebMCP registration; agents must infer actions from hundreds of links and forms. F32 low: The booking service exposes no structured agent capability |
be-agent-readyon-device-inference | not-applicable | medium | No summarisation, freeform generation, or other task was observed where local model inference is necessary to complete the booking journey. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten scroll/modal-close attempts, heap self size increased only 0.33% (49,896,605 to 50,063,435 bytes); no unbounded retained growth was observed. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap contains 886,774 nodes and 49.9MB self size before meaningful interaction. F33 medium: The static homepage has a disproportionately large heap footprint |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Native-node count decreased slightly and no Detached* constructor appeared among heap summary leaders; the comparison showed no direct detached-DOM growth signal. |
Provenance
Canonical report: results/atomic/reports/0209-beauty_hotpepper_jp.json
Report SHA-256: 5eee7ab00729c89bf917dd749dba90f27c0a04474b191a849e9bbea2a78f09ff
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/beauty_hotpepper_jp/2026-07-19T04-32-09-138Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/beauty_hotpepper_jp/2026-07-19T04-32-09-138Z
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.