Manifest position 987 · CrUX rank bucket 1000
https://www.ynet.co.il
Coverage complete
Coverage-complete model-led audit across representative home, section, article, breaking-news, account-entry and error templates.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Light/dark captures are visually identical. F01 high: The interface does not meaningfully adapt to dark, reduced-motion, or increased-contrast preferences. |
respect-user-preferencesrespects-reduced-motion | issues | high | Ten animations remained active, including infinite animations. F01 high: The interface does not meaningfully adapt to dark, reduced-motion, or increased-contrast preferences. |
respect-user-preferencesrespects-contrast | issues | high | Preference matched but no contrast/forced-colors adaptation was present. F01 high: The interface does not meaningfully adapt to dark, reduced-motion, or increased-contrast preferences. |
implement-natural-interactionsview-transitions | issues | medium | No view-transition use was found for MPA navigation. F02 medium: Navigation changes are abrupt and do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No intentional parallax, scrollytelling, or scroll-linked reveal requiring a scroll timeline was identified on sampled templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No primary pull, swipe-to-remove, or other gesture-driven task was present in the sampled editorial and login journeys. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | Long pages lacked scroll-state query or progress signaling. F03 low: Long pages do not expose modern scroll-state-aware navigation chrome. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or viewport-edge anchored menu was required by the sampled primary journeys; the blocking consent modal is not an anchored overlay. |
provide-guided-navigationdirects-attention | pass | medium | Persistent labelled navigation, section headings, real internal hrefs, and a clear 404 home action orient users despite density. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Full-page consent interstitial obscures content. F04 high: A consent interstitial blocks the full page on every fresh visit. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Blocking modal uses generic divs; no dialog/popover exists. F05 medium: The blocking consent UI is built from generic divs rather than a dialog primitive. |
maximize-content-reduce-noisereduced-chrome | issues | medium | Homepage contains 1,427 links/438 images plus blocking and promotional chrome. F06 medium: The homepage is extremely dense with repeated navigation, cards, ads, and recommendation chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Viewport is fixed at 1240 and scaled to 0.29 on mobile. F07 critical: The site forces a 1,240px desktop layout on a 360px mobile viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | No container-query signal across five templates. F08 medium: Components rely on physical fixed-layout CSS rather than container-responsive composition. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Hundreds of sub-24px targets and invisible sampled focus states. F09 high: Touch targets and keyboard focus are not reliably usable. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Brand, news headlines, section labels and article titles make the editorial purpose and next reading actions clear. |
support-core-task-successprimary-flow-completion | issues | high | Consent modal blocks the representative read-an-article flow. F10 high: Reading primary content is gated by a full-page consent decision. |
support-core-task-successclear-system-state-and-recovery | pass | high | Unknown URL shows a specific error heading and a home-page recovery link. |
be-fast-and-stablegood-core-web-vitals | issues | high | LCP 9.6–11.3s, TBT 2.04–2.74s, CLS up to 0.32. F11 critical: Load and interaction performance are far outside good ranges. |
be-fast-and-stablevisual-stability | issues | high | Article CLS 0.466; 23/23 sampled article images lacked dimensions. F12 high: Article content shifts substantially during load. |
be-fast-and-stableefficient-main-thread | issues | high | 23 long tasks and severe TBT. F13 high: Heavy scripting repeatedly blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | 607 requests/16.98MB and extensive unoptimized image delivery. F14 critical: The homepage transfers an excessive network and image payload. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | 2.8–2.9MiB unused JavaScript and 500–568KiB unused CSS estimated. F15 high: Large amounts of unused JavaScript and CSS ship on initial load. |
be-inclusivenames-roles-labels | issues | high | Unnamed links/buttons and missing image alternatives were found. F16 high: Important links, buttons, and images lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Five home and two article contrast failures. F17 high: Text contrast fails on representative surfaces. |
be-inclusivestructure-and-focus | issues | high | First 25 sampled controls showed no visible focus; consent adds multiple H1s to document structure. F09 high: Touch targets and keyboard focus are not reliably usable. |
be-inclusivelegible-text | issues | high | Fixed 1240px canvas shrinks Hebrew text to an illegible scale on mobile. F18 critical: Mobile reflow and media accessibility are seriously compromised. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Shrink-to-fit viewport, hundreds of tiny targets, and captionless article video. F18 critical: Mobile reflow and media accessibility are seriously compromised. |
follow-best-practicesno-console-errors | issues | high | 16 home and 7 article console errors. F19 high: Representative pages log many browser errors. |
follow-best-practicessound-document-and-assets | issues | high | Doctype/charset pass, but nearly all homepage images lack intrinsic dimensions and many are oversized. F20 medium: Document assets are not soundly sized and browser inspector issues remain. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Inspector issues and broken source-map mappings were reported. F20 medium: Document assets are not soundly sized and browser inspector issues remain. |
be-discoverabletitle-and-description | issues | high | Login template has no meta description. F23 low: The login template has no meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Non-crawlable links, fixed-width viewport and only 4–10% raw content coverage. F21 medium: Mobile and crawler signals are inconsistent. |
be-discoverablecanonical-and-indexing-signals | issues | high | Pages have canonicals and robots is reachable, but /sitemap.xml is a 404 and no sitemap is advertised. F22 medium: The standard sitemap endpoint is missing and robots.txt does not advertise an alternative. |
be-discoverablestructured-and-shareable-metadata | pass | high | Editorial templates expose 2–3 JSON-LD blocks and 6–7 Open Graph fields matching visible titles. |
be-private-and-securesecure-transport-and-headers | issues | high | Missing HSTS/nosniff/referrer/permissions headers and insecure cookie attributes. F24 high: Security headers and cookie attributes are materially incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | 71 third-party origins and 27 known trackers with asymmetric consent choices. F25 critical: The page activates an extreme tracking and third-party footprint before a clear rejection choice. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | No on-load permission request was detected, but relevant auth flow lacks passkeys. F26 medium: The account flow offers email/social sign-in but no passkey path. |
be-private-and-securedefensive-browser-policies | issues | high | Frame protection exists, but HSTS, robust CSP directives, nosniff, Referrer-Policy and Permissions-Policy are absent. F24 high: Security headers and cookie attributes are materially incomplete. |
be-resilientprogressive-enhancement | issues | high | Article/news are classified as JS shells with 4–5% content overlap and blank crawler views. F27 high: Core article and listing content is largely unavailable without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | medium | Across five templates, content rendered, consent could be managed, and the explicit invalid route reached a stable recovery page. |
be-resilientoffline-and-installable | not-applicable | high | This public news MPA is not presented as an installable app; no offline app intent is declared, so PWA installability is not required for this check. |
be-resilientnetwork-and-http-failure-states | pass | high | A missing URL produces a specific “page does not exist” state and a link back home rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | lang=he but computed direction is ltr; physical CSS overwhelmingly dominates. F28 high: Hebrew pages compute left-to-right direction and depend heavily on physical CSS. |
be-internationalisedlocale-aware-data | pass | medium | Dates, temperatures, breaking-news times and surrounding labels are rendered in Hebrew conventions consistently on sampled pages. |
be-internationalisedtime-zone-correctness | not-applicable | high | No user-created event, cross-time-zone schedule, recurring interval, or editable time data was present in the sampled editorial/login journeys. |
be-trustworthyno-dark-patterns | issues | high | No initial Reject all; Manage options exposes 289 toggles with 63 checked. F29 high: Consent choices are asymmetric and many purposes are preselected. |
be-trustworthyhumane-error-handling | issues | high | No error, aria-invalid, describedby, focus move or invalid state appeared. F30 high: Submitting the empty email step provides no visible or accessible error state. |
be-trustworthytrustworthy-input-assistance | issues | high | Visible email field has no autocomplete token. F31 medium: The visible email sign-in field omits autocomplete metadata. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Sign-in lacks passkeys/autofill assistance, and account entry remains behind asymmetric consent UI. F26 medium: The account flow offers email/social sign-in but no passkey path. F29 high: Consent choices are asymmetric and many purposes are preselected. F31 medium: The visible email sign-in field omits autocomplete metadata. |
be-sustainableoptimised-assets | issues | high | 10.27MB/403 image requests with extensive legacy, oversized and eager assets. F32 high: Image delivery is wasteful for a text-led news homepage. |
be-sustainableno-wasteful-work | issues | high | Large startup workload and 74 new resource entries during repeated traversal. F33 high: Third-party scripts and background work dominate the resource budget. |
be-sustainablethird-party-and-media-budget | issues | high | 71 third-party origins, 5.46MB scripts, and 27 known tracking endpoints are disproportionate. F33 high: Third-party scripts and background work dominate the resource budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No agent-facing capability or declared agent integration intent was present; for this emerging contextual principle, absence is an opportunity rather than a failure. |
be-agent-readyon-device-inference | not-applicable | high | No product task requiring on-device inference was exposed in the sampled editorial/login journeys, and no agent-facing intent is declared. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | Heap/DOM grew materially after repeated traversal; confidence is medium because dynamic feed loading may explain part of growth. F34 medium: Repeated navigation-like scrolling grows retained heap and DOM materially. |
be-memory-efficientbounded-footprint | issues | high | Baseline is 147.4MB/2.05M heap nodes and 13,735 live DOM elements. F35 high: The initial page footprint is disproportionate for a news index. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appeared among the largest retained constructor populations; listener accumulation was not directly exposed, so confidence is medium. |
Provenance
Canonical report: results/atomic/reports/0987-www_ynet_co_il.json
Report SHA-256: 7a0dd6a45cdc78906e6131243a3758ad80fc48a27f4459a5b0ee0b8ddffa0546
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ynet_co_il/2026-07-24T08-56-12-753Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ynet_co_il/2026-07-24T08-56-12-753Z
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.