Manifest position 324 · CrUX rank bucket 1000
https://m.autoplius.lt
Coverage complete
58/58 atomic checks judged. Representative secondary routes exposed bot verification and a broken login render; these are recorded as observed issues rather than unexecuted 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 | screenshot under emulated dark mode is pixel-identical to light mode; no color-scheme CSS was found F-001 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 | pass | high | reduced-motion probe matched the preference and found no running animations or motion CSS |
respect-user-preferencesrespects-contrast | pass | medium | forced-colors/prefers-contrast screenshot retained readable consent controls and text |
implement-natural-interactionsview-transitions | issues | medium | CSS/animation probe found no View Transition rules or animations for state/route changes F-002 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 | high | No parallax, scrollytelling, or scroll-linked animation was present on the inspected surfaces |
implement-natural-interactionsphysical-gestures | issues | medium | content carousels and long mobile surfaces expose no scroll-snap/overscroll declarative gesture CSS F-003 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 | medium | long 6,122px page uses static header chrome; no scroll-state/progress CSS was found F-004 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 | high | No tooltip or edge-positioned popover was present in the inspected entry experience |
provide-guided-navigationdirects-attention | issues | medium | navigation/state changes expose no directional transition, marker, highlight, or focus cue F-005 low: Navigation and in-page jumps guide attention (highlight effects, scroll/carousel markers, directional transitions, drill-down and drawer navigation) so the user can follow where focus moved. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | first viewport is fully obscured by a consent interstitial before any interaction F-006 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 | probe found 3 custom modal-role elements but zero native dialog, popover, or details elements F-007 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 | medium | consent chrome consumes the whole first viewport and persistent header/chat controls compete with marketplace content F-008 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 | 390x844 layout measured scrollWidth=clientWidth=390 with zero overflow and viewport meta present |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | CSS probe found no container queries or container-type; adaptation relies on a separate mobile surface F-009 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 | focused first link computed outline is none; many links are only 13-18px high F-010 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 | issues | high | search/listing purpose exists behind the page, but the blocking consent wall hides it on first load F-011 high: The page communicates what it is for and exposes the primary next action without requiring users to hunt through decorative content, generic copy, or competing calls to action. |
support-core-task-successprimary-flow-completion | issues | high | listing, detail, and article navigations returned a Cloudflare human-verification wall; the login endpoint rendered escaped HTML text F-012 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 | pass | high | rate-limit challenge clearly explains the state, offers Lithuanian/English, and provides a visible verification recovery action |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 12.2s, CLS 0.131 and TBT 230ms; trace measured LCP 6.78s and TBT 2.17s F-013 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 | issues | high | Lighthouse measured CLS 0.131 despite the shorter layout observation measuring 0.012 F-014 medium: No cumulative layout shift from late content (images, banners, fonts) that arrives without reserved space. |
be-fast-and-stableefficient-main-thread | issues | high | trace found a 2,199ms main-thread task and 2,174ms total blocking time F-015 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 five VeryHigh render-blocking stylesheets and several synchronous classic scripts; probe confirmed key scripts lack async/defer F-016 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 | 976KB of script was transferred; ad, analytics, Facebook and chat bundles dominate the 1.58MB load F-017 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 found unnamed links; image audit found 42 images without alt; search text input has no label F-018 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 | Lighthouse found white VIN badge text at 3.24:1, below the required 4.5:1 F-019 medium: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | visible headings begin at H3 and no visible page H1 exists; focused first link has outline:none F-020 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 | pass | medium | mobile screenshot shows readable body typography and the 390px layout has no clipping or horizontal overflow |
be-inclusivezoom-reflow-targets-and-media | issues | high | viewport disables zoom with maximum-scale=1 and user-scalable=0; many targets are 13-18px high F-021 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 | pass | high | Lighthouse console-errors audit passed |
follow-best-practicessound-document-and-assets | issues | medium | doctype/charset are valid, but image audit found 43 images without width/height and 46 without srcset F-022 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 | pass | high | Lighthouse best-practices score was 100 with no deprecated API or console-error failure |
be-discoverabletitle-and-description | pass | high | descriptive title and meta description are present in rendered and raw HTML |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found a feedback anchor with no href; robots and viewport otherwise exist F-023 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 | home returns 200, canonical/hreflang are present, robots permits normal crawlers and names a sitemap |
be-discoverablestructured-and-shareable-metadata | issues | high | Open Graph title/description/url exist, but no JSON-LD was present for marketplace/product entities F-024 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/HSTS/nosniff are present, but CSP is missing and 6 of 8 cookies lack Secure F-025 high: 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 | 18 third-party origins and 7 known trackers loaded; 80/82 requests and 1.56MB were classified third-party F-026 high: 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 | medium | no permission prompt fired on home, but the sign-in endpoint rendered escaped markup and no usable modern-auth surface could be reached F-027 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 | CSP and Permissions-Policy are absent; Referrer-Policy is the weak no-referrer-when-downgrade default F-028 high: 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 | pass | medium | raw HTML is substantial (141KB), not a JS shell, and retains 65% of rendered content words |
be-resilientresilient-runtime-behaviour | issues | high | representative internal navigations degrade to a bot wall, and login renders escaped markup instead of an interactive form F-029 high: 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 | pass | medium | a service worker API is active and the page remains server-rendered; installability is not central to this marketplace |
be-resilientnetwork-and-http-failure-states | pass | high | the HTTP/rate-limit challenge is explicit, localized and offers a verification action instead of a blank shell |
be-internationalisedlang-dir-and-logical-properties | pass | high | html lang=lt is correct and hreflang links expose Lithuanian, Russian, English and Latvian variants |
be-internationalisedlocale-aware-data | pass | medium | rendered prices use Lithuanian spacing and euro notation and localized variants are explicitly linked |
be-internationalisedtime-zone-correctness | not-applicable | high | no scheduled event or user-facing time-zone-sensitive workflow was present in the audited marketplace entry experience |
be-trustworthyno-dark-patterns | pass | medium | consent accept and reject actions are both clearly labeled and similarly prominent; no confirmshaming was observed |
be-trustworthyhumane-error-handling | pass | medium | the observed verification error state explains why it appeared and offers a clear recovery action without blame |
be-trustworthytrustworthy-input-assistance | issues | high | primary text search has autocomplete=off, no name and no accessible label F-030 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 | sign-in endpoint displays escaped HTML rather than a usable account form, preventing a clear account flow F-031 high: 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 | 46/49 images lack responsive srcset, 11 use legacy formats and 46 below-fold images are not lazy-loaded F-032 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 | trace found 2.17s blocking time and HAR shows ad/analytics work loading before user intent F-033 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 1.56MB and 80 of 82 requests, including ad, analytics, Facebook and chat code F-034 high: 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 | issues | high | robots.txt explicitly blocks anthropic-ai, Claude-Web and Applebot-Extended; no JSON-LD or agent tool registration was found F-035 medium: Where it makes sense, the site exposes structured, safe capabilities to agents via WebMCP tools, agentic forms, and agentic JavaScript tools rather than leaving agents to scrape and guess. |
be-agent-readyon-device-inference | not-applicable | high | no clear user task in this marketplace entry experience requires on-device language-model inference |
be-memory-efficientno-leak-under-repeated-interaction | pass | low | after 10 repeated full-page scroll cycles, snapshot size rose only ~0.50MB (1.6%); no unbounded trend was demonstrated |
be-memory-efficientbounded-footprint | pass | medium | heap summary was ~30.9MB for a content- and third-party-heavy marketplace page; proportionate though optimizable |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | low | heap summaries exposed no Detached* constructor among reported populations and repeated scrolling did not show runaway size growth |
Provenance
Canonical report: results/atomic/reports/0324-m_autoplius_lt.json
Report SHA-256: e7d8ca86bd549ec5a6c43544f6cd1dc945d0c2b5205dd29e8a45d5148ac6a8eb
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_autoplius_lt/2026-07-19T23-18-54-119Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_autoplius_lt/2026-07-19T23-18-54-119Z
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.