Manifest position 594 · CrUX rank bucket 1000
https://www.sportybet.com
Coverage complete
Coverage-complete remote audit. No source was provided and no state-changing wager, registration, login, or account action was performed.
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-mode screenshot is visually identical to the light capture, while the DOM reports color-scheme: normal and a white html background. F-01 high: The interface ignores the user’s dark color-scheme preference |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe matched reduce but still found a running 3,000 ms highlight animation. F-02 medium: Motion continues when reduced motion is requested |
respect-user-preferencesrespects-contrast | pass | medium | The forced-colors screenshot preserves visible text, controls, odds, focus outlines, and selected states across the first viewport. |
implement-natural-interactionsview-transitions | issues | high | The CSS/script probe found no ::view-transition rule or startViewTransition call across the interactive dashboard and detail route. F-03 low: State and route changes do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, or scroll-linked reveal surface was observed on the representative pages. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The audited desktop-oriented market, help, and recovery surfaces expose no required swipe, pull, or drag gesture journey. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The 2,680 px home document uses static navigation and the CSS probe found no scroll-state or scroll-position treatment. F-04 low: Long pages lose primary navigation context while scrolling |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or viewport-edge overlay requiring anchored positioning was present in the exercised states. |
provide-guided-navigationdirects-attention | pass | medium | Home, sport tabs, detail breadcrumb, active tab underlines, market grouping, and selected controls visibly orient the user across home and event detail. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | medium | Desktop, mobile, help, recovery, live, and event captures loaded without a modal, consent wall, or full-viewport interstitial obscuring content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The platform probe found role=listbox, role=button spans, and checkbox divs, but no dialog, popover, or native disclosure primitives. F-05 medium: Rich controls rely on custom roles instead of native primitives |
maximize-content-reduce-noisereduced-chrome | issues | high | The desktop first viewport devotes large regions to two nav rows, promotional hero and banner, registration panel, winner feed, mini games, and betslip around the odds content. F-06 high: Promotional and application chrome crowds the core betting content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a requested 360x800 viewport, layout metrics reported a 1,000 CSS px layout viewport, no viewport meta, and the screenshot shows the entire dense desktop page scaled to unreadable text. F-07 critical: The mobile viewport receives a scaled desktop layout |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The platform probe found zero container rules and the narrow screenshot preserves desktop sidebars and tables rather than adapting reusable cards and betslip modules. F-08 medium: Dashboard components do not adapt at component level |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focused phone and password fields had outline none and no box shadow; several controls measured 32 px high and the checkbox 13x13 px. F-09 high: Key inputs lack visible focus and targets are undersized |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The first viewport clearly identifies sports betting, exposes odds as the primary action, and keeps a labelled betslip adjacent on desktop. |
support-core-task-successprimary-flow-completion | pass | medium | The non-transactional portion of the core flow is clear: event markets expose odds, selection leads to a labelled betslip, and account-required actions are visibly signposted. |
support-core-task-successclear-system-state-and-recovery | issues | high | After entering a one-digit phone number on Forgot Password and attempting Next, the captured state remained unchanged with no visible validation explanation. F-10 medium: Invalid recovery input gives no actionable feedback |
be-fast-and-stablegood-core-web-vitals | issues | high | The trace measured LCP 8.54 s and 3.66 s total blocking time; Lighthouse measured LCP 19.4 s, TBT 990 ms, and performance 42. F-11 critical: The primary page loads far outside good performance ranges |
be-fast-and-stablevisual-stability | issues | high | The mobile layout observer measured CLS 0.116 with seven shifts, including 0.063 and 0.042 shifts after four seconds; 31 images lacked dimensions. F-12 medium: Mobile load produces visible layout shift |
be-fast-and-stableefficient-main-thread | issues | high | The trace found seven long tasks, including a 3,438.86 ms task, with 3,655.35 ms total blocking time. F-13 critical: A multi-second startup task blocks the main thread |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR recorded 201 requests and 6.66 MB transferred, including 17 stylesheets, 61 scripts, 9 fonts, multiple parser-inserted stylesheets, and large assets without cache headers. F-14 high: The page ships a heavy, inefficient dependency chain |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 1,017 KiB of removable JavaScript, with several bundles between 48% and 75% unused. F-15 high: Large amounts of JavaScript are unused on initial load |
be-inclusivenames-roles-labels | issues | high | The DOM probe found login and registration fields with no labels or aria-labels, the images audit found 22 missing alt attributes, and Lighthouse found an unnamed logo link. F-16 high: Forms, images, and links lack accessible names |
be-inclusivesufficient-contrast | pass | medium | Lighthouse color-contrast audit scored 1, and the forced-colors capture preserves distinguishable text and controls. |
be-inclusivestructure-and-focus | issues | high | The home page has no h1, starts its sparse headings at h5, has no main landmark, and focused text inputs show no visible outline. F-17 high: Heading, landmark, and focus structure is weak |
be-inclusivelegible-text | issues | high | The 360 px screenshot scales a 1,000 px desktop surface down to 36%, making odds, labels, winner entries, and help text too small to read comfortably. F-18 high: Mobile text is rendered at an unreadably small scale |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse found user-scalable=no or maximum-scale below 5, while the live page had no desktop viewport meta and rendered a fixed 1,000 px layout into 360 px. F-19 critical: The mobile viewport disables useful scaling and reflow |
follow-best-practicesno-console-errors | pass | medium | Lighthouse recorded no browser errors in the console during the audited mobile load. |
follow-best-practicessound-document-and-assets | issues | high | All 31 audited images lacked width and height, 22 below-fold images were not lazy-loaded, and 28 used legacy formats. F-20 medium: Images omit intrinsic dimensions and modern delivery hints |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found a deprecated unload listener and six BFCache failure reasons, including an unload handler in the main frame. F-21 medium: Deprecated unload handling blocks browser lifecycle optimizations |
be-discoverabletitle-and-description | pass | medium | Rendered DOM has a descriptive SportyBet sports-betting title and a concrete meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The discoverability fetch returned HTTP 500 with 0% rendered-word coverage, no raw title or description, and only a JavaScript-required message in crawler view. F-22 high: The public page is a JavaScript shell for non-JS crawlers |
be-discoverablecanonical-and-indexing-signals | pass | medium | Rendered head exposes a canonical /ng/ URL and localized hreflang alternatives; robots.txt permits core paths and points to sitemap.xml. |
be-discoverablestructured-and-shareable-metadata | pass | medium | Rendered head includes JSON-LD plus Open Graph title, description, image, URL, site name and type metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS, nosniff and X-Frame-Options are present, but CSP is missing and all 11 observed cookies lacked Secure and used SameSite=None. F-23 high: Security policy and cookie protections are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The page contacted 15 third-party origins, including five known tracker domains; 152 third-party requests transferred 6.21 MB. F-24 high: Tracking and third-party collection are extensive by default |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No permission prompt fired on load, and completing or changing authentication methods would require a real account; passkey availability was not asserted. |
be-private-and-securedefensive-browser-policies | issues | high | Headers include HSTS, nosniff, SAMEORIGIN and strict-origin-when-cross-origin, but omit both Content-Security-Policy and Permissions-Policy. F-25 medium: Permissions and content security policies are incomplete |
be-resilientprogressive-enhancement | issues | high | The crawler/no-JS capture shows only a JavaScript-required notice; raw fetch returned 500 and had 0% coverage of rendered content words. F-26 critical: Core content disappears without JavaScript |
be-resilientresilient-runtime-behaviour | pass | medium | Representative home, live, event, help, and recovery routes loaded with stable visible content and no clipped modal or broken navigation state. |
be-resilientoffline-and-installable | issues | high | The platform probe found no manifest; the non-JS/failure state is only a generic JavaScript-required notice. F-27 medium: The app-like betting experience has no web manifest or offline fallback signal |
be-resilientnetwork-and-http-failure-states | issues | high | The raw document request returned 500 and crawler view exposed no retry, status, or useful fallback beyond enabling JavaScript. F-28 high: The origin failure state is a broken shell rather than recovery UI |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The rendered Nigerian English document declares html lang=en, and localized hreflang alternatives are exposed for multiple markets. |
be-internationalisedlocale-aware-data | pass | medium | Rendered content uses Nigerian NGN currency, +234 phone context, localized day/date labels, and region-specific country routing. |
be-internationalisedtime-zone-correctness | pass | medium | The interface explicitly exposes GMT+01:00 next to live and scheduled market times, making the displayed time basis visible. |
be-trustworthyno-dark-patterns | issues | high | The first viewport shows “Keep me signed in” selected by default next to sign-in, while deposit and registration prompts dominate the surrounding page. F-29 high: The sign-in form defaults to persistent session retention |
be-trustworthyhumane-error-handling | issues | high | A one-digit mobile number and Next attempt produced no visible field-level message or recovery instruction. F-30 medium: Account recovery does not explain invalid input |
be-trustworthytrustworthy-input-assistance | issues | high | The login phone and password inputs have autocomplete=off and no labels, preventing reliable autofill and password-manager semantics. F-31 high: Sign-in inputs explicitly disable browser assistance |
be-trustworthysafe-commercial-and-account-flows | pass | medium | The audited unauthenticated states display odds, account recovery, responsible-gaming, terms, privacy, and self-exclusion navigation; no wager or account mutation was performed. |
be-sustainableoptimised-assets | issues | high | The images audit found 28 legacy-format images, 22 below-fold images without lazy loading, 11 without srcset, and all 31 without intrinsic dimensions. F-32 high: Asset delivery wastes bytes and decoding work |
be-sustainableno-wasteful-work | issues | high | The load performs 201 requests, 61 scripts, 62 fetch/XHR requests, and a 3.44 s main-thread task before the dashboard settles. F-33 high: Startup work and network activity are disproportionate |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 152 requests and 6.21 MB, including 703.9 KB from Tag Manager and about 1.43 MB of fonts overall. F-34 high: Third-party code and fonts consume most transferred bytes |
be-agent-readystructured-agent-capabilities | issues | high | The platform probe found no agent tooling signal and the no-JS representation exposes none of the visible market or account-recovery capability. F-35 low: Transactional capabilities are not exposed in a structured agent-safe form |
be-agent-readyon-device-inference | not-applicable | high | On-device summarisation or language-model inference is not necessary for the betting, help, or account-recovery tasks audited. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten repeated odds select/deselect interactions, heap self size increased from 125.10 MB to 127.01 MB (1.5%) with no constructor showing runaway growth; this does not establish an unbounded leak. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap summary contains 3,123,569 nodes and 125.1 MB self size, including 523,055 native nodes and 464,305 closures, which is high for one dashboard view. F-36 medium: The initial page has a very large memory footprint |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Before/after heap summaries show small object and closure deltas and no Detached constructor among the leading retained populations. |
Provenance
Canonical report: results/atomic/reports/0594-www_sportybet_com.json
Report SHA-256: 38efeca53f46492fdb3dd80b25c46aa5911195397879334ec467f861c3db73bd
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_sportybet_com/2026-07-21T19-47-00-140Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_sportybet_com/2026-07-21T19-47-00-140Z
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.