Manifest position 960 · CrUX rank bucket 1000
https://www.mobiledokan.com
Coverage complete
Atomic coverage complete across five representative templates plus a recovery route.
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 pixel-identical in page surfaces to the light/contrast captures, and the CSS probe found zero prefers-color-scheme rules. F01 medium: The site remains light under a dark color-scheme preference |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion emulation matched and getAnimations() returned no active animations; 32 CSS reduced-motion rules were detected. |
respect-user-preferencesrespects-contrast | issues | high | The CSS probe found zero prefers-contrast or forced-colors rules; Lighthouse failed color-contrast. F02 medium: High-contrast preferences are not handled and baseline contrast failures remain |
implement-natural-interactionsview-transitions | issues | high | The CSS/DOM probe found zero view-transition usage across the representative MPA templates. F03 low: Navigation swaps are abrupt rather than using view transitions |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, reveal, or other scroll-linked motion was present on the representative templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull, draggable carousel, or gesture-driven primary interaction was present. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Representative pages are 3,295 to 13,646px tall, while the CSS probe found no scroll-timeline or scroll-state technique. F04 low: Long pages provide no scroll-state-aware navigation cue |
provide-guided-navigationanchored-positioning | not-applicable | high | No author-controlled tooltip or popover surface requiring edge-aware anchoring appeared in the audited paths. |
provide-guided-navigationdirects-attention | issues | high | The source probe found no View Transition, highlight, or scroll-marker technique on long product and comparison pages. F05 low: Navigation and in-page movement do not visibly guide attention |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Mobile screenshots show a 323px-wide modal covering nearly the entire 360x800 viewport before users can read product, article, listing, or comparison content. F06 high: A full-screen consent wall obscures every representative mobile page on load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM probe found zero dialog, popover, or details elements while screenshots show a modal interaction. F07 medium: The blocking consent overlay is not exposed through native dialog/popover primitives |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop and mobile screenshots show nearly every section and row boxed with borders while the consent layer adds further chrome. F08 low: Dense borders and repeated cards compete with primary content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All five templates reported 360px scrollWidth/clientWidth with 0px horizontal overflow and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The stylesheet probe found zero @container rules across reused product-card, filter, and comparison components. F09 low: Responsive behavior relies on viewport rules rather than reusable component queries |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse failed target-size; the focus probe found visible controls as small as 32x32 and computed outline-style none on sampled links, buttons, inputs, and selects. F10 high: Touch targets and keyboard focus are inadequate |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport clearly identifies MobileDokan and exposes phone filtering, search, products, prices, and comparison navigation. |
support-core-task-successprimary-flow-completion | issues | high | Every representative mobile route opens behind the same full-screen consent wall, adding a mandatory detour before product discovery or comparison. F11 medium: The primary browse flow is interrupted before it begins |
support-core-task-successclear-system-state-and-recovery | pass | high | A deliberately invalid route returned a clear 404, explained the problem, and provided “Go to Home” recovery. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 10.5s, FCP 2.9s, TTI 10.6s and performance 66; the raw trace measured LCP 3.78s. F12 high: Mobile loading is slow |
be-fast-and-stablevisual-stability | pass | high | CLS was 0 to 0.0283 across all five 360px templates, within the good range. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded 3 long tasks, a longest task of 175.65ms, and 283.3ms total blocking time. F13 medium: Main-thread scripting blocks responsiveness during load |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR found nine parser-inserted stylesheet candidates; Lighthouse estimated 770ms render-blocking savings and 585KiB cache-lifetime savings. F14 high: Render-blocking and cache inefficiencies delay content |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 313KiB unused JavaScript and 39KiB unused CSS; HAR shows 15 scripts and 9 stylesheets. F15 medium: The page ships substantial unused code |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed button-name, link-name, label, select-name, aria-valid-attr-value, and list semantics; the probe also found unlabelled search/email/password inputs. F16 high: Core controls lack accessible names and labels |
be-inclusivesufficient-contrast | issues | high | Lighthouse color-contrast failed on the homepage under its mobile accessibility audit. F17 high: Text and controls fail minimum contrast |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed heading-order, while the focus probe reported outline-style none for sampled interactive controls. F18 high: Heading order and focus visibility are not reliable |
be-inclusivelegible-text | issues | high | Mobile screenshots show long consent copy in a narrow overlay and tightly packed card/specification layouts. F19 medium: Dense mobile text and controls reduce reading comfort |
be-inclusivezoom-reflow-targets-and-media | issues | high | Although all tested templates reflowed without horizontal overflow at 360px, Lighthouse failed target-size. F20 high: Small targets undermine touch and zoomed use |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 68/69 images without both dimensions, 29 oversized images, 52 without srcset, and Lighthouse found incorrect aspect ratios. F21 medium: Image markup is poorly sized |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed inspector-issues even though console, BFCache, paste prevention, source maps, and prompt-on-load audits passed. F22 medium: Chrome reports browser platform issues |
be-discoverabletitle-and-description | pass | high | DOM and Lighthouse confirmed a descriptive title and meta description. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | 798 anchors had hrefs, viewport meta was present, robots allowed crawling, and Lighthouse SEO link audits passed. |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage returned 200, canonical matched, robots was index/follow, and robots.txt linked the sitemap index. |
be-discoverablestructured-and-shareable-metadata | pass | high | DOM probe found one JSON-LD block and seven Open Graph tags; Lighthouse SEO scored 100. |
be-private-and-securesecure-transport-and-headers | issues | high | Header capture found no CSP, HSTS, nosniff, frame policy, referrer policy, or permissions policy; all three cookies lacked Secure and used SameSite=None. F23 high: Transport is HTTPS but headers and cookies are weak |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR recorded 30 third-party requests and 779,961 transferred bytes; tracker capture found 10 third-party origins and three known trackers. F24 high: Tracking and advertising dominate the network footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | Lighthouse geolocation-on-start and notification-on-start audits passed; authentication is not part of the representative public browsing task. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive found HSTS, clickjacking protection, Referrer-Policy, Permissions-Policy and CSP all absent. F25 high: Browser-enforced defensive policies are absent |
be-resilientprogressive-enhancement | pass | high | Discoverability capture found 92% raw-HTML coverage with title, H1 and description preserved and no JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | All templates rendered without narrow-viewport overflow, and the invalid route produced a stable recovery page. |
be-resilientoffline-and-installable | issues | high | The platform probe found two service-worker registrations but no web app manifest. F26 low: The site registers service workers but is not installable and no offline fallback was demonstrated |
be-resilientnetwork-and-http-failure-states | pass | high | The representative 404 state clearly explained failure and supplied a home recovery action. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The public English document declares html lang="en" and rendered left-to-right consistently on all representative templates. |
be-internationalisedlocale-aware-data | issues | high | Representative content renders prices as “TK.” and English date prose, with no locale selector or observed locale-aware alternative. F27 medium: Locale-sensitive content is hard-coded for one locale |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited catalog and article paths did not expose event scheduling, recurring times, or cross-zone time data. |
be-trustworthyno-dark-patterns | pass | high | The consent wall gives equally prominent Consent and Do not consent actions plus Manage options and close; no forced continuity or disguised advertising was observed. |
be-trustworthyhumane-error-handling | not-applicable | high | The representative core browsing and comparison paths contain no required free-text submission with a user-error state to exercise. |
be-trustworthytrustworthy-input-assistance | issues | high | The DOM probe found email, password, text, and search inputs without appropriate autocomplete tokens. F28 medium: Sign-in and other text fields omit autofill assistance |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | The site provides specifications and price information but no first-party checkout, subscription, or account-management journey in the audited scope. |
be-sustainableoptimised-assets | issues | high | The image audit found 29 oversized images, 63 below-fold images without lazy loading, 52 without srcset, and 8 legacy-format images. F29 high: Images are transferred at wasteful resolutions |
be-sustainableno-wasteful-work | issues | high | HAR shows 30 third-party requests while the trace records 283.3ms blocking time; major script bytes come from ad and analytics vendors. F30 medium: Advertising and analytics create avoidable background work |
be-sustainablethird-party-and-media-budget | issues | high | Third parties transferred 779,961 of 1,422,977 bytes, led by advertising, tag management, consent, and fonts. F31 high: Third parties consume more than half of transferred bytes |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent was available; this public catalog does not currently expose a task API that users must complete through agents. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model feature is part of the current user experience, so on-device inference is not required. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten repeated control toggles, retained summary grew only about 0.19MB (24.94MB to 25.13MB) and ~2.5k nodes across fresh equivalent sessions; no unbounded growth signal was observed. |
be-memory-efficientbounded-footprint | pass | medium | Baseline retained summary was 437,386 nodes and 24,935,156 self-size bytes, proportionate to this content-heavy page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The repeated-interaction snapshot showed modest bounded total growth rather than an accumulating detached-DOM or timer signature; confidence is medium because captures used fresh sessions. |
Provenance
Canonical report: results/atomic/reports/0960-www_mobiledokan_com.json
Report SHA-256: 83c442c5ac98b2840be0cd30142da0ca05e7497853e5343af099105857878744
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_mobiledokan_com/2026-07-24T03-57-07-899Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_mobiledokan_com/2026-07-24T03-57-07-899Z
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.