Manifest position 347 · CrUX rank bucket 1000
https://keirin.jp
Coverage complete
Coverage-complete model audit across desktop and mobile home templates plus schedule, voting, beginner guide, recovery, and 404 archetypes.
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-condition screenshot remains a light interface; colorScheme is normal, body is rgb(245,244,242), and no prefers-color-scheme rule was found. F01 medium: Add preference-driven dark theme |
respect-user-preferencesrespects-reduced-motion | pass | medium | The reduce preference matched and no active Web Animations or CSS reduced-motion-relevant animations were present after load. |
respect-user-preferencesrespects-contrast | pass | high | Under forced-colors: active, text and controls resolve to system black/white colors with visible borders; the screenshot remains operable. |
implement-natural-interactionsview-transitions | issues | high | Navigation between the homepage, schedule, voting list, guide, and recovery pages is an abrupt full-document swap; no view-transition CSS was found. F02 low: Make route changes preserve spatial continuity |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | The audited templates contain no parallax, scrollytelling, or scroll-linked reveal effect to implement. |
implement-natural-interactionsphysical-gestures | pass | medium | The tested pages use ordinary native scrolling and taps and expose no custom pointer-driven gesture that fights platform behavior. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The long homepage and schedule retain static chrome with no scroll-state query, progress cue, or conditional scroll affordance. F03 low: Add useful scroll-state navigation cues |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or tethered menu was present on the audited templates. |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs, selected day tabs, section headings, and the 404 top-page action visibly preserve orientation and direct the next step. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No full-screen interstitial, consent wall, or load-time overlay obscured content on any captured path. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No transient overlay or disclosure control was present on the audited paths. |
maximize-content-reduce-noisereduced-chrome | issues | high | The homepage devotes substantial space to repeated race chrome, sidebars, ticker copy, dense banners, borders, and tiny link lists, crowding the core schedule and voting actions. F04 medium: Refocus the homepage on current races and primary actions |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The desktop route has no viewport meta and renders as a 1263 CSS-pixel page scaled to 0.285; the dedicated mobile route disables zoom with user-scalable=0. F05 high: Replace scaled desktop rendering and restore zoom |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | No @container/container-type rules were found; separate /pc and /sp templates are shipped instead of reusable components adapting to available space. F06 medium: Consolidate PC/mobile templates around adaptive components |
adapt-to-the-form-factorinput-modality-aware | issues | high | The first focused control computes outline-style none, and visible controls as small as 18px high were measured, below robust touch-target sizing. F07 high: Restore visible focus and enlarge small targets |
support-core-task-successclear-purpose-and-primary-action | pass | high | Current races immediately expose LIVE and 投票 actions, while the schedule, voting list, beginner guide, and recovery page each state their purpose. |
support-core-task-successprimary-flow-completion | pass | medium | Representative public tasks are reachable with real links, schedule browsing exposes venue detail links, and recovery presents three explicit account-recovery branches. |
support-core-task-successclear-system-state-and-recovery | pass | high | Unavailable race actions are visibly disabled; a real 404 response shows a clear Japanese explanation and a top-page recovery button. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.2s and CLS 0.301; the independent trace measured LCP/FCP 3.65s. These miss good CWV thresholds. F08 high: Bring LCP and CLS into good ranges |
be-fast-and-stablevisual-stability | issues | high | Lighthouse measured CLS 0.301 and 98 of 100 desktop images lacked explicit dimensions, leaving widespread late-layout risk. F09 high: Reserve image and dynamic-content space |
be-fast-and-stableefficient-main-thread | pass | high | The trace recorded zero long tasks and 0ms TBT; Lighthouse also measured 0ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | The load transfers 3.0MB in 133 requests; nine parser-inserted stylesheets and many synchronous non-defer head scripts precede content, and large text resources are uncompressed. F10 high: Shorten the critical chain and compress resources |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 189KiB unused JS and 208KiB unused CSS, including 97% unused Bootstrap CSS; the HAR includes jQuery 1.11.3 and jQuery UI. F11 medium: Remove unused legacy CSS and JavaScript |
be-inclusivenames-roles-labels | issues | high | The page has missing alt attributes (Lighthouse examples and 72 DOM images without alt) and unlabeled search/login/recovery inputs. F12 high: Give controls and images accessible semantics |
be-inclusivesufficient-contrast | issues | high | Lighthouse found multiple failures, including cyan tab text at 2.83:1 and disabled LIVE text near 1.5:1. F13 high: Raise text and control contrast |
be-inclusivestructure-and-focus | issues | high | There is no h1 or main landmark, and the programmatically focused first control has no visible outline. F14 high: Add landmarks, h1, and robust focus styles |
be-inclusivelegible-text | issues | high | The desktop layout is highly dense; at 360px it is scaled down wholesale, making body links and status text extremely small and difficult to scan. F15 high: Reflow and simplify dense content at small widths |
be-inclusivezoom-reflow-targets-and-media | issues | high | The /sp viewport sets maximum-scale=1 and user-scalable=0, while the PC route scales a desktop canvas; several controls are only 18-22px high. F16 high: Allow zoom and meet target/reflow requirements |
follow-best-practicesno-console-errors | pass | high | Lighthouse reported no browser console errors during load. |
follow-best-practicessound-document-and-assets | issues | high | Doctype, charset and aspect ratio pass, but 98/100 images lack dimensions, 91 use legacy formats, and 77 below-fold images are not lazy-loaded. F17 medium: Add image dimensions and modern delivery attributes |
follow-best-practicesbrowser-platform-hygiene | issues | high | The mobile page is not BFCache eligible due to an unload handler and no-store responses, and ships legacy jQuery 1.11.3. F18 medium: Restore BFCache eligibility and retire legacy libraries |
be-discoverabletitle-and-description | pass | high | The title and descriptive meta description are present in both rendered and raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse reports crawlable anchors and valid robots.txt; representative navigation uses real hrefs and a dedicated mobile route exists. |
be-discoverablecanonical-and-indexing-signals | issues | high | Public pages return 200 and allowlisted robots paths, but no canonical was exposed and /sitemap.xml redirects to the homepage instead of serving a sitemap. F19 medium: Publish canonical URLs and a real sitemap |
be-discoverablestructured-and-shareable-metadata | issues | high | The sports/event homepage exposes zero JSON-LD blocks and zero Open Graph tags, so race/event entities and social previews lack structured metadata. F20 low: Add accurate event/organization and social metadata |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and nosniff/X-Frame-Options are present and no cookies were set, but CSP and HSTS are missing. F21 high: Deploy CSP and HSTS |
be-private-and-securedata-minimisation-and-third-parties | pass | high | All 133 observed requests were first-party; no known trackers, cookies, or exposed secrets were detected. |
be-private-and-securein-context-permissions-and-modern-auth | issues | medium | No load-time permission request was found, but the relevant account login exposes password-only authentication and no WebAuthn/passkey capability was detected. F22 medium: Offer passkey authentication |
be-private-and-securedefensive-browser-policies | issues | high | X-Frame-Options and nosniff are present, but HSTS, CSP, Referrer-Policy, and Permissions-Policy are all absent. F23 high: Complete defensive response policies |
be-resilientprogressive-enhancement | issues | high | Only 33% of rendered content words are present in raw HTML; substantial race content is lost without JavaScript even though the page is not an empty shell. F24 medium: Render core race information in server HTML |
be-resilientresilient-runtime-behaviour | pass | medium | The MPA routes loaded without runtime errors; no edge-clipped overlay exists and breadcrumb/top-page recovery preserves navigation context. |
be-resilientoffline-and-installable | not-applicable | high | Installability/offline transaction support is not expected for a live wagering and current-race service that intrinsically depends on real-time server state. |
be-resilientnetwork-and-http-failure-states | pass | high | A missing route returns HTTP 404 and presents a readable Japanese error with a prominent top-page recovery action. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | html lang is correctly ja and the Japanese left-to-right reading order is consistent across representative templates. |
be-internationalisedlocale-aware-data | pass | medium | Dates, month/day labels, years, and race times are consistently rendered in conventions appropriate to the declared Japanese locale. |
be-internationalisedtime-zone-correctness | pass | medium | All audited event times refer to domestic Japanese velodromes in a single national time zone; no cross-zone or DST-sensitive workflow was present. |
be-trustworthyno-dark-patterns | pass | high | No consent nag, disguised advertisement, confirmshaming, forced continuity, or preselected commercial option appeared; age and purchase-limit links are prominent. |
be-trustworthyhumane-error-handling | issues | high | Recovery inputs have no programmatic labels or required attributes and expose no semantic validation state, undermining timely, accessible error recovery. F25 high: Make recovery validation semantic and accessible |
be-trustworthytrustworthy-input-assistance | issues | high | Login has autocomplete off for the password and recovery fields have empty autocomplete values, preventing appropriate autofill assistance. F26 high: Use correct autocomplete tokens |
be-trustworthysafe-commercial-and-account-flows | pass | medium | The site prominently states the 20+ restriction and purchase-limit setting, and provides visible password recovery and account help before transaction entry. |
be-sustainableoptimised-assets | issues | high | The homepage downloads 96 images/1.44MB; 91 of 100 DOM images use PNG/JPEG/GIF, 77 below-fold images are eager, and responsive sources are largely absent. F27 medium: Modernise and defer image delivery |
be-sustainableno-wasteful-work | issues | high | The page eagerly fetches 133 resources and ships hundreds of KiB of unused CSS/JS, including multiple old UI libraries, despite zero measured main-thread need. F28 medium: Stop eager delivery of unused work |
be-sustainablethird-party-and-media-budget | issues | high | Third-party cost is zero, but total first-party transfer is still 3.0MB with 96 images, disproportionate to a schedule-and-links first viewport. F29 medium: Set a first-party page-weight budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent exists; this public information/wagering site does not currently expose a safe agent transaction surface, so absence is an opportunity rather than a failure. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, translation, or generative workflow requiring on-device inference was identified on the audited paths. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten bottom/top scroll cycles, the independently loaded post snapshot was 10.60MB/157,411 nodes versus baseline 10.50MB/155,557 nodes; the small bounded delta gives no evidence of runaway growth. |
be-memory-efficientbounded-footprint | pass | high | The loaded homepage heap is approximately 10.5MB with 155,557 nodes, proportionate to this dense but finite document. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The compact before/after heap summaries show no growing Detached* constructor population or order-of-magnitude node growth after repeated scrolling. |
Provenance
Canonical report: results/atomic/reports/0347-keirin_jp.json
Report SHA-256: 4e6a458fec4fe773ae0f0b959b49340dff74a4d3632b776f6372d848f217cc1a
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/keirin_jp/2026-07-20T03-16-42-691Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/keirin_jp/2026-07-20T03-16-42-691Z
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.