Manifest position 419 · CrUX rank bucket 1000
https://indown.io
Coverage complete
Atomic coverage complete: all 58 checks judged across five 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 | Light and dark emulation screenshots retain the same dark #212529 page surface; DOM computed styles report color-scheme: dark. F03 medium: Theme is hard-coded dark instead of following the user color-scheme preference |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe reports a running color-change animation with 1000ms duration even though prefers-reduced-motion: reduce matches. F04 medium: A decorative animation continues under reduced-motion |
respect-user-preferencesrespects-contrast | issues | high | CSS evidence contains reduced-motion rules but no prefers-contrast or forced-colors adaptation, while Lighthouse directly identifies essential tabs, headings, and brand text at only 2.22:1 to 2.69:1. F19 medium: The fixed theme has no high-contrast adaptation and already loses essential contrast |
implement-natural-interactionsview-transitions | issues | high | The platform probe found no authored transition components, anchor positioning, or scroll timelines; navigation is conventional full-document links and the sampled FAQ/menu state uses Bootstrap-style abrupt state changes. F07 low: Route and state changes lack authored transition/attention cues |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked parallax, scrollytelling, carousel motion, or reveal effect exists on the representative paths, so there is no scroll animation implementation to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No custom drag, swipe, pull, or gesture-driven interaction exists; the site uses ordinary native scrolling, links, and buttons. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The platform probe found no authored transition components, anchor positioning, or scroll timelines; navigation is conventional full-document links and the sampled FAQ/menu state uses Bootstrap-style abrupt state changes. F07 low: Route and state changes lack authored transition/attention cues |
provide-guided-navigationanchored-positioning | not-applicable | high | No trigger-attached tooltip, popover, or edge menu exists on the representative paths; the centered modal consent dialog does not require anchor positioning. |
provide-guided-navigationdirects-attention | issues | high | The platform probe found no authored transition components, anchor positioning, or scroll timelines; navigation is conventional full-document links and the sampled FAQ/menu state uses Bootstrap-style abrupt state changes. F07 low: Route and state changes lack authored transition/attention cues |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and 360x800 screenshots on the home, Reels, TikTok, contact, and Arabic paths show a modal consent wall before the downloader or form can be used. On mobile it fills most of the viewport. F01 high: Consent wall obscures every primary surface on first load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM evidence identifies .fc-consent-root containing a div role=dialog and a separate overlay; no <dialog>, popover, or details primitives exist on the page. F02 medium: Consent UI is a custom div dialog rather than a native dialog primitive |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop and 360x800 screenshots on the home, Reels, TikTok, contact, and Arabic paths show a modal consent wall before the downloader or form can be used. On mobile it fills most of the viewport. F01 high: Consent wall obscures every primary surface on first load |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800 the layout primitive reports scrollWidth=clientWidth=360 and zero horizontal overflow; viewport meta is present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSSOM probing found zero CSSContainerRule entries even though the downloader/form/navigation components recur across templates. F08 low: Reusable downloader components rely only on viewport layout |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe shows the navbar toggle, URL input, search button, and FAQ buttons with outline none while focused; many navigation targets are 20-40px tall. Lighthouse also reports an invalid H2-to-H4 heading order. F06 high: Keyboard focus and target sizing are inconsistent, and heading order skips levels |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first page content and raw HTML identify “Instagram Video Downloader” and expose one URL field plus a SEARCH submit action. |
support-core-task-successprimary-flow-completion | pass | high | DOM walkthrough shows a one-step POST form to /download with one required URL and no account or upsell step; the consent choice offers an equally prominent rejection action. |
support-core-task-successclear-system-state-and-recovery | issues | high | The primary URL field has no label or aria-invalid state, and the invalid submission navigation closed the inspected target without an in-place role=alert or recoverable error captured. F09 medium: Downloader failure and recovery states are not exposed accessibly |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 7.1s and CLS 0.225; the mobile layout primitive independently observed CLS 0.205. TBT remained low at 100ms. F10 high: Largest content paint and layout stability miss the good range |
be-fast-and-stablevisual-stability | issues | high | Lighthouse measured LCP 7.1s and CLS 0.225; the mobile layout primitive independently observed CLS 0.205. TBT remained low at 100ms. The images primitive found all three images without width/height and two legacy JPEGs; Lighthouse reports three deprecated API warnings from the Cloudflare challenge script. F10 high: Largest content paint and layout stability miss the good range F12 medium: Images lack dimensions and third-party code uses deprecated APIs |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded zero long tasks and 0ms TBT; Lighthouse TBT was 100ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse measured LCP 7.1s and CLS 0.225; the mobile layout primitive independently observed CLS 0.205. TBT remained low at 100ms. HAR records 930,902 transferred bytes, 821,879 third-party bytes and 805,862 script bytes. Lighthouse estimates 370 KiB unused JS and 45 KiB unused CSS. F10 high: Largest content paint and layout stability miss the good range F11 high: Third-party advertising and analytics dominate bytes and unused code |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR records 930,902 transferred bytes, 821,879 third-party bytes and 805,862 script bytes. Lighthouse estimates 370 KiB unused JS and 45 KiB unused CSS. F11 high: Third-party advertising and analytics dominate bytes and unused code |
be-inclusivenames-roles-labels | issues | high | The contact DOM shows required email and message controls with placeholders but no associated labels or aria-labels; email autocomplete is empty. The downloader URL input also has no label and autocomplete=off. F18 medium: Forms depend on placeholders and omit durable labels/autocomplete assistance |
be-inclusivesufficient-contrast | issues | high | Lighthouse reports contrast ratios of 2.22:1 to 2.69:1 for the brand, active tabs, H1, and H2 text against dark surfaces, below required 3:1 or 4.5:1 thresholds. F05 high: Primary brand, tab, and heading colours fail WCAG contrast |
be-inclusivestructure-and-focus | issues | high | The focus probe shows the navbar toggle, URL input, search button, and FAQ buttons with outline none while focused; many navigation targets are 20-40px tall. Lighthouse also reports an invalid H2-to-H4 heading order. F06 high: Keyboard focus and target sizing are inconsistent, and heading order skips levels |
be-inclusivelegible-text | pass | high | Mobile and desktop captures plus DOM styles show 16px base text, fluid widths, and no horizontal clipping; contrast divergences are separately recorded. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The focus probe shows the navbar toggle, URL input, search button, and FAQ buttons with outline none while focused; many navigation targets are 20-40px tall. Lighthouse also reports an invalid H2-to-H4 heading order. F06 high: Keyboard focus and target sizing are inconsistent, and heading order skips levels |
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 | The images primitive found all three images without width/height and two legacy JPEGs; Lighthouse reports three deprecated API warnings from the Cloudflare challenge script. F12 medium: Images lack dimensions and third-party code uses deprecated APIs |
follow-best-practicesbrowser-platform-hygiene | issues | high | The images primitive found all three images without width/height and two legacy JPEGs; Lighthouse reports three deprecated API warnings from the Cloudflare challenge script. F12 medium: Images lack dimensions and third-party code uses deprecated APIs |
be-discoverabletitle-and-description | pass | high | DOM and raw HTML contain the descriptive title “Instagram Video Downloader | Fast & Secure” and a matching meta description. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse SEO passed; links have href values, viewport metadata exists, and robots.txt allows crawling. |
be-discoverablecanonical-and-indexing-signals | pass | high | HTTP returned 200; canonical and 22 hreflang/x-default links are present; robots.txt allows all and points to a populated sitemap. |
be-discoverablestructured-and-shareable-metadata | issues | high | The metadata probe found no JSON-LD, Open Graph, or Twitter card tags on the public downloader page, despite a canonical URL and rich tool/organization content. F13 low: Rich entity and social-preview metadata are absent |
be-private-and-securesecure-transport-and-headers | issues | high | Headers evidence shows no CSP or HSTS, and no Referrer-Policy or Permissions-Policy. Cookie evidence reports six non-Secure analytics/consent cookies and SameSite=None usage. F14 high: Security headers and cookie attributes are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Trackers evidence finds 10 third-party origins and four known tracker domains; HAR assigns 20 requests and 821,879 bytes to third parties while the consent wall is still present. F15 high: Tracking starts with a broad third-party footprint before a consent choice |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No authentication flow or browser-permission request exists on the representative public downloader and contact paths. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence shows no CSP or HSTS, and no Referrer-Policy or Permissions-Policy. Cookie evidence reports six non-Secure analytics/consent cookies and SameSite=None usage. F14 high: Security headers and cookie attributes are incomplete |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 88% raw/rendered content coverage, title/H1/description in raw HTML, and no empty JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | Desktop and 360x800 screenshots on the home, Reels, TikTok, contact, and Arabic paths show a modal consent wall before the downloader or form can be used. On mobile it fills most of the viewport. F01 high: Consent wall obscures every primary surface on first load |
be-resilientoffline-and-installable | issues | high | A manifest and active service worker exist, but serviceworker.js caches only six icon files and falls through to fetch() for every page without an offline response. F16 medium: Installed PWA has no offline fallback for core pages |
be-resilientnetwork-and-http-failure-states | issues | high | The primary URL field has no label or aria-invalid state, and the invalid submission navigation closed the inspected target without an in-place role=alert or recoverable error captured. F09 medium: Downloader failure and recovery states are not exposed accessibly |
be-internationalisedlang-dir-and-logical-properties | issues | high | The Arabic path correctly sets lang=ar and exposes hreflang links, but documentElement.dir is empty while the visible content is Arabic. F17 high: Arabic pages omit RTL direction metadata |
be-internationalisedlocale-aware-data | not-applicable | high | No dates, prices, currencies, durations, or other locale-sensitive data appear on the sampled downloader, support, or localized pages. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event or time-zone-sensitive data appears on the sampled site. |
be-trustworthyno-dark-patterns | issues | high | Trackers evidence finds 10 third-party origins and four known tracker domains; HAR assigns 20 requests and 821,879 bytes to third parties while the consent wall is still present. F15 high: Tracking starts with a broad third-party footprint before a consent choice |
be-trustworthyhumane-error-handling | issues | high | The contact DOM shows required email and message controls with placeholders but no associated labels or aria-labels; email autocomplete is empty. The downloader URL input also has no label and autocomplete=off. The primary URL field has no label or aria-invalid state, and the invalid submission navigation closed the inspected target without an in-place role=alert or recoverable error captured. F18 medium: Forms depend on placeholders and omit durable labels/autocomplete assistance F09 medium: Downloader failure and recovery states are not exposed accessibly |
be-trustworthytrustworthy-input-assistance | issues | high | The contact DOM shows required email and message controls with placeholders but no associated labels or aria-labels; email autocomplete is empty. The downloader URL input also has no label and autocomplete=off. F18 medium: Forms depend on placeholders and omit durable labels/autocomplete assistance |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication, or account-management flow is present. |
be-sustainableoptimised-assets | issues | high | The images primitive found all three images without width/height and two legacy JPEGs; Lighthouse reports three deprecated API warnings from the Cloudflare challenge script. F12 medium: Images lack dimensions and third-party code uses deprecated APIs |
be-sustainableno-wasteful-work | issues | high | HAR records 930,902 transferred bytes, 821,879 third-party bytes and 805,862 script bytes. Lighthouse estimates 370 KiB unused JS and 45 KiB unused CSS. F11 high: Third-party advertising and analytics dominate bytes and unused code |
be-sustainablethird-party-and-media-budget | issues | high | HAR records 930,902 transferred bytes, 821,879 third-party bytes and 805,862 script bytes. Lighthouse estimates 370 KiB unused JS and 45 KiB unused CSS. Trackers evidence finds 10 third-party origins and four known tracker domains; HAR assigns 20 requests and 821,879 bytes to third parties while the consent wall is still present. F11 high: Third-party advertising and analytics dominate bytes and unused code F15 high: Tracking starts with a broad third-party footprint before a consent choice |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent was found; this public downloader does not currently present an agent integration surface. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or inference use case is part of the downloader’s visible product intent. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten FAQ open/close cycles, heap node count fell from 406,191 to 404,034 and self size from 21,951,073 to 21,666,809 bytes; no retained-growth signal appeared. |
be-memory-efficientbounded-footprint | pass | medium | Heap summaries show about 22MB self size for this advertising-supported page, while trace reports no long tasks; judged proportionate with medium confidence. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after heap summaries contain no Detached* constructor rows and node/edge counts did not grow after repeated FAQ interaction. |
Provenance
Canonical report: results/atomic/reports/0419-indown_io.json
Report SHA-256: 1df717e33132210bf1791e1ab2a494288ecd2736ca5476d12439560b74643a7e
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/indown_io/2026-07-20T16-51-44-351Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/indown_io/2026-07-20T16-51-44-351Z
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.