Manifest position 756 · CrUX rank bucket 1000
https://sattamatkadpboss.mobi
Coverage complete
Coverage complete. Six representative paths cover homepage/listing, Jodi chart, panel chart, interactive forum, contact form, and HTTP error recovery. Other market chart URLs were excluded because they share these templates; APK execution, account login, and real-money off-site phone transactions were not performed for safety.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Normal and prefers-color-scheme: dark screenshots are visually identical; DOM CSS contains no color-scheme or prefers-color-scheme rule, while large white panels remain bright. F1 medium: The page does not adapt its palette to the user’s color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe matched reduce but still found transform 0.2s/0.3s and multiple 0.3s card transitions; there is no reduced-motion override. F2 low: Reduced-motion mode leaves non-essential transform and disclosure transitions enabled. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot preserves visible text, borders and controls. |
implement-natural-interactionsview-transitions | issues | medium | DOM/CSS inspection across homepage and chart templates found no view-transition-name, @view-transition, or document.startViewTransition use. F3 low: Navigation between the long listing and chart details swaps abruptly. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation exists on the representative templates, so there is no scroll animation implementation to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The audited templates expose links, forms and disclosures but no gesture-driven UI. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Mobile layout measured a 17,784px document; screenshot and DOM show no sticky navigation, progress indicator, or scroll-state-aware chrome. F4 medium: The 17,784px homepage provides no persistent location or progress aid. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover or floating menu is present on the representative paths. |
provide-guided-navigationdirects-attention | issues | high | Recon enumerated scores of consecutive links whose accessible/visible text is only “Jodi” or “Panel”, forcing users to infer the associated market from surrounding layout. F5 medium: Repeated generic “Jodi” and “Panel” links do not identify their destinations. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots show no modal, consent wall or interstitial obscuring content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | DOM inspection found nine native details disclosures and no custom modal overlay. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop/mobile screenshots show nearly every block using a different heavy border, fill, shadow and text treatment; the first viewport has several competing result, refresh and play treatments. F6 high: Dense borders, gradients, shadows, competing colors and repeated calls-to-action overwhelm the result content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360×800, layout measured scrollWidth=clientWidth=360 with zero horizontal overflow and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | Captured CSS uses max-width viewport media queries but contains no @container/container-type rules, despite reusable cards and link panels appearing in varied contexts. F7 low: Repeated cards respond only through page-wide viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse target-size failed; footer links are 17px tall with safe clickable diameters as low as 0–23.6px. The direct probe also measured repeated Jodi links at about 35×21px. F8 high: Many links are too small or tightly packed for reliable touch use. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport clearly identifies Satta Matka, exposes the live result and a chart/play path. |
support-core-task-successprimary-flow-completion | pass | high | Homepage links reached representative Jodi and panel charts with current result and historical table content. |
support-core-task-successclear-system-state-and-recovery | pass | high | The tested 404 has noindex, a clear explanation, useful links and a back-home action; empty contact submission focuses the first invalid field with native messages. |
be-fast-and-stablegood-core-web-vitals | pass | high | Lighthouse measured LCP 1.1s, CLS 0 and TBT 50ms; trace LCP was 870ms. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observer and Lighthouse both measured CLS 0; images have explicit dimensions. |
be-fast-and-stableefficient-main-thread | pass | high | Trace found two small long tasks, 31.11ms total blocking time and a 73.96ms longest task; Lighthouse TBT was 50ms. |
be-fast-and-stableefficient-resource-delivery | pass | high | HAR recorded only 7 requests/29,835 transferred bytes, no render-blocking candidate, redirects or HTTP errors. |
be-fast-and-stabletrim-unused-and-duplicate-code | pass | high | HAR shows no external JavaScript or third-party code and only 29,835 transferred bytes; no shipped bundle dominates load. |
be-inclusivenames-roles-labels | issues | high | Forum form probe found the Comm textarea with no label, placeholder or accessible-name attribute. The image audit found 10 repeated arrow GIFs with no alt attribute. F9 medium: The forum composer lacks an associated accessible label; repeated decorative images also omit alt semantics. |
be-inclusivesufficient-contrast | pass | high | Lighthouse accessibility scored 0.94 with no contrast failure, and forced-colors capture remains readable. |
be-inclusivestructure-and-focus | pass | high | Homepage has one H1 followed by H2/H3 structure plus main/footer landmarks; focused controls retain a browser outline. |
be-inclusivelegible-text | issues | high | Screenshots show long centered/italic paragraphs, all-caps forum rules, tiny table headings, text shadows and tightly packed mixed-color content; the homepage reaches 17,784px on mobile. F10 high: Typography and information density impede scanning and comprehension. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse target-size failed; footer links are 17px tall with safe clickable diameters as low as 0–23.6px. The direct probe also measured repeated Jodi links at about 35×21px. F8 high: Many links are too small or tightly packed for reliable touch use. |
follow-best-practicesno-console-errors | pass | high | Lighthouse did not report a console-error or uncaught-exception audit failure. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse image-size-responsive failed: the 25×11 GIF is displayed at 38×17 and should provide about 57×26 physical pixels for the tested density. F11 low: A prominent animated image is displayed above its intrinsic resolution. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse reported no deprecated API, paste prevention, permission-prompt, vulnerable-library or browser-inspector failure. |
be-discoverabletitle-and-description | pass | high | Homepage and forum probes show descriptive, route-specific titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Links have real hrefs, viewport meta is present, and robots.txt allows public crawling. |
be-discoverablecanonical-and-indexing-signals | pass | high | HTTP 200, canonical, hreflang, index/follow robots and sitemap_index.xml were all directly observed. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage exposes matching Open Graph/Twitter metadata plus Website, Organization, SoftwareApplication and FAQ JSON-LD. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers primitive found no CSP, HSTS, nosniff, clickjacking control, Referrer-Policy or Permissions-Policy. PHPSESSID is Secure but HttpOnly is false and SameSite=None. F12 high: HTTPS is used, but browser security defenses and session-cookie hardening are largely absent. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | HAR found zero third-party requests; tracker scan found no known trackers and secrets scan found no exposed credential. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No browser permission request or user authentication flow is exposed in the audited public result/contact journey. |
be-private-and-securedefensive-browser-policies | issues | high | Headers primitive found no CSP, HSTS, nosniff, clickjacking control, Referrer-Policy or Permissions-Policy. PHPSESSID is Secure but HttpOnly is false and SameSite=None. F12 high: HTTPS is used, but browser security defenses and session-cookie hardening are largely absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 100% raw-HTML content coverage, title/H1/description in raw HTML and no JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Representative pages are server-rendered with native links/details and no overlay or async shell that could be cut off or stall. |
be-resilientoffline-and-installable | not-applicable | high | This is a server-rendered public results/content site rather than an offline-first application; an offline/installability requirement was judged out of scope. |
be-resilientnetwork-and-http-failure-states | pass | high | A genuine unknown route returns a dedicated noindex 404 with explanation and recovery links rather than a broken shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Homepage declares lang=en and the Hindi contact route declares lang=hi; both use natural LTR direction. |
be-internationalisedlocale-aware-data | issues | high | Rendered posts use strings such as “22 Jul 09:05:49 pm” without <time datetime>, year/time-zone context or an indicated user locale; the forum probe contains no machine-readable timestamp representation. F13 medium: Forum timestamps are ambiguous and not exposed as locale/time-zone-aware data. |
be-internationalisedtime-zone-correctness | issues | high | Rendered posts use strings such as “22 Jul 09:05:49 pm” without <time datetime>, year/time-zone context or an indicated user locale; the forum probe contains no machine-readable timestamp representation. F13 medium: Forum timestamps are ambiguous and not exposed as locale/time-zone-aware data. |
be-trustworthyno-dark-patterns | issues | high | Homepage copy says “100% free” and “No payment.” The forum’s top/admin posts repeatedly claim “Guarantee 100% Fix,” “Office Se Game Milega,” and “To Book Your Membership,” with phone numbers. This can induce financial harm in a gambling context. F14 critical: The site’s “100% free” promise conflicts with prominent paid-membership solicitations and guaranteed-win claims. |
be-trustworthyhumane-error-handling | pass | high | Empty contact submission uses native required validation, focuses the first invalid field and provides specific browser messages. |
be-trustworthytrustworthy-input-assistance | issues | high | Contact probe found required name and email inputs with empty autocomplete values. F15 low: Contact identity fields omit autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Homepage copy says “100% free” and “No payment.” The forum’s top/admin posts repeatedly claim “Guarantee 100% Fix,” “Office Se Game Milega,” and “To Book Your Membership,” with phone numbers. This can induce financial harm in a gambling context. F14 critical: The site’s “100% free” promise conflicts with prominent paid-membership solicitations and guaranteed-win claims. |
be-sustainableoptimised-assets | issues | high | Images primitive found 10 legacy GIFs and 10 below-fold images without lazy loading, although the total transfer is a very small 29,835 bytes. F16 low: Decorative assets use legacy GIFs and below-fold images are eagerly loaded. |
be-sustainableno-wasteful-work | pass | high | HAR recorded 7 requests, no external script and 29,835 bytes; trace duration showed no ongoing background workload. |
be-sustainablethird-party-and-media-budget | pass | high | HAR found zero third-party requests and no audio/video; total transfer was only 29,835 bytes. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing transactional capability or WebMCP surface is intended; the public content remains fully crawler-readable. |
be-agent-readyon-device-inference | not-applicable | high | No user task on these result/chart pages warrants built-in on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten native details open/close cycles, live DOM count remained exactly 1,356; heap delta across equivalent captures was about 48KB (1.4%), not unbounded growth. |
be-memory-efficientbounded-footprint | pass | high | Heap summary measured 59,110 nodes and 3.63MB self size for the unusually long 1,356-element page, proportionate to its static content. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Repeated details interaction did not increase live DOM count, and heap constructor summary showed no Detached* population among retained constructors. |
Provenance
Canonical report: results/atomic/reports/0756-sattamatkadpboss_mobi.json
Report SHA-256: 9a35ca7efbf12f71ae20d919e30d42e2290276483bb4876ba5dfbc2bc121b993
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/sattamatkadpboss_mobi/2026-07-22T21-06-49-634Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/sattamatkadpboss_mobi/2026-07-22T21-06-49-634Z
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.