Manifest position 566 · CrUX rank bucket 1000
https://sattamatkano1.me
Coverage complete
Coverage-complete audit of four representative MPA templates. Other chart/result URLs sharing these templates were de-duplicated.
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-emulated screenshot is pixel-identical in size and appearance to the default capture (139,152 bytes), and the CSS probe found no color-scheme, prefers-color-scheme, or light-dark() rule. F01 medium: The site does not adapt to the user’s dark colour-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | Rendered CSS on the weekly template contains an infinite 1s blink-animation and the contact template contains an infinite spinner, but no prefers-reduced-motion rule was found by the CSS probe. F02 medium: Blinking and decorative animations do not respect reduced-motion. |
respect-user-preferencesrespects-contrast | issues | high | The CSS probe found no prefers-contrast or forced-colors rules; the contrast-emulated capture did not reveal an authored alternative palette. F03 low: The fixed colour palette does not explicitly adapt to increased contrast or forced colours. |
implement-natural-interactionsview-transitions | issues | high | The CSS probe found no view-transition usage across an MPA with 81 homepage links and many chart routes. F04 low: Cross-document navigation swaps abruptly rather than preserving context. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation is present; DOM/CSS inspection found neither scroll handlers nor scroll timelines, so there is no implementation to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The audited templates expose ordinary document scrolling and links, with no custom swipe, drag, carousel, pull-to-refresh, or other gesture surface. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Mobile layout measured a 20,950px homepage and 30,091px chart page; DOM/CSS inspection found no scroll-state query or progress indicator. F05 medium: Very long pages provide no scroll-state navigation or progress context. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, menu, popover, or anchored overlay exists on the representative templates. |
provide-guided-navigationdirects-attention | pass | high | Representative screenshot, DOM, and objective probes found the expected outcome for “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.” on the audited paths. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Desktop and mobile load screenshots show no modal, consent wall, or full-viewport interstitial obscuring content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No modal, transient popover, disclosure control, or custom overlay is present on the representative templates. |
maximize-content-reduce-noisereduced-chrome | issues | high | The first mobile/desktop viewport is dominated by a purple promotional block, a red banner, repeated borders, and two fixed controls before the result list; the homepage is 20,950px tall. F06 high: Dense banners, repeated borders, fixed buttons, and long promotional copy overwhelm the live-result content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout evidence at 360x800 reports scrollWidth=clientWidth=360 and 0px horizontal overflow on both homepage and chart; viewport meta is present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | DOM/CSS inspection found many repeated card-like components but no @container or container-type rule. F08 low: Reusable content blocks rely only on viewport media queries. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The evaluate probe measured 79 of 88 interactive elements below 24px in at least one dimension; many chart links are only 22px high. F07 high: Most interactive targets are too small for comfortable touch use. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The H1 and visible “Fastest Result Updates”/named result panels communicate the result-reading purpose immediately, despite excess surrounding noise. |
support-core-task-successprimary-flow-completion | pass | high | The primary read-results journey completes on load: current named result panels and linked historical chart pages render without login or an intervening flow. |
support-core-task-successclear-system-state-and-recovery | issues | high | The first viewport showed “Loading...” with only a full-page Refresh action; result state is plain text with no status/live-region semantics or timeout guidance. F09 medium: Live-result loading states do not explain progress or recovery. |
be-fast-and-stablegood-core-web-vitals | pass | high | Lighthouse measured LCP 1.1s, CLS 0, TBT 0ms and performance 1.0; trace measured FCP/LCP 1.213s. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observer and Lighthouse both measured CLS 0 with no recorded shifts. |
be-fast-and-stableefficient-main-thread | pass | high | Trace found one 106ms long task and 56ms TBT; Lighthouse measured 0ms TBT. This is light for the page purpose. |
be-fast-and-stableefficient-resource-delivery | pass | high | HAR captured only 3 requests/20,117 transferred bytes, no cache/header hygiene flags, redirects, or errors; one small parser stylesheet was confirmed in DOM. |
be-fast-and-stabletrim-unused-and-duplicate-code | pass | high | HAR shows no JavaScript payload on the homepage and only 20KB transferred total; duplication is an authored maintainability issue rather than costly shipped bundles. |
be-inclusivenames-roles-labels | pass | high | axe found no name/label violations; all homepage links/buttons have discernible names, and the contact inputs have explicit labels. |
be-inclusivesufficient-contrast | pass | medium | Lighthouse color-contrast audit passed and axe reported no definite contrast violation (manual review remained incomplete for dynamic areas). |
be-inclusivestructure-and-focus | issues | high | axe reported heading-order, landmark-one-main, and region violations; the probe found no main, nav, header, footer, aside, or role landmarks. F10 medium: Heading order and landmarks do not provide a reliable document structure. |
be-inclusivelegible-text | issues | high | Chart CSS explicitly sets td to 9px below 500px and 3px below 320px; the mobile screenshot shows a dense 30,091px table. F11 high: Chart text becomes extremely small on narrow screens. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At 360px the layout reports no overflow, but authored media rules reduce table cells to 9px and then 3px, defeating usable reflow. F12 medium: The chart technically avoids overflow by shrinking thousands of cells below readable size. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no logged browser errors. |
follow-best-practicessound-document-and-assets | issues | high | DOM artifacts show duplicated .link/.chart_btn/.faq blocks, inline style sections, align/font/big markup, and the chart contains 4,257 th plus 9,244 td nodes. F13 medium: Templates contain extensive repetitive inline CSS and obsolete presentational markup. |
follow-best-practicesbrowser-platform-hygiene | issues | high | The chart probe found BACK href="javascript:javascript:history.go(-1)", which is not crawlable or robust when opened directly. F14 low: The chart footer uses a javascript: history link instead of a normal navigable URL. |
be-discoverabletitle-and-description | issues | high | The contact DOM has a descriptive title but no meta[name=description]. F15 low: The contact page lacks a meta description. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse SEO passed; all 81 homepage anchors have href values, viewport meta is present, and robots.txt permits crawling outside /cdn-cgi/. |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage and chart return 200, expose canonical/index-follow signals, and robots.txt points to a populated sitemap containing representative routes. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage probe found one JSON-LD block and six Open Graph tags, aligned with visible public content. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive found no CSP, HSTS, X-Content-Type-Options, clickjacking protection, Referrer-Policy, or Permissions-Policy. F16 high: The HTTPS site omits baseline security response headers. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Contact DOM/probe found Google Analytics and Google Tag Manager scripts, while the homepage tracker capture was otherwise third-party-free. F17 medium: The contact page loads Google Analytics before the user interacts with a personal-data form. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | The representative public pages have no permission request or authentication flow. |
be-private-and-securedefensive-browser-policies | issues | high | Header inspection found no HSTS, frame protection, Referrer-Policy, Permissions-Policy, or CSP frame-ancestors. F18 medium: Browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 100% content availability without JavaScript, raw HTML status 200, and no empty app shell. |
be-resilientresilient-runtime-behaviour | pass | high | Representative templates use ordinary links and static HTML; no menus/overlays are cut off, and mobile layouts have no horizontal overflow. |
be-resilientoffline-and-installable | not-applicable | high | This is a frequently changing result publication rather than an app-like installed workflow; offline/installability is not necessary to complete the current-results task. |
be-resilientnetwork-and-http-failure-states | issues | high | The captured homepage shows “Loading...” and a manual page Refresh, with no timeout, stale-data label, or targeted retry state in the DOM. F19 medium: Dynamic results can remain in an indefinite loading state without an explicit network failure message. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The root is lang="en-IN" while substantial Hindi content has no lang="hi" wrapper; CSS probe found no logical properties and 17 physical left/right declarations. F20 medium: Mixed English/Hindi content is not language-marked and layout CSS is physical-direction based. |
be-internationalisedlocale-aware-data | issues | high | Rendered templates include strings such as “21 July, 2026” and “Tuesday” with no locale selector or locale-aware semantic time markup visible in the DOM. F21 low: Displayed dates are hard-coded in one English format. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative pages do not schedule events or expose times that require time-zone/DST coordination. |
be-trustworthyno-dark-patterns | issues | high | The page claims it does not support or associate with gambling while publishing “Satta Matka” results, “market tips,” number charts, and a persistent WhatsApp channel action. F22 high: The site’s disclaimers conflict with the content and calls to action. |
be-trustworthyhumane-error-handling | issues | high | The phone input has type=tel and maxlength=10 but no pattern or inputmode; its script allows spaces and hyphens, so the stated exact-digit constraint can disagree with accepted input. F23 medium: The “exactly 10 digits” phone requirement is not encoded in validation. |
be-trustworthytrustworthy-input-assistance | issues | high | The contact probe found no autocomplete attribute on name, phone, subject, or message controls. F24 low: Contact fields omit autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, login, account-management, or cancellation flow exists on the audited paths. |
be-sustainableoptimised-assets | pass | high | Images primitive found zero content images, and HAR transferred only 20,117 bytes total on the homepage. |
be-sustainableno-wasteful-work | pass | high | Trace/HAR show no homepage JavaScript or background fetch loop, one short long task, and only three requests. |
be-sustainablethird-party-and-media-budget | pass | high | Homepage tracker/HAR capture found no third-party origins, media, fonts, or autoplay and only 20KB transferred. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The site publishes read-only public result content and exposes no agent-executable workflow; adding WebMCP tools is not currently applicable. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, or language-model task is part of the core result-reading experience, so on-device inference would not add justified value. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page down/up scroll cycles, heap self size rose only 63,036 bytes (2.0%) and node count 1,375 (2.6%); no unbounded trend was observed in this bounded test. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap is approximately 3.12MB across 53,878 nodes, proportionate for a long static page with no large JS application. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Baseline/post heap summaries show small bounded growth after repeated scrolling and no Detached* constructor among the top retained constructors; no repeated component lifecycle exists. |
Provenance
Canonical report: results/atomic/reports/0566-sattamatkano1_me.json
Report SHA-256: de20eb21d3fe5832e9c73ac1d544f0c7e9e2cc0a15e1e6ee4420a76257616c47
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/sattamatkano1_me/2026-07-21T15-11-31-859Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/sattamatkano1_me/2026-07-21T15-11-31-859Z
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.