Manifest position 468 · CrUX rank bucket 1000
https://m.ss.com
Coverage complete
Coverage-complete report-mode audit across seven representative read-only paths. Payments, registration completion, message sending, and ad publication were not executed because they require credentials or create consequential external state.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-mode screenshot is pixel-identical to the normal mobile capture, and the DOM reports color-scheme: normal with a white body. F01 medium: The site is fixed to a light theme. |
respect-user-preferencesrespects-reduced-motion | issues | high | Normal and prefers-reduced-motion menu videos retain the same scripted transition behavior; the page exposes no reduced-motion adaptation. F02 low: Motion is not adapted for reduced-motion users. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/prefers-contrast capture retains visible yellow/white text, green imagery, controls, and focus boundaries on black. |
implement-natural-interactionsview-transitions | issues | high | The recorded menu interaction and route walkthrough show immediate state/page swaps; probes found no view-transition usage. F03 low: Route and menu state changes are abrupt and have no View Transition treatment. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, entry reveals, carousels, or other scroll-linked animation was present on the representative pages. |
implement-natural-interactionsphysical-gestures | pass | high | Catalog and detail pages use native document scrolling and ordinary taps; no pointermove-driven gesture layer or scroll hijacking was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The results page is 2,785px tall; its mobile capture and probe show a fixed visual header but no progress indicator or scroll-state-responsive treatment. F04 low: Long catalog pages provide static chrome but no scroll-position feedback. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored action preview, or edge-positioned popover was present in the tested surfaces. |
provide-guided-navigationdirects-attention | issues | high | The home, category, results, and detail captures swap content without directional transition or semantic heading landmarks; probes report no headings. F05 low: Navigation changes do not clearly cue where context moved. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Fresh-profile screenshots show the fixed consent panel covering roughly the lower 38% of the 390x844 viewport, including listing and detail content. F06 high: The consent panel obscures a large share of every first view. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM evidence shows #cookie_confirm_dv as a fixed div; probes report zero dialog/popover elements and inline onclick handlers. F07 medium: The blocking consent surface is an ad-hoc fixed div rather than a semantic dialog. |
maximize-content-reduce-noisereduced-chrome | pass | high | Outside the consent panel, the UI is content-first: a 50px header and compact catalog rows devote nearly all space to listings. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 390x844, home and results both report scrollWidth 390, clientWidth 390, zero horizontal overflow, and CLS 0. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | 390px and 1440px captures show the same single-column catalog stretched across the viewport; probes found no container-query support. F08 low: The layout only stretches globally rather than adapting components to available space. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Across probes, selects and actions are 25-36px high; every visible detail action was below 44px and the results page had 14 undersized targets. F09 high: Many controls are too short for comfortable touch use. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home categories, result filters, listing rows, detail contact actions, login, and new-ad entry each expose a clear purpose and next action. |
support-core-task-successprimary-flow-completion | pass | high | A representative browse flow completed from home to Transport, Audi results, a vehicle detail, and visible email/phone contact actions without an account wall. Posting/sending was not executed because it would create external state. |
support-core-task-successclear-system-state-and-recovery | issues | high | The invented /lv/this-route-does-not-exist-web-uplift/ path returned responseStatus 200 and ordinary homepage content with no not-found message or recovery explanation. F10 high: Invalid routes silently return the homepage with HTTP 200. |
be-fast-and-stablegood-core-web-vitals | pass | high | Lighthouse measured LCP 2.15s, CLS 0, TBT 0; trace measured LCP 768ms and no long tasks in a separate run. |
be-fast-and-stablevisual-stability | pass | high | Home and results layout observers recorded CLS 0 with no shift entries; all 19 home images have dimensions. |
be-fast-and-stableefficient-main-thread | pass | high | Trace and layout captures recorded zero long tasks and 0ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | pass | high | The compact page loads quickly with no redirects, no uncompressed text issues, and no missing cache-header signals; the parser script is only 38.5KB and observed LCP remains good. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR recorded 511,629 transferred bytes; two Google tag scripts plus analytics account for about 326KB, while third parties total 461,058 bytes. F11 medium: Analytics scripts dominate an otherwise small page load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse reports image-alt and link-name failures; the image primitive found 17 of 19 images without alt, including logo/menu/category imagery. F12 high: Core images and controls lack accessible names. |
be-inclusivesufficient-contrast | pass | high | Lighthouse reported no color-contrast failure and the forced-colors capture remains readable with clearly separated controls. |
be-inclusivestructure-and-focus | issues | high | All six page probes report zero headings and zero main/nav/header/footer landmarks, despite long category, result, and detail content. F13 high: Pages have no semantic heading or landmark structure. |
be-inclusivelegible-text | issues | high | The mobile results capture compresses description, price, year, engine, and mileage into a dense row; probes show 15px-high footer links. F14 medium: Dense listing and footer text reduces reading comfort. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport is user-scalable=0 and Lighthouse fails meta-viewport; multiple controls are also below 44px. F15 high: Mobile zoom is explicitly disabled. |
follow-best-practicesno-console-errors | pass | high | Lighthouse best-practices score is 0.96 and did not report the errors-in-console audit as failed; route probes completed without uncaught execution failure. |
follow-best-practicessound-document-and-assets | issues | high | DOM contains presentational table/align/border attributes and inline handlers; image evidence shows 16 legacy-format assets and five below-fold images loaded eagerly. F16 low: Document markup and image delivery rely on obsolete patterns. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports Cache-Control: no-store on the main resource and cookie-modifying requests as BFCache blockers. F17 low: The page is excluded from the back/forward cache. |
be-discoverabletitle-and-description | issues | high | Home, category, results, detail, login, and new-ad probes all report metaDescription: null; Lighthouse fails meta-description. F18 medium: Public pages have no meta description. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Core catalog navigation uses real href links, viewport metadata is present, robots permits public Latvian routes, and raw content remains visible. |
be-discoverablecanonical-and-indexing-signals | pass | high | Public pages returned 200, expose matching canonical URLs, robots points to a current sitemap index, and no accidental noindex was found. |
be-discoverablestructured-and-shareable-metadata | issues | high | The public vehicle detail probe reports no JSON-LD and no Open Graph tags despite exposing product-like price, model, location, and images. F19 medium: Listing details lack structured data and social preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers evidence confirms HTTPS and HSTS, but no CSP, X-Content-Type-Options, clickjacking protection, Referrer-Policy, or Permissions-Policy. F20 high: Important browser security headers are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | A fresh-profile HAR captured Google Tag Manager, Google Analytics, DoubleClick, Puls, and Europuls while the consent overlay remained visible; 27 of 34 requests and 461KB were third-party. F21 high: Tracking loads while the consent decision is still blocking the page. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login probe exposes only text/password fields with no autocomplete tokens or passkey/WebAuthn affordance; no permission prompt occurred on load. F22 medium: Authentication is password-only and lacks modern credential support. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence confirms HTTPS and HSTS, but no CSP, X-Content-Type-Options, clickjacking protection, Referrer-Policy, or Permissions-Policy. F20 high: Important browser security headers are missing. |
be-resilientprogressive-enhancement | pass | high | Raw HTML exposes 84% of home and 88% of detail rendered content; both are non-shell pages with title and core content available without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Menu, catalog, result, and detail surfaces remained usable at 390px with no overflow or clipped overlay trigger; navigation uses server URLs rather than a fragile SPA shell. |
be-resilientoffline-and-installable | issues | high | The page declares apple-mobile-web-app-capable and links native apps, but all probes report no manifest and no controlling service worker. F23 low: The app-like mobile site is not installable and has no offline fallback. |
be-resilientnetwork-and-http-failure-states | issues | high | The invented /lv/this-route-does-not-exist-web-uplift/ path returned responseStatus 200 and ordinary homepage content with no not-found message or recovery explanation. F10 high: Invalid routes silently return the homepage with HTTP 200. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Pages correctly use lang=lv, but expose no hreflang links and no dir attribute; authored markup repeatedly uses physical left/right alignment and margins. F24 medium: Localized variants lack explicit alternate-language and bidi-ready signals. |
be-internationalisedlocale-aware-data | pass | high | Latvian detail content displays currency as “4 390 €”, mileage with grouped digits, and dates in local day.month.year form; LV/RU/EN language choices are exposed. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative marketplace surfaces contain listing dates but no cross-zone event scheduling, recurring intervals, or user-entered time concepts. |
be-trustworthyno-dark-patterns | issues | high | The panel emphasizes a filled green “Allow all” action while “Choose” is outlined; there is no equally direct reject-all choice and content remains obscured. F25 medium: Consent choices are visually asymmetric and rejection is not direct. |
be-trustworthyhumane-error-handling | issues | high | Login fields have no required, aria-invalid, or associated label values; the visible captions are not programmatically connected. F26 medium: Sign-in fields do not expose native validation or associated labels. |
be-trustworthytrustworthy-input-assistance | issues | high | The login probe reports empty autocomplete values for both login and password fields. F27 medium: Sign-in inputs omit autocomplete assistance. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The account flow is password-only, has no WebAuthn/passkey path, and its inputs lack autocomplete assistance. F22 medium: Authentication is password-only and lacks modern credential support. F27 medium: Sign-in inputs omit autocomplete assistance. |
be-sustainableoptimised-assets | issues | high | Home uses 16 PNG/GIF assets and eagerly loads five below-fold images; detail loads 910px JPEGs and many thumbnails without srcset or lazy loading. F28 medium: Image delivery is not responsive or deferred. |
be-sustainableno-wasteful-work | issues | high | A fresh-profile HAR captured Google Tag Manager, Google Analytics, DoubleClick, Puls, and Europuls while the consent overlay remained visible; 27 of 34 requests and 461KB were third-party. F21 high: Tracking loads while the consent decision is still blocking the page. F11 medium: Analytics scripts dominate an otherwise small page load. |
be-sustainablethird-party-and-media-budget | issues | high | HAR recorded 511,629 transferred bytes; two Google tag scripts plus analytics account for about 326KB, while third parties total 461,058 bytes. F11 medium: Analytics scripts dominate an otherwise small page load. F21 high: Tracking loads while the consent decision is still blocking the page. |
be-agent-readystructured-agent-capabilities | not-applicable | high | This public classifieds site exposes ordinary HTML links and forms but no declared agent-facing transaction surface; the emerging WebMCP opportunity was not treated as an obligation. |
be-agent-readyon-device-inference | not-applicable | high | No summarization, language-model, or other inference use case is part of the tested catalog, login, or posting entry flows. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 menu open/close cycles, heap self size changed only 1,123 bytes (2,146,998 to 2,148,121); a same-session probe showed modest bounded growth and no active animations. |
be-memory-efficientbounded-footprint | pass | high | The baseline heap is proportionate for the small page: 44,251 nodes in the V8 snapshot graph and 2.15MB total self size; the DOM itself had 139 elements in the metric probe. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Post-interaction constructors show no Detached* population; closures rose by only 7 and same-session DOM elements stabilized at 153 after repeated menu toggles. |
Provenance
Canonical report: results/atomic/reports/0468-m_ss_com.json
Report SHA-256: 6b5f47c74f7afd109e22273d326d181d671c0d618eacee0bf927ef4fa2dd623b
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_ss_com/2026-07-21T00-29-29-400Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/m_ss_com/2026-07-21T00-29-29-400Z
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.