Manifest position 891 · CrUX rank bucket 1000
https://isaidub.guru
Coverage complete
Coverage-complete audit of the redirected canonical site https://isaidub.ceo/ across home, listing, detail, download-step, updates, and error 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 | Under emulated prefers-color-scheme: dark, the body remained rgb(249,249,249) with black text and computed color-scheme was normal; the dark screenshot matched the light rendering. F001 medium: Honours prefers-color-scheme: a usable dark mode exists and is driven by the user's preference (color-scheme / prefers-color-scheme / light-dark()), not hard-coded light only. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, document.getAnimations() returned an empty list on the home template, so no active non-essential motion remained to suppress. |
respect-user-preferencesrespects-contrast | pass | high | Under forced-colors: active, body colors mapped to black/white system colors and links to yellow; text and links remained visible. |
implement-natural-interactionsview-transitions | issues | high | The MPA has meaningful home, listing, detail, and download-step navigations, but DOM/CSS inspection found no view-transition CSS or opt-in; route changes are abrupt full-document swaps. F002 low: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, entry/exit reveal, carousel, or other scroll-linked motion exists on the sampled templates, so there is no scroll-linked effect to implement declaratively. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The site exposes ordinary links and pagination only; no swipe, drag, pull-to-refresh, carousel, or custom pointer gesture was present on sampled paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The recent-updates template is 57,034 CSS pixels tall, but CSS/DOM inspection found no sticky progress, shrinking header, or scroll-state affordance. F003 low: Sticky/affixed UI reacts to scroll state and position (e.g. the new scroll-state(scrolled) query, shrinking headers, progress indicators) so chrome responds to position instead of static or JS-driven toggling. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, menu, or other anchored overlay appears on the sampled templates (zero dialog/popover elements). |
provide-guided-navigationdirects-attention | issues | high | Detail and updates templates have no h1 and no breadcrumb or main/nav landmarks; the 57,034px updates stream offers no location/progress cue beyond date text. F004 low: Navigation and in-page jumps guide attention (highlight effects, scroll/carousel markers, directional transitions, drill-down and drawer navigation) so the user can follow where focus moved. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots across four templates show content immediately with no full-viewport popup, consent wall, interstitial, or overlay; DOM reports no dialog/popover. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No transient disclosure, modal flow, select, or overlay exists on the sampled paths, so no dismissible custom primitive needs evaluation. |
maximize-content-reduce-noisereduced-chrome | issues | high | The home page repeats keyword-heavy promotional copy and 21 near-identical update rows before its category navigation; the updates page is a 57,034px undifferentiated stream. F005 low: Minimise non-content chrome and borders so the content is the focus, not the application frame; expressive/decorative visuals serve the content rather than crowd it. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, all four templates reported scrollWidth 360, clientWidth 360, viewport meta present, and 0px horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found no @container or container-type rules; reusable movie, folder, pagination, and form components adapt only through viewport media queries. F006 low: Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Keyboard focus is visible, but many category links measure only 14px high and update links 17px high, well below a comfortable touch target. F007 medium: Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The home h1 and introductory text identify the Tamil-dubbed catalog, listing titles name their year, and detail content presents movie facts; the next content links are visible in each first viewport. |
support-core-task-successprimary-flow-completion | pass | high | The representative journey completed predictably from a home Download Now link to movie detail, then Red Eye (Original), then explicit 720p/360p choices with real hrefs and no account wall. |
support-core-task-successclear-system-state-and-recovery | issues | high | A missing URL returns a bare Apache 404 with no site chrome, home link, search, retry, or recovery action. F008 medium: Loading, empty, success, error, offline, and partial-completion states are visible and actionable; users can retry, undo, cancel, go back, or continue without losing context. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 4.2s (poor), despite CLS 0 and TBT 0ms; the separate desktop trace measured LCP about 1.0s, so the mobile load remains the failing common condition. F009 high: Core Web Vitals are in the good range: LCP is fast, interaction latency (INP) is low, and CLS is minimal; work is prioritised and deferred sensibly. |
be-fast-and-stablevisual-stability | pass | high | Layout observers measured CLS 0 to 0.000103 across all four templates, and Lighthouse measured CLS 0. |
be-fast-and-stableefficient-main-thread | pass | high | The trace and all layout captures recorded no long tasks and 0ms total blocking time; Lighthouse also measured TBT 0ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR confirms two parser-inserted high-priority stylesheets (site CSS plus Google Fonts), while the document is cache-control:no-store and mobile LCP is 4.2s; the async scripts are not counted as render-blocking. F010 low: Critical resources are delivered efficiently: cache headers are useful, render-blocking chains are short, fonts do not block or shift text, HTTP delivery is modern, and network dependency trees do not delay the main content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 67 KiB unused JavaScript; HAR shows Google Tag Manager alone transfers 152,705 bytes versus 15,701 first-party bytes. F011 low: The page does not ship large unused or duplicated JavaScript/CSS, avoidable legacy bundles, or third-party code that dominates the load without user value. |
be-inclusivenames-roles-labels | pass | high | All 17 home images have alt text, links use native anchors, and no form controls or canvas are present; Lighthouse image-alt passed. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found repeated red 14px rating text at 3.79:1 and the white Page Keywords label on #36a8da at 2.7:1, below the required 4.5:1. F012 medium: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | Focus is visible, but only a header landmark exists on home and the detail/updates templates contain no headings; there are no main, nav, or footer landmarks. F013 medium: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves. |
be-inclusivelegible-text | issues | high | Body text is fixed at 14px and the updates page renders a 57,034px dense stream with long link labels and little grouping; screenshots show cramped scanability on mobile. F014 low: Text is legible and inclusively rendered: comfortable line layout, precise alignment, stable rendering across mixed fonts, no clipping or cramped wrapping that harms comprehension. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Reflow has no horizontal overflow and user scaling is allowed, but many links have only 14px to 17px high hit areas, failing comfortable touch-target sizing. F015 low: The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling. |
follow-best-practicesno-console-errors | pass | high | Lighthouse reported no browser errors logged to the console. |
follow-best-practicessound-document-and-assets | issues | high | Doctype and UTF-8 are valid, but all sampled folder images omit authored width/height attributes; the detail poster also omits dimensions. F016 low: Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.) |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports three BFCache failure reasons due cache-control:no-store/cookie modification and DevTools Issues entries from the ad-tech request chain. F017 low: The page uses the platform cleanly: no deprecated APIs, no avoidable BFCache blockers, no broken source maps or inspector issues, no stale vulnerable libraries, no paste-prevention on inputs, and no notification/geolocation prompts on load. |
be-discoverabletitle-and-description | pass | high | Home, listing, detail, and updates templates each expose a descriptive title and meta description; raw no-JS HTML preserves them. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Content links use real hrefs and the viewport is mobile-friendly, but footer Contact Us and DMCA links both point to the homepage, and the home page repeats generic “Download Now” link text for many different destinations. F018 low: Links are crawlable (real href), there is a viewport meta tag, robots does not block indexing, and link text is descriptive. |
be-discoverablecanonical-and-indexing-signals | issues | high | Public pages return 200 and robots allows search indexing, but no canonical or hreflang appears on sampled templates and /sitemap.xml returns an Apache 404 page. F019 low: Public pages expose the indexing signals search engines need: successful HTTP status, canonical URL when appropriate, hreflang for localized variants, robots/sitemap consistency, and no accidental noindex/noarchive policy. |
be-discoverablestructured-and-shareable-metadata | issues | high | The movie detail is a rich entity but exposes no JSON-LD, Open Graph, or Twitter Card metadata on the visible movie page. F020 low: Where the page represents an article, product, organization, event, place or other rich entity, structured data and share-preview metadata accurately describe the visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS, nosniff, framing protection, Referrer-Policy, and Permissions-Policy are absent; PHPSESSID is neither Secure nor HttpOnly and has SameSite=None. F021 high: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The page contacts five third-party origins, including Google Analytics and an ad-tech script; third parties account for 178,172 of 193,873 transferred bytes and analytics cookies live 400 days. F022 high: No over-collection of user data, no leaky third parties, and analytics/background data collection is minimised and batched rather than chatty or session-wide by default. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No sign-in/account flow exists and no geolocation, notification, camera, microphone, or other permission prompt fired on load. |
be-private-and-securedefensive-browser-policies | issues | high | No HSTS, clickjacking protection, Referrer-Policy, Permissions-Policy, or CSP frame-ancestors is configured, and cookies use a weak SameSite=None posture. F023 low: Browser-enforced defenses are configured where appropriate: HSTS, clickjacking protection (frame-ancestors / X-Frame-Options), Trusted Types for XSS-sensitive apps, origin isolation, privacy-preserving third-party cookie posture, and sensible Referrer-Policy / Permissions-Policy. |
be-resilientprogressive-enhancement | pass | high | Raw server HTML contains 100% of rendered content words on both home and detail, with title/description intact and no empty JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | The sampled site is server-rendered with ordinary links, no overlays or fragile async UI, no horizontal overflow, and no console errors during representative navigation. |
be-resilientoffline-and-installable | not-applicable | high | This is a public content/download catalog rather than an app-like installed experience; no manifest exists, so offline/installability is not a proportionate requirement for this check. |
be-resilientnetwork-and-http-failure-states | issues | high | The tested 404 is a bare server page with no branded context, home link, search, retry, or useful recovery path. F024 medium: HTTP errors, network failures, timeouts and stale data states are handled intentionally: users see useful recovery options rather than blank screens, infinite spinners, broken shells, or misleading success states. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang=en matches most sampled prose, but CSS uses physical padding-left, margin-right, and border-left in reusable components and has no dir strategy, so the layout is not translation/bidi ready for its Tamil-language audience. F025 low: Correct lang and dir attributes, logical CSS properties (inline/block) rather than physical left/right, and translation-ready markup so the layout and reading order survive other languages and writing modes. |
be-internationalisedlocale-aware-data | not-applicable | high | The public catalog renders fixed editorial dates and numeric ratings but has no user locale selector, currency, input, or dynamic locale-sensitive calculation to exercise. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event scheduling, user-entered time, recurring interval, or cross-zone time calculation exists on the sampled catalog pages. |
be-trustworthyno-dark-patterns | pass | high | First-load and download-journey screenshots show no consent wall, confirmshaming, forced continuity, disguised control, or cancellation flow; links behave predictably. |
be-trustworthyhumane-error-handling | not-applicable | high | No user-submittable form or editable field exists on the representative public templates. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, sign-up, search, or other input field appears on the sampled templates. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, consent, authentication, or account-management surface appears in the representative journey. |
be-sustainableoptimised-assets | pass | high | The home transfers only 4,336 image bytes; repeated folder art is one cached 713-byte SVG and no legacy raster formats appear there. |
be-sustainableno-wasteful-work | issues | high | A simple static catalog transfers 178,172 third-party bytes, mainly analytics/ad scripts, versus 15,701 first-party bytes; Lighthouse estimates 67 KiB of JavaScript is unused. F026 low: Background work and fetching are not wasteful: background processing is efficient and de-prioritised, and the lightest technique that achieves the result is preferred over heavy or redundant work. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties consume about 92% of transferred bytes, with Google Tag Manager at 152,705 bytes and additional analytics/ad origins despite no rich media requirement. F027 low: Third-party scripts, fonts, video, audio, animation and heavy media are proportionate to the user value they provide; autoplay or background media is avoided unless essential and resource use is cached or deferred where possible. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The site is a read-only crawlable content catalog with no transactional or productivity capability that needs WebMCP tool registration; raw content is already fully machine-readable. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, translation workflow, or other inference feature is offered where on-device AI would improve the experience. |
be-memory-efficientno-leak-under-repeated-interaction | not-applicable | high | The server-rendered site has ordinary document navigations and no modal, SPA route, editor, infinite scroll, or other same-document interaction to repeat about ten times without fabricating a test. |
be-memory-efficientbounded-footprint | pass | high | A settled home state used about 3.51 MB JS heap with 220 DOM elements; the heap summary reports 3.56 MB total self size, proportionate for the page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The single-state heap summary shows no Detached* constructor among the reported populations, and the static page has no repeated same-document lifecycle that accumulates listeners or timers. |
Provenance
Canonical report: results/atomic/reports/0891-isaidub_guru.json
Report SHA-256: 05640538c0fdbf2ebca22107aa02090cdf343364252521ecb4b193801d18e20c
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/isaidub_guru/2026-07-23T16-29-17-461Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/isaidub_guru/2026-07-23T16-29-17-461Z
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.