Manifest position 883 · CrUX rank bucket 1000
https://www.carsensor.net
Coverage complete
Coverage-complete representative-template audit. Excluded: login/account internals, actual dealer enquiry submission, purchase completion and private member pages, because they require credentials or would create real external side effects.
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 light and dark preference screenshots are pixel-identical (654,292 bytes each); the white navigation and orange/white surfaces do not retint under prefers-color-scheme: dark. F001 medium: The site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, matchMedia matched and getAnimations() returned no active animations; no auto-advance motion was observed in the captured first viewport. |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast: more screenshot retained visible text, controls and boundaries; independent contrast defects are recorded under be-inclusive. |
implement-natural-interactionsview-transitions | issues | high | The DOM/CSS probe found no view-transition usage; the site is an MPA with conventional full-document route changes. F002 low: Route and state changes use abrupt legacy navigation rather than View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked animation was observed and the probe found no animation-timeline usage, so no main-thread scroll animation anti-pattern was present. |
implement-natural-interactionsphysical-gestures | issues | high | The detail page instructs users to swipe, while the computed-style probe found zero scroll-snap elements and custom touch-action on four elements. F003 low: The vehicle gallery’s swipe interaction is custom rather than platform-native scrolling. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Screenshots showed no persistent sticky chrome obscuring content; scroll position did not create an orientation loss on representative templates. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or viewport-edge popover was present on the representative paths; anchor positioning has no applicable target in the observed surfaces. |
provide-guided-navigationdirects-attention | pass | high | Home, listing, detail and article templates provide visible headings and breadcrumbs that identify location and next content. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The desktop homepage screenshot shows a fixed ¥10,000 campaign banner covering the bottom-right of the search/content area; the close button is only 32px wide and has no accessible name. F004 medium: Promotional chrome competes with content and overlays the viewport. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM probes found 0 dialog, popover, and details elements but many custom Slick controls; Lighthouse reports invalid carousel ARIA, focusable controls inside aria-hidden slides, and malformed lists. F005 medium: Interactive chrome relies on ad-hoc legacy widgets rather than semantic modern primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | The desktop homepage screenshot shows a fixed ¥10,000 campaign banner covering the bottom-right of the search/content area; the close button is only 32px wide and has no accessible name. F004 medium: Promotional chrome competes with content and overlays the viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360px visual viewport, layout measured 1,103px homepage content width (743px overflow) and 1,080px listing width (720px overflow). Mobile screenshots clip the search flow, vehicle image, filters, and render the article as a tiny desktop page. F006 critical: Desktop-width templates are exposed at mobile viewports, making core browsing and reading horizontally clipped. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | At a 360px visual viewport, layout measured 1,103px homepage content width (743px overflow) and 1,080px listing width (720px overflow). Mobile screenshots clip the search flow, vehicle image, filters, and render the article as a tiny desktop page. F006 critical: Desktop-width templates are exposed at mobile viewports, making core browsing and reading horizontally clipped. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The first focusable link computed to outline-style none; Lighthouse reports insufficient target sizing and a viewport containing user-scalable=no, which blocks user zoom. F007 high: Input modality and zoom support are inadequate. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport clearly communicates used-car search and exposes manufacturer, region, price and search actions. |
support-core-task-successprimary-flow-completion | issues | high | At a 360px visual viewport, layout measured 1,103px homepage content width (743px overflow) and 1,080px listing width (720px overflow). Mobile screenshots clip the search flow, vehicle image, filters, and render the article as a tiny desktop page. F006 critical: Desktop-width templates are exposed at mobile viewports, making core browsing and reading horizontally clipped. |
support-core-task-successclear-system-state-and-recovery | pass | high | The invalid route renders a clear Japanese error, a homepage link and two alternate search methods instead of a blank or broken shell. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured performance 0.43, FCP 4.0s, LCP 8.1s, TBT 520ms, Speed Index 12.9s and CLS 0.082; the independent trace measured LCP 7.07s. F008 high: The homepage misses the Core Web Vitals performance bar. |
be-fast-and-stablevisual-stability | pass | high | Lighthouse measured CLS 0.082 (good range) and the layout observer measured CLS 0 in its observation window. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured performance 0.43, FCP 4.0s, LCP 8.1s, TBT 520ms, Speed Index 12.9s and CLS 0.082; the independent trace measured LCP 7.07s. F008 high: The homepage misses the Core Web Vitals performance bar. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 260 requests and 4,834,063 transferred bytes: 94 scripts/2.74MB, 192 third-party requests/2.64MB. Images found 45 legacy formats, 41 without srcset, 15 oversized and 50 below-fold images without native lazy loading. F009 high: Resource delivery is dominated by scripts, third parties and oversized legacy imagery. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR captured 260 requests and 4,834,063 transferred bytes: 94 scripts/2.74MB, 192 third-party requests/2.64MB. Images found 45 legacy formats, 41 without srcset, 15 oversized and 50 below-fold images without native lazy loading. F009 high: Resource delivery is dominated by scripts, third parties and oversized legacy imagery. |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility scored 0.55 and found invalid carousel ARIA, five hidden-but-focusable slide controls, unnamed buttons/links/selects, malformed lists and no main landmark; the direct homepage probe counted 67 unnamed buttons. F010 high: Core controls and document structure have substantial accessibility failures. |
be-inclusivesufficient-contrast | issues | high | Lighthouse identified five failures, including #808080 on white at 3.94:1 and orange price text on white at 3.02:1. F011 medium: Some text and prices fail minimum color contrast. |
be-inclusivestructure-and-focus | issues | high | The first focusable link computed to outline-style none; Lighthouse reports insufficient target sizing and a viewport containing user-scalable=no, which blocks user zoom. Lighthouse accessibility scored 0.55 and found invalid carousel ARIA, five hidden-but-focusable slide controls, unnamed buttons/links/selects, malformed lists and no main landmark; the direct homepage probe counted 67 unnamed buttons. F007 high: Input modality and zoom support are inadequate. F010 high: Core controls and document structure have substantial accessibility failures. |
be-inclusivelegible-text | issues | high | At a 360px visual viewport, layout measured 1,103px homepage content width (743px overflow) and 1,080px listing width (720px overflow). Mobile screenshots clip the search flow, vehicle image, filters, and render the article as a tiny desktop page. F006 critical: Desktop-width templates are exposed at mobile viewports, making core browsing and reading horizontally clipped. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At a 360px visual viewport, layout measured 1,103px homepage content width (743px overflow) and 1,080px listing width (720px overflow). Mobile screenshots clip the search flow, vehicle image, filters, and render the article as a tiny desktop page. The first focusable link computed to outline-style none; Lighthouse reports insufficient target sizing and a viewport containing user-scalable=no, which blocks user zoom. F006 critical: Desktop-width templates are exposed at mobile viewports, making core browsing and reading horizontally clipped. F007 high: Input modality and zoom support are inadequate. |
follow-best-practicesno-console-errors | issues | high | Lighthouse best-practices scored 0.54, reported browser console errors, a deprecated API warning, inspector issues and blocked third-party script requests. F012 medium: The page emits runtime and platform hygiene errors. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 7 images without both dimensions and 10 without useful alt coverage (including 4 with no alt attribute in the direct probe), alongside distorted/oversized candidates. F013 medium: Image markup is incomplete and inefficient. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse best-practices scored 0.54, reported browser console errors, a deprecated API warning, inspector issues and blocked third-party script requests. F012 medium: The page emits runtime and platform hygiene errors. |
be-discoverabletitle-and-description | pass | high | Home, listing, detail and article probes found unique descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The homepage recon includes “スマホ用ページを見る” and “ログイン” anchors with javascript:void(0), and Lighthouse failed crawlable-anchors. F014 low: Some navigation actions are not crawlable links. |
be-discoverablecanonical-and-indexing-signals | pass | high | Representative pages returned 200, exposed canonical URLs, and robots.txt lists extensive template-specific sitemap indexes without blocking audited public paths. |
be-discoverablestructured-and-shareable-metadata | pass | high | Home/listing/detail/article each expose JSON-LD; detail and article expose content-matched Open Graph title/image metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive found no CSP, HSTS, nosniff, clickjacking defense, Referrer-Policy or Permissions-Policy. Cookie inspection found 43 of 44 cookies without Secure and widespread SameSite=None. F015 high: The main document lacks baseline browser-enforced security headers and most cookies are insecurely scoped. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker capture observed 72 third-party origins and 12 known tracker domains. HAR attributes 192 requests and 2.64MB to third parties, including Google Tag Manager, Facebook, TikTok, DoubleClick and Criteo. F016 high: Tracking and advertising integrations create a disproportionate privacy footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No browser permission prompt appeared on load across the representative paths; authenticated account internals were not needed for the public browse journey. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive found no CSP, HSTS, nosniff, clickjacking defense, Referrer-Policy or Permissions-Policy. Cookie inspection found 43 of 44 cookies without Secure and widespread SameSite=None. F015 high: The main document lacks baseline browser-enforced security headers and most cookies are insecurely scoped. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 94% raw-HTML coverage on home and 100% on detail, with title/description and core content available without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Representative menus/content loaded to stable usable states; no clipped open overlay or broken async shell was observed beyond the separately reported mobile layout defect. |
be-resilientoffline-and-installable | not-applicable | high | The audited public marketplace is intrinsically network-backed and was not presented as an installable app; offline/installability is contextual. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately invalid URL produced a clear error message, homepage recovery link and alternative vehicle searches. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | The service is explicitly Japan-only and Japanese-language; no alternate-locale intent or variant was exposed. |
be-internationalisedlocale-aware-data | not-applicable | high | The service is explicitly Japan-only and displayed only Japanese yen/local values; multi-locale formatting is outside the observed intent. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduled cross-time-zone events or user-entered time concepts were present on the representative paths. |
be-trustworthyno-dark-patterns | pass | high | Pricing and vehicle identity were visible on the detail page and no forced-continuity, confirmshaming or disguised-ad interaction was observed. |
be-trustworthyhumane-error-handling | pass | high | Search controls accept an empty/default state without premature blame; native validation remains enabled on all five listing forms and the 404 state gives actionable recovery. |
be-trustworthytrustworthy-input-assistance | issues | high | The detail probe found 16 of 22 visible controls without a programmatic label and zero autocomplete attributes; the listing has 746 visible controls with no autocomplete and one unlabelled control. F017 medium: Enquiry and search controls lack robust input assistance. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The representative detail page visibly presents vehicle price and seller context before enquiry; no forced purchase/subscription step was encountered. |
be-sustainableoptimised-assets | issues | high | HAR captured 260 requests and 4,834,063 transferred bytes: 94 scripts/2.74MB, 192 third-party requests/2.64MB. Images found 45 legacy formats, 41 without srcset, 15 oversized and 50 below-fold images without native lazy loading. F009 high: Resource delivery is dominated by scripts, third parties and oversized legacy imagery. |
be-sustainableno-wasteful-work | issues | high | HAR captured 260 requests and 4,834,063 transferred bytes: 94 scripts/2.74MB, 192 third-party requests/2.64MB. Images found 45 legacy formats, 41 without srcset, 15 oversized and 50 below-fold images without native lazy loading. F009 high: Resource delivery is dominated by scripts, third parties and oversized legacy imagery. |
be-sustainablethird-party-and-media-budget | issues | high | HAR captured 260 requests and 4,834,063 transferred bytes: 94 scripts/2.74MB, 192 third-party requests/2.64MB. Images found 45 legacy formats, 41 without srcset, 15 oversized and 50 below-fold images without native lazy loading. The tracker capture observed 72 third-party origins and 12 known tracker domains. HAR attributes 192 requests and 2.64MB to third parties, including Google Tag Manager, Facebook, TikTok, DoubleClick and Criteo. F009 high: Resource delivery is dominated by scripts, third parties and oversized legacy imagery. F016 high: Tracking and advertising integrations create a disproportionate privacy footprint. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent was found; this emerging capability is contextual and absence is not a failure. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the audited paths required on-device language-model or summarization inference; this emerging check is contextual. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten repeated listing scroll cycles, heap size was 53.03MB versus 52.20MB baseline (about 1.6%); constructor populations were broadly stable, with no evidence of unbounded retained growth in this bounded exercise. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap summary recorded 885,731 heap nodes and 52,201,348 bytes for a listing whose DOM exposes 746 form controls; a post-scroll run reached 53,029,564 bytes. F018 medium: The listing has a heavy initial memory footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Heap summaries showed no Detached* constructor among leading populations and repeated scrolling produced only small bounded growth; no accumulating listener/timer symptom was observed. |
Provenance
Canonical report: results/atomic/reports/0883-www_carsensor_net.json
Report SHA-256: b70317e6d272790dea5d082232c929dc8fe1b63f77f4570f1dee42a51ebe17ea
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_carsensor_net/2026-07-23T15-29-16-263Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_carsensor_net/2026-07-23T15-29-16-263Z
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.