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.

Attempts
3 / 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 / checkStatusConfidenceEvidence or reason
respect-user-preferences
respects-color-scheme
issueshighDesktop 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-preferences
respects-reduced-motion
passhighUnder prefers-reduced-motion: reduce the probe found the preference active, one matching CSS rule, and zero active animations after load.
respect-user-preferences
respects-contrast
issueshighLighthouse 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-interactions
view-transitions
issueshighThe 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-interactions
scroll-driven-animations
not-applicablemediumNo scroll-linked parallax, reveal, carousel, or scrollytelling interaction is present to implement.
implement-natural-interactions
physical-gestures
passhighCSS/DOM inspection found native scrolling and links, with no custom pointermove/swipe handlers fighting platform behavior.
provide-guided-navigation
scroll-state-aware-chrome
issueshighMobile 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-navigation
anchored-positioning
not-applicablemediumNo tooltip, attached popover, or edge-positioned menu requiring anchor positioning was present in the audited surfaces.
provide-guided-navigation
directs-attention
passhighThe 6,187px mobile page and rendered CSS were inspected for sticky/scroll-state, anchor-positioning, and attention cues.
maximize-content-reduce-noise
no-intrusive-interruptions
passhighThe 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-noise
semantic-dismissible-primitives
issueshighProbe 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-noise
reduced-chrome
passhighThe 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-factor
responsive-no-horizontal-scroll
passhighAt 360x800 layout reported 360px scrollWidth, 360px clientWidth, viewport meta present, and 0px horizontal overflow.
adapt-to-the-form-factor
component-level-responsiveness
issueshighThe 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-factor
input-modality-aware
issueshighThe 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-success
clear-purpose-and-primary-action
issuesmediumThe 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-success
primary-flow-completion
issuesmediumHomepage 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-success
clear-system-state-and-recovery
passhighRaw 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-stable
good-core-web-vitals
issueshighLighthouse 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-stable
visual-stability
passhighLayout observer measured CLS 0.000246 with only two tiny shifts and image cards generally reserve a 16:9 aspect ratio.
be-fast-and-stable
efficient-main-thread
passhighTrace 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-stable
efficient-resource-delivery
issueshighHAR 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-stable
trim-unused-and-duplicate-code
issueshighHAR 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-inclusive
names-roles-labels
issueshighLighthouse 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-inclusive
sufficient-contrast
issueshighLighthouse failed its color-contrast audit and reported links distinguishable only by color.
F014 high: Text and link contrast is below WCAG minimums.
be-inclusive
structure-and-focus
issueshighThe 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-inclusive
legible-text
passhighLighthouse 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-inclusive
zoom-reflow-targets-and-media
issueshighDOM 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-practices
no-console-errors
passhighLighthouse errors-in-console audit scored 1 with no captured console errors.
follow-best-practices
sound-document-and-assets
issueshighImages primitive found two images without width/height; Lighthouse unsized-images also failed partially.
F017 medium: Some images lack intrinsic dimensions.
follow-best-practices
browser-platform-hygiene
issueshighLighthouse 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-discoverable
title-and-description
passhighDiscoverability 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-discoverable
crawlable-and-mobile-friendly
issueshighLighthouse 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-discoverable
canonical-and-indexing-signals
passhighDiscoverability 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-discoverable
structured-and-shareable-metadata
passhighDiscoverability 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-secure
secure-transport-and-headers
issueshighHeaders 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-secure
data-minimisation-and-third-parties
issueshighHAR 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-secure
in-context-permissions-and-modern-auth
issueshighLogin 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-secure
defensive-browser-policies
issueshighHeaders 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-resilient
progressive-enhancement
passhighDiscoverability measured 96% raw/rendered content coverage, no empty SPA mount, and title/H1/description survived without JavaScript.
be-resilient
resilient-runtime-behaviour
issuesmediumDetail 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-resilient
offline-and-installable
not-applicablemediumThis public media catalogue is an MPA, not an installable application; offline media playback is not part of the observed intent.
be-resilient
network-and-http-failure-states
passhighThe origin returns a real HTTP 404 with explanatory copy and a home recovery link rather than a soft-404 or empty shell.
be-internationalised
lang-dir-and-logical-properties
issueshighDOM 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-internationalised
locale-aware-data
not-applicablemediumNo rendered dates, numbers, currencies, durations, or calendar data requires locale formatting on the audited templates.
be-internationalised
time-zone-correctness
not-applicablemediumNo events, schedules, recurring intervals, or time-zone-sensitive values appear on the audited templates.
be-trustworthy
no-dark-patterns
passhighObserved advertising is labelled AD and the age check does not use confirmshaming, forced continuity, preselected consent, or a disguised decline control.
be-trustworthy
humane-error-handling
passmediumReport-form markup marks required controls with aria-required and initial aria-invalid=false, providing a semantic basis for post-interaction validation.
be-trustworthy
trustworthy-input-assistance
issueshighLive forms probe found null autocomplete on username, password, reset-email, and search fields.
F026 medium: Sign-in and search inputs omit autocomplete assistance.
be-trustworthy
safe-commercial-and-account-flows
issueshighThe 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-sustainable
optimised-assets
issueshighImages 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-sustainable
no-wasteful-work
passhighTrace and layout recorded negligible blocking work after load and no repeating long tasks; no autoplay media began behind the age gate.
be-sustainable
third-party-and-media-budget
issueshighHAR 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-ready
structured-agent-capabilities
not-applicablemediumNo declared agent-facing transaction/tool surface exists for this media catalogue; emerging WebMCP exposure is not required.
be-agent-ready
on-device-inference
not-applicablemediumNo summarisation, generation, or inference task is part of the observed core experience, so built-in on-device AI is not applicable.
be-memory-efficient
no-leak-under-repeated-interaction
passmediumAfter 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-efficient
bounded-footprint
passhighA 7.5MB summarized heap and about 131k heap nodes are proportionate to a 42-image WordPress catalogue page.
be-memory-efficient
no-detached-dom-or-unbounded-listeners
passhighNo 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.