Manifest position 743 · CrUX rank bucket 1000
https://www.kooora.com
Coverage complete
Coverage complete: all 58 catalog checks have conclusive outcomes.
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 computed root colorScheme is normal, and static CSS inspection found no prefers-color-scheme rule. F01 high: The site remains light under a dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe matched the preference but reported 171 animations, including pulse and repeated 1s openweb animations still running. F02 medium: Continuous animations remain active when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast: more screenshot is pixel-equivalent in appearance to the default capture; static inspection found no forced-colors support. F03 high: High-contrast preference produces no visible adaptation. |
implement-natural-interactionsview-transitions | pass | medium | Rendered CSS contains view-transition usage; representative routes load coherently without a jarring broken intermediate state. |
implement-natural-interactionsscroll-driven-animations | pass | medium | Static rendered CSS contains scroll-timeline rules and the trace does not show scroll-listener evidence as a specific failure. |
implement-natural-interactionsphysical-gestures | pass | medium | Rendered CSS contains scroll-snap and overscroll-behavior rules for score/navigation scrollers. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The homepage is 22,760 CSS px tall; static inspection found no scroll-state rules and screenshots show static chrome with no article/page progress cue. F05 medium: Long pages do not expose scroll-aware orientation or progress. |
provide-guided-navigationanchored-positioning | pass | medium | Rendered CSS contains anchor-name, position-anchor and position-try rules, providing edge-aware anchoring support. |
provide-guided-navigationdirects-attention | pass | medium | Screenshots show stable RTL nav hierarchy and selected competition tabs; real descriptive links carry users to article/match/detail templates. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots of home, article, match and competition all show a large modal before content can be used; mobile CTA text is clipped at the edge. F04 high: A consent wall obscures the entire primary experience on every tested template. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The quality probe found a large fixed DIV with role=dialog and aria-modal=true, while the DOM probe found zero dialog, popover and details elements. F06 medium: The consent modal is implemented as a fixed div rather than a native dialog. |
maximize-content-reduce-noisereduced-chrome | issues | high | All representative screenshots reserve a large top ad slot and then cover the remaining content with consent UI, leaving little immediately usable content. F07 medium: Advertising and consent chrome dominate the initial viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | At 360x800 the layout primitive measured scrollWidth=clientWidth=360 with zero horizontal overflow and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | medium | The rendered probe counted 144 container-rule objects and mobile/desktop captures show distinct component arrangements. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The active probe counted 17 controls below 24 px in one dimension; Lighthouse target-size failed 12 elements, although keyboard focus itself was visible. F08 medium: Numerous controls are too small for reliable touch interaction. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The homepage title, scores strip, news hero and navigation clearly communicate live sports/news purpose. |
support-core-task-successprimary-flow-completion | pass | medium | Real homepage anchors led successfully to representative article, match and competition pages; article content rendered with an H1. |
support-core-task-successclear-system-state-and-recovery | pass | medium | The invalid-route probe produced a titled Arabic apology page while retaining extensive working navigation back to content. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 18.1s, CLS 0.645, TBT 2,820ms and Time to Interactive 41.3s, producing performance score 0.09. F09 critical: Cold-load performance and stability are far outside good ranges. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse measured CLS 0.645; image inspection found 85 of 100 images without explicit dimensions. F10 high: The page shifts substantially during the measured load. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded 5 long tasks, a 379.68ms longest task and 508.84ms TBT; Lighthouse measured 2,820ms TBT under throttling. F11 high: Long JavaScript tasks block interaction. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 551 requests and 3.97MB transferred, including 88 scripts totaling 2.84MB and 156 fetch/XHR requests. F12 high: The initial page makes an excessive network request set. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 1,994KiB unused JavaScript and 115KiB unused CSS; HAR recorded 88 script requests. F13 high: Large amounts of shipped JavaScript and CSS are unused. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found 14 unnamed buttons, 5 unnamed links, one prohibited ARIA use, one unlabeled select and an untitled iframe. F14 high: Interactive controls lack accessible names and valid ARIA. |
be-inclusivesufficient-contrast | issues | high | Lighthouse color-contrast audit failed 189 nodes. F15 high: Many text/control combinations fail minimum contrast. |
be-inclusivestructure-and-focus | issues | high | Rendered homepage probe found zero H1 elements and the focusable list begins with an anchor with no text or aria-label; Lighthouse found unnamed links. F16 medium: The homepage lacks a primary H1 and includes unnamed focusable links. |
be-inclusivelegible-text | pass | medium | Representative screenshots show readable Arabic body and heading text with coherent RTL alignment; no clipping was seen outside the consent CTA issue. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse reports maximum-scale below 5 or user-scalable=no plus 12 insufficient target-size failures. F17 high: Viewport settings restrict zoom and targets are undersized. |
follow-best-practicesno-console-errors | issues | high | Lighthouse errors-in-console failed with 9 table entries. F18 medium: The page logs browser errors during load. |
follow-best-practicessound-document-and-assets | issues | high | Image inspection found 85 of 100 images without width/height and 97 legacy-format URLs; Lighthouse unsized-images only partially passed. F19 medium: Most images lack intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found one deprecated API, two BFCache blockers, 10 missing source maps for large first-party scripts, and one inspector issue. F20 medium: The page has deprecation, BFCache, source-map and DevTools issues. |
be-discoverabletitle-and-description | pass | medium | DOM probe found a descriptive Arabic title and meta description; both survived raw no-JS fetch. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse crawlable-anchors failed 97 items, despite the page having a valid viewport and robots.txt. F21 high: Many links are not crawlable anchors. |
be-discoverablecanonical-and-indexing-signals | pass | medium | Homepage has a canonical URL, index/follow robots meta, successful 200 response and robots.txt advertises a sitemap. |
be-discoverablestructured-and-shareable-metadata | pass | medium | Homepage exposes one JSON-LD block and complete core Open Graph title, description and 1200x630 image metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers probe found no HSTS and CSP allows unsafe-inline and unsafe-eval; cookies probe found three non-Secure cookies and every observed cookie had SameSite=None. F22 high: Transport policy and cookie attributes are weaker than the HTTPS origin suggests. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture saw 48 third-party origins and seven known tracker domains; Spot.IM alone made 337 requests across two origins. F23 high: The page contacts an extreme number of third parties and trackers. |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No notification, geolocation, camera or microphone prompt fired on load; Permissions-Policy disables geolocation, camera and microphone. Authentication was not required for the audited public task. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS is missing and CSP permits unsafe-inline/unsafe-eval; clickjacking, nosniff, referrer and permissions policies are present. F24 medium: Browser defenses are incomplete. |
be-resilientprogressive-enhancement | pass | medium | Discoverability captures show 90% homepage and 100% article content coverage in raw server HTML; neither is a JS shell. |
be-resilientresilient-runtime-behaviour | pass | medium | Article, match and competition templates all rendered navigable content at tested viewports; fixed consent overflow is recorded separately as an interruption issue. |
be-resilientoffline-and-installable | not-applicable | high | This public news/scores site is content-oriented rather than an installable application; offline installation is not necessary for the audited core task. |
be-resilientnetwork-and-http-failure-states | pass | medium | A deliberately invalid route produced an Arabic apology state with links back to the primary content instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The document declares lang=ar and renders coherent RTL navigation/content across desktop and mobile. |
be-internationalisedlocale-aware-data | pass | medium | Representative cards render Arabic-localised dates and times consistently (for example 22 يوليو 2026) rather than ambiguous numeric-only strings. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public content shows publication dates but no scheduling, recurring event creation, or user-entered time-zone-sensitive flow to evaluate. |
be-trustworthyno-dark-patterns | issues | high | The blocking modal has a bright accept button but no equally prominent reject action; the alternative is a smaller cookie-customisation text link. F25 high: Consent presents acceptance more prominently than refusal. |
be-trustworthyhumane-error-handling | not-applicable | high | No user-submitted form appears on the audited public content, article, match, competition, or error templates. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, or sign-up form was present on the representative public content paths. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Checkout, subscription, cancellation, and account-management are not part of the audited public scores/news journey. |
be-sustainableoptimised-assets | issues | high | Image inspection found 97 legacy-format URLs, 85 missing dimensions, two oversized images and two missing srcset opportunities. F26 high: The image pipeline rarely provides responsive modern assets. |
be-sustainableno-wasteful-work | issues | high | HAR recorded 551 requests while tracker evidence shows 201 API and 136 pixel requests to Spot.IM during initial load. F27 high: Background integrations perform hundreds of requests before user intent. |
be-sustainablethird-party-and-media-budget | issues | high | The page loads 48 third-party origins, 88 scripts and 2.84MB of script transfer before the user engages with optional features. F28 high: Third-party script cost is disproportionate to the core score/news task. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent or transactional capability was found; this emerging check is not applicable to the public editorial scope. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model interaction is offered or necessary for the audited editorial and score-consumption task. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten full-page down/up cycles retained heap grew only 327,383 bytes (0.32%) and 1,799 nodes (0.09%), with no monotonic leak signal in the summary. |
be-memory-efficientbounded-footprint | pass | medium | The loaded, third-party-heavy homepage retained about 103MB; post-interaction size remained essentially flat, proportionate though optimization is desirable. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appeared among the largest heap constructors and repeated scrolling did not produce material object/array growth. |
Provenance
Canonical report: results/atomic/reports/0743-www_kooora_com.json
Report SHA-256: 77b1ce9e7fd3d47d3ff6b93d059fc40c1278307ff209215143bdafaeed72b6e7
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_kooora_com/2026-07-22T19-37-12-471Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_kooora_com/2026-07-22T19-37-12-471Z
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.