Manifest position 848 · CrUX rank bucket 1000
https://www.nesine.com
Coverage complete
All 58 catalog checks received a conclusive outcome across five representative paths.
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 probe reported colorScheme "normal", hasDarkCss false, and the dark screenshot is visually identical to the light screenshot. F01 medium: The interface does not adapt to the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found no prefers-reduced-motion CSS, while rendered CSS includes a 9-second animated logo. F02 medium: Motion is not reduced when the user requests reduced motion. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse identifies ratios from 2.21:1 to 4.24:1, below the required 4.5:1 for the shown text sizes. F03 high: Several controls and data labels fail minimum contrast. |
implement-natural-interactionsview-transitions | issues | high | The CSS probe found no view-transition rules on a multi-route, state-heavy experience. F04 low: Major route and state changes swap abruptly without View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface was present on the representative paths, so there is no applicable scroll-animation implementation to judge. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No core swipe, pull-to-reveal, drag, or comparable gesture-driven flow was present in the tested paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Rendered CSS contains fixedSticky/fixedStickyUp body-class selectors and no scroll-state container-query signal. F05 low: Sticky navigation state is toggled through script-oriented body classes rather than declarative scroll state. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored popover, or edge-positioned transient menu was exercised on the representative paths. |
provide-guided-navigationdirects-attention | pass | medium | Persistent labeled sport tabs, active mobile category treatment, and an actionable 404 guide users to the next location. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a large consent sheet covering the lower half of the page; the /iddaa path is replaced by a full-screen educational interstitial. F06 high: Load-time overlays obscure the primary content and flows. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The recon found 0 dialog, 0 popover, and 0 details elements despite many modal-like controls and full-screen overlays. F07 medium: Overlays are implemented as custom structures instead of dialog/popover primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | The first desktop viewport devotes multiple stacked bars plus a banner to chrome before content; the mobile view is similarly crowded. F08 medium: Dense navigation and promotional chrome compete with the core content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800 the layout reported scrollWidth 360, clientWidth 360, horizontalOverflowPx 0, and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no @container use across a highly reused card/widget interface. F09 low: Components rely on viewport breakpoints without container-aware adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found outline none on the first visible links/buttons and counted 157 interactive targets below 24px in at least one dimension; Lighthouse also failed target-size. F10 high: Keyboard focus is invisible and many targets are too small. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The home, help, and signup pages communicate betting/help/signup purpose and expose labeled next actions. |
support-core-task-successprimary-flow-completion | issues | high | The /iddaa mobile path opens on a full-screen explainer instead of the betting list, while signup fields are covered by the consent sheet. F11 high: Load-time overlays interrupt the primary betting and signup journeys. |
support-core-task-successclear-system-state-and-recovery | pass | medium | Invalid form submission produces required-field feedback, and an unknown URL shows “Aradığınız sayfa bulunamadı” with a home action. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 32.7s, TBT 650ms, and interactive at 32.9s; the trace also measured a 5.09s LCP. F12 critical: Largest Contentful Paint and interaction readiness are far outside good ranges. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observation measured CLS 0.039 with no horizontal overflow, within the good CLS range. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reports 4.7s main-thread work and 2.2s JS execution; the trace recorded two long tasks and 101.88ms TBT. F13 high: Heavy scripting blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 294 requests and 5.96MB transferred; DOM confirmation shows nine candidate scripts with async=false and defer=false. F14 high: The critical resource chain is large and contains synchronous parser-blocking scripts. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 1,141KiB unused JavaScript and 354KiB unused CSS, alongside a 630KiB vendor bundle. F15 high: The page ships substantial unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed button-name and prohibited ARIA; the probe counted 24 unnamed buttons and 8 unlabeled controls, while image evidence found 10 missing alt values. F16 high: Interactive controls and images lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reports multiple failures as low as 2.21:1 for visible labels. F17 high: Text and essential UI fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | Homepage has no h1 or main landmark, starts with many empty h3 elements, and focused controls generally compute to outline none. F18 high: The document lacks a coherent heading/main structure and visible keyboard focus. |
be-inclusivelegible-text | pass | medium | Body and form copy is generally readable at the tested mobile size with clear labels and line spacing, apart from separately recorded contrast failures. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse failed target-size and meta-viewport; the ad-hoc probe counted 157 undersized interactive targets, despite the direct homepage viewport string allowing scaling. F19 high: Target sizing and viewport accessibility are not consistently safe. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit scored 1 with no logged items. |
follow-best-practicessound-document-and-assets | issues | high | Image audit found 60 missing dimensions, 26 oversized images, and 34 legacy-format images. F20 medium: Many images lack dimensions or are delivered inefficiently. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports missing source maps for large first-party JavaScript and a WebSocket-related BFCache failure. F21 medium: Platform hygiene issues prevent fast return navigation and debuggability. |
be-discoverabletitle-and-description | pass | high | Homepage, help, and signup expose distinct descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The DOM probe found 14 javascript: links, 24 unnamed buttons, and no h1 on homepage/help, though robots and viewport signals otherwise exist. F22 medium: Some interactive navigation is not crawlable and heading semantics are weak. |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage returned 200, has a valid canonical, valid robots.txt and a populated sitemap without accidental noindex. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage includes Organization JSON-LD and Open Graph title, description, type, site name and image matching the visible brand. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers audit found no CSP; cookies audit found one cookie without Secure and all five with SameSite=None. F23 high: Security policy and cookie configuration have avoidable gaps. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence observed 23 third-party origins and Google Tag Manager, Facebook, New Relic; HAR attributed 5.86MB to non-main origins. F24 high: The initial page has a broad tracking and third-party footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Signup DOM exposes new-password fields but no user-visible WebAuthn/passkey action; no permission prompt fired on load. F25 medium: The signup surface presents password-only authentication without a passkey path. |
be-private-and-securedefensive-browser-policies | issues | high | Headers audit found no Referrer-Policy or Permissions-Policy, although HSTS, nosniff, and X-Frame-Options are present. F26 medium: Several browser-enforced defense headers are absent. |
be-resilientprogressive-enhancement | issues | high | Discoverability measured only 42% raw/rendered word coverage on home and 38% on help, with no h1 surviving as meaningful structure. F27 high: A majority of rendered content is unavailable to non-JavaScript clients. |
be-resilientresilient-runtime-behaviour | issues | high | Full-screen custom overlays are present while the DOM contains no dialog or popover primitives. F28 medium: Custom modal and menu behavior lacks native top-layer resilience. |
be-resilientoffline-and-installable | not-applicable | high | The site is a regulated, real-time wagering service whose core transactions intrinsically require a network connection; offline task completion is not appropriate, although a manifest exists. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately unknown route shows a localized not-found message and an “Anasayfaya git” recovery action rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=tr, manifest declares ltr/tr, and the CSS probe found logical properties. |
be-internationalisedlocale-aware-data | pass | medium | Rendered dates, currency values, decimal punctuation, and Turkish labels use the expected Turkish locale conventions. |
be-internationalisedtime-zone-correctness | pass | medium | Live schedules show an explicit local date/time consistently across header and events; no contradictory time representation appeared in tested paths. |
be-trustworthyno-dark-patterns | issues | high | The load-time sheet gives large equal-row buttons to “Çerez Tercihleri” and “Kabul Et”, while “Reddet” is only an inline text link. F29 high: Consent choice architecture visually favors acceptance and hides rejection in body copy. |
be-trustworthyhumane-error-handling | issues | high | Submitting the available form yielded English “Please fill in this field” messages on a Turkish page and no aria-invalid state. F30 medium: Signup validation is not localized or programmatically announced. |
be-trustworthytrustworthy-input-assistance | issues | high | Signup probe shows identity, email, telephone and several text fields with empty autocomplete; only password fields use new-password. F31 high: Signup fields omit useful autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The signup view exposes password fields but no passkey action, and the consent sheet covers the lower form. F32 medium: Account onboarding lacks modern phishing-resistant authentication and is obscured by consent UI. |
be-sustainableoptimised-assets | issues | high | Image audit found 26 oversized images, 55 below-fold images not lazy-loaded, 20 without srcset, and 34 legacy-format assets; Lighthouse estimates 1,185KiB image savings. F33 high: Image delivery wastes bandwidth. |
be-sustainableno-wasteful-work | issues | high | HAR captured 294 requests including live data endpoints; Lighthouse reports 4.7s main-thread work and 1,141KiB unused JS. F34 high: The page performs extensive eager network and background work. |
be-sustainablethird-party-and-media-budget | issues | high | The load transfers 5.96MB; 45 scripts use 2.28MB, 155 images use 2.17MB, and known trackers include GTM, Facebook, and New Relic. F35 high: Third-party scripts and media consume a disproportionate budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Exposing autonomous agent actions for regulated wagering is not an appropriate default surface without an explicit safe agent intent. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the audited wagering/help/signup surfaces has a clear need for on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After ten select/deselect cycles, heap grew from 81.67MB/1,456,823 nodes to 85.04MB/1,540,012 nodes; Object count rose from 122,003 to 196,108. Independent-page snapshots add variability, so confidence is medium. F36 medium: Repeated selection interaction retains a notable amount of additional heap. |
be-memory-efficientbounded-footprint | issues | high | Baseline heap summary contains 1,456,823 nodes and 81.67MB self size before extended use. F37 medium: The initial page has a very large heap/object footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | low | Neither heap summary lists Detached* constructors among the largest retained constructors; closures increased only 187 after the interaction loop. |
Provenance
Canonical report: results/atomic/reports/0848-www_nesine_com.json
Report SHA-256: 04f119b1b3e7e1f002108c53f0994dabd6234d0ab33fa5c772bac5612de2414b
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_nesine_com/2026-07-23T09-53-01-878Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_nesine_com/2026-07-23T09-53-01-878Z
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.