Manifest position 925 · CrUX rank bucket 1000
https://www.navitime.co.jp
Coverage complete
Atomic coverage is complete. Three linked representative destinations returned CloudFront 403 responses; those observed site failures are findings rather than untested checks.
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-preference screenshot is still white and green, and computed color-scheme is normal. F01 medium: The interface does not follow the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The reduced-motion probe matched the preference and the only active fade used a 0.01 ms duration, effectively removing motion. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse reports ratios of 3.16, 3.62 and 3.87 where 4.5:1 is required; the prefers-contrast capture remains visually unchanged. F02 medium: Several text colors fail minimum contrast and contrast preference does not materially adapt them. |
implement-natural-interactionsview-transitions | issues | high | The DOM/CSS probe found no view-transition rules, while route links navigate to abrupt full-page states including raw 403 pages. F03 low: Route changes use ordinary full navigations with no authored transition treatment. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No applicable surface was identified. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No applicable surface was identified. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Homepage screenshots and CSS inspection show persistent multi-row navigation; no scroll-state or scroll-timeline rules were found. F04 low: The large, dense global chrome remains static instead of adapting as the user scrolls. |
provide-guided-navigationanchored-positioning | not-applicable | high | No applicable surface was identified. |
provide-guided-navigationdirects-attention | issues | high | The platform probe found zero H1 and no main landmark; the first viewport includes multiple dense navigation rows and ads around the route form. F05 medium: The homepage lacks a page heading/main landmark and presents many competing navigation choices. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots show no modal, consent wall or full-viewport interstitial obscuring the route form. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The probe found zero dialog, popover and details elements, while resource inspection found vue-js-modal and custom modal assets. F06 medium: Rich controls rely on custom Vue modal/autocomplete code rather than native semantic overlay primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | The desktop first view devotes three navigation rows and an ad banner to chrome; the mobile view clips the same desktop composition. F07 medium: Navigation, promotional links and advertising crowd the primary route-search task. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Layout metrics report scrollWidth 769 versus visual viewport 360, producing 409 px overflow; controls and navigation are cut off in the screenshot. F08 critical: The homepage is a fixed desktop canvas on a 360 px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The live stylesheet probe found zero container rules, while the route form and nav remain desktop-sized in a 360 px viewport. F09 medium: Components do not adapt to their available container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe reports outline-style none on origin/destination inputs, date/time controls and the icon-only search button; the button also has no accessible name. F10 high: Keyboard focus is invisible on several primary controls. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first desktop view clearly presents origin, destination, time and a prominent green search action. |
support-core-task-successprimary-flow-completion | issues | high | Direct attempts to /transfer/, /maps/poi and the selected POI all produced raw CloudFront 403 pages, preventing end-to-end flow completion in this run. F11 critical: Representative transit, map and place-detail destinations fail with CloudFront 403 responses. |
support-core-task-successclear-system-state-and-recovery | issues | high | All three failed destinations show the generic CloudFront “request could not be satisfied” page with no retry, back, status or support action tailored to NAVITIME. F12 high: Failure states expose infrastructure text without useful recovery. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.3 s, TBT 530 ms, Speed Index 12.3 s and TTI 32.6 s; an independent trace observed LCP 7.56 s. F13 high: Loading performance misses the good LCP and responsiveness ranges. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observation measured CLS 0.033, within the good threshold; Lighthouse measured 0 in its run. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 530 ms TBT and 32.6 s TTI; the HAR contains 61 scripts. F14 high: Script execution and delayed interactivity are excessive. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR records 252 requests and 3.19 MB, seven parser-inserted stylesheets, multiple synchronous first-party scripts, and missing cache headers on large images/scripts. F15 high: The page has a heavy request graph and weak caching for important resources. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The HAR records 61 scripts and 69 third-party origins; resources include Vue 2-era plugins, multiple analytics stacks and ad bidders. F16 high: Third-party and legacy script volume dominates the load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse flags unnamed links and images without alt; the custom probe finds an unnamed icon search button and unlabeled controls. F17 high: Key controls and images lack accessible names or labels. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reports multiple failures, including #32a632 on white at 3.16:1 and grey text at 3.62:1. F18 medium: Text and UI colors fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse reports no main landmark; the homepage has no H1; multiple focused inputs and links have no visible outline. F19 high: Document structure and focus treatment do not support efficient keyboard or assistive-technology navigation. |
be-inclusivelegible-text | issues | high | At 360 px the 769 px layout cuts navigation labels, the route form and the search button off-screen. F20 high: Mobile text and controls are clipped rather than reflowed. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Homepage overflow is 409 px at 360 px; the maps route has no viewport meta and renders a 980 px desktop surface scaled down. F21 high: Key surfaces do not reflow for a narrow/zoomed viewport. |
follow-best-practicesno-console-errors | issues | high | Lighthouse records a third-party console.error, a blocked CORS XHR and failed/400 resources. F22 medium: The page logs runtime, CORS and network errors. |
follow-best-practicessound-document-and-assets | issues | high | The image audit finds 53 images without both dimensions, 23 oversized images and 35 legacy-format images; Lighthouse detects a distorted 864x1079 image shown at 188x140. F23 medium: Image markup and rendering are not consistently sound. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports deprecated Topics and Shared Storage usage from ad scripts; resources include axios 0.19.2 and several old Vue plugins. F24 medium: Deprecated APIs and aging client libraries remain in the dependency surface. |
be-discoverabletitle-and-description | pass | high | The homepage has a descriptive Japanese title and meta description, both also present in raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The homepage has 409 px horizontal overflow and /maps/poi lacks viewport metadata, despite crawlable href links. F25 high: The public site is not consistently mobile friendly across templates. |
be-discoverablecanonical-and-indexing-signals | pass | high | The homepage returns 200, declares a canonical URL, robots permits general crawling, and a public sitemap was successfully fetched. |
be-discoverablestructured-and-shareable-metadata | issues | high | The metadata probe found zero Open Graph tags and zero JSON-LD blocks on the public homepage. F26 medium: The homepage exposes no social preview or structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP and HSTS are absent; all 25 observed first-party cookies were flagged insecure and many use SameSite=None. F27 critical: Baseline transport defenses and cookie attributes are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker audit found 69 third-party origins and 25 known tracker domains; Lighthouse found 39 third-party cookies. F28 critical: The homepage has an exceptionally broad tracking and advertising footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The sign-in probe found a password field and no WebAuthn/Passkey usage; no permission prompt on load was detected. F29 high: Authentication is password-only and lacks phishing-resistant options. |
be-private-and-securedefensive-browser-policies | issues | high | Headers lack CSP/frame-ancestors or X-Frame-Options, HSTS, Referrer-Policy and Permissions-Policy; only nosniff is present. F30 critical: Browser-enforced defensive policies are largely absent. |
be-resilientprogressive-enhancement | issues | high | Discoverability comparison reports only 8% raw-HTML coverage; the crawler screenshot contains global chrome but omits the route task and recommendations, while category coverage is 100%. F31 high: Most homepage content is unavailable to non-JavaScript clients. |
be-resilientresilient-runtime-behaviour | pass | high | On the reachable homepage and category templates, repeated disclosure toggles and scrolling completed without a blank screen or cut-off modal; there were no active native overlays. |
be-resilientoffline-and-installable | not-applicable | high | No applicable surface was identified. |
be-resilientnetwork-and-http-failure-states | issues | high | Three representative destinations returned bare CloudFront 403 pages with no application recovery controls. F32 high: Network/HTTP failures fall through to raw infrastructure pages. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The probe confirms html lang=ja but finds zero logical-property rules in loaded stylesheets; the clipped mobile layout relies on physical desktop geometry. F33 medium: The Japanese document declares language but its CSS is not writing-mode adaptable. |
be-internationalisedlocale-aware-data | pass | high | Rendered date and time controls use Japanese ordering and units (2026年07月23日, 22時, 53分), and a Japanese Day.js locale resource is loaded. |
be-internationalisedtime-zone-correctness | not-applicable | high | No applicable surface was identified. |
be-trustworthyno-dark-patterns | pass | high | The reachable homepage and sign-in page show straightforward labels and no consent wall, confirmshaming, preselected purchase or forced-continuity prompt. |
be-trustworthyhumane-error-handling | issues | high | After an empty submit attempt the screenshot is visually unchanged; login/password inputs also omit autocomplete tokens and rely on placeholders. F34 high: Empty sign-in submission does not reveal clear, visible recovery guidance. |
be-trustworthytrustworthy-input-assistance | issues | high | Homepage route inputs use autocomplete=off; sign-in ID/password fields have empty autocomplete values instead of username/current-password. F35 high: Route and sign-in inputs disable or omit useful autocomplete semantics. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The sign-in page offers NAVITIME ID/password and Yahoo login; the probe found no WebAuthn/Passkey capability. F36 medium: The account flow relies on password authentication without a visible phishing-resistant option. |
be-sustainableoptimised-assets | issues | high | The image audit finds 23 oversized images, 18 without srcset and 35 legacy-format images; one 334 KB image lacks cache headers. F37 high: Images are frequently oversized, unresponsive or legacy-format. |
be-sustainableno-wasteful-work | issues | high | The homepage makes 252 requests, including 90 XHR/fetch calls, across 69 third-party origins, with several failed or redirected ad-tech requests. F38 high: Advertising and analytics create substantial background network work. |
be-sustainablethird-party-and-media-budget | issues | high | The HAR transfers 3.19 MB with 61 scripts; the tracker inventory finds 69 third-party origins and 25 known trackers. F39 critical: Third-party scripts and advertising are disproportionate to the navigation task. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No applicable surface was identified. |
be-agent-readyon-device-inference | not-applicable | high | No applicable surface was identified. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten repeated detail-toggle and scroll interactions, heap self-size changed from 49,454,661 to 49,603,746 bytes (about 0.3%) and total snapshot nodes decreased, providing no evidence of unbounded retained growth. |
be-memory-efficientbounded-footprint | pass | high | The runtime probe measured about 44.4 MB used JavaScript heap and 1,701 DOM elements; the heap snapshot was about 49.5 MB, substantial but bounded for this ad/script-heavy page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The before/after heap summaries show no Detached* constructor among top retained constructors and no total-node growth after ten interactions. |
Provenance
Canonical report: results/atomic/reports/0925-www_navitime_co_jp.json
Report SHA-256: d62ab0c72a8b481da1c951c2a2d873e711eb5e4f00b287473154ee3355287e76
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_navitime_co_jp/2026-07-23T21-48-40-375Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_navitime_co_jp/2026-07-23T21-48-40-375Z
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.