Manifest position 910 · CrUX rank bucket 1000
https://www.yallakora.com
Coverage complete
Coverage-complete representative audit of six paths across four primary templates, search and HTTP failure recovery. Not covered: authenticated/account, checkout and editorial CMS surfaces because none are exposed by the public journeys.
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-condition screenshot is visually identical to the light capture; the preference probe reports color-scheme: normal and the CSS probe found no prefers-color-scheme rule. F01 medium: The site stays light when the user requests dark mode. |
respect-user-preferencesrespects-reduced-motion | pass | high | The reduced-motion probe confirmed the emulated preference and found zero active animations on the homepage. |
respect-user-preferencesrespects-contrast | issues | medium | Under prefers-contrast: more the probe still reports the normal scheme, while CSS inspection found no prefers-contrast or forced-colors rules. F02 low: High-contrast preferences are not handled explicitly. |
implement-natural-interactionsview-transitions | issues | medium | CSS inspection found no view-transition opt-in on the homepage, so navigation from the entry page cannot participate in a cross-document transition. F03 low: Primary cross-document navigation lacks a consistent transition. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked parallax, scrollytelling or reveal behavior was observed on the representative templates, so there is no scroll animation implementation to assess. |
implement-natural-interactionsphysical-gestures | pass | high | CSS inspection found scroll-snap support and the visible match/news carousels retain explicit previous/next controls on touch layouts. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | Mobile screenshots show a fixed header and fixed ticker, while CSS inspection found no scroll-state container/query or progress treatment. F04 low: Site chrome does not adapt to scroll state. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored popover or viewport-edge menu was encountered in the representative journeys. |
provide-guided-navigationdirects-attention | pass | high | Current day/section states are visibly highlighted in blue on homepage and match-center navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a fixed notification prompt/ticker across the bottom; the desktop entry also dedicates both side rails and large blank blocks to advertising. F05 high: Persistent prompts and advertising obscure or displace core content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM probes found zero dialog, popover and details elements despite the visible notification prompt and custom close controls. F06 medium: Dismissible UI is built from ad-hoc controls rather than semantic overlay primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | The 1440px screenshots show side-rail ads, large reserved ad gaps and a bottom ticker; the article headline does not begin until roughly 570px down the viewport. F07 high: Advertising and persistent chrome dominate the reading surface. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout captures on homepage, news listing and matches report 360px content width, 360px viewport and 0 horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | Across four templates, CSS probes found no @container rules even though the same match/news cards appear in wide and narrow placements. F08 low: Reusable components depend on viewport-oriented CSS rather than container-aware adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The homepage probe found 19 of 210 visible interactive targets below 24px in one dimension; axe also found two unnamed carousel buttons. F09 medium: Some controls are undersized or lack clear keyboard semantics. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, article, listing and matches screenshots make news, article reading and fixtures purpose visually clear with descriptive navigation. |
support-core-task-successprimary-flow-completion | issues | high | Navigating to /search?q=الأهلي redirected to the homepage and displayed “no search results” while unrelated homepage articles were listed beneath it. F10 high: Search does not complete its core journey predictably. |
support-core-task-successclear-system-state-and-recovery | issues | high | The unknown URL renders the raw ASP.NET “Server Error in / Application” page with framework versions and no links, search, retry or route back to content. F11 high: The not-found state offers no recovery path. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured homepage LCP 4.30s and article LCP 3.71s, with performance scores 0.74 and 0.76. F12 high: Mobile LCP is outside the good range on primary templates. |
be-fast-and-stablevisual-stability | pass | high | Measured CLS was near zero: 0.000065 in Lighthouse and 0.000083 in mobile layout observation, with no visible content jump in captures. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 343ms TBT on the homepage and 306ms on the article even though the separate warm trace did not record a long task. F13 medium: Main-thread blocking remains material in mobile lab runs. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR recorded 157 requests and 2.42MB transferred, including 38 scripts totaling 1.52MB and numerous parser-inserted stylesheet candidates. F14 medium: The request graph is large and script-heavy. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 672KiB of unused JavaScript and 17KiB of unused CSS; multiple analytics tags and ad libraries dominate the waste. F15 medium: Large amounts of shipped JavaScript and CSS are unused. |
be-inclusivenames-roles-labels | issues | high | axe found two critical unnamed carousel buttons and a missing-alt image on both homepage and article; the image probe counted 59 images without alt values. F16 high: Core carousel controls and imagery lack accessible names or alternatives. |
be-inclusivesufficient-contrast | issues | high | axe reported a serious color-contrast violation on #PollVote and marked 11 additional homepage nodes for manual contrast review. F17 medium: At least one primary action fails minimum color contrast. |
be-inclusivestructure-and-focus | issues | high | The homepage has no h1; axe found article heading-order, list and listitem violations, and probes show heading sequences beginning at h4. F18 medium: Heading and list structure is inconsistent across templates. |
be-inclusivelegible-text | pass | high | Representative desktop/mobile screenshots show readable Arabic body and heading text without clipping, and narrow layouts do not overflow. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At 360px the page reflows without overflow, but the probes counted 19 undersized homepage targets and 9 undersized match-page targets. F19 medium: Several controls remain too small for reliable touch use. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured failed service-worker registration and repeated 429 failures for the manifest, menu, carousel and page scripts. F20 medium: Primary pages log runtime and network errors. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 14 images without dimensions and 8 oversized images; Lighthouse found a poll image displayed at an incorrect aspect ratio. F21 medium: Image metadata and sizing are inconsistent. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported deprecated Attribution Reporting usage and inspector issues in both tested primary templates. F22 low: The page uses a deprecated browser API and produces DevTools issues. |
be-discoverabletitle-and-description | pass | high | All four template probes found descriptive titles and meta descriptions; the article title describes its visible story. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable anchors; the homepage includes javascript:void(0) links, and template probes found multiple empty/unlabelled href anchors. F23 medium: Some navigation controls are not crawlable links. |
be-discoverablecanonical-and-indexing-signals | pass | high | All tested templates expose canonical URLs and index/follow robots metadata; robots.txt is valid and points to a populated feed sitemap. |
be-discoverablestructured-and-shareable-metadata | pass | high | Probes found JSON-LD and Open Graph metadata on all representative templates, including three JSON-LD blocks and 16 social properties on the article. |
be-private-and-securesecure-transport-and-headers | issues | high | The header primitive found no CSP, HSTS or nosniff; the cookie audit found 8 of 9 cookies without Secure and several SameSite=None cookies. F24 high: Transport is HTTPS, but baseline security headers and cookie flags are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker scan found 24 third-party origins and 9 known tracker domains; the HAR attributes 105 requests and 1.96MB to third parties. F25 high: Tracking and advertising execute across a very broad third-party surface. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No account/authentication flow exists in the tested public surfaces; Lighthouse confirms no notification or geolocation permission request on load. |
be-private-and-securedefensive-browser-policies | issues | high | No frame protection, Referrer-Policy or Permissions-Policy was present, in addition to missing HSTS and CSP. F26 high: Browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 100% rendered-word coverage in raw HTML for homepage and article, with title/description and article h1 present without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Core homepage, listing, article and match content rendered in mobile/desktop states and mobile layouts reported no clipping from horizontal overflow. |
be-resilientoffline-and-installable | issues | high | A standalone manifest exists, but Lighthouse repeatedly received 429 for it and service-worker registration failed because firebase-messaging-sw.js returned 429. F27 medium: Installability and offline support are unreliable. |
be-resilientnetwork-and-http-failure-states | issues | high | The tested missing route returns a bare ASP.NET 404 containing framework versions and no navigation or recovery control. F28 high: HTTP failure handling exposes a raw framework error. |
be-internationalisedlang-dir-and-logical-properties | issues | high | All templates set lang=ar but omit dir=rtl; the homepage CSS probe counted 534 physical directional declarations and only 1 logical-property occurrence. F29 medium: RTL intent is implicit and CSS relies overwhelmingly on physical directions. |
be-internationalisedlocale-aware-data | issues | high | The Arabic matches page visibly renders MON/TUE/WED/THU beneath dates, indicating fixed labels rather than consistently locale-aware formatting. F30 low: Date presentation mixes Arabic content with fixed English labels. |
be-internationalisedtime-zone-correctness | not-applicable | high | The tested public pages display published/match times but expose no user-created or cross-time-zone scheduling flow whose storage/DST behavior can be exercised. |
be-trustworthyno-dark-patterns | pass | high | No checkout, forced continuity, confirmshaming or disguised primary action was observed; notification choices are visibly separate and dismissible. |
be-trustworthyhumane-error-handling | pass | high | The poll uses associated radio labels and exposes a specific “answer the question first” validation message after interaction. |
be-trustworthytrustworthy-input-assistance | issues | high | Across templates the visible search input has no associated label or aria-label and an empty autocomplete value. F31 low: The search input lacks an accessible label and input assistance metadata. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription purchase, authentication or account-management flow is present in the tested public site surfaces. |
be-sustainableoptimised-assets | issues | high | The image audit found 19 below-fold images not lazy-loaded, 33 without srcset, 8 oversized and 12 legacy-format images. F32 medium: Asset delivery still wastes bytes despite broad WebP adoption. |
be-sustainableno-wasteful-work | issues | high | Third parties account for 105 of 157 requests and 1.96MB; multiple GTM/gtag files and advertising auctions start during initial load. F33 high: Background advertising and analytics work is disproportionate to the content load. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party traffic is about 81% of transfer weight; the HAR includes a 193KB advertising video plus large ad and analytics scripts before user request. F34 high: Third-party media and scripts consume most transferred bytes. |
be-agent-readystructured-agent-capabilities | not-applicable | high | This public sports publisher exposes no declared agent-facing capability surface; the emerging WebMCP opportunity is outside current site intent. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the tested publisher surfaces declares a need for on-device inference; absence is not penalized for this emerging contextual check. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten next/previous carousel cycles, retained snapshot totals decreased from 28.22MB/544,368 nodes to 26.05MB/507,119 nodes rather than growing. |
be-memory-efficientbounded-footprint | pass | medium | Heap summary measured 28.22MB self size for the fully loaded, ad-heavy homepage; the post-interaction state was lower at 26.05MB. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The post-interaction heap was smaller in nodes, edges, closures, objects and native size; no Detached constructor appeared among the largest retained constructors. |
Provenance
Canonical report: results/atomic/reports/0910-www_yallakora_com.json
Report SHA-256: 1320d0bba3da8c9ecd571c48a6bcb1aa4e5d12203aafbeeb697f640baba6f701
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_yallakora_com/2026-07-23T19-16-16-743Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_yallakora_com/2026-07-23T19-16-16-743Z
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.