Manifest position 161 · CrUX rank bucket 1000
https://thisvid.com
Coverage complete
Coverage-complete agentic audit across five representative paths. Authenticated/account-only surfaces, uploads, checkout, private media, albums, community member areas, and destructive account actions were not covered because no credentials were provided and representative public templates already covered the primary anonymous journeys.
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 screenshots are byte-identical, and the CSS probe found no color-scheme or prefers-color-scheme rules. F01 medium: The site ignores the user’s color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe matched reduce but still reported body transition: 0.3s; CSS contains no reduced-motion override. F02 low: A body fade remains active under reduced-motion. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse found contrast failures including 2.62:1 red text on #151515 and multiple gray-on-black labels. F03 high: Important text does not meet minimum contrast. |
implement-natural-interactionsview-transitions | issues | high | CSS/DOM probe found no View Transition usage across an MPA with repeated header and listing/detail navigation. F04 low: Full-page navigation has no continuity treatment. |
implement-natural-interactionsscroll-driven-animations | issues | high | The homepage is 6,608px tall on mobile and the CSS probe found no scroll timeline or equivalent progress affordance. F05 low: Long listing pages provide no scroll progress or state cue. |
implement-natural-interactionsphysical-gestures | pass | high | Native scrolling remains unhijacked and the mobile layout has no horizontal overflow; no custom pointer-drag anti-pattern was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | A 6,608px mobile listing retains static chrome, with no scroll-state query or progress behavior in the probe. F06 medium: The long browse page offers no scroll-state-aware navigation. |
provide-guided-navigationanchored-positioning | issues | high | Rendered DOM uses data-toggle="popover" and custom dropable elements; no Popover API or CSS anchor-positioning signal was found. F07 low: Menus and search popovers use legacy custom positioning. |
provide-guided-navigationdirects-attention | pass | medium | Headings, selected navigation, large thumbnails, and the detail-page player establish a visible next focus on the representative paths. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Mobile screenshots show a fixed consent banner covering cards, form footer, or player metadata before interaction. F08 high: The cookie banner obscures primary content on every tested mobile path. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The consent action is an <a> without href and positive tabindex; probe found zero dialog or popover elements. F09 medium: Dismissible UI is built from custom anchors and divs. |
maximize-content-reduce-noisereduced-chrome | issues | high | The header reaches roughly 214px and the fixed cookie banner covers the bottom ~116px of an 800px viewport. F10 medium: Chrome and overlays consume too much of the first mobile viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All four representative mobile layouts reported scrollWidth 360, clientWidth 360, and zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | medium | Listing cards reflow from three columns on desktop to two on mobile, and the player and login form fit at 360px. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focused link computed outline is none 0px; probe counted 18 visible targets below 24px and Lighthouse failed target-size. F11 high: Keyboard focus and touch target support are inadequate. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The homepage states “Most Recent Porn Videos”, exposes filters, and presents immediately selectable content; detail and login pages have clear headings. |
support-core-task-successprimary-flow-completion | issues | high | Lighthouse on /login recorded an uncaught TurnstileError for an invalid or missing sitekey parameter while the screenshot remained at “Verifying…”. F12 high: The login flow’s verification widget throws a runtime error. |
support-core-task-successclear-system-state-and-recovery | issues | high | The login probe found zero aria-live/alert regions; fields omit required and aria-invalid, while native pattern messages only appear after synthetic values. F13 high: Form errors and recovery state are not announced accessibly. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured homepage LCP 8.2s and login LCP 5.5s, despite low TBT and CLS. F14 high: Cold-load LCP is slow on primary pages. |
be-fast-and-stablevisual-stability | pass | high | Observed CLS was 0 on home/categories, 0.018 on video, and 0.037 on login, all below the 0.1 good threshold. |
be-fast-and-stableefficient-main-thread | pass | high | The trace recorded no long tasks and 0ms TBT; Lighthouse TBT was 70ms on home and 20ms on login. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 184 requests and 3.70MB transferred; multiple parser-inserted stylesheets and classic scripts are high-priority render-blocking candidates confirmed in DOM. F15 high: The homepage over-fetches and blocks rendering. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 262KiB unused JavaScript and 17KiB unused CSS on the homepage. F16 medium: A large share of shipped JS and CSS is unused. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found the mobile menu button, pagination link, and multiple iframes without accessible names or titles. F17 high: Interactive controls and frames lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reported multiple 2.62:1 to 4.49:1 foreground/background combinations on all tested templates. F18 high: Text contrast fails WCAG thresholds. |
be-inclusivestructure-and-focus | issues | high | Lighthouse found no main landmark and positive tabindex values 1 and 2; focus probe showed no visible outline. F19 high: Landmarks and focus order are incomplete. |
be-inclusivelegible-text | issues | high | Screenshots and Lighthouse show 9–12px gray labels and footer links on black, several with insufficient contrast. F20 medium: Small muted text is difficult to read. |
be-inclusivezoom-reflow-targets-and-media | issues | high | meta viewport contains user-scalable=no; Lighthouse failed meta-viewport and target-size on home and login. F21 high: The viewport disables zoom and many targets are undersized. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured an uncaught Cloudflare TurnstileError on /login. F22 medium: The login page logs an uncaught verification exception. |
follow-best-practicessound-document-and-assets | pass | high | Representative pages have an HTML doctype, UTF-8 charset, viewport meta, image dimensions, and valid image aspect ratios. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed Inspector Issues and reported 17 bfcache failure reasons on home, including no-store responses and WebSocket use. F23 medium: The page triggers browser issues and prevents bfcache. |
be-discoverabletitle-and-description | pass | high | All representative templates provide distinct titles and meta descriptions in raw server HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable-anchors for the href-less consent action and meta-viewport for user-scalable=no; the DOM probe counted three anchors without href. F24 medium: Some controls are non-crawlable anchors and zoom is disabled. |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt returned 200, but /sitemap.xml returned HTTP 404 with an HTML error body. F25 medium: The advertised sitemap endpoint is missing. |
be-discoverablestructured-and-shareable-metadata | issues | high | Probe found zero JSON-LD blocks; homepage og:image is only “https:”, og:description is empty, and video dimensions are empty. F26 medium: Structured and social metadata is incomplete or malformed. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers lack CSP and nosniff; cookies probe found PHPSESSID and analytics cookies without Secure; Lighthouse saw two HTTP ad beacons upgraded to HTTPS. F27 high: Security headers and cookie transport flags are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Trackers found 19 third-party origins; HAR attributes 156 requests and 3.67MB to third parties, including GTM, Yandex and ad networks, while only “Got it” is offered. F28 high: Tracking starts before meaningful consent across a very large third-party surface. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Login fields omit autocomplete tokens and the DOM contains no passkey/WebAuthn flow despite browser support. F29 medium: Authentication lacks modern credential assistance. |
be-private-and-securedefensive-browser-policies | issues | high | CSP, Referrer-Policy and Permissions-Policy are absent; 12 cookies were flagged for insecure or SameSite=None behavior. F30 high: Defensive browser policies are incomplete. |
be-resilientprogressive-enhancement | pass | high | Raw HTML retained 84–96% of rendered content and titles/descriptions across all representative templates; none was a JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | The login widget stays in verification while Lighthouse records an uncaught TurnstileError, with no accessible fallback state. F31 medium: A third-party verification failure is not handled gracefully. |
be-resilientoffline-and-installable | not-applicable | high | This server-rendered media/community site does not present itself as an installable app; no manifest or controlling service worker is declared, so offline installability was judged outside its current product intent. |
be-resilientnetwork-and-http-failure-states | issues | high | A deliberately unknown URL returned HTTP 200 and rendered the homepage instead of a clear not-found state and recovery choices. F32 medium: Unknown routes produce a soft 404. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Probe found html lang=en but no dir and no logical-property signals in loaded CSS. F33 low: The document language is set but layout CSS is not direction-ready. |
be-internationalisedlocale-aware-data | issues | high | Rendered cards use strings such as “3 hours ago” and raw count formatting, with no locale-aware formatting evidence in the page DOM/CSS. F34 low: Relative time and large counts appear as hard-coded English formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited public surfaces show relative ages, not scheduled events or user-entered absolute times, so no time-zone conversion task applies. |
be-trustworthyno-dark-patterns | issues | high | The fixed banner states continued use implies agreement and exposes only “Got it” plus Learn more, while trackers already run. F35 high: Consent offers acceptance but no equivalent rejection or preference choice. |
be-trustworthyhumane-error-handling | issues | high | Fields are not required, have no aria-invalid, and there are no live regions; invalid values yield generic “Please match the format requested.” F36 medium: Login validation relies on terse browser pattern errors and lacks announced recovery. |
be-trustworthytrustworthy-input-assistance | issues | high | Username and password inputs returned empty autocomplete values. F37 medium: Login fields omit autocomplete semantics. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The unauthenticated login flow is blocked by a Turnstile exception and exposes no passkey option. F38 medium: The account entry flow lacks resilient verification and modern reauthentication support. |
be-sustainableoptimised-assets | issues | high | Images audit found 40 without srcset, 14 legacy-format images, no modern-format img sources, and 34 below-fold images without native lazy loading. F39 medium: Images are not responsively or format optimized. |
be-sustainableno-wasteful-work | issues | high | HAR recorded 42 fetch/XHR requests and three MP4 fetches, including 2.47MB from one media CDN before the user selected content. F40 high: The homepage performs substantial idle/background network work. |
be-sustainablethird-party-and-media-budget | issues | high | Of 3.70MB transferred, 3.67MB and 156 requests were third-party; individual MP4 requests reached 1.15MB and 0.79MB. F41 high: Third-party and media transfer dominates the page budget. |
be-agent-readystructured-agent-capabilities | issues | high | Probe found no WebMCP/tool registration; Lighthouse agentic-browsing score was 0.33 and reported a malformed accessibility tree. F42 low: Search and account capabilities have no machine-readable agent interface. |
be-agent-readyon-device-inference | not-applicable | high | The site offers no summarization, writing, or inference feature whose privacy or latency would benefit from built-in on-device AI. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten mobile-menu open/close cycles, DOM count stayed 1,137 and independent post heap totals were lower (336,437 nodes/18.38MB vs 344,343/18.64MB baseline); no retained-growth signal was observed. |
be-memory-efficientbounded-footprint | pass | medium | The measured 18.6MB JS heap snapshot and 1,137-element DOM are proportionate to a media listing; no unbounded footprint was observed in the sampled state. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Repeated menu interaction left DOM/resource counts unchanged and the post heap node count decreased; no accumulation signal was observed, though dedicated retainer analysis was not run. |
Provenance
Canonical report: results/atomic/reports/0161-thisvid_com.json
Report SHA-256: f272407b1aad42e266f82d7681565cf80fbbe5b04ed61ebcc1eb0740ac646e5b
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/thisvid_com/2026-07-18T20-23-20-921Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/thisvid_com/2026-07-18T20-23-20-921Z
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.