Manifest position 471 · CrUX rank bucket 1000
https://ge.xhamster45.desi
Coverage complete
Coverage-complete audit. The requested host redirected to https://ge.xhamster46.desi/; findings cover the redirected experience.
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 | Light and dark media probes produced different foreground colors (rgb(48,48,48) vs rgb(245,245,245)); the dark-condition screenshot remained usable. |
respect-user-preferencesrespects-reduced-motion | issues | medium | Preference probes found the same eight running 2,000ms animations both normally and under prefers-reduced-motion: reduce. F01 medium: Reduced-motion preference does not reduce active animation |
respect-user-preferencesrespects-contrast | pass | high | The forced-colors/prefers-contrast screenshot retained visible text, controls, borders, and selection affordances. |
implement-natural-interactionsview-transitions | issues | medium | The CSS/platform probe found zero declared view-transition rules, and route changes between listing, category, signup and detail were instant reloads. F02 low: Route and state changes have no transition continuity |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface was present on the representative pages. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No gesture-driven control, swipe flow, carousel, or pull interaction was present to assess. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The long listing keeps a large static header/sidebar; the CSS probe found no scroll-state query/progress treatment and screenshots show no position-aware reduction. F03 low: Long-page chrome does not respond to scroll state |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored popover, or edge-positioned menu was opened on the audited paths. |
provide-guided-navigationdirects-attention | pass | high | Screenshots show a persistent labelled navigation bar, active red underline, clear section heading, and a direct “Zurück zur Homepage” recovery link on the 404 page. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | medium | The first desktop viewport is obscured by a large cookie dialog while a separate age-verification banner and dense chrome remain visible behind it. F04 medium: Load-time consent chrome obscures the primary content |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | medium | DOM probes found zero native dialog/popover/details elements; signup uses a custom role=dialog overlay and the cookie prompt is custom chrome. F05 medium: Custom overlays replace semantic dialog primitives |
maximize-content-reduce-noisereduced-chrome | issues | medium | At 360px, persistent header, age banner and 207px sidebar leave a narrow clipped content column; the first viewport is dominated by chrome. F06 medium: Persistent chrome crowds out mobile content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | medium | Layout at a 360px visual viewport measured scrollWidth 1024 and 664px horizontal overflow; the signup screenshot places the dialog almost entirely off-screen. F07 critical: Narrow viewports retain a 1024px desktop layout |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The CSS probe found zero container queries, while reused listing/signup components visibly fail to adapt to the narrow container. F08 medium: Reused components do not adapt to their containers |
adapt-to-the-form-factorinput-modality-aware | issues | medium | Programmatic focus found outline-style none on key buttons/input, and the target probe found many 16×16 and 20px-high interactive links. F09 high: Keyboard focus and touch targets are inadequate |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home, category, and detail screenshots expose descriptive headings, labelled navigation, and prominent video/category actions. |
support-core-task-successprimary-flow-completion | issues | medium | The guest signup route at 360px renders its custom dialog mostly beyond the right viewport edge, preventing a mobile user from reading or completing the flow. F10 critical: The mobile signup journey is off-screen |
support-core-task-successclear-system-state-and-recovery | pass | high | The intentionally missing route rendered “Seite nicht gefunden”, explained the error, offered support, and linked back to the homepage. |
be-fast-and-stablegood-core-web-vitals | pass | high | Trace measured LCP 1.94s and Lighthouse measured LCP 2.5s, CLS 0, TBT 0ms; layout observation measured CLS 0.0037. |
be-fast-and-stablevisual-stability | pass | high | Layout observers recorded CLS 0 on mobile and 0.0037 on desktop with only two very small shifts. |
be-fast-and-stableefficient-main-thread | issues | medium | Trace/layout captured 2 long tasks, longest 138.6–148ms, and trace total blocking time of 105.2ms after load. F11 medium: Post-load scripting creates long main-thread tasks |
be-fast-and-stableefficient-resource-delivery | issues | medium | HAR recorded 144 requests and 1.68MB transferred, including three parser-inserted VeryHigh-priority stylesheets and a redirect to a different host. F12 medium: Critical resource delivery is request-heavy |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | medium | HAR shipped 61 scripts (1.02MB); Lighthouse found 26KiB unused in assetsLoader.js, and the largest index script alone transferred 400KB. F13 low: Large and partially unused JavaScript is shipped |
be-inclusivenames-roles-labels | pass | high | Lighthouse image-alt and heading/name-related audits passed; the search input and submit button expose explicit accessible labels. |
be-inclusivesufficient-contrast | issues | medium | Lighthouse accessibility scored 0.75 and found age-banner text at 1.75:1/2.15:1 plus view-count text at 3.29:1. F14 high: Important age and metadata text fails contrast |
be-inclusivestructure-and-focus | issues | medium | Focus probe returned outline none and no focus box-shadow on search, login and other primary buttons, so keyboard location is not reliably visible. F15 high: Keyboard focus is not visibly indicated |
be-inclusivelegible-text | pass | high | Across listing, category, detail, and 404 screenshots, primary headings and body copy are readable and consistently aligned; the separate contrast failures are recorded under sufficient-contrast. |
be-inclusivezoom-reflow-targets-and-media | issues | medium | The 360px layout overflows by 664px, signup is off-screen, and many controls measure only 16×16 or 20px high. F16 high: Zoom/reflow and target sizing fail on mobile |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no logged errors or uncaught exceptions. |
follow-best-practicessound-document-and-assets | issues | medium | Image audit found 29/36 images without dimensions, 12 oversized, 8 below-fold images not lazy, 16 legacy-format assets, and one missing alt. F17 medium: Image delivery lacks dimensions and right-sizing |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices score was 1.0 and reported no console/deprecation/prompt-on-load failure in the captured load. |
be-discoverabletitle-and-description | pass | high | Entry and detail probes found descriptive, route-specific titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | The DOM has a viewport meta and real href links; robots.txt permits public content and Lighthouse SEO/crawlable-anchor audits passed. |
be-discoverablecanonical-and-indexing-signals | issues | medium | Localized German pages expose no hreflang links, while canonical URLs point from the .desi mirror to ge.xhamster.com; indexing intent across host/language variants is ambiguous. F18 medium: Localized mirror indexing signals are ambiguous |
be-discoverablestructured-and-shareable-metadata | issues | medium | The video detail has Open Graph tags but no JSON-LD/VideoObject structured data, limiting machine-readable rich-result metadata. F19 low: Video detail pages omit VideoObject structured data |
be-private-and-securesecure-transport-and-headers | issues | medium | HTTPS/HSTS are present, but CSP is only frame-ancestors self and provides no script/style XSS policy; X-Content-Type-Options and Referrer-Policy are absent. F20 high: Security response headers provide weak XSS/referrer protection |
be-private-and-securedata-minimisation-and-third-parties | issues | medium | Network capture contacted 15 third-party origins, including Google Accounts and tsyndicate; the ad request included a persistent xhStatsUid and page keywords. F21 high: Guest load exposes a broad third-party data surface |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No browser permission prompt fired on load; the guest signup surface offered federated/account actions rather than exposing a password-only form. |
be-private-and-securedefensive-browser-policies | issues | medium | Headers lack nosniff and Referrer-Policy; Permissions-Policy only declares UA client-hint fields and does not restrict sensitive capabilities. F22 medium: Defensive browser policies are incomplete |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 89% raw-HTML content coverage, a server-rendered H1/title/description, no empty app mount, and no JS shell. |
be-resilientresilient-runtime-behaviour | issues | medium | The custom signup overlay is mostly outside the 360px viewport and there is no native dialog/anchor-position fallback, demonstrating a runtime overlay failure. F23 critical: Custom overlay positioning is not resilient |
be-resilientoffline-and-installable | pass | high | PWA probe found an active service worker, a complete manifest with icons/start_url/display, and the worker source contains install/fetch/cache/offline handling. |
be-resilientnetwork-and-http-failure-states | pass | high | The tested nonexistent route produced a designed German error page with explanation, support, and homepage recovery rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The rendered German experience declares html lang="de" and maintains coherent left-to-right reading order across representative templates. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative listing, category, detail, signup, and error surfaces showed no dates, currencies, durations, or locale-sensitive numeric input. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event, calendar, recurring interval, or time-zone-sensitive feature was present on the audited paths. |
be-trustworthyno-dark-patterns | pass | high | The cookie prompt presents equally prominent “Annehmen” and “Ablehnen” actions plus settings; the age gate states its legal purpose and expected duration. |
be-trustworthyhumane-error-handling | not-applicable | high | The exposed signup journey used action buttons rather than user-editable account fields, and no other validation flow was present. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, or sign-up text fields requiring autocomplete assistance were exposed in the audited guest flows. |
be-trustworthysafe-commercial-and-account-flows | issues | medium | The account/signup overlay is not usable at 360px because its content and actions are positioned beyond the right viewport edge. F24 critical: Account flow is not safely completable on mobile |
be-sustainableoptimised-assets | issues | medium | Image audit found 12 images rendered at less than half natural dimensions, 16 legacy-format results, and 29 missing intrinsic dimensions. F25 medium: Media assets are not consistently resolution-optimised |
be-sustainableno-wasteful-work | issues | medium | The page loads 144 requests and 61 scripts; 26KiB of one loader is unused and post-load long tasks reach 138.6ms. F26 medium: Background and deferred work are heavier than necessary |
be-sustainablethird-party-and-media-budget | issues | medium | The 1.68MB load includes 1.02MB of scripts and 142 cross-origin requests by request-origin accounting, plus Google/advertising resources before user interaction. F27 medium: Third-party and script weight is disproportionate on entry |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared intent or user-facing need for agent-controlled capabilities was found on this media-browsing site. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, or other inference task was part of the representative user journeys. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll cycles, retained heap grew about 1.11MB (3.0%) with no Detached* constructor population; this bounded delta is consistent with warmed lazy content, not unbounded growth. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap was 36.47MB for a script-rich media listing; the post-interaction snapshot remained 37.59MB, proportionate and bounded during the tested window. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither baseline nor post-scroll heap summary reported Detached* constructors, and the repeated-cycle delta remained bounded. |
Provenance
Canonical report: results/atomic/reports/0471-ge_xhamster45_desi.json
Report SHA-256: 00a86c636010b91517df9264b9218109f0307a70a885e976d6df4a6b6b666505
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/ge_xhamster45_desi/2026-07-21T00-46-23-842Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/ge_xhamster45_desi/2026-07-21T00-46-23-842Z
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.