Manifest position 772 · CrUX rank bucket 1000
https://sexmupxinh.net
Coverage complete
Atomic coverage complete across 58 checks and five representative path archetypes.
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 platform probe found no color-scheme declaration or prefers-color-scheme rule, and default and dark-emulated screenshots are byte-identical (229,260 bytes). F01 medium: The site is hard-coded to one dark palette instead of following the user’s light/dark preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under emulated prefers-reduced-motion: reduce, matchMedia was true and the page exposed no active animations or transition elements. |
respect-user-preferencesrespects-contrast | pass | high | The forced-colors capture retained visible text, controls, current navigation state, and content boundaries. |
implement-natural-interactionsview-transitions | issues | high | CSS/DOM inspection found no view-transition-name, @view-transition, or startViewTransition usage across the listing and detail templates. F02 low: Route changes and state changes swap abruptly without View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | The representative templates contain no parallax, scrollytelling, or scroll-linked animation to implement. No scroll handlers or animation timelines were observed. |
implement-natural-interactionsphysical-gestures | pass | high | Mobile navigation uses native horizontal overflow and content uses normal document scrolling; no custom pointer handlers fight platform gestures. |
provide-guided-navigationscroll-state-aware-chrome | not-applicable | high | The templates have no sticky or affixed chrome whose state needs to react to scrolling. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or floating menu was present in the representative paths. |
provide-guided-navigationdirects-attention | pass | high | Current navigation is visually highlighted, detail pages name the selected item above the player, and search results repeat the query as the section heading. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Initial and 12-second delayed screenshots show no interstitial, modal, or banner obscuring core content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No visible transient overlay or disclosure control was present during representative loads. |
maximize-content-reduce-noisereduced-chrome | pass | high | The listing and detail templates reserve most post-header space for thumbnails or the player, with compact navigation and controls. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360×800 the layout primitive reported scrollWidth=clientWidth=360, zero horizontal overflow, and a valid viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | not-applicable | high | Cards appear in one grid context per viewport and are not reused simultaneously in differently sized containers; viewport adaptation is already evidenced separately. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focused search field computed to outline: none and no box-shadow. The submit control measured 32×28 px and the text input 170×28 px, below the 44×44 CSS-pixel target guidance. F03 high: Keyboard focus is invisible on the search input, and several mobile controls are undersized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The homepage immediately identifies a new-video listing; cards are direct links, search is visible, and detail pages place the player directly beneath the title. |
support-core-task-successprimary-flow-completion | issues | medium | After 5 seconds on the detail page at desktop and mobile sizes, the 16:9 player showed a broken-document icon. The iframe URL was present, but the core playback surface did not render. F04 high: The representative watch flow reaches a broken player instead of playable media. |
support-core-task-successclear-system-state-and-recovery | issues | high | The detail screenshot shows only the browser broken-resource icon; there is no status text, retry action, or accessible error announcement near the player. F05 high: The failed player state has no explanation or recovery action. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP at 3.0 s (score 0.77), above the 2.5 s good threshold, although the local trace measured 1.11 s and TBT remained low. F06 medium: Mobile lab LCP exceeds the good threshold. |
be-fast-and-stablevisual-stability | pass | high | The mobile layout observer recorded CLS 0 with no shifts over five seconds; thumbnail dimensions reserve grid space. |
be-fast-and-stableefficient-main-thread | pass | high | The trace and layout observers found zero long tasks and total blocking time of 0–10.5 ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse identified a Google font stylesheet with about 812 ms wasted time and estimated 643 KiB image-delivery savings; the HAR transferred 1,026,355 bytes over 45 requests. F07 medium: Render-blocking CSS and inefficient image delivery delay useful content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 89 KiB of unused JavaScript: about 70 KiB from Google Tag Manager and 21 KiB from jQuery 3.4.1. F08 low: The page ships avoidable unused JavaScript. |
be-inclusivenames-roles-labels | issues | high | The detail probe found Server controls as clickable list items and rating actions as SPAN elements with tabindex=-1; they are not exposed as operable buttons. F09 medium: Player controls are implemented as non-semantic, non-keyboard controls. |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured 3.45:1 for white text on the active #ff4141 navigation chip, 3.84:1 for pagination text, and 3.59:1 for the footer link, below 4.5:1. F10 medium: Several text/control combinations fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | A direct focus probe confirmed document.activeElement was the search input while its computed outline was none and box-shadow was none. F11 high: Keyboard users cannot see focus on the search field. |
be-inclusivelegible-text | pass | high | Mobile and desktop captures show readable line spacing and stable two-column reflow; card truncation uses ellipsis without clipping the grid. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The probe measured the search submit at 32×28 px and many navigation/text links at 40 px or 32 px tall. The viewport itself permits zoom and reflows without horizontal overflow. F12 medium: Touch targets are too small on the mobile template. |
follow-best-practicesno-console-errors | pass | high | Lighthouse’s errors-in-console audit scored 1 with zero logged browser errors. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse reported displayed ratios around 1.45 versus source ratios around 1.43, while markup declares 320×180 for 500×350 files; the image audit also found 28 oversized images. F13 medium: Thumbnail dimensions/aspect ratios do not match the delivered images. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported three deprecations from the Cloudflare challenge script, including Shared Storage and Protected Audience API warnings. F14 low: A Cloudflare script triggers deprecated API warnings. |
be-discoverabletitle-and-description | pass | high | The probe found a descriptive title and meta description; detail pages also use a content-specific title. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse passed crawlable anchors, link text, robots, and viewport audits; raw content coverage was 100%. |
be-discoverablecanonical-and-indexing-signals | issues | high | The fetched robots.txt contains “Sitemap: https:/sexmupxinh.net/sitemap.xml” with only one slash after the scheme, even though /sitemap.xml itself returns 200. F15 medium: robots.txt declares a malformed Sitemap URL. |
be-discoverablestructured-and-shareable-metadata | issues | high | The detail probe found only BreadcrumbList JSON-LD. The page represents a video and exposes title/description/player information, but no VideoObject entity is provided. F16 medium: Video detail pages omit VideoObject structured data. |
be-private-and-securesecure-transport-and-headers | issues | high | The header audit found no CSP or HSTS. Cookie evidence found both _ga cookies lacked Secure, used SameSite=None, and persisted for 400 days. F17 high: Important transport defenses are missing and analytics cookies are insecure. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker audit found 8 third-party origins, including Google Tag Manager and Google Analytics. The HAR records third-party scripts and the 12-second screenshot shows no privacy choice. F18 high: The page loads a broad tracking/third-party footprint without an evident consent choice. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No authentication surface or permission request exists on the audited public video/listing flows. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence found no clickjacking protection, Referrer-Policy, Permissions-Policy, HSTS, or CSP; only X-Content-Type-Options was present. F19 high: Browser-enforced security policies are largely absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability evidence measured 100% raw/rendered content coverage, no JS shell, and matching title/H1/description without JavaScript. |
be-resilientresilient-runtime-behaviour | issues | medium | Across desktop and mobile detail captures, the player iframe rendered a browser failure icon while the surrounding page stayed live; no fallback player or semantic error state replaced it. F20 high: The embedded player does not degrade robustly when its external runtime fails. |
be-resilientoffline-and-installable | not-applicable | high | This is a public streaming/content MPA rather than an installable app, and playback intrinsically requires network media. |
be-resilientnetwork-and-http-failure-states | issues | high | The broken media surface provides neither a timeout message nor retry. By contrast, the tested 404 and empty-search pages do provide clear messages, isolating the gap to playback. F21 high: Media/network failure is not translated into a useful recovery state. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The document correctly declares lang=vi, but the platform probe found no logical CSS properties; the captured stylesheet repeatedly uses left, right, margin-left, and padding-left. F22 low: The stylesheet is tied to physical left/right directions. |
be-internationalisedlocale-aware-data | not-applicable | high | Audited templates present no dates, numbers, prices, currencies, durations, or calendar values requiring locale formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduled events or time-zone-sensitive values appear on audited paths. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, confirmshaming, forced continuity, disguised control, or subscription upsell appeared on initial or delayed loads; navigation and outbound actions are visually distinct. |
be-trustworthyhumane-error-handling | not-applicable | high | The only form is an optional search field with no invalid/required state. Empty search results are explained clearly. |
be-trustworthytrustworthy-input-assistance | pass | high | The only input is a free-text site search, for which address/payment/sign-in autocomplete tokens do not apply; it accepts text without obstruction. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, consent, authentication, or account-management flow is exposed on audited paths. |
be-sustainableoptimised-assets | issues | high | The image audit found 28 oversized images, 29 images without srcset, 29 legacy-format images, and zero modern-format images. Lighthouse estimated 643 KiB potential image savings. F23 high: Almost every thumbnail is oversized, legacy-format, and non-responsive. |
be-sustainableno-wasteful-work | pass | high | Trace/layout evidence recorded no long tasks, content is server-rendered, and below-fold thumbnails use lazy loading. |
be-sustainablethird-party-and-media-budget | issues | high | The page contacts 8 third-party origins; Lighthouse attributes about 70 KiB unused JavaScript to GTM and about 21 KiB to jQuery, while the page’s core listing can render server-side without them. F24 medium: Third-party scripts consume bytes without proportionate visible value. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared intent indicates agent-facing transactions or tools; this public content catalogue has no action requiring WebMCP exposure. |
be-agent-readyon-device-inference | not-applicable | high | The experience has no summarization or inference task where on-device AI is necessary. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten real server-control toggles, heap size was 6.49 MB versus 6.24 MB baseline (+4.0%) and node count 137,360 versus 134,929 (+1.8%); this bounded one-pass growth does not indicate an unbounded leak. |
be-memory-efficientbounded-footprint | pass | medium | The detail page baseline heap was 6.24 MB across 134,929 nodes, proportionate to a page with an embedded player and scripts. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Baseline/post heap top constructors contained no Detached* population, and the small node increase after ten toggles did not show a growing detached-DOM signature. |
Provenance
Canonical report: results/atomic/reports/0772-sexmupxinh_net.json
Report SHA-256: 52a13c67abba569e14c99299f8c37d87afd3130f6763ab0749f737d640030bc7
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/sexmupxinh_net/2026-07-22T23-04-08-295Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/sexmupxinh_net/2026-07-22T23-04-08-295Z
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.