Manifest position 429 · CrUX rank bucket 1000
https://race.sp.netkeiba.com
Coverage complete
Coverage-complete multi-path remote audit; no source was provided and no fixes were applied.
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 | Computed color-scheme is normal and the dark-preference screenshot remains light, with the same white consent and content surfaces. F001 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, two bell_active animations still run for 5 seconds and many 0.2–0.5s transitions remain enabled. F002 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 found multiple WCAG contrast failures, including white GIII text on #58af4a at 2.74:1. F003 high: Honours prefers-contrast / forced-colors: controls, text and scrollbars remain visible under high-contrast preferences. |
implement-natural-interactionsview-transitions | issues | high | Platform probe found no view-transition usage; navigation and content-state changes use abrupt legacy swaps. F004 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 | not-applicable | medium | No parallax, scrollytelling, or scroll-linked animation surface was found on the representative pages, so there is no scroll-linked motion implementation to judge. |
implement-natural-interactionsphysical-gestures | issues | high | The carousel uses Slick controls but no CSS scroll snap or overscroll primitive was detected. F005 low: Gesture-driven interactions and entry/exit motion feel native (declarative overscroll/scroll-snap, physics-based easing, animating to intrinsic sizes, pull/swipe gestures) rather than fighting the platform with custom pointer handlers. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long 4,505px page has static header chrome and no container/scroll-state implementation in the DOM/CSS probe. F006 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 | not-applicable | medium | No tooltip or edge-sensitive anchored popover was found on the representative race surfaces. |
provide-guided-navigationdirects-attention | pass | medium | Screenshots show the active レース navigation item with an underline and race-list controls provide visible directional affordances. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | On every first-visit capture, a near-full-viewport consent modal obscures the race content before interaction. F007 high: No intrusive pop-ups, interstitials or banners that obscure content on load; overlays are dismissible and content-first. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The rendered page has zero dialog, popover, and details elements although the consent UI is modal and custom controls are extensive. F008 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 | The first viewport is dominated by app promotion, two navigation bars, and the consent layer rather than race data. F009 medium: 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 | pass | high | At 390px, layout metrics report scrollWidth=clientWidth=390 and zero horizontal overflow; viewport meta is present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | No container-query rules were detected; the mobile-specific page relies on global/mobile templates rather than reusable container adaptation. F010 low: 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 found unnamed links and an unnamed submit input; 32 javascript: anchors act as controls, weakening keyboard semantics and focus clarity. F011 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 | pass | high | The race card title, date, venue, distance, runners, odds and tabs are explicit in the rendered text and table structure. |
support-core-task-successprimary-flow-completion | issues | high | The race list, odds, and race-card paths are all blocked on first visit by consent; rejection requires the secondary Manage options path. F012 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 | issues | high | The tested missing route returns only “Not Found” with no navigation, explanation, retry, or route recovery. F013 medium: Loading, empty, success, error, offline, and partial-completion states are visible and actionable; users can retry, undo, cancel, go back, or continue without losing context. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 12.4s, TBT 795ms and performance 0.42; the independent trace measured LCP 4.68s. Both LCP results miss the good threshold. F014 high: 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 | pass | high | The layout observer measured CLS 0.023, within the good range, with only small shifts. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reported 795ms total blocking time and 23.6s to interactive despite the shorter trace window finding no long task. F015 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 recorded 282 requests and 3.12MB, including many parser-inserted VeryHigh-priority stylesheets and missing cache headers. F016 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 | Lighthouse estimated 733KiB unused JavaScript and 161KiB unused CSS; repeated GTM/gtag and ad bundles dominate script transfer. F017 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 image-alt, input-button-name and link-name; the image probe found 57 of 85 images without alt text. F018 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 | Automated contrast testing found failures as low as 2.74:1 for small text. F019 high: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | The document has no html lang, no main landmark in the platform probe, five H1 elements after CMP injection, and unnamed focusable links. F020 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 | The mobile UI uses dense race chrome and Lighthouse flags 9–12px labels with weak contrast, reducing reading comfort. F021 medium: 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 fails the viewport audit because maximum-scale=1 limits zoom; it also reports accessibility failures on controls. F022 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 recorded repeated CORS failures from ad.ad-stir.com and aladdin.genieesspv.jp. F023 medium: The page loads without console errors or uncaught exceptions. |
follow-best-practicessound-document-and-assets | issues | high | Image audit found 75/85 images missing one or both dimensions and Lighthouse found incorrect aspect ratios. F024 medium: 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 reports a deprecated Topics API call, inspector issues and a BFCache failure signal. F025 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 | The page has a descriptive Japanese title and a race-specific meta description in both raw and rendered HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The platform probe found 32 javascript: links; Lighthouse failed crawlable anchors and the viewport uses maximum-scale=1. F026 medium: 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 | Main response was 200, robots.txt allows crawling, and canonical metadata is present; no noindex was observed. |
be-discoverablestructured-and-shareable-metadata | issues | high | The listing declares og:type=article and no JSON-LD was observed, so share/entity metadata does not accurately model a race listing/event surface. F027 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, nosniff, clickjacking protection, Referrer-Policy and Permissions-Policy are all absent; all 14 observed first-party cookies lack Secure. F028 critical: 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 | Tracker capture found 56 third-party origins and 18 known tracker domains; HAR attributed 274/282 requests and 3.08MB to third parties. F029 critical: 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 | issues | high | The account page exposes password-only inputs with no autocomplete tokens and no WebAuthn/passkey implementation detected. F030 high: Permission prompts are requested in context (not on load), and authentication uses modern, phishing-resistant methods (passkeys / WebAuthn) where relevant rather than passwords alone. |
be-private-and-securedefensive-browser-policies | issues | high | Header inspection found no clickjacking, HSTS, referrer, permissions or CSP defenses, and Lighthouse observed ten third-party cookies. F031 critical: 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 | issues | high | The no-JavaScript crawler received only 21% rendered-content coverage and the crawler screenshot shows navigation plus a loader rather than race data. F032 high: Core content and primary flows are reachable and usable without JavaScript and on older or non-Baseline browsers; modern features layer on as enhancements with fallbacks, and reactive/transition state stabilises rather than flickering before it settles. |
be-resilientresilient-runtime-behaviour | issues | high | The HAR recorded 52 status-0 requests and one 502 while Lighthouse logged repeated third-party CORS errors. F033 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 | issues | high | The race service is app-like and service-worker capable, but no web app manifest was linked; installability/offline fallback was not exposed. F034 low: Where the site is an app, it is installable (web app manifest) and offers an offline fallback and works on flaky networks. (Contextual: a brochure or intrinsically-online site may reasonably not need this.) |
be-resilientnetwork-and-http-failure-states | issues | high | The representative missing route renders bare “Not Found” and offers no recovery action. F035 medium: HTTP errors, network failures, timeouts and stale data states are handled intentionally: users see useful recovery options rather than blank screens, infinite spinners, broken shells, or misleading success states. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The Japanese page has an empty html lang attribute; Lighthouse independently failed html-has-lang. F036 high: Correct lang and dir attributes, logical CSS properties (inline/block) rather than physical left/right, and translation-ready markup so the layout and reading order survive other languages and writing modes. |
be-internationalisedlocale-aware-data | not-applicable | medium | The audited service is deliberately Japanese-only and did not expose currency, user-entered locale data, or locale selection in the representative public race paths. |
be-internationalisedtime-zone-correctness | not-applicable | medium | Race times are venue-local schedule labels and no cross-zone scheduling or user-editable time concept was exposed in the audited paths. |
be-trustworthyno-dark-patterns | issues | high | The consent first layer offers Consent and Manage options but no direct Reject all, while describing sharing with 214 partners and precise geolocation. F037 high: No deceptive design: no confirmshaming, forced continuity, disguised ads, or nagging consent walls; honest defaults; clear pricing and consent; easy reversal/cancel; predictable, declaratively-wired actions; and no hidden-text tricks (hidden content stays deep-linkable and indexable rather than used to deceive). |
be-trustworthyhumane-error-handling | not-applicable | medium | The representative public race paths contain no user-submitted validation form; account submission was not attempted with credentials. |
be-trustworthytrustworthy-input-assistance | issues | high | The login ID and password fields have empty autocomplete attributes. F038 medium: 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 | issues | high | The race card promotes a 14-day free premium trial without the ongoing price or cancellation commitment visible in the captured context. F039 medium: Checkout, subscription, consent, authentication and account-management flows are clear, reversible, and proportionate: pricing and commitments are visible, cancellation is findable, sensitive actions re-authenticate when appropriate, and users are not tricked into continuity. |
be-sustainableoptimised-assets | issues | high | Image audit found 84/85 legacy-format images, zero modern-format images, 15 oversized images, and 27 below-fold images without lazy loading. F040 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 | HAR recorded 282 requests including 116 fetch/XHR calls and multiple slow ad/affiliate requests during initial load. F041 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 parties account for 274 requests and 3.08MB of 3.12MB transferred, disproportionate to the core text/table experience. F042 critical: 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 | medium | No declared agent-facing intent or transactional agent surface was present; this emerging capability is outside the current public race-page scope. |
be-agent-readyon-device-inference | not-applicable | medium | No experience requiring on-device inference was identified; absence is not a failure for this content and race-data site. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten carousel advances, retained heap increased only about 72KB (52,842,648 to 52,914,797 bytes); closures rose by 3 and arrays by 22, not an unbounded-growth signal. |
be-memory-efficientbounded-footprint | issues | high | A single homepage state retained about 52.8MB across roughly 1,000,010 heap nodes, a high footprint for a race listing dominated by text and tables. F043 medium: 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 | The before/after summaries show stable closures (45,439 to 45,442), promises (401 to 399), and no Detached* constructor among top retained constructors. |
Provenance
Canonical report: results/atomic/reports/0429-race_sp_netkeiba_com.json
Report SHA-256: 98438fb3b094c7352884cb468226cc33fd6dec8f11753dadcfa790eed15dc574
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/race_sp_netkeiba_com/2026-07-20T18-31-48-445Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/race_sp_netkeiba_com/2026-07-20T18-31-48-445Z
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.