Manifest position 669 · CrUX rank bucket 1000
https://ko.xhname.com
Coverage complete
Coverage-complete agentic audit of five representative public templates plus a 404 recovery state.
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 | pass | high | The rendered surface is dark and remains coherent under emulated dark preference; CSS contains both light and dark media branches. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, eight 2-second continuously running animations remained active and no reduced-motion media rule was found. F01 medium: Continuous animation ignores reduced-motion preference |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors and increased-contrast capture retained readable text, visible controls, and clear boundaries. |
implement-natural-interactionsview-transitions | issues | high | No view-transition CSS/API signal was present; navigation between homepage, category, search and detail surfaces is an abrupt document swap. F02 low: Navigation changes are abrupt |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked parallax, scrollytelling, or reveal interaction was observed on the representative surfaces. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The audited homepage, listing, search, signup and detail paths expose conventional links and controls rather than a gesture-dependent flow. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Long listing pages retain static navigation chrome; no scroll-state query, progress indicator, or shrinking-header signal was found. F03 low: Long pages provide no scroll-state guidance |
provide-guided-navigationanchored-positioning | issues | high | The site exposes dropdown/menu UI but no anchor-name or position-anchor CSS signal was found, so edge-aware anchoring is not implemented declaratively. F04 low: Dropdown positioning is not declaratively anchored |
provide-guided-navigationdirects-attention | issues | high | Route changes and in-page navigation provide no transition or highlight cue showing where attention moved. F02 low: Navigation changes are abrupt |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | A large cookie dialog covers most of the first desktop viewport and obscures the primary content before interaction. F05 medium: Cookie consent obscures the first viewport |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The signup consent surface is a custom DIV with role=dialog rather than a native dialog/popover primitive; dismissal is manually wired. F06 low: Consent/signup overlay uses a custom dialog DIV |
maximize-content-reduce-noisereduced-chrome | pass | high | After consent, content cards occupy the main reading area and persistent chrome is limited to header, navigation and a sidebar appropriate to a catalogue. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x800 viewport the layout reports 1024px content width and 664px horizontal overflow, with desktop sidebar/navigation consuming most of the screen. F07 high: Mobile layout is a 1024px desktop canvas |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | No container-query signal was found and catalogue components retain desktop-sized structure in the narrow capture. F08 medium: Reusable catalogue components do not adapt at component level |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focused search controls compute to outline:none/0 and Lighthouse found insufficient target size/spacing. F09 high: Keyboard focus and touch targeting are inadequate |
support-core-task-successclear-purpose-and-primary-action | pass | high | The homepage has a clear H1, prominent search field, catalogue cards and primary navigation that communicate the service and next actions. |
support-core-task-successprimary-flow-completion | pass | high | Search produced a populated result page, a catalogue card led to a detail page, and signup exposed social and email options. |
support-core-task-successclear-system-state-and-recovery | pass | high | Invalid signup submission produced specific Korean required/password messages, and an unknown URL returned a branded 404 with recovery navigation. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 3.1s, outside the good <=2.5s range; desktop trace LCP was 1.26s, showing a mobile-specific gap. F10 medium: Mobile LCP misses the good threshold |
be-fast-and-stablevisual-stability | pass | high | The mobile layout observer recorded CLS 0 with no shift entries during the capture window. |
be-fast-and-stableefficient-main-thread | pass | high | The trace found two long tasks, 159ms total blocking time and a 167ms longest task; this is bounded and Lighthouse still scored performance 0.91. |
be-fast-and-stableefficient-resource-delivery | issues | high | The load made 141 requests; Lighthouse estimated 118KiB cache-lifetime savings and the HAR found three parser-blocking stylesheets plus uncompressed SVG assets. F11 medium: Resource delivery has avoidable cache and critical-path cost |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 56KiB unused CSS, 26KiB unused JS and 11KiB legacy JavaScript. F12 low: Unused and legacy code ships on first load |
be-inclusivenames-roles-labels | issues | high | Lighthouse found an unnamed button, role misuse on a list item, label/name mismatches, and malformed list semantics; the expanded email field also lacked a label/ARIA name. F13 high: Controls and lists have accessibility-tree defects |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured key age-verification text at 2.15:1 and 1.75:1 against green, below the 4.5:1 requirement, plus low-contrast metadata and indistinct links. F14 high: Important text fails contrast minimums |
be-inclusivestructure-and-focus | issues | high | Search controls show no computed focus outline; Lighthouse also found invalid list structure and an inappropriate button role. F15 high: Focus is invisible and semantic structure is invalid |
be-inclusivelegible-text | pass | high | Body and heading text in desktop, mobile and forced-colors captures is generally readable, consistently aligned, and not clipped vertically. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse found user-scalable=no, undersized/overlapping touch targets, and the video detail exposed no caption track in the inspected player markup. F16 high: Zoom, touch targeting and media alternatives are incomplete |
follow-best-practicesno-console-errors | pass | high | Lighthouse best-practices scored 1.0 and reported no console-error or uncaught-exception failure. |
follow-best-practicessound-document-and-assets | issues | high | The document has a valid doctype and UTF-8 charset, but image inspection found 29 images missing dimensions and 12 oversized images; Lighthouse independently flagged unsized images. F17 medium: Many images lack dimensions or are oversized |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices scored 1.0; no load-time permission prompt or paste-prevention behavior was observed. |
be-discoverabletitle-and-description | pass | high | Homepage, search and video detail each expose descriptive localized titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Links use real href values, viewport metadata is present, robots permits public surfaces, and Lighthouse SEO scored 1.0. |
be-discoverablecanonical-and-indexing-signals | issues | high | Canonical URLs point to the different ko.xhamster2.com host, no hreflang links are exposed despite many localized hosts, and /sitemap.xml returned 404. F18 medium: Localized indexing signals are inconsistent |
be-discoverablestructured-and-shareable-metadata | issues | high | No Open Graph tags or JSON-LD were present on the homepage, and the representative video detail exposed no VideoObject JSON-LD. F19 medium: Video/content pages lack rich and share metadata |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and HSTS are present, but CSP only declares frame-ancestors, nosniff and Referrer-Policy are missing, and two first-party cookies lack Secure while two use SameSite=None. F20 high: Security policy and cookie hardening are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Before consent, 116 of 141 requests and 1.70MB of 1.89MB were classified third-party; an ad request included a persistent stats UID and page keywords in its query. F21 high: Third-party data flows start before consent |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | No permission prompt fired on load, but the account/signup surface offered password and social sign-in with no passkey/WebAuthn option or signal. F22 medium: Account flow lacks a phishing-resistant sign-in option |
be-private-and-securedefensive-browser-policies | issues | high | Clickjacking protection and HSTS exist, but the CSP provides no script/style policy, Referrer-Policy and nosniff are missing, and Permissions-Policy is narrowly configured. F20 high: Security policy and cookie hardening are incomplete |
be-resilientprogressive-enhancement | pass | high | Raw HTML returned 200 with 80% rendered-content coverage and retained title, H1 and description; the page is not a JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | At narrow width, overlays/navigation remain tied to a 1024px desktop layout and are cut off rather than repositioning within the 360px viewport. F23 high: Top-layer/navigation UI is cut off on narrow screens |
be-resilientoffline-and-installable | pass | high | A manifest with start_url/icons/display exists and an active service worker contains fetch, cache and offline/fallback handling. |
be-resilientnetwork-and-http-failure-states | pass | high | A representative unknown route returned an intentional HTTP 404 with a localized branded error view and navigation, rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The root lang=ko is correct, but no hreflang links are exposed and stylesheet inspection counted 599 physical left/right declarations, reducing writing-mode resilience. F24 medium: Localized layout is not writing-mode resilient |
be-internationalisedlocale-aware-data | not-applicable | high | The audited surfaces show catalogue durations/count labels but no currency, calendar date, address or user-entered locale-sensitive value whose formatting could be exercised. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduled event, timestamp entry or cross-zone recurring-time flow appeared in the representative paths. |
be-trustworthyno-dark-patterns | pass | high | Consent offers equally prominent approve/reject actions and signup disclosure states data use and links terms/privacy; third-party content is labelled in the accessibility tree. |
be-trustworthyhumane-error-handling | pass | high | Submitting incomplete signup data produced specific Korean required-field and minimum-password messages rather than a generic failure. |
be-trustworthytrustworthy-input-assistance | issues | high | The email signup field uses autocomplete=off instead of email, while the password correctly uses new-password; this obstructs autofill for a primary account flow. F25 medium: Email signup disables autofill |
be-trustworthysafe-commercial-and-account-flows | issues | high | Signup explains terms and data use, but the relevant account flow offers no phishing-resistant passkey option and relies on passwords/social identity. F22 medium: Account flow lacks a phishing-resistant sign-in option |
be-sustainableoptimised-assets | issues | high | Image inspection found 12 oversized images, 16 legacy-format assets, 29 without dimensions and eight below-fold images not lazy-loaded; Lighthouse estimated 54KiB image savings. F26 medium: Thumbnail delivery wastes bytes |
be-sustainableno-wasteful-work | issues | high | The initial load ships 62 script requests and Lighthouse identifies unused CSS/JS plus legacy code, indicating avoidable transfer and parse work. F27 medium: Initial bundles include avoidable work |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 116 requests and 1.70MB of 1.89MB transferred, including Google identity and ad/media origins before a consent choice. F28 high: Third-party cost dominates the page budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | The public catalogue is crawlable server-rendered content, but recon found no declared agent-facing transaction or productivity capability requiring WebMCP tools. |
be-agent-readyon-device-inference | not-applicable | high | No summarization, generation, translation-assistance or other inference task is exposed by the audited pages. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten language-menu open/close cycles, DOM nodes and animation count stayed exactly 1794 and 8; JS heap increased only ~314KB. Independent heap summaries differed by ~0.9%, not an unbounded signal. |
be-memory-efficientbounded-footprint | pass | high | The loaded catalogue retained about 36MB self-size for 1,794 rendered DOM nodes, proportionate to a media catalogue with 141 network resources. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Repeated interaction did not increase DOM node count or animation count, and no Detached* constructor appeared among the largest heap constructors. |
Provenance
Canonical report: results/atomic/reports/0669-ko_xhname_com.json
Report SHA-256: 653ef5996c8f3167d22cac64787d4b255cb88d71140bddb12dd143e5af7b190a
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/ko_xhname_com/2026-07-22T06-54-41-394Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/ko_xhname_com/2026-07-22T06-54-41-394Z
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.