Manifest position 747 · CrUX rank bucket 1000
https://it.xvideos.com
Coverage complete
Coverage complete: 58/58 checks judged. 34 findings (14 high, 14 medium, 6 low).
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 probe still reported colorScheme “normal” and a white rgb(255,255,255) body; the dark screenshot is visually unchanged. F01 medium: The site ignores the user’s dark-colour preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | No active animations were reported with prefers-reduced-motion: reduce; the only observed gate pulse is short and interaction-triggered. |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast screenshot retained readable text and visible controls; Lighthouse found one separate ordinary-contrast failure. |
implement-natural-interactionsview-transitions | issues | medium | DOM/CSS inspection across home, category and detail found no view-transition declarations; the entry recording shows direct overlay swaps. F02 low: Navigation and state changes use abrupt full-document swaps. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, scroll-linked reveal or carousel animation exists on the representative templates, so there is no scroll-driven effect to implement. |
implement-natural-interactionsphysical-gestures | pass | high | Listings use native scrolling and links; no custom pointermove gesture system or scroll fighting was found. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The homepage has a long/infinite feed, but DOM/CSS inspection found no scroll-state query, progress marker, or shrinking-header behaviour. F03 low: The long feed has no scroll-state-aware navigation or progress affordance. |
provide-guided-navigationanchored-positioning | issues | medium | The navigation exposes menus, but CSS inspection found no anchor-name, position-anchor, or position-try usage. F04 low: Dropdown/menu positioning is custom rather than anchored to its trigger. |
provide-guided-navigationdirects-attention | pass | high | Category pagination marks the current page and uses clear Previous/Next navigation; the 404 provides a direct home recovery link. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The first-load screenshot shows the age gate; after accepting it, the recording reveals a second cookie wall that obscures the whole page. F05 medium: Two consecutive full-viewport gates interrupt entry before content can be used. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Across five DOM captures, the gates expose no <dialog>, role=dialog, or popover; the recon found zero semantic dialogs. F06 high: Blocking overlays are generic divs without dialog semantics. |
maximize-content-reduce-noisereduced-chrome | pass | high | After consent, the listing dedicates most of the viewport to the content grid with a compact two-row header. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360×800, home, detail and account all reported zero horizontal overflow; viewport metadata is present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | DOM/CSS inspection found no @container rules even though video cards are reused in desktop grids and narrow layouts. F07 low: Reusable cards rely on viewport layouts rather than container-aware adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The active focus probe found header buttons and search controls at outline:none with no box-shadow; multiple links were only 15–16px high. F08 high: Several controls lose visible keyboard focus and text links have very small hit areas. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first content view clearly presents searchable video cards; category and account pages have descriptive task labels. |
support-core-task-successprimary-flow-completion | pass | high | The representative home→category/search→detail surfaces loaded successfully; age confirmation and cookie rejection completed without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | Empty form submission produced a localized error summary and the deliberate missing route showed a clear “page not found” message with a home link. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured FCP 4.1s and LCP 5.4s; the independent trace measured LCP 4.41s. CLS remained near zero. F09 high: Homepage loading is slow enough to miss the good LCP range. |
be-fast-and-stablevisual-stability | pass | high | CLS was 0 on mobile home/account and 0.0011 on detail, with no meaningful visual shift. |
be-fast-and-stableefficient-main-thread | pass | high | Trace TBT was 1.57ms on home and 0.41ms on detail, with only one ~51ms long task in each capture. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR recorded 124 requests/2.89MB, parser-inserted high-priority CSS/JS, and many images without useful cache headers; Lighthouse estimated 3.0s render-blocking savings and 1.44MB cache savings. F10 high: Render-blocking and cache policy delay first content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 580KiB unused JavaScript and 206KiB unused CSS; HAR shows a 517KB default.js plus HLS code on the listing page. F11 high: Large amounts of unused CSS and JavaScript ship on the homepage. |
be-inclusivenames-roles-labels | issues | high | The images primitive found 98 of 100 images without alt; Lighthouse found 100 missing image alternatives, two unnamed buttons and one unnamed link. F12 high: Many images and controls have no accessible name or text alternative. |
be-inclusivesufficient-contrast | issues | high | Lighthouse’s colour-contrast audit reported a failing node on both the homepage and account surface. F13 medium: Some text fails minimum colour contrast. |
be-inclusivestructure-and-focus | issues | high | All five representative DOM captures contain zero h1 elements; the focus probe found focused header/search buttons with outline:none and no replacement. F14 high: The main templates lack heading structure and several buttons suppress focus indication. |
be-inclusivelegible-text | pass | high | Desktop and mobile captures show readable body sizes, clear spacing and no text clipping on the representative category/account surfaces. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse failed meta-viewport because user scaling is restricted; inspection of the representative player found no caption tracks in the tested state. F15 high: The viewport restricts zoom and video alternatives are not evident. |
follow-best-practicesno-console-errors | issues | high | Lighthouse reported one errors-in-console item on /account/create while the homepage had none. F16 low: The account page emits a console error during load. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found 99 of 100 images without width/height; Lighthouse reported 101 unsized images. F17 high: Nearly all thumbnail images omit intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported one deprecated-API warning on both audited templates and legacy JavaScript with an estimated 51KiB saving. F18 medium: Deprecated browser API usage remains in production code. |
be-discoverabletitle-and-description | issues | high | The account/create page is titled “Account login” despite also being registration, and Lighthouse SEO was 0.58 there. F19 medium: Metadata is generic or mismatched on some important templates. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse reported one non-crawlable anchor and one non-descriptive link on the homepage. F20 low: A small set of navigation links is not crawlable or descriptively named. |
be-discoverablecanonical-and-indexing-signals | issues | high | All five DOM captures lacked rel=canonical, although robots.txt permits public content, hreflang exists and sitemap.xml is present. F21 medium: Representative public pages omit canonical URLs. |
be-discoverablestructured-and-shareable-metadata | issues | high | Recon and detail DOM inspection found no JSON-LD, including no VideoObject, despite the page representing a rich video entity. F22 medium: The video detail page lacks structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers inspection found no HSTS or nosniff and a CSP containing unsafe-inline and unsafe-eval; the session cookie is Secure/HttpOnly but SameSite=None. F23 high: Transport is HTTPS, but important response defenses are absent or weakened. |
be-private-and-securedata-minimisation-and-third-parties | pass | high | After rejecting optional cookies, tracker capture found no known tracker domains; third-party-labelled traffic was limited to site CDN subdomains, and secrets scan found no exposed secret. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The account DOM exposes email/password forms but no WebAuthn/passkey signal; no permission prompt fired on load. F24 medium: Authentication is password-only with no phishing-resistant option. |
be-private-and-securedefensive-browser-policies | issues | high | Headers inspection found no HSTS, Permissions-Policy or nosniff, a permissive no-referrer-when-downgrade policy, and no Trusted Types requirement; X-Frame-Options is present. F25 high: The browser-policy baseline is incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 98% raw-HTML content coverage, no empty app mount, and matching browser/crawler content. |
be-resilientresilient-runtime-behaviour | pass | high | The required gates remained centred and usable at 360px, and category/account layouts showed no clipping or horizontal overflow. |
be-resilientoffline-and-installable | not-applicable | high | This is a public server-rendered streaming/content MPA whose core watch task intrinsically requires the network; an offline app experience is not part of the observed product intent. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberate unknown URL rendered a localized error heading and an actionable return-home link rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The homepage/category/search/account declare lang=it, but the representative Italian detail page declares lang=en-GB. F26 medium: The Italian video detail page declares the wrong document language. |
be-internationalisedlocale-aware-data | pass | high | The Italian surfaces localise interface copy and displayed counts/durations with Italian conventions (for example decimal commas and “min.”). |
be-internationalisedtime-zone-correctness | not-applicable | high | No events, appointments, absolute timestamps, recurring schedules or other time-zone-sensitive data appeared on the representative paths. |
be-trustworthyno-dark-patterns | issues | high | After the mandatory age step, “Accetta tutti i cookie” is a large red button while “Rifiuta tutti i cookie” is a small underlined text control below it. F27 high: Cookie choice is visually asymmetric. |
be-trustworthyhumane-error-handling | issues | high | Empty submission produced a localized error summary, but the probe found no role=alert and no aria-invalid on invalid controls. F28 medium: Validation errors are visible but not programmatically announced or attached to invalid fields. |
be-trustworthytrustworthy-input-assistance | issues | high | Email/current-password and sign-up email/password fields returned empty autocomplete values; only new-password fields were annotated. F29 medium: Sign-in and sign-up fields omit standard autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The account screenshot gives half the viewport to “Registrazione Premium” benefits and a join CTA, but no price, renewal or cancellation terms are visible. F30 medium: The account surface promotes premium membership without pricing or commitment details in the decision context. |
be-sustainableoptimised-assets | issues | high | Images audit found 99 legacy-format images, 100 without srcset, 90 below-fold images without lazy loading and three oversized assets. F31 high: Thumbnail delivery is not resource-efficient. |
be-sustainableno-wasteful-work | issues | medium | After ten bottom/top feed traversals, DOM nodes grew from 2,870 to 19,432 and measured JS heap from 10.1MB to 13.8MB. F32 medium: Repeated feed traversal retains a rapidly growing DOM and heap. |
be-sustainablethird-party-and-media-budget | issues | high | HAR recorded 2.89MB and 124 requests, including 106 images, 760KB script and HLS code on the feed; 116 requests came from CDN subdomains. F33 high: The listing page pays a large image and player-code budget before the user chooses media. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared intent asks this public media catalogue to expose transactional agent tools; emerging WebMCP capability is therefore an opportunity, not an audit requirement. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, writing or inference task was present where built-in on-device AI would materially improve the observed core browse/watch journey. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | Baseline-to-post heap summaries grew from 386,850 to 495,584 nodes and 27.9MB to 36.2MB self size; in-page DOM count rose 2,870→19,432. This indicates unbounded feed retention, though no Detached* constructor was observed. F34 medium: The long feed grows substantially under repeated traversal without releasing prior content. |
be-memory-efficientbounded-footprint | pass | high | The post-load baseline heap was 27.9MB self size for a media-rich 100-thumbnail page, proportionate before repeated feed expansion. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither heap summary listed a Detached* constructor, and the dedicated probe found no detached marker; the separate retained-feed growth is reported under repeated interaction. |
Provenance
Canonical report: results/atomic/reports/0747-it_xvideos_com.json
Report SHA-256: 0522fad4a4af338246baf4c0e9f20d24ac645310ed9901c49601d58076a7e9cc
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/it_xvideos_com/2026-07-22T20-09-04-317Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/it_xvideos_com/2026-07-22T20-09-04-317Z
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.