Manifest position 418 · CrUX rank bucket 1000
https://okxxx1.com
Coverage complete
Coverage-complete agentic audit of five representative page archetypes plus an HTTP failure state. Account/payment/auth routes were not covered because they are not exposed in the public journey; those contextual checks are explicitly N/A.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-condition capture retains the same fixed dark age panel and blurred light page treatment; the probe reports `color-scheme: normal` and no site colour-scheme adaptation. F01 high: The site does not adapt to the user’s dark colour-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | With `prefers-reduced-motion: reduce`, `document.getAnimations()` returned an empty list; no auto-advance motion was observed. |
respect-user-preferencesrespects-contrast | issues | high | Under `prefers-contrast: more`, the probe reports the focused button outline as `none`; Lighthouse also identifies multiple 2.35–3.16:1 text contrast failures. F02 high: High-contrast preferences do not preserve visible focus and sufficient contrast. |
implement-natural-interactionsview-transitions | issues | medium | The UI probe found no `document.startViewTransition` use; navigation is a conventional multi-page anchor flow and custom overlays swap state without a transition. F03 low: Route and state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface exists on the representative templates, so there is no scroll animation implementation to assess. |
implement-natural-interactionsphysical-gestures | pass | high | Representative pages use native scrolling and links; no custom pointer-driven gesture layer or scroll-snap override was found. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The mobile layout is 22,604px tall while the UI probe found zero sticky elements; no progress, shrinking header, or position-aware chrome was observed. F04 medium: Very long listings provide no scroll-state-aware navigation aid. |
provide-guided-navigationanchored-positioning | issues | medium | The rendered DOM has a custom `.lang_trigger` and four custom fixed layers, but zero popovers/dialogs; the gate and banners are manually layered at high z-index. F05 low: Menus and overlays use custom positioning rather than semantic anchored primitives. |
provide-guided-navigationdirects-attention | pass | high | Visible global navigation, current-page headings and descriptive taxonomy links provide clear destination cues across covered templates. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The first viewport is entirely occupied by the age overlay; DOM/network evidence also shows `popunder1000.js`, multiple ad-provider scripts, a cookie banner and fixed ad layers. F06 high: Popunder/ad code and stacked full-screen UI interrupt content before the user can browse. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | medium | The UI probe found 0 dialogs, 0 popovers and 0 details while the DOM contains custom `age-popup`, `cookiesBanner`, ad layers and `agego-overlay-container`. F07 medium: Dismissible UI is built from custom fixed divs rather than platform primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | Recon found multiple ad iframes and fixed ad layers; the HAR records 116 third-party requests across 15 origins before the user reaches content. F08 high: Promotional chrome competes heavily with the core video content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, layout reports scrollWidth=clientWidth=360 and horizontalOverflowPx=0 with a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The UI probe found zero elements with a non-normal `container-type`; sampled tags/list/video components also report `container-type: normal`. F09 low: Components rely on page-level sizing rather than container-aware adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found the cookie OK and search submit buttons with `outline: none`; many metadata links are only 18–20px high. F10 high: Some controls lack visible keyboard focus and many link targets are too short. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The entry gate clearly explains age requirements and exposes a dominant Verify Age action; underlying pages have descriptive titles/navigation. |
support-core-task-successprimary-flow-completion | pass | medium | The age gate exposes explicit adult/underage branches and the server-rendered catalogue, listings and detail links are present behind it. |
support-core-task-successclear-system-state-and-recovery | issues | medium | The invalid-route probe returns only “Not Found / The requested URL was not found on this server” and exposes zero links. F11 medium: The 404 state has no recovery route or useful next action. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 6.7s, TBT 390ms and performance 0.55; the independent trace measured LCP 3.36s and 196ms blocking time. F12 high: Load performance misses the good Core Web Vitals bar. |
be-fast-and-stablevisual-stability | pass | high | The mobile layout observer recorded CLS 0 with no layout-shift entries over the observation window. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded a 240ms long task and 196ms TBT; Lighthouse reported 3.4s of main-thread work and 390ms TBT. F13 high: Third-party and legacy scripting blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse estimates 1.82s savings from render-blocking requests; HAR identifies parser-inserted synchronous scripts, and Lighthouse flags cache/font/image delivery opportunities. F14 high: Resource delivery has long blocking chains and weak cache/image delivery. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 874KiB of unused JavaScript and 53KiB of legacy JavaScript; the HAR loads 18 scripts. F15 high: The page ships substantial unused and legacy JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse fails image-alt, link-name and frame-title; the direct probe finds an unlabelled search input and untitled iframes. F16 high: Search, images, links and third-party frames have missing accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reports repeated 2.35–2.45:1 blue-on-white failures and a 3.16:1 age-verification label. F17 high: Text and essential controls fail WCAG contrast minimums. |
be-inclusivestructure-and-focus | issues | high | Direct focus testing found buttons with no outline; the video detail has no H1, while its player is the primary content surface. F18 high: Focus visibility and document structure are inconsistent. |
be-inclusivelegible-text | pass | high | Screenshots and computed styles show 16px policy/body text with readable line spacing and no horizontal clipping on the sampled templates. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The direct probe lists many 18–20px-high targets; the representative video has zero `<track>` captions. The viewport allows scaling, but those failures remain. F19 high: Compact targets and captionless video reduce inclusive access. |
follow-best-practicesno-console-errors | pass | high | Lighthouse did not fail its errors-in-console audit in the clean load. |
follow-best-practicessound-document-and-assets | issues | medium | Lighthouse fails image aspect ratio and partially fails unsized images; the images primitive finds 2 missing dimensions. F20 medium: Several assets are unsized or displayed at the wrong aspect ratio. |
follow-best-practicesbrowser-platform-hygiene | issues | medium | Lighthouse reports one deprecated-API warning and fails the Inspector Issues audit. F21 medium: Deprecated APIs and DevTools inspector issues remain. |
be-discoverabletitle-and-description | pass | high | Homepage and video probes show descriptive, route-specific titles and non-empty meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Discoverability found 87% raw/rendered content overlap and a non-shell page; real href links, viewport metadata and permissive robots are present. |
be-discoverablecanonical-and-indexing-signals | issues | medium | Canonical URLs, 200 status and robots.txt are present, but `/sitemap.xml` returns HTTP 200 with Content-Length 0. F22 medium: The sitemap endpoint is empty despite a large public catalogue. |
be-discoverablestructured-and-shareable-metadata | pass | high | The video detail includes JSON-LD plus matching Open Graph title, description, image, URL and duration metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers evidence finds no CSP, HSTS or nosniff; all four observed cookies lack Secure and use SameSite=None. F23 critical: Core security headers are missing and cookies are not Secure. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The load contacts 15 third-party origins with 116 requests; known Google trackers and numerous ad origins run before content access. F24 critical: The pre-consent third-party and tracking footprint is excessive. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt fired on load and no public authentication flow is part of the representative journey; the browser capability alone is not treated as site usage. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence shows no HSTS, Referrer-Policy, Permissions-Policy, CSP or nosniff; only X-Frame-Options is present. F25 high: Browser-enforced privacy and isolation policies are largely absent. |
be-resilientprogressive-enhancement | pass | high | Raw HTML returns 200 with 87% of rendered content tokens, title, H1 and description present without JavaScript. |
be-resilientresilient-runtime-behaviour | issues | medium | Recon shows four high-z-index custom fixed layers and untitled ad frames; several captures show the gate panel before its content finishes, leaving an opaque blocking surface. F26 medium: The startup experience depends on fragile custom overlays and third-party frames. |
be-resilientoffline-and-installable | not-applicable | high | This public streaming catalogue is not presented as an offline-capable app; offline playback/installability is not a reasonable core requirement. |
be-resilientnetwork-and-http-failure-states | issues | medium | The tested 404 has no navigation, search, retry or home link, only the server’s generic error text. F27 medium: HTTP failure states are unbranded and unrecoverable. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The English page declares `lang=en-GB`, language variants are linked, and the LTR reading order is coherent; logical CSS properties are present. |
be-internationalisedlocale-aware-data | not-applicable | high | Representative routes do not expose prices, dates, calendars or locale-sensitive numeric input; language variants are separate hosts. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduled events, appointments or user-entered times appear in the covered journeys. |
be-trustworthyno-dark-patterns | issues | high | Loaded source includes `popunder1000.js` and multiple ad-provider scripts; 116 third-party requests occur while the age wall blocks the core content. F28 high: Popunder advertising and pre-consent tracking undermine predictable, honest interaction. |
be-trustworthyhumane-error-handling | pass | high | The covered search form has no required fields or premature validation, and no blame-oriented validation behaviour was observed. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | The only covered text input is site search; there are no address, payment, sign-in or sign-up fields requiring autofill tokens. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication or account-management flow is exposed in the representative public routes. |
be-sustainableoptimised-assets | issues | high | The images audit finds 98/100 without srcset, 9 oversized and 10 legacy-format images; Lighthouse estimates 441KiB image savings. F29 high: Images are not delivered responsively or in efficient formats. |
be-sustainableno-wasteful-work | issues | high | HAR records 124 requests and 1.39MB in this capture, including 62 fetch/XHR calls; Lighthouse separately observes a 4.6MiB load and 874KiB unused JS. F30 high: The page performs disproportionate background/ad work before core content. |
be-sustainablethird-party-and-media-budget | issues | high | 116 of 124 HAR requests and 1.30MB of 1.39MB transferred are classified third-party; GTM alone transfers 161KB and 15 third-party origins run. F31 critical: Third parties dominate the request and byte budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The site exposes public media browsing, not a declared agent-facing transactional capability; absence of WebMCP is treated as an emerging opportunity, not a failure. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or generative task is part of the covered core journey, so on-device inference is not required. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 language-menu toggles, heap self size differed by about 0.66MB (3.8%) with no evidence of unbounded retained growth; confidence is medium because captures use comparable fresh sessions. |
be-memory-efficientbounded-footprint | pass | high | Heap summaries are about 17.2–17.9MB self size for a media catalogue page, proportionate to the loaded DOM and scripts. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither heap summary exposes a growing Detached* constructor among dominant populations; closures grew modestly in the exercised capture, not enough to establish a leak. |
Provenance
Canonical report: results/atomic/reports/0418-okxxx1_com.json
Report SHA-256: 060a0700add5eb843737c03bc29f8eb26c3f09281b93c94d07379aa886a679d4
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/okxxx1_com/2026-07-20T16-36-04-989Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/okxxx1_com/2026-07-20T16-36-04-989Z
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.