Manifest position 41 · CrUX rank bucket 1000
https://zebawy.com
Coverage complete
Coverage-complete representative-template audit. Not covered: exhaustive pagination/taxonomy URLs, legal-policy text review, account mutation, comment submission, and full media-library playback; sampled templates represent those repeated surfaces.
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 is pixel-identical in appearance and byte size to the light capture (245,560 bytes), while the DOM probe finds no color-scheme, prefers-color-scheme, or light-dark() CSS. F01 medium: The site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion probe reports zero active animations under prefers-reduced-motion: reduce; there is no non-essential motion to suppress. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/high-contrast screenshot retains visible text, media labels, navigation, and controls. |
implement-natural-interactionsview-transitions | issues | high | DOM and evaluate probes across all four templates found no view-transition CSS or startViewTransition use; the menu recording contains only a single abrupt state frame. F02 low: Route changes and menu state changes have no View Transition treatment. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation is present, so there is no scroll handler or declarative timeline to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The audited templates expose no gesture-driven interaction requiring snap, swipe, pull, or overscroll behavior. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The mobile homepage is 9,774 CSS pixels tall and the category is 10,224 pixels tall, but probes found no sticky scroll-state query, progress indicator, or related scroll-position affordance. F03 low: Very long listing pages provide no scroll-position feedback. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, contextual popover, or edge-positioned menu appears on the exercised paths. |
provide-guided-navigationdirects-attention | pass | high | Selected filter is underlined, page headings identify context, and content cards provide clear linked targets on desktop/mobile. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots show content immediately with no viewport-blocking modal; the Telegram notice is inline and does not obscure content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Rendered DOM contains duplicate login/reset forms and hash-triggered overlay links, but zero dialog, popover, or details elements across templates. F04 medium: Login and password overlays are custom hidden markup rather than semantic dialog/popover primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | Homepage and detail screenshots devote the main viewport to media cards/player with compact site chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Mobile layout probes report 0 horizontal overflow at 360px for home, category, and detail. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The same card template appears in homepage, category and search-result contexts, but all DOM probes found no @container or container-type rules. F05 low: Reusable listing cards adapt only through page-level CSS, with no component-level container behavior. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The active focus probe found no outline or box shadow on 34 of the first 40 focusable elements on home/category and 38 of 40 on detail. It also found 5 to 9 sampled controls under 44 CSS pixels; Lighthouse flags 24 target-size failures. F06 high: Keyboard focus is usually invisible and several controls are too small. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage/category visibly present browsable media cards; detail page places a large play control first. |
support-core-task-successprimary-flow-completion | pass | high | Listing links reach a detail page; direct player probe reports readyState 4 and a 720-second media resource with no media error. |
support-core-task-successclear-system-state-and-recovery | issues | high | The search page says “0 video found” and “nothing matched” but immediately renders a long grid of unrelated videos; the screenshot shows no retry field or suggested action in the state block. F07 medium: The empty-search state contradicts itself and does not provide a clear recovery action. |
be-fast-and-stablegood-core-web-vitals | issues | medium | The DevTools trace measured LCP at 2,853 ms; Lighthouse measured 2.5 s. CLS was excellent and TBT low, so the risk is concentrated in largest-content discovery and delivery. F08 medium: Homepage LCP is at or beyond the good Core Web Vitals threshold. |
be-fast-and-stablevisual-stability | pass | high | CLS was 0.000017 on home and 0 on category/detail mobile captures. |
be-fast-and-stableefficient-main-thread | pass | high | Trace summaries show 47ms homepage TBT and 0ms detail TBT; layout found no homepage long tasks and one 54ms detail task. |
be-fast-and-stableefficient-resource-delivery | issues | high | Images probe: 30/32 homepage images oversized, 31/32 without srcset, 27 below-fold images not lazy, and 30 legacy-format images. HAR transferred 720 KB of images and identified parser-blocking styles/scripts; Lighthouse flags LCP discovery. F09 high: Image and critical-resource delivery is substantially wasteful. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 67 KiB unused JavaScript and 14 KiB unused CSS. The detail page ships 20 scripts and 380,317 third-party bytes, including old Video.js and advertising code. F10 medium: Unused and third-party code adds avoidable work. |
be-inclusivenames-roles-labels | issues | high | The probe found the visible search input and several login fields without associated labels or aria-label; duplicate hidden login/reset forms repeat the problem. Several image/icon links also have empty text. F11 high: Search and authentication inputs lack reliable accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reports three insufficient foreground/background contrast failures and two cases where links rely on color alone. F12 high: Text and links fail color-contrast requirements. |
be-inclusivestructure-and-focus | issues | high | Homepage headings begin H2 then H1 and category has two H1 elements; focus is invisible on 34–38 of 40 sampled controls. Main/nav and a skip link do exist. F13 high: Heading order and focus treatment do not provide a robust reading/navigation structure. |
be-inclusivelegible-text | pass | high | Mobile screenshots show readable Arabic headings/card titles with wrapping and no clipping or horizontal overflow. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Every template declares maximum-scale=1.0 and user-scalable=0; Lighthouse fails meta-viewport. The detail player markup contains a video source but no track element. F14 high: Zoom is disabled and the representative video has no captions track. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with zero items. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse reports 16 deprecation warnings and an inspector issue. Its responsive-image audit fails, while the image probe finds two images without dimensions and 30 oversized images. F15 medium: The page uses deprecated APIs and ships incorrectly sized image assets. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports 16 deprecation warnings and an inspector issue. Its responsive-image audit fails, while the image probe finds two images without dimensions and 30 oversized images. F15 medium: The page uses deprecated APIs and ships incorrectly sized image assets. |
be-discoverabletitle-and-description | issues | high | The no-result search template has no meta description and no canonical URL, unlike home/category/detail. F16 medium: Search-result metadata is incomplete. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Every template declares maximum-scale=1.0 and user-scalable=0; Lighthouse fails meta-viewport. The detail player markup contains a video source but no track element. F14 high: Zoom is disabled and the representative video has no captions track. |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt points to https://zebawy.com/sitemap.xml, but direct request and headers returned 403 Forbidden. F17 medium: The sitemap URL advertised by robots.txt returns HTTP 403. |
be-discoverablestructured-and-shareable-metadata | pass | high | Home/category/detail DOM contains JSON-LD and Open Graph metadata aligned to page title and canonical content. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers probe found no CSP, HSTS, nosniff, clickjacking protection, Referrer-Policy, or Permissions-Policy. All three cookies lacked Secure; two analytics cookies used SameSite=None and lasted 400 days. F18 high: Core browser security headers are absent and cookies are insecurely scoped. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker probe observed 13 third-party origins and known Google trackers. HAR attributed 221,006 third-party bytes on home and 380,317 on detail; advertising domains load before any observed consent choice. F19 high: Advertising and analytics create a large, opaque third-party privacy footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | DOM probes found password/login fields with no autocomplete values and no WebAuthn or navigator.credentials use; some duplicate login fields are also unlabeled. F20 medium: Authentication uses password-only forms without autofill tokens or passkey support. |
be-private-and-securedefensive-browser-policies | issues | high | Headers probe found no CSP, HSTS, nosniff, clickjacking protection, Referrer-Policy, or Permissions-Policy. All three cookies lacked Secure; two analytics cookies used SameSite=None and lasted 400 days. F18 high: Core browser security headers are absent and cookies are insecurely scoped. |
be-resilientprogressive-enhancement | pass | high | Discoverability captures show 100% content visibility without JavaScript on home and detail, with title, H1 and description in raw HTML. |
be-resilientresilient-runtime-behaviour | issues | medium | The detail HAR records two 403 responses from wp-admin/admin-ajax.php while the visible page provides no failed-action or retry message. F21 medium: Detail-page background requests fail without a user-facing recovery state. |
be-resilientoffline-and-installable | not-applicable | high | This is a server-rendered media catalogue rather than an installable application; offline playback is not a declared product capability. |
be-resilientnetwork-and-http-failure-states | issues | high | The search page says “0 video found” and “nothing matched” but immediately renders a long grid of unrelated videos; the screenshot shows no retry field or suggested action in the state block. The detail HAR records two 403 responses from wp-admin/admin-ajax.php while the visible page provides no failed-action or retry message. F07 medium: The empty-search state contradicts itself and does not provide a clear recovery action. F21 medium: Detail-page background requests fail without a user-facing recovery state. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The Arabic document correctly sets lang=ar and dir=rtl, but the homepage/category DOM contains physical left/right rules and the probe finds no logical-property CSS. F22 low: The RTL layout relies on physical left/right CSS rather than logical properties. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative pages show no dates, currencies, localized numbers, or calendar data. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative pages contain no event time or timezone-sensitive workflow. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, confirmshaming, forced continuity, disguised CTA, or irreversible action appeared in the exercised paths. |
be-trustworthyhumane-error-handling | pass | high | The exercised search error uses plain-language feedback without blaming the user; its contradictory recommendations are separately recorded under system recovery. |
be-trustworthytrustworthy-input-assistance | issues | high | DOM probes found password/login fields with no autocomplete values and no WebAuthn or navigator.credentials use; some duplicate login fields are also unlabeled. F20 medium: Authentication uses password-only forms without autofill tokens or passkey support. |
be-trustworthysafe-commercial-and-account-flows | issues | high | DOM probes found password/login fields with no autocomplete values and no WebAuthn or navigator.credentials use; some duplicate login fields are also unlabeled. F20 medium: Authentication uses password-only forms without autofill tokens or passkey support. |
be-sustainableoptimised-assets | issues | high | Images probe: 30/32 homepage images oversized, 31/32 without srcset, 27 below-fold images not lazy, and 30 legacy-format images. HAR transferred 720 KB of images and identified parser-blocking styles/scripts; Lighthouse flags LCP discovery. F09 high: Image and critical-resource delivery is substantially wasteful. |
be-sustainableno-wasteful-work | issues | high | Lighthouse estimates 67 KiB unused JavaScript and 14 KiB unused CSS. The detail page ships 20 scripts and 380,317 third-party bytes, including old Video.js and advertising code. Tracker probe observed 13 third-party origins and known Google trackers. HAR attributed 221,006 third-party bytes on home and 380,317 on detail; advertising domains load before any observed consent choice. F10 medium: Unused and third-party code adds avoidable work. F19 high: Advertising and analytics create a large, opaque third-party privacy footprint. |
be-sustainablethird-party-and-media-budget | issues | high | Tracker probe observed 13 third-party origins and known Google trackers. HAR attributed 221,006 third-party bytes on home and 380,317 on detail; advertising domains load before any observed consent choice. F19 high: Advertising and analytics create a large, opaque third-party privacy footprint. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No transactional or productivity capability was found that needs WebMCP exposure; the emerging agent interface is out of scope for this media catalogue. |
be-agent-readyon-device-inference | not-applicable | high | No summarization, generation, or language-model task is part of the observed experience. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 20 menu toggles, heap node count decreased by 39 and self size grew only 13,818 bytes (0.14%), with no Detached* constructor in top summaries. |
be-memory-efficientbounded-footprint | pass | high | Homepage probe reports about 10.4MB used JS heap and 727 DOM nodes; heap summary is about 10.2MB self size, proportionate to the listing. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Baseline/post heap summaries show no Detached* top constructor and stable node count after repeated menu toggles. |
Provenance
Canonical report: results/atomic/reports/0041-zebawy_com.json
Report SHA-256: 67b37f157bea4079286faa17f7bfba28b95d722703fa8e4a62cc87d425bd0035
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/zebawy_com/2026-07-18T00-34-32-970Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/zebawy_com/2026-07-18T00-34-32-970Z
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.