Manifest position 991 · CrUX rank bucket 1000
https://ssstik.io
Coverage complete
Atomic coverage complete across 58 checks and six 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-mode screenshot is visually identical to the light screenshot, and the CSS probe found no color-scheme or prefers-color-scheme rule. F01 medium: The site ignores the user’s dark color preference |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce active, getAnimations() still reported a running 10-second infinite gradient animation; CSS has no reduced-motion rule. F02 medium: A perpetual header animation continues under reduced-motion |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse contrast-related accessibility audits passed and screenshots show high-contrast white text and outlined controls on the gradient. |
implement-natural-interactionsview-transitions | issues | high | Rendered CSS contains no view-transition rules; the MPA navigation and form replacement rely on abrupt state swaps. F03 low: Route and state changes do not provide directional continuity |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | The representative pages use no scroll-linked parallax, reveal, carousel, or scrollytelling effect to implement. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No gesture-driven carousel, swipe, pull-to-reveal, or custom pointer interaction is present. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The mobile layout is 7,987px tall, but the CSS probe found no scroll timeline/state behavior or progress affordance. F04 low: The long page offers no scroll-state guidance |
provide-guided-navigationanchored-positioning | not-applicable | high | No owned tooltip, popover, or anchored menu was present on the representative pages. |
provide-guided-navigationdirects-attention | issues | high | The state probe found no view-transition/highlight/scroll-marker treatment; the valid submission replaced the main content without a visible result or focused status. F05 low: Navigation and replaced form state do not guide attention |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | A fresh contact-page session placed focus in a full consent dialog before the form, covering the core content and presenting Consent and Manage options only. F06 high: Consent can obscure the requested content on entry |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection found zero dialog/popover elements while the page ships custom .modal markup and a third-party consent dialog. F07 medium: Overlays use custom modal markup instead of native dialog primitives |
maximize-content-reduce-noisereduced-chrome | pass | high | Desktop and mobile screenshots devote the first viewport to the named task and one primary form with limited chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, layout measured scrollWidth 360 and horizontalOverflowPx 0; viewport meta allows scaling to 5x. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no container queries despite reusable header, form, and content components across templates. F08 low: Responsive behavior is only viewport-level |
adapt-to-the-form-factorinput-modality-aware | issues | high | Programmatic focus on the primary URL field produced outline: none; the platform probe also found four interactive targets below 24px in one dimension. F09 medium: Keyboard focus and control sizing are inconsistent |
support-core-task-successclear-purpose-and-primary-action | pass | high | Desktop and mobile first viewports show a specific H1, one URL field, and a prominent Download action. |
support-core-task-successprimary-flow-completion | issues | high | After submitting a representative public TikTok URL and waiting 8 seconds, the result contained no download links and no explanatory error, while the page body collapsed to header/footer content. F10 high: A representative valid TikTok URL dead-ends without a result |
support-core-task-successclear-system-state-and-recovery | issues | high | Invalid input produced clear text, but a representative valid-looking URL produced an empty error node and no recovery message or status announcement. F11 high: The primary flow has an unannounced blank failure state |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP at 8.6s, Speed Index 5.8s, TBT 120ms, and performance 0.69; the unthrottled trace’s LCP was 1.17s, confirming network/device conditions drive the regression. F12 high: Mobile LCP is well outside the good range |
be-fast-and-stablevisual-stability | pass | high | The mobile layout observer measured CLS 0 with no shift entries over the sampled load. |
be-fast-and-stableefficient-main-thread | pass | high | The raw trace recorded no tasks over 50ms and 0ms TBT; throttled Lighthouse TBT was still 120ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse reported the ad image was not discoverable in initial HTML and lacked fetchpriority; the longest request chain was 1.33s with unused preconnect warnings. F13 medium: The LCP resource is discovered late and critical hints are ineffective |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR measured 605KB of script across seven requests; Lighthouse estimated 268KiB unused JS, led by AdSense and two Google tag bundles. F14 high: Third-party scripts dominate transferred and unused JavaScript |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed the label audit for the hidden hamburger checkbox; DOM probes found no label for the required URL input and no labels for contact email/message fields. F15 high: Primary and contact form controls lack programmatic labels |
be-inclusivesufficient-contrast | pass | high | Lighthouse accessibility scored 0.94 with no color-contrast failure; sampled text and controls remain legible. |
be-inclusivestructure-and-focus | issues | high | The primary URL field has no outline when focused, and the valid submission did not move focus to a named result/status region. F16 medium: Focus feedback and post-action focus management are weak |
be-inclusivelegible-text | pass | high | Representative screenshots show readable text sizing, line length, and spacing on mobile and desktop. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The platform probe found four interactive targets below 24px in one dimension, although the page reflowed without horizontal overflow and permits 5x scaling. F17 medium: Several controls fall below robust target sizing |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no recorded errors. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found three of 12 images missing width or height, seven without responsive sources, and four SVGs rendered far below intrinsic width. F18 medium: Several images omit intrinsic dimensions |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse best-practices scored 0.77 and reported a Cookie inspector issue plus a third-party cookie from DoubleClick. F19 medium: Browser inspector issues are generated by advertising cookies |
be-discoverabletitle-and-description | pass | high | DOM shows a descriptive unique title and populated meta description on sampled templates. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Real href links, viewport meta, and permissive robots.txt were observed. |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage returned 200, has canonical and complete hreflang set; robots points to a populated sitemap. |
be-discoverablestructured-and-shareable-metadata | issues | high | The homepage JSON-LD declares a 4.9 aggregateRating with 297,531 reviews while no rating or review evidence appears in the rendered page; og:type is article for an app utility. F20 medium: Structured metadata makes unsupported rating claims |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show HTTPS, HSTS and nosniff, but no CSP; all four observed first-party cookies lacked Secure and used SameSite=None. F21 high: Cookies and CSP do not meet the secure baseline |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 10 third-party origins and five known tracker domains; the consent copy states data may be shared with 210 partners. F22 high: The page sends data to a broad advertising and analytics surface |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No authentication surface or browser permission request exists in the audited public flows. |
be-private-and-securedefensive-browser-policies | issues | high | The header audit found no Referrer-Policy or Permissions-Policy in addition to the missing CSP; clickjacking protection and HSTS were present. F23 medium: Key browser-enforced policy headers are absent |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 100% raw/rendered content coverage, with title, H1, and description in server HTML. |
be-resilientresilient-runtime-behaviour | pass | high | Mobile samples did not clip menus/content; invalid state preserved the form and the 404 page retained navigation. |
be-resilientoffline-and-installable | issues | high | The manifest has empty name and short_name and no start_url; navigator.serviceWorker.ready did not resolve during the test. F24 medium: The app-like site advertises a manifest but is not installable or offline-capable |
be-resilientnetwork-and-http-failure-states | pass | high | Invalid URL input gets a clear corrective message, and unknown routes get a descriptive 404 with return link. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Arabic sample sets lang=ar and dir=rtl, publishes hreflang alternates, and rendered correctly at 360px. |
be-internationalisedlocale-aware-data | not-applicable | high | The sampled pages render no user-facing dates, numbers, currencies, durations, or calendars. |
be-internationalisedtime-zone-correctness | not-applicable | high | The sampled pages expose no time-zone-sensitive events or date/time data. |
be-trustworthyno-dark-patterns | issues | high | The consent dialog says data may be shared with 210 partners and exposes Consent plus Manage options, but no equally prominent reject action on the first layer. F25 high: Consent prioritizes acceptance over refusal |
be-trustworthyhumane-error-handling | issues | high | Invalid URL text is clear, but #errorContainer has no alert/live semantics; the contact form fields are not required and empty submission was intercepted by consent. F26 medium: Errors are visible but not exposed as accessible status |
be-trustworthytrustworthy-input-assistance | issues | high | The URL, contact email, and message controls have empty autocomplete values; contact email is type=text and fields have no associated labels. F27 medium: Forms omit labels and autofill assistance |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, sign-in, or account-management flow exists on the sampled site. |
be-sustainableoptimised-assets | issues | high | Lighthouse identified a 360x300 ad image inserted after parse as LCP without initial discovery; the image audit also found missing dimensions and responsive sources. F28 medium: The dynamically selected LCP ad image is not responsively delivered |
be-sustainableno-wasteful-work | issues | high | HAR recorded 29 requests and 646KB transferred, including 605KB script; Lighthouse found 268KiB unused JS. F29 high: Advertising and analytics ship substantial work before user value |
be-sustainablethird-party-and-media-budget | issues | high | Ten third-party origins and five known tracker domains support a simple URL form; scripts account for nearly all transferred bytes. F30 high: Third-party tracking consumes a disproportionate page budget |
be-agent-readystructured-agent-capabilities | issues | high | The site is fully visible to non-JS crawlers, but the DOM probe found only a conventional form and no WebMCP or agentic-tool registration. F31 low: The downloader capability is not exposed as a structured agent action |
be-agent-readyon-device-inference | not-applicable | high | Summarisation or language-model inference is not material to the simple URL-download task. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 mobile-menu open/close cycles, retained heap differed by only 263KB (2.4%) across snapshots; no Detached constructor appeared. |
be-memory-efficientbounded-footprint | pass | medium | Baseline heap was 10.8MB self size and 225,175 nodes, proportionate to the page plus advertising stack. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither baseline nor post-interaction heap summary listed Detached constructors; repeated interaction showed modest bounded growth. |
Provenance
Canonical report: results/atomic/reports/0991-ssstik_io.json
Report SHA-256: a065a28f499b50660db0a410402a8d19a0bd2a0b99f4ae87662bb6d056f65c35
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/ssstik_io/2026-07-24T09-42-28-919Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/ssstik_io/2026-07-24T09-42-28-919Z
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.