Manifest position 915 · CrUX rank bucket 1000

https://www.promiedos.com.ar

Coverage complete

Atomic coverage complete across 58 checks and four representative content archetypes plus a recovery route.

Attempts

1 / 3

Judged checks

58 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	Desktop screenshots under default and prefers-color-scheme: dark are pixel-identical (both 508,720 bytes) and remain fixed dark-green; the CSS probe found no color-scheme preference rule. F-001 low: Honours prefers-color-scheme: a usable dark mode exists and is driven by the user's preference (color-scheme / prefers-color-scheme / light-dark()), not hard-coded light only.
respect-user-preferences `respects-reduced-motion`	pass	high	Under prefers-reduced-motion: reduce, matchMedia returned true, getAnimations() returned none, and no motion CSS was detected.
respect-user-preferences `respects-contrast`	issues	high	axe found two serious color-contrast failures in the consent UI and 14 more nodes requiring manual review. F-002 medium: Honours prefers-contrast / forced-colors: controls, text and scrollbars remain visible under high-contrast preferences.
implement-natural-interactions `view-transitions`	issues	high	The CSS probe found no view-transition rules; navigation among home, league, game and calendar uses abrupt full state swaps. F-003 medium: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	No applicable surface was present on the representative routes.
implement-natural-interactions `physical-gestures`	pass	high	DOM/CSS and route walkthrough found conventional links, buttons and scrolling, with no custom drag or pointer gesture that fights native interaction.
provide-guided-navigation `scroll-state-aware-chrome`	issues	high	The long scores feed has static chrome; CSS inspection found no scroll-state query or progress/position affordance. F-004 low: Sticky/affixed UI reacts to scroll state and position (e.g. the new scroll-state(scrolled) query, shrinking headers, progress indicators) so chrome responds to position instead of static or JS-driven toggling.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No applicable surface was present on the representative routes.
provide-guided-navigation `directs-attention`	issues	high	Screenshots and route walkthrough show no directional transition, target highlight or other cue when moving from fixture to league/game detail. F-005 low: Navigation and in-page jumps guide attention (highlight effects, scroll/carousel markers, directional transitions, drill-down and drawer navigation) so the user can follow where focus moved.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	Fresh-load screenshots on home, league and game show a consent interstitial dimming and obscuring the primary scores content; on 360x800 it occupies almost the whole viewport. F-006 high: No intrusive pop-ups, interstitials or banners that obscure content on load; overlays are dismissible and content-first.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	DOM probe found 0 dialog, 0 popover and 0 details elements while the full-screen consent overlay is implemented by injected div/button chrome. F-007 medium: Overlays and rich controls use the right primitive: popover (with declarative light-dismiss) for transient UI, dialog for modal flows, details for disclosure, native-but-branded selects and pickers, rather than ad-hoc divs.
maximize-content-reduce-noise `reduced-chrome`	pass	high	After accounting for the consent overlay, screenshots show a content-dense scores layout with navigation and compact match cards rather than decorative framing.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	At 360x800, layout measured scrollWidth 360, clientWidth 360 and horizontalOverflowPx 0; viewport meta is present.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	CSS probe found no @container usage despite match cards and tables being reused across sidebars, league and game layouts. F-008 low: Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints.
adapt-to-the-form-factor `input-modality-aware`	issues	high	The first focused link computed to outline none, and axe found 21 critical button-name failures, making keyboard and alternative-input operation unclear. F-009 medium: Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	The home H1 says PARTIDOS DE HOY and prominent real links lead directly to fixtures, leagues and games.
support-core-task-success `primary-flow-completion`	issues	high	The core score-browsing journey is interrupted on every fresh route by a blocking consent wall; reject is not available at the same level as accept. F-010 high: The representative primary flow can be completed end-to-end with predictable steps, no avoidable dead ends, no hidden required information, and no needless detours through modals, account walls, or upsells.
support-core-task-success `clear-system-state-and-recovery`	pass	high	A deliberately invalid route presents a clear “Página no encontrada” state and a direct link back to the homepage.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse mobile lab score was 0.56 with simulated LCP 11,283 ms, FCP 4,046 ms and TBT 273 ms, despite the separate desktop trace being faster (LCP 1,605 ms). F-011 high: Core Web Vitals are in the good range: LCP is fast, interaction latency (INP) is low, and CLS is minimal; work is prioritised and deferred sensibly.
be-fast-and-stable `visual-stability`	pass	high	Mobile layout observation measured CLS 0.0338 and Lighthouse measured 0, both inside the good range.
be-fast-and-stable `efficient-main-thread`	issues	high	Lighthouse measured 273 ms TBT and 205 ms max potential FID; the first-party trace also recorded a 70 ms long task. F-012 medium: The main thread is not blocked by long tasks or heavy scripting; work is deferred, chunked, prioritised, or moved off-thread.
be-fast-and-stable `efficient-resource-delivery`	issues	high	HAR recorded parser-blocking local CSS plus two Google Fonts stylesheets and 207 KB of font transfer; Lighthouse simulated LCP was 11.3 s. F-013 medium: Critical resources are delivered efficiently: cache headers are useful, render-blocking chains are short, fonts do not block or shift text, HTTP delivery is modern, and network dependency trees do not delay the main content.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	HAR recorded 894 KB of scripts; the three largest scripts were advertising/tag-manager resources totalling about 537 KB before other consent/ad code. F-014 medium: The page does not ship large unused or duplicated JavaScript/CSS, avoidable legacy bundles, or third-party code that dominates the load without user value.
be-inclusive `names-roles-labels`	issues	high	axe found 21 critical unnamed buttons and 2 critical images without alt; the image primitive independently found a missing-alt image. F-015 high: Interactive elements have accessible names, correct roles, and form fields have labels; images have alt text where meaningful; canvas/expressive content is exposed to assistive technology.
be-inclusive `sufficient-contrast`	issues	high	axe reported serious color-contrast failures, including consent FAQ/vendor UI. F-016 medium: Text and essential UI meet WCAG colour-contrast minimums against their background.
be-inclusive `structure-and-focus`	issues	high	axe found a heading-order failure; the first programmatically focused link had no visible computed outline, while 21 buttons lacked names. F-017 medium: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves.
be-inclusive `legible-text`	pass	high	Across desktop and mobile screenshots, core fixture text reflows without clipping and remains readable when not covered by consent.
be-inclusive `zoom-reflow-targets-and-media`	pass	high	The viewport permits normal scaling, the 360 px layout reflows with no horizontal overflow, and no essential video/audio content requiring captions was present.
follow-best-practices `no-console-errors`	issues	high	Lighthouse captured a network console error: a team image endpoint returned HTTP 500. F-018 medium: The page loads without console errors or uncaught exceptions.
follow-best-practices `sound-document-and-assets`	issues	high	Document has HTML doctype/UTF-8, but image audit found one missing dimension and 52 images over 2x displayed size. F-019 medium: Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.)
follow-best-practices `browser-platform-hygiene`	pass	high	Lighthouse best-practices was 0.88; probes found no permission prompt on load or input paste-prevention surface, and no deprecated API evidence beyond the separately reported network error.
be-discoverable `title-and-description`	pass	high	Homepage exposes a descriptive football-results title and a detailed meta description; league and game DOM captures also have specific titles.
be-discoverable `crawlable-and-mobile-friendly`	issues	high	Links and viewport pass, but /robots.txt returns the site’s HTML 404 page rather than robots directives, so crawler policy is malformed. F-020 medium: Links are crawlable (real href), there is a viewport meta tag, robots does not block indexing, and link text is descriptive.
be-discoverable `canonical-and-indexing-signals`	issues	high	Homepage returned 200 and sitemap exists, but no canonical URL was present and /robots.txt incorrectly served an HTML 404 representation. F-021 medium: Public pages expose the indexing signals search engines need: successful HTTP status, canonical URL when appropriate, hreflang for localized variants, robots/sitemap consistency, and no accidental noindex/noarchive policy.
be-discoverable `structured-and-shareable-metadata`	issues	high	Probe found 0 JSON-LD blocks and no Open Graph metadata for this public sports-results page and its match/league entities. F-022 medium: Where the page represents an article, product, organization, event, place or other rich entity, structured data and share-preview metadata accurately describe the visible content.
be-private-and-secure `secure-transport-and-headers`	issues	high	HTTPS is used, but headers probe found no CSP or HSTS; all three observed first-party cookies lacked Secure and used SameSite=None. F-023 high: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	Trackers probe found 11 third-party origins and Google Ads, GTM and DoubleClick; the consent copy says data may be shared with 210 partners and precise geolocation may be used. F-024 high: No over-collection of user data, no leaky third parties, and analytics/background data collection is minimised and batched rather than chatty or session-wide by default.
be-private-and-secure `in-context-permissions-and-modern-auth`	not-applicable	high	No applicable surface was present on the representative routes.
be-private-and-secure `defensive-browser-policies`	issues	high	Headers probe found no frame protection, Referrer-Policy, Permissions-Policy, CSP/Trusted Types policy, HSTS or nosniff. F-025 medium: Browser-enforced defenses are configured where appropriate: HSTS, clickjacking protection (frame-ancestors / X-Frame-Options), Trusted Types for XSS-sensitive apps, origin isolation, privacy-preserving third-party cookie posture, and sensible Referrer-Policy / Permissions-Policy.
be-resilient `progressive-enhancement`	issues	high	Discoverability comparison found only 16% of rendered content words in raw HTML; live results are largely unavailable to non-JS clients even though the shell is server-rendered. F-026 high: Core content and primary flows are reachable and usable without JavaScript and on older or non-Baseline browsers; modern features layer on as enhancements with fallbacks, and reactive/transition state stabilises rather than flickering before it settles.
be-resilient `resilient-runtime-behaviour`	pass	high	Consent and route layouts remained within tested desktop/mobile viewports, and conventional route links preserved predictable browser navigation.
be-resilient `offline-and-installable`	not-applicable	high	No applicable surface was present on the representative routes.
be-resilient `network-and-http-failure-states`	pass	high	The representative invalid route renders an intentional recovery page with explanatory copy and a home link instead of a blank shell.
be-internationalised `lang-dir-and-logical-properties`	pass	high	html lang is es and Spanish reading order is correct; no bidirectional content is part of this deliberately Spanish-language service.
be-internationalised `locale-aware-data`	pass	high	Visible dates and day names are rendered in Spanish (for example “JUEVES 23 DE JULIO DE 2026”) and scores use locale-appropriate simple numerals.
be-internationalised `time-zone-correctness`	issues	high	Fixtures display bare times such as 23:30 without a visible time-zone label or user-zone explanation on a globally reachable sports site. F-027 medium: Time handling survives time zones and DST: events coordinate across zones, partial time concepts are modelled, and stored times are unambiguous.
be-trustworthy `no-dark-patterns`	issues	high	The first-layer consent UI gives a one-click Accept/Consent action but no equivalent reject action; refusal requires entering Manage options, creating asymmetric friction. F-028 medium: No deceptive design: no confirmshaming, forced continuity, disguised ads, or nagging consent walls; honest defaults; clear pricing and consent; easy reversal/cancel; predictable, declaratively-wired actions; and no hidden-text tricks (hidden content stays deep-linkable and indexable rather than used to deceive).
be-trustworthy `humane-error-handling`	not-applicable	high	No applicable surface was present on the representative routes.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	No applicable surface was present on the representative routes.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	No applicable surface was present on the representative routes.
be-sustainable `optimised-assets`	issues	high	Image probe found 85 below-fold images without lazy loading and 52 assets more than 2x their displayed width; HAR recorded 251 image requests. F-029 medium: Images and decorative assets are optimised and served at appropriate resolutions; decorative pseudo-element imagery and heavy decorative images are resolution-optimised rather than oversized.
be-sustainable `no-wasteful-work`	issues	high	HAR recorded 293 requests, including multiple analytics/ad calls and a 55 KB sound file on initial load before the user asks for audio. F-030 medium: Background work and fetching are not wasteful: background processing is efficient and de-prioritised, and the lightest technique that achieves the result is preferred over heavy or redundant work.
be-sustainable `third-party-and-media-budget`	issues	high	HAR transferred 1.66 MB and trackers found 11 third-party origins; advertising/tag-manager scripts dominate the largest resources. F-031 medium: Third-party scripts, fonts, video, audio, animation and heavy media are proportionate to the user value they provide; autoplay or background media is avoided unless essential and resource use is cached or deferred where possible.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	No applicable surface was present on the representative routes.
be-agent-ready `on-device-inference`	not-applicable	high	No applicable surface was present on the representative routes.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	medium	After ten full-page down/up scroll cycles, heap grew only 449 KB (31.35 MB to 31.79 MB, 1.4%) and no Detached constructor appeared; no unbounded growth was observed in this bounded run.
be-memory-efficient `bounded-footprint`	issues	high	Baseline heap contained 605,115 nodes and 31.35 MB self size for a scores page, disproportionate to its visual complexity and amplified by consent/ad technology. F-032 medium: Heap size and DOM node count are reasonable for what the page is; the footprint is proportionate rather than bloated.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	Neither baseline nor post-scroll heap summaries listed Detached constructors; the bounded 10-cycle run did not show detached-DOM accumulation.

Provenance

Canonical report: results/atomic/reports/0915-www_promiedos_com_ar.json
Report SHA-256: 0d7a847503243881c421e1c303479e368585d45d0e6351fc0f2883d506d4e834
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_promiedos_com_ar/2026-07-23T20-00-40-694Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_promiedos_com_ar/2026-07-23T20-00-40-694Z
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.