Manifest position 835 · CrUX rank bucket 1000
https://www.betika.com
Coverage complete
Coverage-complete representative audit of home betting, casino listing, registration, and failure-state 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 | Separate light- and dark-preference screenshots both rendered the same html.dark theme; the DOM contains a manual dark class and no root color-scheme declaration driven by the media preference. F02 medium: Theme is not driven by the system color preference |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, the probe still found a running 500 ms animation and found no prefers-reduced-motion rule. F03 medium: Motion continues when reduced motion is requested |
respect-user-preferencesrespects-contrast | pass | high | The forced-colors/prefers-contrast screenshot retained visible navigation labels, controls, and close affordance around the promotional image. |
implement-natural-interactionsview-transitions | issues | high | The DOM/CSS feature probe found no View Transition rules, and route changes use full abrupt state swaps. F04 low: Route and state changes are abrupt |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked parallax, scrollytelling, reveal, or carousel animation was present on the representative pages, so there is no scroll-linked implementation to assess. |
implement-natural-interactionsphysical-gestures | pass | high | The mobile catalog uses native vertical scrolling and ordinary click/tap controls; no custom pointermove gesture layer was found in the DOM/CSS probe. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Mobile evidence shows top navigation, sports navigation, filters, and bottom navigation remain fixed/static while scrolling; the CSS probe found no scroll-state query. F05 low: Persistent navigation does not adapt to scroll state |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, edge-positioned popover, or anchored transient menu was exposed in the representative public paths. |
provide-guided-navigationdirects-attention | pass | high | Mobile screenshots show selected Home/Casino destinations, selected filters, and active navigation state with distinct yellow/green treatment. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The first-load desktop screenshot is almost entirely covered by an advertising roadblock; at the 780x493 evidence viewport its close button is outside the visible modal bounds. F01 critical: An advertising roadblock obscures the core experience on load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The rendered overlay is a fixed DIV.modal mask; the probe found zero dialog, popover, and details elements. F06 medium: The modal is an ad-hoc DIV rather than a platform primitive |
maximize-content-reduce-noisereduced-chrome | issues | high | The mobile home view stacks a header, sports strip, tabs, filters, promotional carousel, and bottom bar, substantially reducing the match-content area. F07 medium: Stacked navigation and filters crowd the betting content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800 the layout primitive measured scrollWidth=clientWidth=360 and 0 px horizontal overflow; home, casino, and registration screenshots reflow to one-column/mobile layouts. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS/DOM probe found no @container rules on a component-rich responsive application; adaptation is viewport-wide only. F08 low: Reusable components do not use container-aware adaptation |
adapt-to-the-form-factorinput-modality-aware | issues | high | The viewport disables scaling, visible controls include 26-32 px targets, and the focused registration link computed outline-style none with no box shadow. F09 high: Zoom, target sizing, and focus treatment exclude input modes |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home immediately identifies soccer betting with match odds, while registration clearly labels its purpose and primary Register action. |
support-core-task-successprimary-flow-completion | issues | high | The mandatory roadblock precedes the betting surface and, at the desktop evidence height, its dismiss control was measured above the viewport; this creates an avoidable detour/blocker before the core flow. F10 high: The promotional roadblock blocks the primary betting journey |
support-core-task-successclear-system-state-and-recovery | issues | high | A deliberately unknown URL rendered the normal betting homepage with no 404/error explanation or recovery state; empty registration submission produced no visible field feedback. F11 medium: Error and not-found states provide no actionable recovery |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 34.1 s, TBT 940 ms, and CLS 0.134; the trace independently measured LCP 42.65 s. F12 high: Core Web Vitals are far outside good ranges |
be-fast-and-stablevisual-stability | issues | high | The mobile layout observer recorded CLS 0.779 with a 0.664 shift; 21 of 25 images lack explicit dimensions. F13 high: Late content causes severe layout shift |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 940 ms TBT; the trace recorded three long tasks up to 107 ms and 112 ms total blocking time in its capture. F14 medium: Heavy scripting blocks the main thread |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 172 requests and 5.86 MB transferred, parser-blocking CSS plus init.js, 12 redirects, and large/slow scripts and banners. F15 high: Initial resource delivery is excessively heavy and delayed |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 1,450 KiB unused JavaScript across 16 resources and 35 KiB unused CSS. F16 high: The page ships about 1.45 MiB of unused JavaScript |
be-inclusivenames-roles-labels | issues | high | axe found two unnamed buttons, six unnamed links, and an unlabeled form element; the image audit also found five images without alt text. F17 high: Controls, links, fields, and images lack accessible names |
be-inclusivesufficient-contrast | issues | high | axe found ten contrast failures in the direct run, including Register and sports-navigation labels; Lighthouse also failed color-contrast. F18 high: Text and control colors fail minimum contrast |
be-inclusivestructure-and-focus | issues | high | axe found content outside landmarks, an invalid list item, and a non-keyboard-focusable scrolling region; the focus probe found no visible outline on the tested registration link. F19 high: Landmark, list, scroll-region, and focus semantics are incomplete |
be-inclusivelegible-text | pass | high | Registration and casino mobile screenshots show readable text sizes, consistent alignment, and no text clipping in the representative viewports. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport declares maximum-scale=1,user-scalable=0; axe/Lighthouse fail the viewport zoom audit, and several controls are below a comfortable 44 px touch target. F20 high: The viewport prevents user zoom |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured four browser console errors during load. F21 medium: The page logs browser errors |
follow-best-practicessound-document-and-assets | issues | high | The document has a valid doctype and charset, but 21/25 images lack explicit dimensions and 20/25 are oversized for display. F22 medium: Images lack stable dimensions and are oversized |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found three deprecated-API warnings, 12 large first-party scripts without valid source maps, and a DevTools inspector issue. F23 medium: Deprecated APIs, missing source maps, and inspector issues reduce platform hygiene |
be-discoverabletitle-and-description | pass | high | The rendered home page has a descriptive soccer-betting title and meta description; the registration and casino routes also have route-specific titles. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found 13 non-crawlable anchors; the viewport prevents zoom even though robots.txt allows public routes. F24 medium: Some links are not crawlable and the viewport is hostile to mobile users |
be-discoverablecanonical-and-indexing-signals | issues | high | Lighthouse reports no valid canonical, and fetching /sitemap.xml returned the application HTML shell rather than XML sitemap entries. F25 high: Canonical and sitemap signals are broken |
be-discoverablestructured-and-shareable-metadata | pass | high | The rendered homepage exposes Open Graph title, description, URL and image plus one JSON-LD block aligned with the visible soccer-betting page. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but the headers primitive found no CSP, HSTS, nosniff, frame protection, Referrer-Policy, or Permissions-Policy; the cookie audit found 24 flagged cookies including non-Secure values. F26 high: Security headers and cookie protections are missing |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe found 58 third-party origins and 15 known tracker domains on first load; HAR attributed 146 requests and 4.67 MB to third-party origins. F27 high: Tracking starts across 58 third-party origins |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | No permission prompt fired on load, but registration exposes password-only account creation and the probes found no passkey/WebAuthn affordance. F28 medium: Registration offers passwords but no phishing-resistant option |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive found no clickjacking defense, CSP/frame-ancestors, HSTS, Referrer-Policy, or Permissions-Policy. F26 high: Security headers and cookie protections are missing |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 2% raw-HTML content coverage, no raw H1/title, and classified the page as a JavaScript shell. F29 high: Public content is a 2% JavaScript shell |
be-resilientresilient-runtime-behaviour | issues | high | The roadblock modal is a custom fixed DIV and its desktop close button was measured at y=-89, outside the 493 px viewport, leaving the overlay cut off. F30 high: The custom overlay is cut off at a common desktop viewport |
be-resilientoffline-and-installable | issues | high | A manifest exists, but the service-worker probe found zero registrations and zero caches, so this app-like site has no evidenced offline fallback. F31 medium: The app-like site has no active offline fallback |
be-resilientnetwork-and-http-failure-states | issues | high | The unknown-route screenshot silently falls back to the betting homepage instead of showing an intentional not-found state or recovery explanation. F11 medium: Error and not-found states provide no actionable recovery |
be-internationalisedlang-dir-and-logical-properties | issues | high | Across home, casino, and registration the html lang value is empty; axe/Lighthouse fail html-has-lang. F32 high: The document language is missing |
be-internationalisedlocale-aware-data | pass | high | Visible prices use KES and match schedules use a Kenya-appropriate day/month and 24-hour presentation on the localized /en-ke route. |
be-internationalisedtime-zone-correctness | pass | medium | Representative match schedules consistently render one localized time convention for the Kenya route; no contradictory or ambiguous cross-zone event state was observed. |
be-trustworthyno-dark-patterns | issues | high | An unsolicited, full-screen gambling promotion interrupts every fresh session before content and uses a dominant PLAY NOW action while dismissal is not visible at the desktop evidence height. F33 high: An aggressive gambling promotion is forced before content |
be-trustworthyhumane-error-handling | issues | high | Submitting the empty registration state produced no visible error announcement; inputs also lack required semantics and field-specific invalid state. F34 medium: Registration does not surface humane invalid-state feedback |
be-trustworthytrustworthy-input-assistance | issues | high | Phone and password fields use generic autocomplete="on" rather than tel/new-password tokens, reducing reliable autofill and password-manager assistance. F35 medium: Registration fields lack specific autocomplete tokens |
be-trustworthysafe-commercial-and-account-flows | pass | high | The registration screenshot presents the age requirement, terms/privacy links, confirmation checkbox, and account-code alternative before submission. |
be-sustainableoptimised-assets | issues | high | Image audit found 20 oversized images, 18 without srcset, and 20 legacy-format assets; banner originals reach 2000-2779 px for a 764 px display. F36 high: Most imagery is oversized, legacy format, and non-responsive |
be-sustainableno-wasteful-work | issues | high | The page starts 172 requests, 51 scripts, 56 XHR/fetches, multiple analytics stacks, and ships an uncompressed 268 KB terms JSON on initial load. F37 high: Initial load performs extensive wasteful background work |
be-sustainablethird-party-and-media-budget | issues | high | HAR records 4.67 MB third-party transfer and 2.52 MB of images; tracker evidence identifies 58 third-party origins and 15 known trackers. F38 high: Third-party and media weight is disproportionate |
be-agent-readystructured-agent-capabilities | not-applicable | high | For a regulated gambling service, autonomous agent actions are not an appropriate default without an explicit, safety-reviewed agent-facing scope; none was declared. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the audited betting, casino, or registration surfaces requires on-device generative inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten representative casino catalog scroll cycles, heap self-size grew 744,018 bytes (1.15%) from a separate fresh baseline, with no evidence of unbounded retained growth. |
be-memory-efficientbounded-footprint | issues | high | A single casino state retained about 64.7 MB across 1.18 million heap nodes, a disproportionate footprint for a game-listing view before gameplay. F39 medium: The casino listing has a large baseline heap footprint |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary exposed Detached* among top constructors, and the repeated-scroll comparison showed only 1.15% total self-size growth. |
Provenance
Canonical report: results/atomic/reports/0835-www_betika_com.json
Report SHA-256: 9568c57fde1396556ff3f7757cd48a8dc3707cee8f978df67d26bd077acd91ff
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_betika_com/2026-07-23T07-56-09-848Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_betika_com/2026-07-23T07-56-09-848Z
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.