Manifest position 428 · CrUX rank bucket 1000
https://xvideo.vlog.br
Coverage complete
Coverage-complete report-only audit of five representative paths. Not covered: duplicate pagination/category instances sharing sampled templates, destructive form submission, authenticated/account/commerce flows (none exposed), and playback beyond initial embed loading.
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 dark-emulated screenshot is pixel-identical in appearance and byte size to the normal desktop capture, and the authored CSS probe found no color-scheme, prefers-color-scheme, or light-dark() usage. F01 medium: The interface does not adapt to the user’s dark colour preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce active, opening the menu produced five running animations lasting 400–600 ms; the stylesheet probe found no reduced-motion query. F02 medium: The mobile navigation animation continues when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | high | The prefers-contrast capture keeps text and controls visible, and Lighthouse reported no colour-contrast failure on the sampled templates. |
implement-natural-interactionsview-transitions | issues | high | The CSS/JS probe across all four templates found no view-transition-name, @view-transition, or startViewTransition usage; the site is an MPA with frequent detail/list navigation. F03 low: Page-to-page navigation swaps abruptly without a View Transition. |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked animation is present: no animation-timeline/scroll-timeline CSS, no inline scroll listener, and no animation was active at rest, so there is no main-thread scroll animation anti-pattern to replace. |
implement-natural-interactionsphysical-gestures | pass | high | The only representative gesture-like interaction is the navigation drawer; it uses click plus CSS animation, not custom pointermove/drag handling, and does not fight native scrolling. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Mobile screenshots show fixed top and bottom chrome while the stylesheet probe found no scroll-state container query, progress indicator, or equivalent state-aware treatment. F04 low: Persistent navigation chrome does not react to scroll state. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or edge-positioned menu requiring anchor positioning appears on the representative templates. |
provide-guided-navigationdirects-attention | pass | high | The persistent bottom navigation labels destinations and visibly marks the current Home item, while each destination begins with a page-specific H1. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No modal, consent wall, or full-viewport interruption appears on load across the four representative templates. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | No modal/dialog/popover/disclosure control is used on sampled paths; the navigation drawer is a persistent navigation pattern with an explicit close control rather than a modal workflow. |
maximize-content-reduce-noisereduced-chrome | pass | high | Primary content occupies most of the viewport; header/category shortcuts and bottom navigation are compact and the page does not add decorative application panels around each content item. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Homepage, detail and contact each report scrollWidth=clientWidth=360, horizontalOverflowPx=0, and a responsive viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The fetched CSS for every sampled template contains no @container or container-type declaration, although the repeated card/navigation components appear in different available widths. F05 low: Reusable cards and navigation adapt only at the page viewport level. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The active focus probe reported outline-style none and no box shadow for the logo, menu close button, search field/button and drawer links. The close button is 32×32 px and the search opener is 35×30 px. F06 high: Keyboard focus is suppressed on prominent controls, and some icon controls are undersized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage clearly identifies the catalogue and exposes content cards; the detail page immediately presents its H1 and embedded player; contact presents labelled fields. |
support-core-task-successprimary-flow-completion | pass | high | A visible homepage card resolves to a successful detail page where the primary embedded player is present in the first viewport; no account wall or detour blocks playback initiation. |
support-core-task-successclear-system-state-and-recovery | issues | high | The form validity probe reported blankValid=true: name, email, subject, and message are all optional, and no role=alert or aria-live region exists. Native email syntax feedback only appears after a non-empty malformed value. F07 medium: The contact form accepts an entirely blank submission and has no accessible error-status region. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse mobile measured LCP 13.6 s, Speed Index 6.2 s, and time to interactive 13.7 s on the primary detail path; the homepage LCP was 4.4 s. F08 high: The representative video detail page has a very slow largest contentful paint. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse measured CLS 0.12 on the detail page, while 31 of 32 images lacked explicit width/height attributes. F09 medium: The detail template shifts noticeably during Lighthouse load. |
be-fast-and-stableefficient-main-thread | pass | high | The trace recorded one 59.52 ms task and 9.52 ms TBT; Lighthouse TBT was 20 ms on home and 110 ms on detail, below the poor threshold despite slow network/LCP. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR found seven parser-inserted VeryHigh-priority stylesheets; Lighthouse failed LCP request discovery and network dependency insights. A font request took about 3.0 s. DOM confirmation showed the stylesheets in head. F10 medium: Critical delivery is delayed by a long render/dependency chain. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The rendered DOM includes cdn.sources.network/init.js twice and the advertising endpoint three times. HAR records 181,475 third-party bytes, including 128,126 bytes from cdn.sources.network. F11 medium: Third-party and duplicated scripts add avoidable work and transfer cost. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed frame-title on homepage/detail and link-name on detail. The detail iframe has no title; probes also found an unnamed menu-close button and one image without alt on each sampled media/listing page. F12 high: The media embed and several controls lack accessible names. |
be-inclusivesufficient-contrast | pass | high | Accessibility scores were 0.96 home, 1.00 contact, and 0.91 detail with no failed colour-contrast audit; essential text remains visible in the contrast capture. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed heading-order on the detail template. Focus probes found outline-style none with no substitute across prominent controls and links. F13 high: Heading order and visible keyboard focus are not dependable. |
be-inclusivelegible-text | pass | high | Body labels and headings remain readable without clipping at 360px, with sensible line wrapping on long Portuguese titles and no horizontal overflow. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The page exposes the player only as a cross-origin iframe with no title or page-level caption/transcript control; the DOM contains no video/audio track. The menu close and search controls measured below 44×44 px. F14 medium: The representative media experience does not expose an equivalent caption track, and some controls miss target-size guidance. |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed errors-in-console on homepage, contact, and detail. HAR also recorded ERR_BLOCKED_BY_RESPONSE for the advertising script and an aborted first-party funcoes.js request. F15 medium: The sampled templates log browser errors. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 40/41 homepage images and 31/32 detail images without width/height, 11–12 oversized images, no modern formats, and broad srcset omissions. F16 medium: Most images omit intrinsic dimensions and several are oversized for their rendered slot. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed inspector-issues on homepage and detail, alongside third-party-cookie and frame accessibility diagnostics. F17 low: Chrome reports inspector/platform issues on primary templates. |
be-discoverabletitle-and-description | issues | high | DOM and Lighthouse both report no meta description on /contato/; Lighthouse SEO for that page is 0.92. The page is intentionally noindex, but a description still improves direct/share context. F18 low: The contact page has no meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable-anchors on the representative detail page; recon also found a javascript:; anchor on the shared shell. F19 medium: Some detail-page anchors are not crawlable. |
be-discoverablecanonical-and-indexing-signals | pass | high | Public home/detail pages return rendered content with canonical URLs and index-friendly robots values; robots.txt advertises a successful sitemap. Contact is intentionally noindex. |
be-discoverablestructured-and-shareable-metadata | issues | high | All probes found zero JSON-LD blocks. The detail page exposes og:type and og:image but no complete Open Graph title/description set in the collected metadata. F20 medium: Rich video pages lack structured data and complete social metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS, nosniff, and Referrer-Policy are present, but CSP is absent and all five first-party cookies lack Secure; one analytics cookie lasts 393 days. F21 high: Security headers and cookie transport protections are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker/HAR evidence records seven third-party origins, 12 requests, and 181,475 third-party bytes, including analytics, advertising, and audience-widget hosts. No consent/privacy control is visible in the initial screenshots. F22 high: The page loads a broad advertising/analytics footprint without an evident privacy control. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No permission request or authentication/account flow exists in the audited public surfaces. |
be-private-and-securedefensive-browser-policies | issues | high | Headers inspection found neither CSP frame-ancestors nor X-Frame-Options, and no Permissions-Policy. HSTS and Referrer-Policy are present. F23 medium: Clickjacking and capability policies are absent. |
be-resilientprogressive-enhancement | pass | high | All four pages have 100% rendered-content word coverage in raw server HTML, are not JS shells, and preserve title/H1 without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | The repeated mobile drawer opens/closes without DOM growth, layouts have no horizontal clipping, and the server-rendered templates remain usable when third-party requests fail. |
be-resilientoffline-and-installable | not-applicable | high | This server-rendered media catalogue is not presented as an installable app, and playback is intrinsically network-dependent; offline installation is not a core journey. |
be-resilientnetwork-and-http-failure-states | pass | high | A nonexistent URL renders a specific Portuguese 404 heading, explanatory copy, navigation, and recovery links instead of a blank shell or infinite spinner. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | The site is deliberately Portuguese/Brazil-only in the sampled content and exposes no locale switch or multi-locale intent. |
be-internationalisedlocale-aware-data | not-applicable | high | No locale-switching or locale-sensitive input/output flow was present beyond static Portuguese text. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduled event, time-zone selection, or user-entered time flow exists on the sampled templates. |
be-trustworthyno-dark-patterns | pass | high | No consent nag, confirmshaming, forced account creation, continuity trap, or disguised primary action was observed in the sampled browse, playback, and contact surfaces. |
be-trustworthyhumane-error-handling | issues | high | Blank contact input passes client validity, required status is not communicated, and there is no live error summary. This makes accidental empty submissions possible and gives assistive technology no explicit recovery state. F24 medium: Contact-form error prevention and recovery are under-specified. |
be-trustworthytrustworthy-input-assistance | issues | high | The named email field reports an empty autocomplete value, while both search inputs explicitly disable autocomplete. F25 low: Contact fields omit useful autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, consent, authentication, or account-management flow is exposed on the audited public routes. |
be-sustainableoptimised-assets | issues | high | All 41 homepage images were JPEG/PNG, 31 lacked srcset, 11 were oversized, and none used AVIF/WebP; the detail sample showed the same pattern. F26 medium: The image pipeline ships legacy, non-responsive assets. |
be-sustainableno-wasteful-work | issues | high | HAR attributes 181,475 bytes to third parties, and DOM evidence shows duplicate init.js plus three advertising loader instances before user interaction. F27 medium: Duplicated and non-essential third-party work runs during initial load. |
be-sustainablethird-party-and-media-budget | issues | high | 12 third-party requests transfer 181,475 bytes, about 21% of the 865,402-byte homepage load, before the user starts media playback. F28 medium: Third-party code consumes a disproportionate share of the initial non-media budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent-facing transaction/tool capability is emerging and no such surface is declared; raw content remains fully server-rendered for crawlers. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, translation, or other inference task is part of the current product experience. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten drawer open/close cycles, heap snapshot node count fell from 128,959 to 128,643; runtime DOM nodes stayed at 479 and used heap fell from 5.1 MB to 3.37 MB. No retained-growth signal was observed. |
be-memory-efficientbounded-footprint | pass | high | The representative page heap was about 7.16 MB self size with 128,959 heap nodes and 479 live DOM elements, proportionate to the listing and not an obvious bloated footprint. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Ten drawer cycles did not increase live DOM count (479 before and after) or heap snapshot node count; no evidence of unbounded listener/DOM accumulation was observed in this interaction window. |
Provenance
Canonical report: results/atomic/reports/0428-xvideo_vlog_br.json
Report SHA-256: 184bee10297df2519c7c282894e7b59b948a1cbad1dfbec350a093053ecd1e09
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/xvideo_vlog_br/2026-07-20T18-19-26-865Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/xvideo_vlog_br/2026-07-20T18-19-26-865Z
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.