Manifest position 388 · CrUX rank bucket 1000
https://turbo.az
Coverage complete
Coverage-complete multi-template audit; no local source was supplied, so 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 | The dark-emulated screenshot remains the same light gray and white palette as the default capture; computed `color-scheme` is `normal`. F01 medium: No dark color scheme |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, the probe found no running animations and only short 0.2s control transitions. |
respect-user-preferencesrespects-contrast | pass | high | The forced-colors/prefers-contrast screenshot retains readable text, control borders, focus shapes, and inventory imagery. |
implement-natural-interactionsview-transitions | issues | high | DOM inspection found no authored transition behavior and navigation uses ordinary full-page swaps; the page does not use same-document or cross-document View Transitions. F02 low: Route and state changes are abrupt |
implement-natural-interactionsscroll-driven-animations | pass | high | DOM/CSS and animation probes found no scroll-linked animation or main-thread scroll animation to implement incorrectly. |
implement-natural-interactionsphysical-gestures | pass | high | Representative listing and detail pages retain native scrolling and ordinary link/control gestures without custom pointer-drag behavior fighting the platform. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long listing keeps static navigation chrome and DOM/CSS evidence contains no scroll-state container rules or progress affordance. F03 low: Page chrome does not respond to scroll state |
provide-guided-navigationanchored-positioning | issues | high | The home DOM contains custom `tz-dropdown` div controls while no `dialog`, `popover`, or `details` elements were found; no anchor-positioning rules were found for floating menus. F04 low: Custom dropdown overlays bypass semantic primitives |
provide-guided-navigationdirects-attention | pass | high | Desktop screenshots show persistent labelled navigation, selected filter states, and detail-page breadcrumbs that preserve orientation. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | All five initial screenshots show core content immediately with no modal, consent wall, or full-viewport interstitial obscuring it. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The home DOM contains custom `tz-dropdown` div controls while no `dialog`, `popover`, or `details` elements were found; no anchor-positioning rules were found for floating menus. F04 low: Custom dropdown overlays bypass semantic primitives |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop screenshots devote both side rails and the top banner to advertising around the primary inventory, reducing the visual share given to the core task. F05 medium: Advertising chrome competes with listings |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x800 viewport, layout metrics report no viewport meta, a 1010 CSS-pixel layout viewport, and visual scale 0.356; the screenshot shows tiny desktop content rather than mobile reflow. F06 critical: Mobile renders a scaled desktop canvas |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The page probe found zero container rules and the narrow capture preserves the same fixed four-column desktop component layout. F07 medium: Components do not adapt to their container |
adapt-to-the-form-factorinput-modality-aware | issues | high | The target probe found 60 controls below 24px in one sampled set, including 17px-high header links and 13px controls; several empty card links focus with `outline: none`. F08 high: Touch targets and some focus states are inadequate |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home, listing, detail, dealer and create screenshots clearly expose vehicles, filtering, seller contact, and create-listing actions. |
support-core-task-successprimary-flow-completion | pass | high | The listing-to-detail path exposes price and seller contact, while create-listing advances to a labelled required-field form without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | A deliberately invalid URL returns a branded 404 with a clear homepage recovery link; invalid listing fields use native required validation. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 16.0s, FCP 7.7s, Speed Index 16.6s and performance 0.50; the independent trace measured LCP 11.09s. F09 high: Loading performance is poor |
be-fast-and-stablevisual-stability | issues | high | The layout observer measured CLS 0.397 with large shifts of 0.157 and 0.113; 38 of 39 images lacked explicit dimensions. F10 high: The mobile load shifts substantially |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reports 3.4s of main-thread work, TBT 240ms and time-to-interactive 33.9s; the trace also recorded a 67ms long task. F11 medium: Main-thread work delays readiness |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 136 requests and 3.53MB transferred; Lighthouse reports 2.51s document response, render-blocking savings of 2.81s, font-display savings of 3s and weak cache lifetimes. F12 high: Critical delivery is slow and heavy |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 773KiB of unused JavaScript, 71KiB unused CSS, and 23KiB legacy JavaScript; HAR shows 51 script requests totalling 1.72MB. F13 medium: Large unused script and style payloads ship on load |
be-inclusivenames-roles-labels | issues | high | Lighthouse fails image-alt and link-name; the image probe found 10 images without alt, and the home probe found 20 visible form controls without labels. F14 high: Accessible names and labels are incomplete |
be-inclusivesufficient-contrast | issues | high | Lighthouse accessibility reports the color-contrast audit as failing. F15 high: Text contrast fails WCAG checks |
be-inclusivestructure-and-focus | issues | high | Lighthouse reports no main landmark; home, listing, create and dealer DOMs contain no `<main>`, and the focus probe found empty card links with no outline. F16 high: Landmarks and focus treatment are incomplete |
be-inclusivelegible-text | pass | high | At desktop size the inventory cards and detail text use clear hierarchy and readable line lengths; observed clipping is confined to the separately failed mobile adaptation. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At a 360x800 viewport, layout metrics report no viewport meta, a 1010 CSS-pixel layout viewport, and visual scale 0.356; the screenshot shows tiny desktop content rather than mobile reflow. F06 critical: Mobile renders a scaled desktop canvas F08 high: Touch targets and some focus states are inadequate |
follow-best-practicesno-console-errors | issues | high | Lighthouse `errors-in-console` audit failed on a clean load. F17 medium: The page logs browser errors |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found 38 of 39 images without dimensions, 26 oversized, 29 without responsive sources, and 30 in legacy formats. F18 high: Image asset markup is unsound |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse inspector-issues audit failed and also identified legacy JavaScript; the document lacks a standard mobile viewport. F19 medium: DevTools reports platform hygiene issues |
be-discoverabletitle-and-description | pass | high | Home has a descriptive Azerbaijani title and meta description; detail and dealer templates also provide route-specific titles. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse fails meta-viewport and the DOM/layout probes confirm the primary templates omit viewport metadata, despite crawlable links and permissive robots. F20 high: Public pages fail mobile-friendly viewport requirements |
be-discoverablecanonical-and-indexing-signals | issues | high | robots points to a sitemap, but the sampled sitemap content lists `http://turbo.az` URLs while page canonicals and transport use HTTPS. F21 medium: Sitemap URLs are inconsistent with HTTPS canonicals |
be-discoverablestructured-and-shareable-metadata | issues | high | The detail page has Open Graph tags but DOM inspection found no JSON-LD block for the visible vehicle, price, availability, and seller data. F22 medium: Vehicle detail pages lack structured product/vehicle data |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS and nosniff are present, but CSP only declares `frame-ancestors`; Permissions-Policy is missing, and 8 sampled first-party cookies lack Secure while many use SameSite=None. F23 high: Security policy and cookies need hardening |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 25 third-party origins and seven known tracker domains; HAR recorded 136 requests and cookies include 400-day analytics identifiers. F24 high: Tracking and third-party footprint is excessive |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The visible sign-in entry and rendered/source probes showed no WebAuthn/passkey capability; no permission prompt fired on load. F25 low: Authentication exposes no phishing-resistant option |
be-private-and-securedefensive-browser-policies | issues | high | HTTPS, HSTS and nosniff are present, but CSP only declares `frame-ancestors`; Permissions-Policy is missing, and 8 sampled first-party cookies lack Secure while many use SameSite=None. F23 high: Security policy and cookies need hardening |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 99% raw/rendered content coverage, with title, h1 and description in server HTML and no empty JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Representative pages and custom controls rendered without clipped open overlays or broken async shells during the inspected states. |
be-resilientoffline-and-installable | issues | high | A web-app manifest link is present, but the PWA probe found zero service-worker registrations and the cross-origin manifest fetch failed. F26 medium: The app-like marketplace has no offline worker |
be-resilientnetwork-and-http-failure-states | pass | high | The 404 route displays a concise error and actionable link back to the homepage rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Primary pages declare `lang=az`, preserve Azerbaijani reading order, and expose a separate RU locale route. |
be-internationalisedlocale-aware-data | pass | high | Screenshots show Azerbaijani relative dates and locally formatted prices/currency, with a dedicated Russian locale available. |
be-internationalisedtime-zone-correctness | not-applicable | high | This Azerbaijan-local marketplace shows relative/local listing dates but has no cross-zone scheduling or event coordination surface in the representative paths. |
be-trustworthyno-dark-patterns | pass | high | Representative browse, detail and create screens show clear prices/actions and no confirmshaming, forced continuity, or consent wall. |
be-trustworthyhumane-error-handling | pass | high | Create form uses required constraints after submit, keeps the user on the form, and exposes browser validation without deleting entered context. |
be-trustworthytrustworthy-input-assistance | issues | high | The create-listing flow exposes name, email, phone and location fields, but name/email/phone have empty autocomplete values and several controls lack labels. F27 medium: Seller form omits useful autocomplete tokens |
be-trustworthysafe-commercial-and-account-flows | pass | high | The inspected marketplace path makes price, seller identity, phone/message actions and listing condition visible before contact, with no checkout or subscription commitment. |
be-sustainableoptimised-assets | issues | high | The image audit found 26 oversized images, 29 without responsive sources, 30 legacy-format assets and no modern-format images; Lighthouse estimates 1.23MiB image savings. F28 high: Image delivery wastes bytes |
be-sustainableno-wasteful-work | issues | high | Tracker capture found 25 third-party origins and seven known tracker domains; HAR recorded 136 requests and cookies include 400-day analytics identifiers. F24 high: Tracking and third-party footprint is excessive |
be-sustainablethird-party-and-media-budget | issues | high | Tracker capture found 25 third-party origins and seven known tracker domains; HAR recorded 136 requests and cookies include 400-day analytics identifiers. F24 high: Tracking and third-party footprint is excessive F28 high: Image delivery wastes bytes |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared or observed agent-facing surface; this emerging capability is an opportunity rather than an obligation for the audited consumer marketplace. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or generative task was observed where on-device inference is necessary; this emerging check is not applicable to the representative flows. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll cycles, heap self size rose only 0.53% (48.11MB to 48.36MB) and Object/Promise populations stayed effectively flat. |
be-memory-efficientbounded-footprint | pass | high | The image-heavy marketplace baseline heap summary is about 48.1MB; despite a large snapshot graph, it remained bounded through the exercise. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | No Detached* constructor appeared in either top-constructor summary; post-scroll edges fell and key constructor populations remained stable. |
Provenance
Canonical report: results/atomic/reports/0388-turbo_az.json
Report SHA-256: e1ca1250447133ee4aeb2101fed5250458a5d4a69f45fd39611d890b0686a72a
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/turbo_az/2026-07-20T10-27-43-187Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/turbo_az/2026-07-20T10-27-43-187Z
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.