Manifest position 439 · CrUX rank bucket 1000
https://www.xpaja.net
Coverage complete
Coverage-complete representative audit of seven paths/conditions. Not covered: authenticated profile management, upload completion, payment/subscription flows, and destructive account actions because they require credentials or irreversible user data.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Dark and light emulation both rendered the same dark theme, and the CSS probe found no color-scheme or prefers-color-scheme rule. F01 medium: Theme follows a site toggle, not the system color preference |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce, getAnimations() still returned two running 3000 ms repeating animations; only Font Awesome utility animation classes had a reduction rule. F02 medium: Continuous motion remains under reduced-motion |
respect-user-preferencesrespects-contrast | issues | high | The CSS preference probe found no prefers-contrast or forced-colors rules, while Lighthouse found footer contrast below 4.5:1. F03 medium: High-contrast preferences are not handled |
implement-natural-interactionsview-transitions | issues | high | The CSS scan found no View Transition or scroll animation timelines, while the HAR loaded Owl Carousel and Hammer.js for interaction behavior. F04 medium: Navigation and carousel state use legacy abrupt/custom behavior |
implement-natural-interactionsscroll-driven-animations | issues | high | The CSS scan found no View Transition or scroll animation timelines, while the HAR loaded Owl Carousel and Hammer.js for interaction behavior. F04 medium: Navigation and carousel state use legacy abrupt/custom behavior |
implement-natural-interactionsphysical-gestures | issues | high | The CSS scan found no View Transition or scroll animation timelines, while the HAR loaded Owl Carousel and Hammer.js for interaction behavior. F04 medium: Navigation and carousel state use legacy abrupt/custom behavior |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The runtime probe found multiple fixed layers and Bootstrap role-dialog UI, but no scroll-state container query, anchor positioning, or position-try CSS. F05 medium: Fixed navigation and overlays are not state or anchor aware |
provide-guided-navigationanchored-positioning | issues | high | The runtime probe found multiple fixed layers and Bootstrap role-dialog UI, but no scroll-state container query, anchor positioning, or position-try CSS. F05 medium: Fixed navigation and overlays are not state or anchor aware |
provide-guided-navigationdirects-attention | pass | high | Category/detail navigation uses descriptive headings and active visual grouping; the screenshots show clear destination context. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a load-time banner plus a fixed third-party video ad and “VIEW MORE” control covering recommendation cards and video detail content. F06 high: Advertising obscures primary content |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM contained role=dialog containers but zero native dialog, popover, or details elements; Lighthouse also found the registration dialog had no accessible name. F07 medium: Dialogs and overlays use ad-hoc Bootstrap containers |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop and mobile screenshots show a load-time banner plus a fixed third-party video ad and “VIEW MORE” control covering recommendation cards and video detail content. F06 high: Advertising obscures primary content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All tested mobile layouts reported scrollWidth=clientWidth=360 with zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Mobile layouts avoid overflow, but the stylesheet scan found no @container/container-type rules, leaving reusable card and navigation components tied to global breakpoints. F08 low: Responsive templates do not use component-level adaptation |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focused links and controls computed to outline-style none with no box shadow; Lighthouse found a 20×20 signup close control, and the viewport sets maximum-scale=1. F09 high: Keyboard focus, touch size, and zoom support are incomplete |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport identifies the content feed and prominent video cards; the detail page places playback first. |
support-core-task-successprimary-flow-completion | pass | high | A user can move from the homepage/category listing to a detail page and reach playback without an account wall. |
support-core-task-successclear-system-state-and-recovery | issues | high | Empty registration submission produced a generic terms/age message, but fields had no required, aria-invalid, or aria-describedby state and no visible role=alert was found. F10 high: Registration errors are not programmatically actionable |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured homepage LCP 3.5 s and signup LCP 6.4 s; the trace measured homepage LCP 3.21 s. TBT stayed low, so load/resource discovery is the main bottleneck. F11 high: Primary pages miss the good LCP range |
be-fast-and-stablevisual-stability | pass | high | Observed CLS was 0.018 mobile home, 0.068 desktop home, 0.00002 detail, and 0.033 category, all in the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Trace TBT was 38.66 ms with one 88.66 ms task; Lighthouse TBT was 50 ms home and 70 ms signup. |
be-fast-and-stableefficient-resource-delivery | issues | high | The image audit found 93/94 images without dimensions, 64 below-fold images not lazy-loaded, 25 oversized images, 61 without srcset, and 93 legacy-format assets. Lighthouse estimated 1,127 KiB image savings and 1,300 ms render-blocking savings. F12 high: Image and resource delivery is wasteful |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 62 KiB unused CSS and 69 KiB unused JavaScript; the HAR loaded legacy carousel, gesture, ad, analytics, and timezone scripts on the homepage. F13 medium: Unused CSS and JavaScript ship on first load |
be-inclusivenames-roles-labels | issues | high | Lighthouse found unnamed menu/search buttons and links on the homepage, unnamed signup controls/selects, and an unnamed registration dialog. F14 high: Core controls lack accessible names |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured #e4006a on #080808 at 4.29:1 for 14 px footer text, below WCAG AA 4.5:1. F15 medium: Some footer text fails minimum contrast |
be-inclusivestructure-and-focus | issues | high | Focused links and controls computed to outline-style none with no box shadow; Lighthouse found a 20×20 signup close control, and the viewport sets maximum-scale=1. Lighthouse found unnamed menu/search buttons and links on the homepage, unnamed signup controls/selects, and an unnamed registration dialog. F09 high: Keyboard focus, touch size, and zoom support are incomplete F14 high: Core controls lack accessible names |
be-inclusivelegible-text | pass | high | Core headings and card labels remain readable and reflow into the 360 px layout without horizontal clipping. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport uses maximum-scale=1; the detail probe found no caption tracks on either video, and Lighthouse found an undersized signup control. F16 high: Zoom is restricted and video equivalents are absent |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit scored 1 on both homepage and signup. |
follow-best-practicessound-document-and-assets | issues | high | Doctype and UTF-8 passed, but Lighthouse found incorrect image aspect ratios and unsized images; its source-map detail also recorded a 404 map reference. F17 low: Document asset hygiene has avoidable defects |
follow-best-practicesbrowser-platform-hygiene | issues | high | Doctype and UTF-8 passed, but Lighthouse found incorrect image aspect ratios and unsized images; its source-map detail also recorded a 404 map reference. F17 low: Document asset hygiene has avoidable defects |
be-discoverabletitle-and-description | pass | high | Homepage, category, detail, and signup probes all returned descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse SEO scored 1.0; real href links, viewport metadata, robots.txt, and a sitemap index were present. |
be-discoverablecanonical-and-indexing-signals | issues | high | The English switch set lang=en but retained a Spanish title and exposed only hreflang=x-default. The video page used og:type=website and WebSite JSON-LD rather than VideoObject, and had no Twitter metadata. F18 medium: Localized and rich-page metadata is incomplete |
be-discoverablestructured-and-shareable-metadata | issues | high | The English switch set lang=en but retained a Spanish title and exposed only hreflang=x-default. The video page used og:type=website and WebSite JSON-LD rather than VideoObject, and had no Twitter metadata. F18 medium: Localized and rich-page metadata is incomplete |
be-private-and-securesecure-transport-and-headers | issues | high | The site is HTTPS, but CSP and HSTS are absent. PHPSESSID is neither Secure nor HttpOnly and reports SameSite=None; analytics cookies are also insecure and long-lived. F19 critical: Session transport defenses are unsafe |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe found 13 third-party origins including Google Analytics; the HAR attributed 19 requests and 943,964 bytes to third parties, including 691 KB autoplay ad media. No consent choice was visible in captured entry states. F20 high: Heavy tracking and ad activity starts without visible consent |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | No permission prompt fired on load, but login/signup are password-only, with no WebAuthn/passkey surface and no autocomplete tokens on email/password fields. F21 medium: Authentication lacks modern assistance |
be-private-and-securedefensive-browser-policies | issues | high | The site is HTTPS, but CSP and HSTS are absent. PHPSESSID is neither Secure nor HttpOnly and reports SameSite=None; analytics cookies are also insecure and long-lived. F19 critical: Session transport defenses are unsafe |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 99% raw-HTML content coverage on both homepage and detail, with title, h1, and description present without JavaScript. |
be-resilientresilient-runtime-behaviour | issues | high | Across mobile templates, a fixed autoplay ad overlaps page content and controls instead of remaining in a bounded, collision-aware region. F22 medium: A fixed third-party layer masks controls and content |
be-resilientoffline-and-installable | not-applicable | high | This public content site is not presented as an installable application; no manifest or service-worker registration exists, so app install/offline behavior is contextual and not required. |
be-resilientnetwork-and-http-failure-states | pass | high | An unknown URL returned HTTP 404 and rendered a useful explanation plus links to recent content. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The language switch changed html lang from es to en and translated primary navigation/headings; no RTL locale is offered. |
be-internationalisedlocale-aware-data | issues | high | After switching to lang=en, the document title remained Spanish and partner/navigation content was mixed-language; the video detail displayed an English-style date on the Spanish route. F23 medium: The English locale remains partially Spanish and date formatting is not localized |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling, recurring event, or timezone-sensitive transaction was present on the representative pages. |
be-trustworthyno-dark-patterns | issues | high | A fixed third-party autoplay panel with a large yellow “VIEW MORE” CTA covers site content, while tracking/advertising starts without a visible consent choice. F24 high: Promotional UI is visually coercive and unlabelled |
be-trustworthyhumane-error-handling | issues | high | Empty registration submission produced a generic terms/age message, but fields had no required, aria-invalid, or aria-describedby state and no visible role=alert was found. F10 high: Registration errors are not programmatically actionable |
be-trustworthytrustworthy-input-assistance | issues | high | Signup username/password/email fields and login email/password fields have no autocomplete tokens; signup controls are not native-required and the action is a type=button. F25 medium: Account fields do not support autofill or native validation |
be-trustworthysafe-commercial-and-account-flows | issues | high | No permission prompt fired on load, but login/signup are password-only, with no WebAuthn/passkey surface and no autocomplete tokens on email/password fields. Signup username/password/email fields and login email/password fields have no autocomplete tokens; signup controls are not native-required and the action is a type=button. F21 medium: Authentication lacks modern assistance F25 medium: Account fields do not support autofill or native validation |
be-sustainableoptimised-assets | issues | high | The homepage transferred 1.85 MB in the HAR, 944 KB from third parties; 93 images use legacy formats and a 341 KB animated GIF plus 691 KB ad video load immediately. Lighthouse observed 7.1 MiB in its run. F26 high: Media and third-party bytes are disproportionate |
be-sustainableno-wasteful-work | issues | high | The tracker probe found 13 third-party origins including Google Analytics; the HAR attributed 19 requests and 943,964 bytes to third parties, including 691 KB autoplay ad media. No consent choice was visible in captured entry states. The homepage transferred 1.85 MB in the HAR, 944 KB from third parties; 93 images use legacy formats and a 341 KB animated GIF plus 691 KB ad video load immediately. Lighthouse observed 7.1 MiB in its run. F20 high: Heavy tracking and ad activity starts without visible consent F26 high: Media and third-party bytes are disproportionate |
be-sustainablethird-party-and-media-budget | issues | high | The tracker probe found 13 third-party origins including Google Analytics; the HAR attributed 19 requests and 943,964 bytes to third parties, including 691 KB autoplay ad media. No consent choice was visible in captured entry states. The homepage transferred 1.85 MB in the HAR, 944 KB from third parties; 93 images use legacy formats and a 341 KB animated GIF plus 691 KB ad video load immediately. Lighthouse observed 7.1 MiB in its run. F20 high: Heavy tracking and ad activity starts without visible consent F26 high: Media and third-party bytes are disproportionate |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing capability or transactional agent surface exists; this emerging check is contextual. |
be-agent-readyon-device-inference | not-applicable | high | No summarization or inference use case is exposed; on-device inference would not improve the observed core watch/browse flow. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten login-modal open/close cycles, summary size rose 2.26% and nodes 1.28%, with no repeated-constructor spike; this single pair shows no unbounded growth. |
be-memory-efficientbounded-footprint | pass | medium | The homepage heap summary was 12.84 MB across 226,362 nodes, proportionate to a media-rich feed. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither heap summary listed Detached constructors among top populations, and closure count changed from 7,764 to 7,873 after ten modal cycles without a large accumulating class. |
Provenance
Canonical report: results/atomic/reports/0439-www_xpaja_net.json
Report SHA-256: 2912c421d398125a18e3ce79c77161d8a1be55acd722124363ada6d44e9808cb
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_xpaja_net/2026-07-20T20-39-57-260Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_xpaja_net/2026-07-20T20-39-57-260Z
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.