Manifest position 133 · CrUX rank bucket 1000
https://www.tamilsexzone.com
Coverage complete
Coverage-complete audit. Representative browser routes encountered Cloudflare verification; those challenge states were directly judged as issues and raw route HTML was also inspected.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Desktop and prefers-color-scheme:dark screenshots are effectively identical; the site is hard-coded dark and the white age-verification card remains white. F001 medium: The experience does not adapt its palette to the user color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce the probe found the preference active, one matching CSS rule, and zero active animations after load. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse failed color-contrast and link-in-text-block; the page relies on color for some links. F002 high: Essential UI does not consistently meet contrast requirements. |
implement-natural-interactionsview-transitions | issues | high | The live style probe found no view-transition marker and navigation is a traditional MPA with no cross-document transition declaration. F003 low: Route changes are abrupt rather than continuity-preserving. |
implement-natural-interactionsscroll-driven-animations | not-applicable | medium | No scroll-linked parallax, reveal, carousel, or scrollytelling interaction is present to implement. |
implement-natural-interactionsphysical-gestures | pass | high | CSS/DOM inspection found native scrolling and links, with no custom pointermove/swipe handlers fighting platform behavior. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Mobile layout is 6,187px tall, while the CSS/DOM probe found no scroll-state query, shrinking header, or progress indicator. F004 low: The long catalogue has no scroll-state navigation feedback. |
provide-guided-navigationanchored-positioning | not-applicable | medium | No tooltip, attached popover, or edge-positioned menu requiring anchor positioning was present in the audited surfaces. |
provide-guided-navigationdirects-attention | pass | high | The 6,187px mobile page and rendered CSS were inspected for sticky/scroll-state, anchor-positioning, and attention cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | The only on-load full-screen interruption is the proportionate age-verification safety gate; it exposes one clear continuation action and no unrelated promotion. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Probe found role=dialog on a DIV, but zero <dialog>, popover, or details elements; login/reset and age UI depend on custom behavior. F005 medium: Modal UI is implemented as custom divs instead of native dialog primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | The underlying page devotes the main document to catalogue cards and content; the safety gate is compact and contains no competing advertising. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800 layout reported 360px scrollWidth, 360px clientWidth, viewport meta present, and 0px horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The rendered stylesheet probe found no @container rules; catalogue cards are reused across sidebar and main grids. F006 low: Reusable content cards do not use component-level responsiveness. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The live probe counted 18 visible links/buttons/inputs under 24px in width or height at desktop; Lighthouse also reported links with weak discernibility. F007 medium: Several interactive targets are too small for reliable touch use. |
support-core-task-successclear-purpose-and-primary-action | issues | medium | The full-viewport age card says only “Start” and “We must check your age,” with no method, privacy link, provider explanation, or alternative before transfer to AgeVerif. F008 medium: The first action is vague and gives no decision context. |
support-core-task-successprimary-flow-completion | issues | medium | Homepage initially rendered the age gate, but the detail route screenshot later showed Cloudflare “Verify you are human”; raw detail HTML was available while the rendered journey could not continue. F009 high: Representative content routes are interrupted by bot verification. |
support-core-task-successclear-system-state-and-recovery | pass | high | Raw 404 returned HTTP 404 with “Page not found” and a Return to Home action; required form fields expose aria-required/aria-invalid state. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.6s and performance 0.74, although a separate trace measured LCP 1.545s; the variance itself signals an unreliable load path. F010 high: Load performance is inconsistent and can miss the good LCP threshold. |
be-fast-and-stablevisual-stability | pass | high | Layout observer measured CLS 0.000246 with only two tiny shifts and image cards generally reserve a 16:9 aspect ratio. |
be-fast-and-stableefficient-main-thread | pass | high | Trace found one 56.59ms long task and only 6.59ms total blocking time, with no long tasks in the mobile layout observer. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR identified seven VeryHigh-priority parser-inserted stylesheets plus parser-inserted jQuery and AgeVerif scripts; Lighthouse estimated 680ms render-blocking savings and weak font/cache delivery. F011 medium: The critical path contains avoidable render-blocking resources. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR loaded 16 scripts and seven stylesheets; Lighthouse found about 11KiB unused CSS plus unminified CSS/JS savings, including Contact Form 7 assets on the homepage. F012 low: Plugin and third-party code ships before it is needed. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed iframe-title and link-name. The live DOM has two iframes with empty titles and search/login text inputs without associated labels. F013 high: Several controls and frames lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed its color-contrast audit and reported links distinguishable only by color. F014 high: Text and link contrast is below WCAG minimums. |
be-inclusivestructure-and-focus | issues | high | The live heading sequence begins H3 Categories, H3 Tags, H2 sections, then reaches the page H1 near the footer; this weakens structural navigation. F015 medium: Heading order does not reflect the visual reading hierarchy. |
be-inclusivelegible-text | pass | high | Lighthouse scored accessibility 0.79 and failed contrast, iframe title, link name, link-in-text, and zoom. DOM found unlabelled search/login fields and a heading sequence beginning H3/H2 before H1. |
be-inclusivezoom-reflow-targets-and-media | issues | high | DOM contains maximum-scale=1.0,user-scalable=0 and Lighthouse failed meta-viewport; this prevents users from magnifying content. F016 high: The viewport explicitly disables user zoom. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit scored 1 with no captured console errors. |
follow-best-practicessound-document-and-assets | issues | high | Images primitive found two images without width/height; Lighthouse unsized-images also failed partially. F017 medium: Some images lack intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found three deprecation warnings from the Cloudflare challenge script and cookie issues in DevTools. F018 medium: The browser reports deprecated APIs and inspector issues. |
be-discoverabletitle-and-description | pass | high | Discoverability found HTTP 200, 96% raw/rendered word coverage, title/H1/description in raw HTML, and no JS shell. robots.txt points to a working sitemap; one ad anchor is not crawlable. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable-anchors for article.ad > a with no href; the probe counted three #/#! or missing destinations. F019 medium: At least one prominent ad card is not a crawlable link. |
be-discoverablecanonical-and-indexing-signals | pass | high | Discoverability found HTTP 200, 96% raw/rendered word coverage, title/H1/description in raw HTML, and no JS shell. robots.txt points to a working sitemap; one ad anchor is not crawlable. |
be-discoverablestructured-and-shareable-metadata | pass | high | Discoverability found HTTP 200, 96% raw/rendered word coverage, title/H1/description in raw HTML, and no JS shell. robots.txt points to a working sitemap; one ad anchor is not crawlable. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers primitive confirms HTTPS, HSTS, nosniff and X-Frame-Options, but no Content-Security-Policy header is served. F020 high: Content Security Policy is missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR recorded 32/55 third-party requests and 424,378 third-party bytes, including AgeVerif statistics and advertising origins; trackers found eight external origins before the user completed verification. F021 high: Third-party requests and statistics calls begin before meaningful consent. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Login markup exposes username and password fields, with no WebAuthn/passkey registration or authentication affordance. F022 medium: Authentication is password-only and omits modern credential support. |
be-private-and-securedefensive-browser-policies | issues | high | Headers primitive found no Referrer-Policy; CSP/frame-ancestors is also unavailable, although X-Frame-Options and Permissions-Policy are present. F023 medium: Referrer Policy is missing and browser defenses are incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 96% raw/rendered content coverage, no empty SPA mount, and title/H1/description survived without JavaScript. |
be-resilientresilient-runtime-behaviour | issues | medium | Detail and 404 screenshots showed Cloudflare verification instead of route content; the 404 capture was nearly blank while raw HTML returned a meaningful recovery page. F024 high: Bot-defense runtime behavior can replace real pages with an unproductive challenge. |
be-resilientoffline-and-installable | not-applicable | medium | This public media catalogue is an MPA, not an installable application; offline media playback is not part of the observed intent. |
be-resilientnetwork-and-http-failure-states | pass | high | The origin returns a real HTTP 404 with explanatory copy and a home recovery link rather than a soft-404 or empty shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | DOM CSS contains extensive margin-left, padding-left/right, text-align:left/right and directional positioning, with no evidence of a logical-property strategy. F025 medium: The stylesheet is heavily tied to physical left/right layout. |
be-internationalisedlocale-aware-data | not-applicable | medium | No rendered dates, numbers, currencies, durations, or calendar data requires locale formatting on the audited templates. |
be-internationalisedtime-zone-correctness | not-applicable | medium | No events, schedules, recurring intervals, or time-zone-sensitive values appear on the audited templates. |
be-trustworthyno-dark-patterns | pass | high | Observed advertising is labelled AD and the age check does not use confirmshaming, forced continuity, preselected consent, or a disguised decline control. |
be-trustworthyhumane-error-handling | pass | medium | Report-form markup marks required controls with aria-required and initial aria-invalid=false, providing a semantic basis for post-interaction validation. |
be-trustworthytrustworthy-input-assistance | issues | high | Live forms probe found null autocomplete on username, password, reset-email, and search fields. F026 medium: Sign-in and search inputs omit autocomplete assistance. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The account surface offers username/password login and lost-password reset only; no passkey management or reauthentication flow is exposed. F027 medium: Account access lacks phishing-resistant authentication and clear modern recovery affordances. |
be-sustainableoptimised-assets | issues | high | Images primitive found 42/42 images in JPEG/PNG, 12 oversized, 10 eager below-fold, and zero AVIF/WebP assets. F028 medium: Image delivery wastes bytes through legacy formats and oversized variants. |
be-sustainableno-wasteful-work | pass | high | Trace and layout recorded negligible blocking work after load and no repeating long tasks; no autoplay media began behind the age gate. |
be-sustainablethird-party-and-media-budget | issues | high | HAR attributed 424,378 of 696,392 transferred bytes to third-party origins and loaded multiple ad/stats/verification services before interaction. F029 medium: Third-party resources consume most transferred bytes without a stated budget. |
be-agent-readystructured-agent-capabilities | not-applicable | medium | No declared agent-facing transaction/tool surface exists for this media catalogue; emerging WebMCP exposure is not required. |
be-agent-readyon-device-inference | not-applicable | medium | No summarisation, generation, or inference task is part of the observed core experience, so built-in on-device AI is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten full-page scroll cycles, heap grew only 67,542 bytes (0.9%) and 865 nodes across independent cold captures; closure count decreased by two. |
be-memory-efficientbounded-footprint | pass | high | A 7.5MB summarized heap and about 131k heap nodes are proportionate to a 42-image WordPress catalogue page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | No Detached constructor appeared in leading heap constructors and closure count was flat (5,859 to 5,857) after repeated scrolling. |
Provenance
Canonical report: results/atomic/reports/0133-www_tamilsexzone_com.json
Report SHA-256: 62bc992e596786c0d5de9df5c64ce6ed53051a061bc6c233e85c6bc327d67c40
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_tamilsexzone_com/2026-07-27T15-46-35-480Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_tamilsexzone_com/2026-07-27T15-46-35-480Z
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.