Manifest position 584 · CrUX rank bucket 1000
https://stripchat.com
Coverage complete
Coverage-complete report-mode audit of five representative public paths. Explicitly excluded: authenticated rooms, payments, private messaging, model broadcasting, account deletion and purchase/cancellation because they require credentials, identity/age steps, money, or interaction with live performers.
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 prefers-color-scheme: dark the page remains usable, but the computed root color-scheme is normal and the loaded stylesheets are dark-only; native controls cannot consistently inherit an explicit scheme. F01 medium: The fixed dark palette is not integrated with the user’s color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe reported two 250 ms SidebarFadeIn animations under prefers-reduced-motion: reduce. F02 medium: Non-essential animation remains active when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse found seven color-contrast failures; the high-contrast capture shows the same authored palette rather than preference-aware system colors. F03 medium: Contrast preferences and baseline contrast are not fully supported. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection found no view-transition rules; the public listing, category and account surfaces swap without a transition contract. F04 low: Route and state changes do not use declarative transition primitives. |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked animation was present, so the page does not use a main-thread scroll-animation anti-pattern. |
implement-natural-interactionsphysical-gestures | pass | high | The audited browse flow uses native scrolling and ordinary links; no custom gesture surface fought platform behavior. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | CSS inspection found no scroll-state, scroll-timeline, or view-transition implementation; the long feed uses static chrome with no progress or post-navigation cue. F05 low: Navigation chrome does not respond to scroll state or direct attention after route changes. |
provide-guided-navigationanchored-positioning | pass | high | No tooltip or transient popover requiring anchored positioning appeared on the audited paths; the menu uses a native dialog element. |
provide-guided-navigationdirects-attention | issues | high | CSS inspection found no scroll-state, scroll-timeline, or view-transition implementation; the long feed uses static chrome with no progress or post-navigation cue. F05 low: Navigation chrome does not respond to scroll state or direct attention after route changes. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show an age banner plus a persistent cookie panel; on mobile the cookie panel overlays the content grid and gives Accept All the dominant action. F06 high: Consent and age-verification chrome consume a large share of the first viewport. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Desktop and mobile screenshots show an age banner plus a persistent cookie panel; on mobile the cookie panel overlays the content grid and gives Accept All the dominant action. F06 high: Consent and age-verification chrome consume a large share of the first viewport. |
maximize-content-reduce-noisereduced-chrome | pass | high | Despite the interruption banners, the underlying browse grid dedicates most remaining viewport area to the primary content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, scrollWidth and clientWidth were both 360 with zero horizontal overflow and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found zero container-query rules while the same card/navigation patterns are reused across desktop and mobile layouts. F07 low: Reusable feed and navigation components rely on viewport CSS rather than container responsiveness. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The active focus probe found outline-style none and no box shadow for the first 20 focusable elements; 18 visible interactive targets were under 24 px in one dimension. F08 high: Keyboard focus and small controls make non-pointer use difficult. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The homepage clearly presents live-category browsing, while signup and login expose explicit account actions. |
support-core-task-successprimary-flow-completion | pass | high | The public browse journey from homepage to a representative category listing completed without an account wall. |
support-core-task-successclear-system-state-and-recovery | issues | high | A request to a representative nonexistent path returned HTTP 406 with an empty body, offering no explanation, home link, search, or retry path. F09 medium: Unknown routes return an empty, nonstandard failure response with no recovery UI. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.7 s, CLS 0.125, and TBT 760 ms; the independent mobile layout observer measured CLS 0.1276. F10 high: Mobile load performance and visual stability miss the Core Web Vitals bar. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse measured LCP 5.7 s, CLS 0.125, and TBT 760 ms; the independent mobile layout observer measured CLS 0.1276. F10 high: Mobile load performance and visual stability miss the Core Web Vitals bar. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured LCP 5.7 s, CLS 0.125, and TBT 760 ms; the independent mobile layout observer measured CLS 0.1276. F10 high: Mobile load performance and visual stability miss the Core Web Vitals bar. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR recorded 158 requests and 2,459,295 transferred bytes, including 1,353,085 bytes of script and 2,296,321 third-party bytes; the largest bootstrap script alone transferred 724,265 bytes. F11 high: The initial page ships a heavy dependency graph dominated by JavaScript and third-party assets. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 1,150 KiB of unused JavaScript and 124 KiB of unused CSS, consistent with the large shared bootstrap observed in the HAR. F12 high: Large amounts of shipped CSS and JavaScript are unused on the audited route. |
be-inclusivenames-roles-labels | issues | high | The DOM probe counted 27 unnamed anchors and three unnamed buttons; Lighthouse independently failed link-name on ten sampled nodes. F13 high: Many links and buttons have no accessible name. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found seven color-contrast failures across the rendered homepage. F30 medium: Text and essential UI include insufficient-contrast color pairs. |
be-inclusivestructure-and-focus | issues | high | The homepage heading sequence starts H2, then H1, then H2, and focused controls computed to outline none with no compensating box shadow. F14 high: Heading order and focus visibility do not provide a dependable keyboard structure. |
be-inclusivelegible-text | issues | high | The About screenshot shows dense 12–14 px gray copy and low-emphasis links on a dark surface; Lighthouse also found seven contrast failures. F15 medium: Secondary and footer copy is cramped and low contrast. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The interaction probe counted 18 visible focusable targets under 24 CSS px in at least one dimension, although the 360 px layout itself did not overflow. F31 high: A set of visible controls is too small for dependable touch and reflow use. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console passed with zero detail items. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found all 36 images missing width/height, 17 oversized, 22 without srcset, and 15 below-fold images without lazy loading. F16 medium: Images omit intrinsic dimensions and many are substantially oversized. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported three deprecation warnings, one BFCache failure reason, and Chrome inspector issues. F17 medium: The page triggers deprecated API, BFCache, and inspector issues. |
be-discoverabletitle-and-description | pass | high | The page has a descriptive title and a matching meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The discoverability run received HTTP 403 for raw HTML, found only 5% rendered-word coverage, no raw title/H1/description, and classified the page as a JS shell; Lighthouse also failed one crawlable-anchor audit. F18 high: Important content is nearly invisible to non-JavaScript crawlers and some anchors are not crawlable. |
be-discoverablecanonical-and-indexing-signals | pass | high | Canonical, hreflang, index/follow robots, robots.txt and multiple sitemaps were present and consistent. |
be-discoverablestructured-and-shareable-metadata | pass | high | Open Graph/Twitter metadata and WebSite/SearchAction JSON-LD describe the visible public site. |
be-private-and-securesecure-transport-and-headers | issues | high | The header audit found no response CSP, nosniff, Referrer-Policy, or Permissions-Policy. The cookie audit found 21 of 26 cookies without Secure; the meta CSP permits unsafe-inline and unsafe-eval. F19 high: Security headers and cookie flags are incomplete despite HTTPS. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The HAR attributed 143 requests and 2,296,321 bytes to third-party origins, while the DOM loaded FingerprintJS2 and the tracker probe observed nine third-party origins before consent was accepted. F20 high: The anonymous landing page has an outsized third-party and fingerprinting footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login probe found username/email and password fields, no navigator.credentials/PublicKeyCredential usage in the page, and no explicit autocomplete tokens. F21 medium: Authentication exposes password-only fields with no passkey path. |
be-private-and-securedefensive-browser-policies | issues | high | The header audit found no response CSP, nosniff, Referrer-Policy, or Permissions-Policy. The cookie audit found 21 of 26 cookies without Secure; the meta CSP permits unsafe-inline and unsafe-eval. F19 high: Security headers and cookie flags are incomplete despite HTTPS. |
be-resilientprogressive-enhancement | issues | high | The no-JavaScript/raw fetch returned 403 and only 5% of rendered words, with no title, H1, or description in raw content; the crawler view shows skeletons rather than useful listings. F22 high: Core public content depends on JavaScript and bot-sensitive rendering. |
be-resilientresilient-runtime-behaviour | pass | high | The observed category, account and menu surfaces rendered without clipped active overlays or broken asynchronous shells in the normal online condition. |
be-resilientoffline-and-installable | pass | high | A standalone web app manifest with 192/512 icons exists and an active scoped service worker is registered. |
be-resilientnetwork-and-http-failure-states | issues | high | The representative unknown route returned 406 with an empty response instead of a resilient not-found page. F23 medium: The observed HTTP failure state is blank rather than recoverable. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The English page declares lang=en and exposes extensive hreflang alternatives, including x-default and more than 20 locales. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative public pages exposed no user-facing dates, currencies, durations, or numeric locale-sensitive data to judge. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event scheduling or displayed time-zone-sensitive data appeared on the audited public paths. |
be-trustworthyno-dark-patterns | issues | high | The cookie panel makes Accept All a bright primary action while Manage is muted and there is no equally direct Reject All action in the first layer. F24 high: Consent choices are visually asymmetric. |
be-trustworthyhumane-error-handling | pass | high | The login form retained context after empty submission and did not erase or navigate away from the form. |
be-trustworthytrustworthy-input-assistance | issues | high | The login probe found empty autocomplete values for username/email and password, and the signup/login controls rely on placeholders instead of persistent visible labels. F25 medium: Login fields omit autofill semantics. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The login path exposes username/email and password fields but no page use of navigator.credentials or PublicKeyCredential; account creation is also CAPTCHA-gated. F32 medium: The account authentication path relies on password entry without a phishing-resistant option. |
be-sustainableoptimised-assets | issues | high | The image audit found 17 oversized images, 22 without responsive sources, 15 legacy-format images, and all 36 without intrinsic dimensions. F26 medium: Image delivery wastes bytes and risks layout work. |
be-sustainableno-wasteful-work | issues | high | Third-party origins account for 2.30 MB of 2.46 MB transferred and 143 of 158 requests, including player, analytics and fingerprinting resources. F27 high: Third-party code dominates the landing-page resource budget before user intent. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party origins account for 2.30 MB of 2.46 MB transferred and 143 of 158 requests, including player, analytics and fingerprinting resources. F27 high: Third-party code dominates the landing-page resource budget before user intent. |
be-agent-readystructured-agent-capabilities | not-applicable | high | This real-time adult entertainment surface has no declared agent-facing task or intent; emerging WebMCP exposure is not assumed appropriate without explicit safety and product scope. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model task is part of the observed core experience, so on-device inference is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After ten bottom/top scroll cycles, the heap summary grew from 53,877,211 to 74,824,271 self-size bytes (+39%), nodes from 1,144,725 to 1,622,430 (+42%), and closures from 104,937 to 160,682. Separate fresh sessions introduce variance, so leak attribution is medium-confidence, but the growth warrants same-session profiling. F28 high: Repeated feed scrolling produced large retained-heap growth. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap summary contains 1,144,725 nodes, 5,112,107 edges, 53.9 MB self size and 104,937 closures before sustained use. F29 medium: The initial discovery page has a large memory footprint for a browsing grid. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary exposed Detached* constructors among the dominant retained populations; no direct detached-DOM evidence was found. |
Provenance
Canonical report: results/atomic/reports/0584-stripchat_com.json
Report SHA-256: f8ea7388708aed44747f8dd99539f367e6eed2489ad300ec384bf9a35e593f13
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/stripchat_com/2026-07-21T18-20-01-992Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/stripchat_com/2026-07-21T18-20-01-992Z
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.