Manifest position 173 · CrUX rank bucket 1000
https://jaya9bangladesh.com
Coverage complete
Coverage complete. The requested URL redirects to https://jaya9bdt.com/, which is the rendered canonical host audited.
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 | Dark emulation produced the same fixed blue/orange/light surfaces as the default capture; the CSS probe found no prefers-color-scheme or color-scheme support. F-01 high: Honours prefers-color-scheme: a usable dark mode exists and is driven by the user's preference (color-scheme / prefers-color-scheme / light-dark()), not hard-coded light only. |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce, 10 animations remained running (one 3500ms and repeated 1000ms animations), and no reduced-motion CSS rule was found. F-02 high: Honours prefers-reduced-motion: non-essential animations and auto-advance are reduced or removed when the user asks for less motion. |
respect-user-preferencesrespects-contrast | issues | high | The high-contrast capture did not change the fixed palette, and the CSS probe found no prefers-contrast or forced-colors handling. F-03 medium: Honours prefers-contrast / forced-colors: controls, text and scrollbars remain visible under high-contrast preferences. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection found no view-transition rules; route/state changes use the legacy Vue shell without directional continuity. F-04 low: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps. |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked animation effect or scroll handler-driven visual effect was observed; CSS inspection found no animation-timeline requirement to assess. |
implement-natural-interactionsphysical-gestures | issues | high | The nine-slide promotional carousel auto-advances, but CSS inspection found no scroll-snap or overscroll affordance for native touch navigation. F-05 low: Gesture-driven interactions and entry/exit motion feel native (declarative overscroll/scroll-snap, physics-based easing, animating to intrinsic sizes, pull/swipe gestures) rather than fighting the platform with custom pointer handlers. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long 4,161px to 7,324px pages expose static header/chrome; CSS inspection found no scroll-state queries or progress feedback. F-06 low: Sticky/affixed UI reacts to scroll state and position (e.g. the new scroll-state(scrolled) query, shrinking headers, progress indicators) so chrome responds to position instead of static or JS-driven toggling. |
provide-guided-navigationanchored-positioning | issues | high | The navigation uses custom dropdown/menu structures, while CSS inspection found no anchor-name, position-anchor, or fallback positioning rules. F-07 low: Tooltips, popovers and menus use CSS anchor positioning (with fallback positions) so they stay attached and reposition correctly rather than being manually positioned. |
provide-guided-navigationdirects-attention | issues | high | The first view is dominated by an unrelated agent promotion; route and in-page navigation provide no visible destination cue or directional transition. F-08 medium: Navigation and in-page jumps guide attention (highlight effects, scroll/carousel markers, directional transitions, drill-down and drawer navigation) so the user can follow where focus moved. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The desktop first viewport is dimmed and almost entirely obscured by a large agent-commission interstitial before any user action. F-09 critical: No intrusive pop-ups, interstitials or banners that obscure content on load; overlays are dismissible and content-first. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM contains eleven custom `div[role=dialog]` overlays rather than native dialog/popover primitives; the visible promotion could not be reliably dismissed by the interaction probe. F-10 high: Overlays and rich controls use the right primitive: popover (with declarative light-dismiss) for transient UI, dialog for modal flows, details for disclosure, native-but-branded selects and pickers, rather than ad-hoc divs. |
maximize-content-reduce-noisereduced-chrome | issues | high | Screenshots show stacked download, primary navigation, announcement, side tabs, floating social controls, carousel, game tabs, and popup competing with core content. F-11 high: Minimise non-content chrome and borders so the content is the focus, not the application frame; expressive/decorative visuals serve the content rather than crowd it. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Mobile layout measurements on home, cricket, and promotion reported 360px scrollWidth for a 360px viewport with zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | No `@container` or `container-type` usage was found despite reusable game, banner, and promotion components appearing across layouts. F-12 low: Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Programmatic keyboard focus on the first control computed to `outline: none` and no box shadow; viewport metadata also disables user scaling. F-13 high: Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike. |
support-core-task-successclear-purpose-and-primary-action | issues | high | The homepage purpose and login/register actions are hidden behind a full-screen agent ad and numerous competing promotional controls. F-14 high: The page communicates what it is for and exposes the primary next action without requiring users to hunt through decorative content, generic copy, or competing calls to action. |
support-core-task-successprimary-flow-completion | issues | high | Login fields are injected without labels; the username field incorrectly uses autocomplete=new-password, and the interstitial remains above the attempted auth state. F-15 high: The representative primary flow can be completed end-to-end with predictable steps, no avoidable dead ends, no hidden required information, and no needless detours through modals, account walls, or upsells. |
support-core-task-successclear-system-state-and-recovery | issues | high | The unknown-route test renders a sparse failure page without the normal navigation context or a clear task-preserving recovery path. F-16 medium: Loading, empty, success, error, offline, and partial-completion states are visible and actionable; users can retry, undo, cancel, go back, or continue without losing context. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 26.5s, TBT 540ms, and CLS 0.604 (performance 0.19); the trace independently measured LCP 7.43s. F-17 critical: Core Web Vitals are in the good range: LCP is fast, interaction latency (INP) is low, and CLS is minimal; work is prioritised and deferred sensibly. |
be-fast-and-stablevisual-stability | issues | high | Layout measured CLS 0.594 on home and 0.800 on promotion; 37 of 47 images lack complete dimensions. F-18 critical: No cumulative layout shift from late content (images, banners, fonts) that arrives without reserved space. |
be-fast-and-stableefficient-main-thread | issues | high | Trace found two long tasks up to 140ms; Lighthouse reported 5.3s main-thread work and 540ms TBT. F-19 high: The main thread is not blocked by long tasks or heavy scripting; work is deferred, chunked, prioritised, or moved off-thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 270 requests and 5.86MB; duplicated parser-blocking CSS and synchronous jQuery scripts delay rendering, and Lighthouse estimated 5.05s render-blocking savings. F-20 critical: Critical resources are delivered efficiently: cache headers are useful, render-blocking chains are short, fonts do not block or shift text, HTTP delivery is modern, and network dependency trees do not delay the main content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 472KiB unused JavaScript and 107KiB unused CSS; app/vendor CSS and app JS are requested both with and without query strings. F-21 high: The page does not ship large unused or duplicated JavaScript/CSS, avoidable legacy bundles, or third-party code that dominates the load without user value. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed button-name, link-name, and image-alt; the image audit found 28 missing alt values and login inputs have no labels. F-22 high: Interactive elements have accessible names, correct roles, and form fields have labels; images have alt text where meaningful; canvas/expressive content is exposed to assistive technology. |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed color-contrast on the rendered homepage (accessibility score 0.74). F-23 high: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | The focus probe found no visible outline; the DOM has no main landmark and uses option/listbox roles for primary navigation. F-24 high: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves. |
be-inclusivelegible-text | issues | high | Dense promotional imagery, long keyword-heavy headings, narrow labels, and competing overlays reduce reading comfort in desktop and mobile captures. F-25 medium: Text is legible and inclusively rendered: comfortable line layout, precise alignment, stable rendering across mixed fonts, no clipping or cramped wrapping that harms comprehension. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Viewport is `user-scalable=no`, Lighthouse failed meta-viewport, and probes found several 15–18px-high links and a 22x18 control. F-26 high: The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling. |
follow-best-practicesno-console-errors | pass | high | Lighthouse did not report its errors-in-console audit as failing during the captured load. |
follow-best-practicessound-document-and-assets | issues | high | Although doctype and UTF-8 are valid, Lighthouse found incorrect image aspect ratios and unsized images; image audit found 37 missing dimensions and 41 oversized images. F-27 high: Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.) |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported DevTools inspector issues, missing source maps for large first-party JS, legacy JavaScript, and third-party cookie issues. F-28 medium: The page uses the platform cleanly: no deprecated APIs, no avoidable BFCache blockers, no broken source maps or inspector issues, no stale vulnerable libraries, no paste-prevention on inputs, and no notification/geolocation prompts on load. |
be-discoverabletitle-and-description | pass | high | Homepage, cricket, and promotion each expose descriptive rendered titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable-anchors, and the viewport disables user scaling even though robots allows the public site. F-29 high: Links are crawlable (real href), there is a viewport meta tag, robots does not block indexing, and link text is descriptive. |
be-discoverablecanonical-and-indexing-signals | pass | high | Public pages return successfully with canonical URLs; robots allows general crawling and points to a populated sitemap. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage and representative routes expose JSON-LD plus Open Graph metadata aligned with visible entities. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS, nosniff, Referrer-Policy, and Permissions-Policy are absent; all eight observed cookies use SameSite=None and seven lack Secure. F-30 critical: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 9 third-party origins and Google Tag Manager/Analytics; HAR attributed 34 requests and 2.67MB to third parties. F-31 high: No over-collection of user data, no leaky third parties, and analytics/background data collection is minimised and batched rather than chatty or session-wide by default. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login surface exposes password-only fields with no passkey/WebAuthn affordance; username is mis-declared as new-password. No permission prompt fired on load. F-32 medium: Permission prompts are requested in context (not on load), and authentication uses modern, phishing-resistant methods (passkeys / WebAuthn) where relevant rather than passwords alone. |
be-private-and-securedefensive-browser-policies | issues | high | X-Frame-Options is present, but HSTS, CSP/frame-ancestors, Referrer-Policy, Permissions-Policy, and nosniff are missing. F-33 high: Browser-enforced defenses are configured where appropriate: HSTS, clickjacking protection (frame-ancestors / X-Frame-Options), Trusted Types for XSS-sensitive apps, origin isolation, privacy-preserving third-party cookie posture, and sensible Referrer-Policy / Permissions-Policy. |
be-resilientprogressive-enhancement | issues | high | Discoverability found only 24% raw/rendered content overlap; title, H1, and description are absent from raw HTML, leaving core content dependent on JavaScript. F-34 high: Core content and primary flows are reachable and usable without JavaScript and on older or non-Baseline browsers; modern features layer on as enhancements with fallbacks, and reactive/transition state stabilises rather than flickering before it settles. |
be-resilientresilient-runtime-behaviour | issues | high | The on-load custom overlay masks the application and could not be reliably dismissed by the scripted interaction; eleven custom dialog containers increase fragile state. F-35 high: The page behaves robustly at runtime: overlays and menus never get cut off, DOM state survives moves, background work and async dependencies are sequenced and conditional rather than fragile, and initial visibility state is detected correctly. |
be-resilientoffline-and-installable | issues | high | This app-like betting product has no manifest link, no service-worker registration, and no installable/offline surface. F-36 medium: Where the site is an app, it is installable (web app manifest) and offers an offline fallback and works on flaky networks. (Contextual: a brochure or intrinsically-online site may reasonably not need this.) |
be-resilientnetwork-and-http-failure-states | issues | high | The tested unknown route provides a weak recovery surface, while HAR also recorded a failed cricket data request without visible task recovery. F-37 medium: HTTP errors, network failures, timeouts and stale data states are handled intentionally: users see useful recovery options rather than blank screens, infinite spinners, broken shells, or misleading success states. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Homepage, cricket, and promotion pages render predominantly Bengali content while `<html lang>` remains `en`; no direction metadata is declared. F-38 high: Correct lang and dir attributes, logical CSS properties (inline/block) rather than physical left/right, and translation-ready markup so the layout and reading order survive other languages and writing modes. |
be-internationalisedlocale-aware-data | issues | high | The UI exposes BDT, locale selection, dates, and countdown behavior, but bundles ship date-fns and Moment while no locale-aware rendered semantics were found. F-39 medium: Dates, numbers, currencies, durations and calendar systems are formatted locale-aware (Intl), location-agnostic where stored, and recurring intervals and event differentials are modelled correctly. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event scheduling, booking, or user-visible zoned-time workflow was present in the representative public surfaces. |
be-trustworthyno-dark-patterns | issues | high | An unsolicited agent-commission popup obscures the site, while bonus and acquisition claims dominate the page before terms or responsible-gaming context. F-40 critical: No deceptive design: no confirmshaming, forced continuity, disguised ads, or nagging consent walls; honest defaults; clear pricing and consent; easy reversal/cancel; predictable, declaratively-wired actions; and no hidden-text tricks (hidden content stays deep-linkable and indexable rather than used to deceive). |
be-trustworthyhumane-error-handling | issues | high | Auth inputs have no associated labels or accessible error contract; generic placeholders are the only visible input assistance. F-41 high: Forms prevent and recover from mistakes humanely: validate after interaction (not prematurely), give clear required-field feedback, announce errors accessibly, and signal invalid fields visibly rather than blaming the user. |
be-trustworthytrustworthy-input-assistance | issues | high | Both login fields use autocomplete=new-password, including the username field, preventing correct sign-in autofill. F-42 high: Input is assisted, not obstructed: correct autocomplete tokens so address, payment, sign-in and sign-up fields autofill, and inputs are highlighted/sized to help the user rather than trip them up. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Promotional bonus/commission messaging is visually dominant, while pricing, wagering commitment, cancellation/account controls, and reauthentication are not visible at entry. F-43 high: Checkout, subscription, consent, authentication and account-management flows are clear, reversible, and proportionate: pricing and commitments are visible, cancellation is findable, sensitive actions re-authenticate when appropriate, and users are not tricked into continuity. |
be-sustainableoptimised-assets | issues | high | Image audit found 41 oversized images, 40 legacy-format images, 20 below-fold images not lazy-loaded, and 12 missing responsive sources. F-44 high: Images and decorative assets are optimised and served at appropriate resolutions; decorative pseudo-element imagery and heavy decorative images are resolution-optimised rather than oversized. |
be-sustainableno-wasteful-work | issues | high | The page loads 270 requests, 53 scripts, duplicate app/vendor bundles, and animations remain active even under reduced-motion. F-45 high: Background work and fetching are not wasteful: background processing is efficient and de-prioritised, and the lightest technique that achieves the result is preferred over heavy or redundant work. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties consume 2.67MB; a 644KB GIF and 412KB animated GIF are major offenders, alongside duplicate analytics tags. F-46 high: Third-party scripts, fonts, video, audio, animation and heavy media are proportionate to the user value they provide; autoplay or background media is avoided unless essential and resource use is cached or deferred where possible. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Emerging contextual capability: this audit found no declared intent to expose gambling actions to AI agents; omission is not treated as a defect. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, or other user task on the reviewed surfaces clearly benefits from on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten attempted login open/close cycles, heap self-size increased about 2.8% (38.79MB to 39.88MB) rather than showing order-of-magnitude or clearly unbounded growth; confidence is limited because snapshots are separate page launches. |
be-memory-efficientbounded-footprint | pass | medium | Heap summary measured 38.79MB self-size at baseline; substantial but proportionate to this media-heavy Vue page, with no single application constructor dominating retained size. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither baseline nor post-interaction top constructor summaries showed a Detached* population; post-interaction growth was modest, with no direct evidence of unbounded listeners/timers. |
Provenance
Canonical report: results/atomic/reports/0173-jaya9bangladesh_com.json
Report SHA-256: 815bf99aadda33d6073531ed9ea998623c3a7ab61937fecd2fcdceacf046d0cd
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/jaya9bangladesh_com/2026-07-18T22-35-29-168Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/jaya9bangladesh_com/2026-07-18T22-35-29-168Z
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.