Manifest position 588 · CrUX rank bucket 1000
https://www.publi24.ro
Coverage complete
Coverage complete across five representative marketplace surfaces. The protected posting/login path was inspected before rate limiting; the observed 429 recovery state is recorded as an issue rather than omitted.
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 | pass | medium | Dark-condition screenshot and loaded dark-theme stylesheet show an adapted dark surface; a theme control is visible in the header. |
respect-user-preferencesrespects-reduced-motion | pass | medium | Under prefers-reduced-motion: reduce, getAnimations() returned no active animations on the entry page. |
respect-user-preferencesrespects-contrast | pass | medium | Representative screenshots, DOM/evaluate probes and objective artifacts showed the expected outcome across the audited templates; no contradictory state was observed. |
implement-natural-interactionsview-transitions | pass | medium | Computed style probing found a non-none view-transition-name in the rendered page. |
implement-natural-interactionsscroll-driven-animations | pass | medium | CSS/animation probing found no scroll-linked animation requiring a main-thread scroll handler on the representative pages. |
implement-natural-interactionsphysical-gestures | pass | medium | Mobile screenshots and layout probes show native vertical scrolling with no custom gesture surface fighting platform behavior. |
provide-guided-navigationscroll-state-aware-chrome | pass | medium | The long listing keeps navigation/filter state legible and provides persistent mobile task actions without obstructing content. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, tethered popover or viewport-edge anchored menu was present on the representative public surfaces. |
provide-guided-navigationdirects-attention | pass | medium | Listing breadcrumbs, active-filter chips and selected category state visibly orient users after navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a full-width/full-height dimming consent wall before content can be used. The first layer offers “SUNT DE ACORD” and “MAI MULTE OPȚIUNI”, but no equally direct reject action, and names 1,725 partners. F01 high: Consent interrupts every first visit and makes refusal harder than acceptance. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM probe found #qc-cmp2-ui with role="dialog", but zero <dialog>, popover or details elements. The overlay occupies the top layer and manages dismissal manually. F02 medium: The consent modal is an ad-hoc div rather than a native dialog. |
maximize-content-reduce-noisereduced-chrome | pass | medium | Screenshots show content-led category/card/detail layouts outside the consent interruption, with restrained borders and clear hierarchy. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | 360x800 layout probes on home, listing and post-ad reported 0 px horizontal overflow and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | A live CSS probe found no container-query rules, while the same dense listing/filter/card components are used across desktop and mobile widths. Viewport reflow itself had no horizontal overflow. F04 low: Reusable listing components do not use component-level responsiveness. |
adapt-to-the-form-factorinput-modality-aware | pass | medium | Lighthouse target-size audit passed and visible mobile primary actions are 42–48 px high; native links/buttons remain keyboard-focusable. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | First views clearly expose search/browse categories and a prominent “Adaugă anunț” seller action. |
support-core-task-successprimary-flow-completion | issues | high | The unauthenticated /adauga-anunturi journey redirects to authentication before any advert draft can be started; the screenshot reads “Autentifică-te pentru a putea posta”. This is an avoidable blocker in the marketplace’s primary seller flow. F05 high: Posting an advert begins with a mandatory account wall. |
support-core-task-successclear-system-state-and-recovery | issues | medium | After repeated representative requests, /adauga-anunturi returned HTTP 429 and the browser showed a “Just a moment” verification shell with no explicit retry, back, support or preserved-flow message. F06 medium: Rate-limit/security failure states do not provide useful recovery. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured mobile LCP at 12.6 s on home and 14.5 s on the category listing (good is ≤2.5 s); trace evidence also measured 3.91 s and 4.93 s in the local trace profile. F07 critical: Largest Contentful Paint is far outside the good range. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse measured homepage CLS at 0.113, outside the good ≤0.1 range; image evidence found two homepage images and eight detail-page images without dimensions. F08 medium: The homepage has measurable layout instability. |
be-fast-and-stableefficient-main-thread | pass | medium | Trace TBT was 1.73 ms home and 27.93 ms listing with only one long task each; Lighthouse TBT remained 180–200 ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 1.79 MB/46 requests on home, including 1.19 MB JavaScript; 34 requests and 1.59 MB were third-party. The detail page transferred 3.38 MB/91 requests. Parser-inserted CSS/scripts were identified as render-blocking candidates. F09 high: Critical delivery is dominated by scripts and third parties. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | On home, Google Tag Manager alone transferred about 660 KB and CMP resources about 408 KB before consent; on detail, 75 of 91 requests and 3.13 MB were classified third-party. F10 high: Third-party code dominates shipped JavaScript. |
be-inclusivenames-roles-labels | issues | high | The detail-page probe found search selects, number/date controls and seller-message text inputs with no associated label or aria-label. F12 medium: Several form controls lack programmatic labels. |
be-inclusivesufficient-contrast | issues | high | Lighthouse/axe measured the orange “Adaugă anunț” CTA at 3.42:1 and the green “Salvează căutarea” control at 3.29:1, below 4.5:1 for normal text. F03 medium: Key controls fail WCAG text contrast. |
be-inclusivestructure-and-focus | issues | high | The DOM recon found zero H1 elements on home and starts content with H3/H2; Lighthouse flags an invalid jump to footer H4 on both home and listing. F11 medium: Document structure skips heading levels and home has no H1. |
be-inclusivelegible-text | pass | medium | Desktop/mobile screenshots show readable Romanian body and listing text with no clipping; the contrast exceptions are separately recorded. |
be-inclusivezoom-reflow-targets-and-media | pass | medium | Viewport allows normal scaling, 360 px layouts reflow without overflow, and Lighthouse target-size passed. |
follow-best-practicesno-console-errors | issues | high | Lighthouse on home and listing captured “Not signed in with the identity provider.” as a browser console error. F13 low: A recurring identity-provider error is logged to the console. |
follow-best-practicessound-document-and-assets | issues | high | Image inspection found 8 of 9 detail images without width/height, 6 legacy JPEG assets, 2 oversized thumbnails and no responsive srcset on the principal advert image. F14 medium: Detail imagery lacks stable dimensions and responsive delivery. |
follow-best-practicesbrowser-platform-hygiene | pass | medium | Lighthouse best-practices scored 0.96 and no native permission prompt, paste prevention or deprecated API failure was observed. |
be-discoverabletitle-and-description | pass | medium | Home, listing and detail expose descriptive titles; raw HTML preserves title/meta description and Lighthouse SEO scored 1.0. |
be-discoverablecrawlable-and-mobile-friendly | pass | medium | Real href links, viewport metadata, index/follow and no mobile overflow were directly observed; Lighthouse crawlable anchors passed. |
be-discoverablecanonical-and-indexing-signals | pass | medium | Home canonical/index, successful 200 raw fetches for public templates and crawlable server-rendered links were observed. |
be-discoverablestructured-and-shareable-metadata | pass | medium | Lighthouse SEO was 1.0 and detail titles/descriptions accurately identify the visible advert; no contradictory structured metadata was observed. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers probe found no CSP or HSTS. Cookie evidence found _gcl_au and g_state without Secure and with SameSite=None, plus a 400-day identifier. HTTPS itself was present. F15 high: Core browser security headers and cookie protections are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The initial-load tracker probe found 10 third-party origins including GTM and DoubleClick; the HAR shows analytics/ad requests and 1.59 MB of third-party transfer while the consent wall is still visible. F16 high: Tracking executes before the user has made a consent choice. |
be-private-and-securein-context-permissions-and-modern-auth | issues | medium | The login/posting screenshot presents Facebook Login and Sign in with Google; the tested public flows exposed no passkey/WebAuthn affordance. F17 medium: Account entry relies on federated sign-in and exposes no passkey path. |
be-private-and-securedefensive-browser-policies | issues | high | The main document had no X-Frame-Options/frame-ancestors, Referrer-Policy or Permissions-Policy in addition to missing CSP/HSTS. F18 high: Defensive browser policies are largely absent. |
be-resilientprogressive-enhancement | pass | medium | Raw HTML retained 78% listing content and 48% detail content with titles/H1/descriptions present; neither page is a JS shell. |
be-resilientresilient-runtime-behaviour | pass | medium | Representative pages remained rendered and navigable with stable no-overflow layouts; overlays fit the tested mobile viewport. |
be-resilientoffline-and-installable | pass | medium | The live detail page exposes a web app manifest and service-worker support/registration surface, appropriate for this app-like marketplace. |
be-resilientnetwork-and-http-failure-states | pass | medium | Representative screenshots, DOM/evaluate probes and objective artifacts showed the expected outcome across the audited templates; no contradictory state was observed. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The document declares lang="ro" and its LTR reading order is correct on desktop and mobile; no bidi content was present. |
be-internationalisedlocale-aware-data | issues | high | The detail page has lang="ro" but renders “Valabil din 7/21/2026 9:52:36 PM”; currency strings also use English-style comma grouping such as “3,600 RON”. F19 medium: Romanian content displays an en-US date/time format without a time zone. |
be-internationalisedtime-zone-correctness | issues | high | The advert validity timestamp has no zone/offset and uses a naive-looking local representation, so users cannot tell which instant it denotes. F20 medium: Rendered times are ambiguous across zones and DST. |
be-trustworthyno-dark-patterns | issues | high | The first consent layer gives a prominent one-click accept action but sends rejection into “More options”; the wall also emphasizes 1,725 partners and blocks the marketplace. F21 high: Consent choice architecture is asymmetric. |
be-trustworthyhumane-error-handling | issues | medium | The detail probe found visible number/date/message inputs with required=false and no associated labels; this prevents reliable native required feedback and accessible error association. F22 medium: Forms do not expose native required/error semantics. |
be-trustworthytrustworthy-input-assistance | issues | high | The search and seller-message fields returned empty autocomplete values, so the browser receives no explicit purpose hints. F23 low: Input assistance metadata is missing. |
be-trustworthysafe-commercial-and-account-flows | issues | medium | Posting redirects directly to an authentication screen and the visible account surface offers social identity providers before users can draft, review commitments or preserve work. F24 medium: Account/commercial flow starts with continuity pressure rather than reversible drafting. |
be-sustainableoptimised-assets | issues | high | Home has 40/42 images without srcset and 9 legacy-format images; detail has 6 legacy JPEGs, missing dimensions and oversized thumbnails. F25 medium: Asset delivery is not consistently optimized for resolution or format. |
be-sustainableno-wasteful-work | issues | high | Before any consent decision, home performs 46 requests and loads multiple tag, CMP, identity, recommendation and analytics resources; 34 requests are classified third-party. F26 high: Initial background/vendor work is disproportionate to the core listing task. |
be-sustainablethird-party-and-media-budget | issues | high | The representative advert transferred 3.38 MB across 91 requests; 3.13 MB and 75 requests were third-party, including ads, tracking, identity and reCAPTCHA. F27 high: Third-party and media weight is excessive for a classifieds detail page. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent was found; this emerging capability is contextual and absence is not penalised. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the audited marketplace surfaces declared a need for on-device inference; the emerging check is contextual. |
be-memory-efficientno-leak-under-repeated-interaction | issues | low | Heap summaries moved from 33,262,571 bytes/688,748 nodes at baseline to 35,840,889 bytes/725,883 nodes after ten full-page scroll cycles, about +7.8% bytes and +5.4% nodes. Separate-load variance lowers confidence, but the growth warrants profiling. F28 low: Repeated long-list interaction increased retained heap noticeably. |
be-memory-efficientbounded-footprint | issues | medium | A fresh listing snapshot contained 688,748 heap nodes and 33.3 MB self size before extended interaction, high for a server-rendered classified list and consistent with its heavy vendor surface. F29 low: The listing has a large initial heap footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Heap summaries did not surface a top retained Detached* constructor population; the growth signal is separately and cautiously reported. |
Provenance
Canonical report: results/atomic/reports/0588-www_publi24_ro.json
Report SHA-256: 938089d1c5c3d4b731bd2bdd44a94f6b09f1fd4550164f173d62cb35c13252bc
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_publi24_ro/2026-07-21T18-53-21-863Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_publi24_ro/2026-07-21T18-53-21-863Z
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.