Manifest position 33 · CrUX rank bucket 1000
https://www.betway.co.bw
Coverage complete
Coverage-complete report-mode audit. The requested .bw URL redirected to the UK canonical site; that observed behavior is included in scope.
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 | medium | Desktop screenshots under default and prefers-color-scheme: dark are pixel-identical (both 627,768 bytes), including fixed light offer and consent surfaces. F02 medium: The landing page does not adapt to dark color preference. |
respect-user-preferencesrespects-reduced-motion | issues | medium | With prefers-reduced-motion: reduce matched, the probe still found four running animations with durations 550ms, 1100ms and 12000ms. F03 medium: Motion continues when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | medium | The prefers-contrast: more screenshot remains visually equivalent to the default; Lighthouse also reports a failing color-contrast audit. F04 medium: Contrast preference is not meaningfully reflected. |
implement-natural-interactionsview-transitions | issues | medium | The platform probe confirms View Transitions support in the browser, while DOM/CSS inspection found no authored transition use and navigation performs full abrupt route changes. F05 low: State and route changes do not use view transitions. |
implement-natural-interactionsscroll-driven-animations | issues | medium | The sports page is 10,678 CSS pixels tall, but the platform probe found zero scroll timelines and screenshots show no progress or state-aware navigation affordance. F06 low: Long content provides no scroll-linked orientation. |
implement-natural-interactionsphysical-gestures | pass | high | Mobile screenshots show horizontally arranged carousels with visible arrow/dot controls and touch-sized controls; interaction does not depend on hover. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The sports page is 10,678 CSS pixels tall, but the platform probe found zero scroll timelines and screenshots show no progress or state-aware navigation affordance. F06 low: Long content provides no scroll-linked orientation. |
provide-guided-navigationanchored-positioning | pass | high | Navigation, carousel indicators and contextual controls remain spatially attached to their content in desktop/mobile screenshots without detached overlays. |
provide-guided-navigationdirects-attention | pass | high | Prominent Join/Register actions, selected tabs and carousel dots provide clear visual direction on the landing, sports and casino paths. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | The only blocking interruption is the legally motivated cookie choice, which presents Accept, Reject all and Manage preferences together without requiring acceptance. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | medium | The platform probe found visible DIV role=dialog surfaces, and Lighthouse failed aria-dialog-name. F07 medium: Visible dialogs are custom and one is unnamed. |
maximize-content-reduce-noisereduced-chrome | pass | high | Screenshots show edge-to-edge content and compact navigation rather than decorative application windows or excessive borders. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Mobile layout primitives report 360px scrollWidth/clientWidth and zero horizontal overflow on landing and sports paths. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Desktop and 360px screenshots show the same offer/navigation/card components recomposed into compact mobile layouts without clipping. |
adapt-to-the-form-factorinput-modality-aware | pass | high | Mobile layouts expose touch-sized primary controls and Lighthouse does not report a tap-target or keyboard-focus audit failure. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Landing and product screenshots immediately identify betting/casino offers and expose Join/Register plus safer-gambling navigation. |
support-core-task-successprimary-flow-completion | issues | medium | Navigation from https://www.betway.co.bw completed a four-hop redirect to https://betway.com/en-gb/ and displayed UK/£ offers. The footer Terms & Conditions URL then rendered an “Oops... page not found” page with an empty document title. F01 high: The requested Botswana domain loses market context and its Terms link dead-ends. |
support-core-task-successclear-system-state-and-recovery | pass | high | The legal-link failure renders a clear 404 state and a homepage recovery link instead of a blank/error stack. |
be-fast-and-stablegood-core-web-vitals | issues | medium | Lighthouse measured LCP 3.5s, FCP 3.0s and estimated 1.87s redirect savings. HAR recorded 71 requests and 1,467,305 transferred bytes, including four document redirects. F08 high: Mobile load is delayed by redirects and excess delivery. |
be-fast-and-stablevisual-stability | pass | high | Mobile landing CLS is 0.01175 and sports CLS is 0.01113, both well below the 0.1 good threshold. |
be-fast-and-stableefficient-main-thread | issues | medium | Mobile layout observation on the sports page recorded six long tasks, including 227ms and 126ms tasks; Lighthouse reports 2.4s main-thread work. F09 medium: The sports template performs long main-thread tasks. |
be-fast-and-stableefficient-resource-delivery | issues | medium | Lighthouse measured LCP 3.5s, FCP 3.0s and estimated 1.87s redirect savings. HAR recorded 71 requests and 1,467,305 transferred bytes, including four document redirects. F08 high: Mobile load is delayed by redirects and excess delivery. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | medium | Lighthouse estimates 244 KiB unused JavaScript and 19 KiB unused CSS, alongside legacy JavaScript savings. F10 medium: Substantial CSS and JavaScript are shipped but unused at load. |
be-inclusivenames-roles-labels | issues | medium | Lighthouse failed aria-dialog-name, label-content-name-mismatch and link-text; the DOM probe also found a visible dialog without aria-modal and controls with mismatched sports-themed aria labels. F11 high: Some interactive elements lack robust accessible names. |
be-inclusivesufficient-contrast | issues | medium | Lighthouse color-contrast audit failed on the rendered landing page; the screenshots show muted grey navigation and controls over very dark backgrounds. F12 high: Text/control contrast does not consistently meet the accessibility floor. |
be-inclusivestructure-and-focus | issues | medium | The landing page exposes two H1 elements, including “Sponsorships” and “Betway: Official Website”, while Lighthouse reports an accessibility-tree failure. F13 medium: Heading and focus semantics are inconsistent. |
be-inclusivelegible-text | pass | high | Primary offer, navigation and consent text remain legible in desktop/mobile screenshots; only one visible element was measured below 12px. |
be-inclusivezoom-reflow-targets-and-media | pass | high | At 360px, landing and sports pages reflow without horizontal overflow and primary controls remain usable. |
follow-best-practicesno-console-errors | pass | high | The completed Lighthouse navigation did not flag the JavaScript errors audit, and ad-hoc resource probes completed without an uncaught page exception. |
follow-best-practicessound-document-and-assets | issues | medium | The images primitive found all 12 images without width/height attributes, seven legacy-format images, and one missing alt value. F14 medium: Images omit intrinsic dimensions and mostly retain legacy formats. |
follow-best-practicesbrowser-platform-hygiene | issues | medium | Lighthouse best-practices score is 0.77 and inspector-issues failed; its report also identifies legacy JavaScript and a third-party-cookie issue. F15 medium: Browser diagnostics report unresolved platform issues. |
be-discoverabletitle-and-description | pass | high | Rendered/raw evidence confirms a descriptive title and meta description on the canonical landing page. |
be-discoverablecrawlable-and-mobile-friendly | issues | medium | Lighthouse failed the link-text audit with one link, despite the page otherwise being server rendered and mobile friendly. F16 medium: Not every link has meaningful crawlable text. |
be-discoverablecanonical-and-indexing-signals | pass | high | The landing declares canonical https://betway.com/en-gb/ and raw server HTML returns 200 with indexable content. |
be-discoverablestructured-and-shareable-metadata | issues | medium | The platform probe found zero JSON-LD scripts and zero Open Graph tags. F17 medium: The landing page lacks structured and social metadata. |
be-private-and-securesecure-transport-and-headers | issues | medium | Headers evidence shows CSP and HSTS, but X-Content-Type-Options, Referrer-Policy and Permissions-Policy are absent; CSP is limited to frame-ancestors. F18 high: The response security policy is incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | medium | Before any consent action, trackers evidence found Google Tag Manager and FullStory across 11 third-party origins. HAR attributes 1,467,161 of 1,467,305 transferred bytes to origins classified third-party relative to the requested host. F19 high: Tracking executes before consent choice and dominates the third-party footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No geolocation/notification permission prompt appeared on load and no browser permission was requested during the audited journeys. |
be-private-and-securedefensive-browser-policies | issues | medium | Headers inspection found no Permissions-Policy or Referrer-Policy and no nosniff; the CSP only defines frame-ancestors rather than script/object/base restrictions. F20 medium: Defensive browser policies are only partially deployed. |
be-resilientprogressive-enhancement | pass | high | Discoverability reports 92% rendered-word coverage in raw HTML, with title, H1 and description present without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | All four templates rendered usable states; the legal failure produced a human-readable recovery page rather than crashing. |
be-resilientoffline-and-installable | not-applicable | high | A real-money betting service cannot complete its core transaction offline; offline transaction capability is not appropriate, though network failure handling remains applicable. |
be-resilientnetwork-and-http-failure-states | pass | high | The observed invalid legal route produced an explicit 404-style message and homepage recovery action. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The canonical page declares lang=en-gb and inspected stylesheets include logical CSS properties. |
be-internationalisedlocale-aware-data | pass | high | The observed UK destination consistently uses English and £-denominated offer copy rather than mixing locale formats. |
be-internationalisedtime-zone-correctness | pass | high | Observed sports dates avoid asserting ambiguous clock times, and no contradictory time-zone rendering was found in the inspected listing. |
be-trustworthyno-dark-patterns | pass | high | Consent presents Reject all with equal prominence to Accept and the page includes safer-gambling/deposit-limit links. |
be-trustworthyhumane-error-handling | pass | high | The broken legal destination explains the failure in plain language and provides a homepage recovery link. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No authored data-entry form is present on the audited landing/product/legal templates; registration is a separate account surface outside this site scope. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Offer screenshots display age/responsible-gambling notices, key eligibility terms, and safer-gambling navigation adjacent to commercial calls to action. |
be-sustainableoptimised-assets | issues | medium | Images evidence found seven legacy-format images and 12/12 without intrinsic dimensions; HAR records 405,316 image bytes. F21 medium: Asset choices waste transfer and layout work. |
be-sustainableno-wasteful-work | issues | medium | HAR shows 318,405 bytes from Google Tag Manager plus 94,341 bytes from FullStory; these load before a consent decision. F22 medium: Background analytics and replay create avoidable work. |
be-sustainablethird-party-and-media-budget | issues | medium | HAR records 69 of 71 requests and almost all transferred bytes as third-party relative to the requested .bw origin, with GTM, OneTrust and FullStory among the largest scripts. F23 medium: Third-party code exceeds a proportionate landing-page budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No safe, bounded agent task was identified for this regulated promotional and wagering surface; emerging WebMCP exposure is not currently appropriate. |
be-agent-readyon-device-inference | not-applicable | high | The audited promotional and wagering tasks do not require summarisation, generation, or another on-device inference use case. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 30 carousel advances, DOM node count remained exactly 504; same-session heap rose transiently from 14.17MB to 15.15MB without DOM growth. |
be-memory-efficientbounded-footprint | pass | high | Heap summaries remained about 16.2–16.5MB self size and under 300k snapshot nodes across baseline and exercised captures. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Thirty repeated carousel advances left the live DOM count unchanged at 504 and produced no detached-node signal in the bounded probe. |
Provenance
Canonical report: results/atomic/reports/0033-www_betway_co_bw.json
Report SHA-256: 3fcdd098bb7712bf2bf2b0f001860e88fc5a81f49851596427acf48aca8f686f
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_betway_co_bw/2026-07-17T23-26-52-425Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_betway_co_bw/2026-07-17T23-26-52-425Z
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.