Manifest position 77 · CrUX rank bucket 1000

https://snaptik.app

Coverage complete

Coverage-complete representative audit of the public downloader, a specialized downloader, an article, successful core flow, and HTTP failure state.

Attempts

1 / 3

Judged checks

58 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	The dark-mode screenshot is visually identical to the light capture: white navigation/content and the same bright blue hero remain. The DOM CSS hard-codes #fff surfaces and contains no prefers-color-scheme rule. F01 medium: The page declares dark color-scheme support but remains a hard-coded light interface.
respect-user-preferences `respects-reduced-motion`	issues	high	With prefers-reduced-motion: reduce active, the probe found 30 sampled elements still transitioning for 86–200 ms, including the menu, loader wrapper, and every FAQ accordion; no reduced-motion override was present. F02 low: Reduced-motion users still receive all component transitions.
respect-user-preferences `respects-contrast`	pass	high	Lighthouse and the prefers-contrast screenshot directly tested text/control visibility.
implement-natural-interactions `view-transitions`	issues	medium	The DOM and interaction probe show no view-transition usage; successful submission replaces the primary view with the video result and download actions as an abrupt state swap. F04 low: The downloader swaps from form to result without spatial continuity.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	No scroll-linked animation or scrollytelling surface exists on the audited templates.
implement-natural-interactions `physical-gestures`	not-applicable	high	No gesture-driven carousel, swipe, drag, or pull interaction exists in the representative paths.
provide-guided-navigation `scroll-state-aware-chrome`	issues	medium	The article is 5,034 CSS px tall at mobile width, while its static header has no progress, sticky state, or scroll-state styling; DOM/CSS inspection found no scroll timeline or scroll-state query. F05 low: Long pages provide no scroll-aware orientation.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No tooltip or edge-positioned popover was present in the representative paths.
provide-guided-navigation `directs-attention`	pass	high	Clear H1, labeled navigation, article hierarchy, and result actions preserve orientation.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	The captured overlay covers the entire viewport and takes focus before the primary task. It exposes “Consent” and “Manage options” but no equivalent one-click rejection on the first layer. F06 high: A full-screen consent interstitial blocks the downloader on load.
maximize-content-reduce-noise `semantic-dismissible-primitives`	pass	high	The consent UI exposes role=dialog and focus; FAQs use native buttons, with no unlabeled overlay div found.
maximize-content-reduce-noise `reduced-chrome`	issues	high	The 360×800 homepage and slideshow captures reserve roughly half the first viewport as blank ad space between the downloader and useful content; the desktop capture also gives a large dark ad box priority. F07 medium: Reserved advertising space dominates the mobile path.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	Layout measured 0 px horizontal overflow at 360 px on home and article.
adapt-to-the-form-factor `component-level-responsiveness`	issues	medium	The page does reflow without overflow, but DOM/CSS inspection found zero @container rules while reusable downloader, card, footer, and navigation components rely on global 769/1024/1216/1400px media queries. F08 low: Responsive behavior is coupled entirely to viewport breakpoints.
adapt-to-the-form-factor `input-modality-aware`	issues	high	After programmatically focusing the URL input, computed style was outline: none 0px and box-shadow: none. The stylesheet explicitly removes outlines from focused inputs. F09 high: The primary text field has no visible keyboard focus indicator.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	First viewport clearly states TikTok Video Download and presents one URL field and Download action.
support-core-task-success `primary-flow-completion`	pass	high	A public TikTok URL completed to titled media plus Download Video and Download Video HD actions.
support-core-task-success `clear-system-state-and-recovery`	pass	high	Successful submission exposes a result state; a true 404 returns status 404, explains the failure, and links home.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured LCP 10.3 s, interactive 10.4 s, TBT 170 ms, and performance 0.69. HAR captured 1,158,193 transferred bytes, of which 1,129,262 bytes and 24/33 requests were third-party. F10 high: Mobile loading is slow and dominated by advertising JavaScript.
be-fast-and-stable `visual-stability`	pass	high	Layout observer measured CLS 0 on desktop and mobile; Lighthouse reported CLS 0.031.
be-fast-and-stable `efficient-main-thread`	pass	high	Trace recorded zero long tasks and 0 ms TBT; Lighthouse TBT was 170 ms.
be-fast-and-stable `efficient-resource-delivery`	issues	high	Lighthouse measured LCP 10.3 s, interactive 10.4 s, TBT 170 ms, and performance 0.69. HAR captured 1,158,193 transferred bytes, of which 1,129,262 bytes and 24/33 requests were third-party. F10 high: Mobile loading is slow and dominated by advertising JavaScript.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	Lighthouse estimated 623 KiB unused JS across seven resources, including ad, prebid, HLS, IMA, analytics, and consent scripts; estimated LCP savings were 3.36 s. F11 high: The initial page ships hundreds of KiB of unused third-party JavaScript.
be-inclusive `names-roles-labels`	issues	high	Lighthouse found both Android and iOS app links in the tab order with no screen-reader-visible text, aria-label, labelledby, or title. The main URL field is only named generically “Name”. F12 high: App-store links have no accessible names.
be-inclusive `sufficient-contrast`	issues	high	Lighthouse/axe reported four serious failures: the Download button is 2.45:1, Search is 3.66:1, and consent text/links are 1.82:1 and 2.8:1. The high-contrast capture also renders the consent surface with effectively invisible labels. F03 high: Primary controls and consent content fail WCAG contrast.
be-inclusive `structure-and-focus`	issues	high	After programmatically focusing the URL input, computed style was outline: none 0px and box-shadow: none. The stylesheet explicitly removes outlines from focused inputs. F09 high: The primary text field has no visible keyboard focus indicator.
be-inclusive `legible-text`	pass	high	Mobile captures show readable 16 px body text, clear headings, and no clipping across home/article.
be-inclusive `zoom-reflow-targets-and-media`	pass	high	Viewport allows maximum-scale=5; 360 px captures reflow without overflow and primary controls are 48 px tall.
follow-best-practices `no-console-errors`	pass	high	Lighthouse errors-in-console audit passed and no uncaught error was observed in the valid core flow.
follow-best-practices `sound-document-and-assets`	pass	high	DOM has HTML doctype, UTF-8 charset, valid viewport; image primitive found no rendered img defects.
follow-best-practices `browser-platform-hygiene`	pass	high	Lighthouse best-practices scored 1.0 and inspector-issues/errors-in-console passed; no permission prompt appeared.
be-discoverable `title-and-description`	pass	high	Home and specialized pages expose descriptive unique titles and meta descriptions.
be-discoverable `crawlable-and-mobile-friendly`	pass	high	40/40 inspected links have hrefs, robots permits indexing, viewport exists, and mobile has no overflow.
be-discoverable `canonical-and-indexing-signals`	pass	high	HTTP 200 content has canonical /en2, index/follow, 24 hreflang alternates, robots and sitemap entries.
be-discoverable `structured-and-shareable-metadata`	pass	high	Three JSON-LD blocks plus Open Graph and Twitter metadata describe the visible public utility.
be-private-and-secure `secure-transport-and-headers`	issues	high	Headers probe found no CSP, HSTS, Referrer-Policy, or Permissions-Policy. All six cookies lacked Secure; three analytics cookies also used SameSite=None and 400-day expiry. F13 high: Browser-enforced security controls and cookie flags are incomplete.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	Tracker probe observed 13 third-party origins and known Google Analytics, DoubleClick, and Tag Manager trackers. HAR recorded 24 third-party requests and 1.13 MB third-party transfer; the CMP says data may be shared with 220 partners and precise geolocation may be used. F14 high: The page contacts a large advertising and analytics surface before an explicit choice.
be-private-and-secure `in-context-permissions-and-modern-auth`	not-applicable	high	The public downloader has no authentication flow and no browser permission request in the tested paths.
be-private-and-secure `defensive-browser-policies`	issues	high	Headers probe found no CSP, HSTS, Referrer-Policy, or Permissions-Policy. All six cookies lacked Secure; three analytics cookies also used SameSite=None and 400-day expiry. F13 high: Browser-enforced security controls and cookie flags are incomplete.
be-resilient `progressive-enhancement`	pass	high	Discoverability found 86% raw-HTML content coverage with title, H1, and description present; not a JS shell.
be-resilient `resilient-runtime-behaviour`	pass	high	Core submission completed and the consent dialog retained focus without a blank/broken shell.
be-resilient `offline-and-installable`	issues	high	The DOM probe found no web app manifest and no controlling service worker. This is an app-like utility with a repeated core action, so an installable shell and an explanatory offline state are applicable even though downloading itself requires connectivity. F15 medium: The app-like downloader is neither installable nor prepared for offline failure.
be-resilient `network-and-http-failure-states`	pass	high	A genuine 404 responds 404 with a clear explanation and homepage recovery link.
be-internationalised `lang-dir-and-logical-properties`	issues	high	The site exposes 24 hreflang alternates including Arabic, but the English page has no dir and source inspection counted 54 physical left/right declarations versus zero logical inline/block declarations. F16 medium: Localized pages are not built with bidirectional layout primitives.
be-internationalised `locale-aware-data`	not-applicable	high	The representative pages display no dates, numbers, currencies, durations, or calendar data requiring locale formatting.
be-internationalised `time-zone-correctness`	not-applicable	high	The representative pages contain no event or time-zone-dependent data.
be-trustworthy `no-dark-patterns`	issues	high	The blocking first-layer CMP offers “Consent” and “Manage options” while omitting an equally prominent reject action, despite describing 220 partners and precise-geolocation use. F17 high: Consent choice is asymmetric and encourages acceptance.
be-trustworthy `humane-error-handling`	pass	high	The tested 404 explains the issue without blame and provides a direct route home.
be-trustworthy `trustworthy-input-assistance`	pass	high	The URL input uses type=text, required, placeholder guidance, and the successful flow did not discard entered context.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	No purchase, subscription, billing, account closure, or authentication flow exists.
be-sustainable `optimised-assets`	issues	high	Lighthouse estimated 623 KiB unused JS across seven resources, including ad, prebid, HLS, IMA, analytics, and consent scripts; estimated LCP savings were 3.36 s. F11 high: The initial page ships hundreds of KiB of unused third-party JavaScript.
be-sustainable `no-wasteful-work`	issues	high	Lighthouse estimated 623 KiB unused JS across seven resources, including ad, prebid, HLS, IMA, analytics, and consent scripts; estimated LCP savings were 3.36 s. F11 high: The initial page ships hundreds of KiB of unused third-party JavaScript.
be-sustainable `third-party-and-media-budget`	issues	high	Tracker probe observed 13 third-party origins and known Google Analytics, DoubleClick, and Tag Manager trackers. HAR recorded 24 third-party requests and 1.13 MB third-party transfer; the CMP says data may be shared with 220 partners and precise geolocation may be used. F14 high: The page contacts a large advertising and analytics surface before an explicit choice.
be-agent-ready `structured-agent-capabilities`	pass	high	Server-rendered content, JSON-LD, canonical URLs, and a semantic GET form expose the primary capability to agents without proprietary UI automation.
be-agent-ready `on-device-inference`	not-applicable	high	The site has no inference feature for which on-device model execution would be appropriate.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	Twenty FAQ toggles produced a 22,515,627-byte heap versus 22,559,684 bytes in the comparable consent-loaded snapshot, with no retained growth signal.
be-memory-efficient `bounded-footprint`	pass	high	Comparable loaded heaps remained about 22.5 MB after repeated interaction; constructor populations were stable.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	Heap summaries showed no Detached* constructor among top retained constructors and repeated toggles did not increase closure count materially (26,285 to 26,288).

Provenance

Canonical report: results/atomic/reports/0077-snaptik_app.json
Report SHA-256: 8ee8f32d4b95353ca1e04a0d2736c73212bae5f33d40e2012528194f9e6d3f62
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/snaptik_app/2026-07-18T06-01-58-882Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/snaptik_app/2026-07-18T06-01-58-882Z
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.