Manifest position 792 · CrUX rank bucket 1000
https://www.twpornstars.com
Coverage complete
Atomic coverage complete: 58/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 | The dark-condition screenshot is pixel-identical to the light screenshot and html computes color-scheme: normal. F01 medium: No system-driven dark theme |
respect-user-preferencesrespects-reduced-motion | pass | high | The emulated reduced-motion preference matched and the page exposed zero active animations. |
respect-user-preferencesrespects-contrast | pass | medium | The forced-colors screenshot preserves visible text, links, controls, and media boundaries. |
implement-natural-interactionsview-transitions | issues | high | No view-transition CSS or cross-document transition rule is present; home-to-detail navigation swaps instantly. F02 low: Route changes are abrupt |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, reveal, carousel, or other scroll-linked animation exists to implement. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The site exposes links, pagination, and menu/search toggles, but no swipe, drag, snap carousel, or gesture-driven control. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The page is 3,077 px tall on desktop and 5,296 px on mobile, but has no sticky/scroll-state-aware chrome or progress affordance. F03 low: Long pages lack scroll-aware navigation |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or viewport-edge anchored overlay is present. |
provide-guided-navigationdirects-attention | issues | medium | Navigating from the masonry listing to a performer detail uses an abrupt full-page swap with no focus/target cue or directional transition. F04 low: Navigation does not cue where attention moved |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No modal, consent wall, or full-viewport interstitial obscured core content in the captured load states. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Mobile menu and search are custom button/div UI; there are no dialog, popover, or details elements and the buttons expose no expanded state. F05 medium: Custom menu/search controls omit semantic state |
maximize-content-reduce-noisereduced-chrome | issues | high | On mobile, two unrelated dating ads occupy the band between navigation and the Top Pornstars heading, delaying the core listing. F06 medium: Advertising displaces primary mobile content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360 px, scrollWidth equals clientWidth (360), horizontal overflow is 0, and the masonry becomes two columns. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Cards resize across viewports, but the live stylesheet exposes no @container rule or container-type for reusable cards. F07 low: Reusable cards rely only on viewport adaptation |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focus receives a native outline, but pagination links are only 10–16 px wide and many card labels are 18 px high. F08 medium: Many controls are too small for touch |
support-core-task-successclear-purpose-and-primary-action | pass | high | Top Pornstars is a clear H1; Popular Videos, pagination, and performer cards expose the browse task immediately. |
support-core-task-successprimary-flow-completion | pass | high | The listing exposes real performer hrefs and the selected TeannaTrump route returned 200 with profile statistics, posts, and pagination. |
support-core-task-successclear-system-state-and-recovery | pass | high | A missing URL returns HTTP 404 and presents a clear Not Found heading, explanation, and navigation back to site sections. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.46 s (outside good <=2.5 s), CLS 0.069, and TBT 117.5 ms; trace LCP was 2.79 s. F09 medium: Largest content appears too slowly |
be-fast-and-stablevisual-stability | issues | high | Desktop layout observed CLS 0.264, dominated by a 0.263 shift; all 34 images lack width/height. F10 high: Desktop load has a large layout shift |
be-fast-and-stableefficient-main-thread | pass | high | The trace found zero long tasks and 0 ms total blocking time; both layout captures also reported no long tasks. |
be-fast-and-stableefficient-resource-delivery | issues | high | The page transfers 2.01 MB over 68 requests; 30 below-fold images are not lazy and 34 lack responsive sources. F11 medium: Images are eagerly and non-responsively delivered |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Scripts transfer 435 KB; Google Tag Manager alone transfers 282 KB and multiple ad/analytics bundles load before user interaction. F12 medium: Third-party scripts dominate avoidable code cost |
be-inclusivenames-roles-labels | issues | high | Lighthouse found two icon-only buttons without names, an unnamed full-page ad link, and an untitled iframe; search controls also have no labels. F13 high: Core controls and ad embeds lack accessible names |
be-inclusivesufficient-contrast | issues | high | Brand/navigation pink has contrast ratios 2.71:1 and 2.9:1 against light surfaces, below 4.5:1 for normal text. F14 high: Brand navigation text fails contrast |
be-inclusivestructure-and-focus | issues | high | The page has one H1 and visible native focus, but no header, nav, main, or footer landmarks despite substantial navigation and content. F15 medium: Page structure lacks landmarks |
be-inclusivelegible-text | pass | medium | Body and headings remain unclipped and readable in both layouts; content labels wrap without horizontal clipping. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Reflow itself succeeds and user scaling is not disabled, but pagination and many labels are materially below recommended target dimensions. F16 medium: Small targets weaken zoom/reflow usability |
follow-best-practicesno-console-errors | issues | high | A Twitter image request logs a 404 console error; the HAR also records one 404 resource. F17 low: A failed image logs a console error |
follow-best-practicessound-document-and-assets | issues | high | Doctype and UTF-8 are valid, but all 34 images omit explicit dimensions and 15 are over 2x their displayed width. F18 high: Image markup omits intrinsic dimensions |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports three deprecated API warnings plus DevTools inspector issues. F19 medium: Deprecated and inspector issues remain |
be-discoverabletitle-and-description | pass | high | Home and performer detail pages have descriptive titles and a meta description, both present in raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Viewport metadata exists and robots permits search, but the language control uses javascript:void(0), four anchors lack href, and many image links have no discernible text. F20 medium: Some navigation is not crawlable or named |
be-discoverablecanonical-and-indexing-signals | issues | high | Pages return 200 and robots allows search, but home/detail expose no canonical or hreflang and /sitemap.xml returns 404. F21 medium: Canonical discovery signals are incomplete |
be-discoverablestructured-and-shareable-metadata | issues | high | The home listing and performer detail expose neither JSON-LD nor Open Graph metadata despite representing crawlable profile/media entities. F22 medium: Profile pages lack rich/share metadata |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used and no sensitive secrets were found, but CSP/HSTS/nosniff are missing and three first-party analytics/ad cookies are not Secure. F23 high: Transport defenses and cookie flags are weak |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The load contacts 11 third-party origins; 46/68 requests and 1.72 MB are third-party, with Google Analytics/GTM and ad-tech domains active before interaction. F24 high: Initial load has a broad tracking footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No geolocation/notification permission prompt fired on load, and no authentication flow exists on the covered public browsing templates. |
be-private-and-securedefensive-browser-policies | issues | high | CSP/frame-ancestors or X-Frame-Options, HSTS, Referrer-Policy, and Permissions-Policy are all absent. F25 high: Browser-enforced policy headers are absent |
be-resilientprogressive-enhancement | pass | high | Raw HTML contains 100% of rendered home content words and 99% on the performer detail; neither page is a JS shell. |
be-resilientresilient-runtime-behaviour | pass | medium | Ten open/close menu cycles left the DOM at 510 nodes, and listing/detail/error routes remained usable. |
be-resilientoffline-and-installable | not-applicable | high | This public media directory is content-oriented rather than an installed application, and exposes no manifest. |
be-resilientnetwork-and-http-failure-states | pass | high | The server returns a real 404 and renders an explanatory recovery page with links to core sections. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The English document has an empty html lang and dir even though it links an Español variant. F26 high: Document language is undeclared |
be-internationalisedlocale-aware-data | issues | medium | Profile dates/durations are rendered as terse fixed strings such as 11y, 4y1m, 6y5m rather than locale-aware human-readable durations. F27 low: Relative durations are not locale-aware |
be-internationalisedtime-zone-correctness | not-applicable | high | Covered templates show relative post ages but no scheduled events, exact local times, or cross-zone coordination. |
be-trustworthyno-dark-patterns | issues | high | Dating ads appear directly under Popular Videos before core content, while Lighthouse found an unnamed viewport-sized outbound ad link, making sponsorship and destination unclear. F28 high: Advertising destination and sponsorship are unclear |
be-trustworthyhumane-error-handling | not-applicable | medium | The only covered form is a search control with no required multi-field validation or user-data submission flow. |
be-trustworthytrustworthy-input-assistance | not-applicable | medium | There are no address, payment, sign-in, sign-up, or other personal-data fields requiring autofill tokens. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, consent, authentication, or account-management journey is exposed in the covered public browsing flow. |
be-sustainableoptimised-assets | issues | high | All 34 images lack srcset, 15 are oversized, 30 below-fold images are eager, and images transfer 1.35 MB. F29 high: Media assets are not proportionately optimised |
be-sustainableno-wasteful-work | issues | high | Ad and analytics requests begin on load across 11 third-party origins despite no user interaction; the main thread is light, but network background work is not. F30 medium: Background network work starts without user value |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 1.72 MB and 46 requests, including 282 KB from GTM and 1.35 MB of third-party Twitter imagery. F31 high: Third-party budget is disproportionate |
be-agent-readystructured-agent-capabilities | not-applicable | high | Robots explicitly blocks major AI agents and this read-only directory declares no agentic actions or tools. |
be-agent-readyon-device-inference | not-applicable | high | The site provides simple server-rendered browsing/search and has no summarisation or language-model workflow that needs on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten cycles, heap nodes decreased 193,264→192,927, self size decreased 9,756,514→9,735,972 bytes, DOM stayed at 510 nodes, and used heap fell. |
be-memory-efficientbounded-footprint | pass | high | The page uses about 9.76 MB heap self size and 510 live DOM elements, proportionate to a 34-card media listing. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary reports Detached constructors, totals decreased after repeated toggles, and live DOM node count remained 510. |
Provenance
Canonical report: results/atomic/reports/0792-www_twpornstars_com.json
Report SHA-256: 0cb5d6396b0a4ab7d0852f0e780deff7928b1b401fd106f1aae76d0befb43bca
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_twpornstars_com/2026-07-23T01-40-38-430Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_twpornstars_com/2026-07-23T01-40-38-430Z
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.