Manifest position 715 · CrUX rank bucket 1000
https://www.namasha.com
Coverage complete
Coverage-complete audit across five representative archetypes/journeys.
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 in theme to the normal capture, and the CSS probe found zero color-scheme or prefers-color-scheme rules. F01 medium: The site does not adapt to the user’s dark color preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The reduced-motion emulation matched successfully and no active page animations remained; the player and navigation remained usable. |
respect-user-preferencesrespects-contrast | pass | high | The increased-contrast probe matched and found two explicit contrast/forced-color CSS rules; Lighthouse separately identified only ordinary-theme contrast defects. |
implement-natural-interactionsview-transitions | issues | high | The live CSS probe found zero view-transition rules despite the browser exposing document.startViewTransition. F02 low: Navigation changes have no View Transition treatment. |
implement-natural-interactionsscroll-driven-animations | issues | high | The homepage is 23,704px tall at mobile size, while the CSS probe found no animation-timeline or scroll-timeline rules. F03 low: The long discovery feed provides no scroll-linked progress or entry feedback. |
implement-natural-interactionsphysical-gestures | pass | high | Mobile screenshots and layouts show native vertical scrolling with no hijacking or horizontal overflow; player controls use direct click/tap interaction. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Mobile layout measured a 23,704px document; recon and CSS probes found no scroll progress or scroll-state treatment in the page chrome. F04 medium: The very long homepage lacks scroll-state-aware orientation. |
provide-guided-navigationanchored-positioning | pass | high | Action menus are visibly tied to their invoking more controls and remain within the card layout; no clipping was observed in representative captures. |
provide-guided-navigationdirects-attention | pass | high | The featured player, section headings, search control, and red account action establish a consistent visual hierarchy across homepage and listings. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No modal, consent wall, ad interstitial, notification prompt, or autoplay-with-sound interruption appeared on any representative path. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The platform probe enumerated many div.action-menu elements with role=dialog, no dialog element, and no popover attribute. F05 medium: Repeated action menus are custom div dialogs rather than semantic top-layer primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | Homepage, listing, search, video, and login captures keep chrome compact and devote the majority of the viewport to video/content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout primitives at 360x800 reported 0px horizontal overflow on homepage, search, and video templates. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | The same header, cards, player, and results adapt from 780px captures to 360px without clipping; mobile layouts fit the viewport. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse and the live target probe found repeated 20x20px more-menu buttons, below even Lighthouse’s 24px minimum and well below a comfortable 44px touch area. F10 medium: Many feed action targets are too small for touch. |
support-core-task-successclear-purpose-and-primary-action | issues | high | Mobile layout measured a 23,704px document; recon and CSS probes found no scroll progress or scroll-state treatment in the page chrome. F04 medium: The very long homepage lacks scroll-state-aware orientation. |
support-core-task-successprimary-flow-completion | pass | high | Search returns populated results, the sampled video reaches readyState 4 and plays, and login submission returns actionable validation. |
support-core-task-successclear-system-state-and-recovery | issues | high | Blank submission produced clear Persian field messages, but none had role=alert or aria-live and fields did not expose aria-invalid. F16 medium: Login validation errors are not announced as status messages. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 4.5s, FCP 3.4s, Speed Index 16.6s, and TTI 10.3s (performance 0.68); the trace observed a late LCP at 32.8s under its network run. F06 high: Slow visual completion delays the core browse/watch experience. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout evidence measured CLS 0 on homepage/search and 0.00079 on video, with no meaningful instability. |
be-fast-and-stableefficient-main-thread | pass | high | Trace summary found zero long tasks and 0ms total blocking time; Lighthouse TBT was 90ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | The image audit found 100/100 legacy-format images, 51 without srcset, 49 below-fold images not lazy-loaded, and four oversized images. HAR transferred 1.99MB, including 1.13MB images. F07 high: Preview images and scripts are delivered inefficiently. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The image audit found 100/100 legacy-format images, 51 without srcset, 49 below-fold images not lazy-loaded, and four oversized images. HAR transferred 1.99MB, including 1.13MB images. F07 high: Preview images and scripts are delivered inefficiently. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found aria-expanded on a roleless div and repeated “مشاهده همه” links whose aria-label excludes their visible text; accessibility score was 0.86. F08 high: ARIA and accessible-name failures affect repeated controls. |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured the blue “مشاهده همه” links at 2.92:1 on #f8f9fa (4.5:1 required), with additional footer text at 4.44:1. F09 medium: Repeated links and footer text miss WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse found aria-expanded on a roleless div and repeated “مشاهده همه” links whose aria-label excludes their visible text; accessibility score was 0.86. F08 high: ARIA and accessible-name failures affect repeated controls. |
be-inclusivelegible-text | pass | high | Visual evidence shows readable Persian typography, spacing, line wrapping, and clear card grouping on desktop and mobile. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse and the live target probe found repeated 20x20px more-menu buttons, below even Lighthouse’s 24px minimum and well below a comfortable 44px touch area. The playable video reached readyState 4 and played, but both player and metadata probes found zero track elements for a 6:22 spoken/animated video. F10 medium: Many feed action targets are too small for touch. F18 high: The sampled video has no captions or subtitle track. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured a FedCM NetworkError and “Not signed in with the identity provider” on the homepage. F11 low: Google Identity emits console errors on ordinary homepage load. |
follow-best-practicessound-document-and-assets | pass | high | Live probe confirmed HTML doctype, UTF-8, viewport metadata, semantic landmarks, descriptive image alt text, and zero mobile overflow. |
follow-best-practicesbrowser-platform-hygiene | pass | high | The page uses HTTPS, native links/forms, visible focus outlines, and no permission prompt or paste prevention appeared during tested flows. |
be-discoverabletitle-and-description | pass | high | Homepage and video pages have unique Persian titles and descriptions in both rendered and raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Raw/rendered coverage was 98% homepage, 90% video, and 100% search; links have href values and mobile viewports do not overflow. |
be-discoverablecanonical-and-indexing-signals | issues | high | GET /sitemap.xml returned an HTML document and HEAD confirmed HTTP 404, while robots.txt declares no alternative Sitemap location. F19 medium: The conventional sitemap URL returns an HTML 404 page. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage has three JSON-LD blocks and Open Graph metadata; video has VideoObject JSON-LD, Open Graph video, Twitter player, and DC metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Header evidence found no CSP, HSTS, nosniff, frame protection, or Permissions-Policy. All three observed cookies lacked Secure and used SameSite=None; response also discloses very old Django/Python server versions. F12 high: Core browser security headers and cookie protections are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found Google Tag Manager and Google Analytics; HAR attributed 33 of 35 requests and 1.95MB to origins outside www.namasha.com (mostly Namasha CDNs, plus Google), and analytics cookies persist for 400 days. F13 medium: Analytics and identity integrations add a broad third-party footprint without visible contextual disclosure. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No browser permission prompt appeared on load; sign-in is user-initiated and offers an in-context Google identity option. |
be-private-and-securedefensive-browser-policies | issues | high | Header evidence found no CSP, HSTS, nosniff, frame protection, or Permissions-Policy. All three observed cookies lacked Secure and used SameSite=None; response also discloses very old Django/Python server versions. F12 high: Core browser security headers and cookie protections are missing. |
be-resilientprogressive-enhancement | pass | high | Discoverability captures show 90–100% raw HTML content coverage across homepage, video, and search, not a JavaScript shell. |
be-resilientresilient-runtime-behaviour | pass | high | Video initially showed a loader but reached readyState 4 and played after waiting; search and login validation completed without a broken state. |
be-resilientoffline-and-installable | issues | high | A valid standalone manifest is linked, but the runtime probe found zero service-worker registrations and no named caches. F14 medium: The site advertises standalone installation but has no offline/runtime support. |
be-resilientnetwork-and-http-failure-states | pass | high | The login flow returns inline recovery messages and the video player retains an explicit loading state during delayed media startup. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html has lang=fa-IR but an empty dir attribute; computed body direction is rtl. F15 medium: The Persian RTL direction is only applied through CSS, not document semantics. |
be-internationalisedlocale-aware-data | pass | high | The Persian interface uses fa-IR, Persian digits and a Persian-calendar publication date while machine metadata includes an ISO timestamp with +03:30. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling or cross-time-zone interaction is present in the representative public and login paths. |
be-trustworthyno-dark-patterns | pass | high | No confirmshaming, forced opt-in, deceptive pricing, or obstructive cancellation pattern appeared on public, search, video, or login paths. |
be-trustworthyhumane-error-handling | issues | high | Blank submission produced clear Persian field messages, but none had role=alert or aria-live and fields did not expose aria-invalid. F16 medium: Login validation errors are not announced as status messages. |
be-trustworthytrustworthy-input-assistance | pass | high | Login controls have programmatic labels and use autocomplete=username and current-password; recovery and privacy links are present. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The sampled login provides password recovery, Google sign-in, sign-up, privacy, and terms links without hidden charges or forced continuity. |
be-sustainableoptimised-assets | issues | high | HAR transferred 1.99MB on initial load, 1.13MB in images; 100 images use legacy formats, 49 below-fold images are eager, and 51 lack responsive sources. F17 high: The media-heavy homepage sends avoidable bytes for previews below the fold. |
be-sustainableno-wasteful-work | issues | high | HAR transferred 1.99MB on initial load, 1.13MB in images; 100 images use legacy formats, 49 below-fold images are eager, and 51 lack responsive sources. F17 high: The media-heavy homepage sends avoidable bytes for previews below the fold. |
be-sustainablethird-party-and-media-budget | issues | high | Tracker evidence found Google Tag Manager and Google Analytics; HAR attributed 33 of 35 requests and 1.95MB to origins outside www.namasha.com (mostly Namasha CDNs, plus Google), and analytics cookies persist for 400 days. HAR transferred 1.99MB on initial load, 1.13MB in images; 100 images use legacy formats, 49 below-fold images are eager, and 51 lack responsive sources. F13 medium: Analytics and identity integrations add a broad third-party footprint without visible contextual disclosure. F17 high: The media-heavy homepage sends avoidable bytes for previews below the fold. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The public video catalogue exposes no user-authorised agent workflow or tool surface for which WebMCP is presently applicable. |
be-agent-readyon-device-inference | not-applicable | high | The site has no summarisation, generation, or other inference feature where on-device AI is relevant. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | Representative screenshots and live DOM/CDP probes showed the expected outcome without an observed failure under the tested desktop, mobile, preference, and journey conditions. |
be-memory-efficientbounded-footprint | pass | high | Heap baseline was 23,922,582 bytes and post-scroll was 23,474,196 bytes; performance.memory used about 8.3MB for a media-heavy feed. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | After ten full-page scroll cycles node count increased only 0.6% (387,848 to 390,121) while total self size decreased; no unbounded retained growth signal appeared. |
Provenance
Canonical report: results/atomic/reports/0715-www_namasha_com.json
Report SHA-256: f96f61a323c49cd2a57a1c655d7548bef8fcb5d698cd108fd5109fd98b8308f0
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_namasha_com/2026-07-28T05-35-56-800Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_namasha_com/2026-07-28T05-35-56-800Z
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.