Manifest position 191 · CrUX rank bucket 1000
https://www.elconfidencial.com
Coverage complete
Complete atomic audit of 58 checks across five representative paths. Excluded destructive subscription/payment/account completion and exhaustive per-section duplication.
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 screenshot remains white and the probe reports colorScheme "normal" and body background rgb(255,255,255). F01 medium: The site ignores the user’s dark colour preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found the 45-second cot-marquee animation still running while matchMedia(reduce) was true. F02 medium: A continuously moving market ticker remains active when reduced motion is requested. |
respect-user-preferencesrespects-contrast | issues | medium | DOM/CSS evidence contains fixed colour tokens and no forced-colors or prefers-contrast adaptation; Lighthouse also found low-contrast consent and LIVE text. F03 low: High-contrast and forced-colour adaptation is not defined. |
implement-natural-interactionsview-transitions | issues | medium | The platform probe found no view-transition CSS or startViewTransition usage despite navigation across MPA templates. F04 low: Navigation changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | medium | DOM CSS includes an @supports(animation-timeline: scroll()) implementation for the skin/header effect, avoiding a scroll event loop. |
implement-natural-interactionsphysical-gestures | pass | medium | Mobile screenshots and CSS show native scrolling and a Swiper CSS scroll-snap mode; no evidence of a platform-fighting pointer gesture on tested paths. |
provide-guided-navigationscroll-state-aware-chrome | pass | medium | DOM CSS defines a sticky/compact header and a declarative scroll-timeline variant; article screenshot shows persistent orientation chrome. |
provide-guided-navigationanchored-positioning | not-applicable | medium | No tooltip or edge-positioned popover was present in the representative reading and listing paths, so anchor positioning was not applicable. |
provide-guided-navigationdirects-attention | pass | medium | Section labels, article hierarchy, latest-news tabs and sticky article progress/navigation cues preserve orientation across tested templates. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Lighthouse captured a 463x496 modal consent dialog occupying most of its mobile viewport before content interaction. F05 medium: The consent experience can cover the primary content on load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM CSS includes custom tp-modal/tp-backdrop and the consent UI is a div with role=dialog; no native dialog or popover elements were found. F06 low: Transient overlays are implemented with custom div-based modal infrastructure rather than native dialog/popover primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop homepage, article and section screenshots reserve roughly 250px-high advertising blocks before primary editorial content; on the article the headline begins below mid-viewport. F28 medium: Large ad reservations displace editorial content from the initial viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The article layout primitive measured scrollWidth 373 vs clientWidth 360, a 13px overflow; the homepage was only 1px and latest-news had none. F07 medium: The article template overflows horizontally on a 360px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The CSS probe found no @container rules, while the same header/card system is reused across homepage, section, article and feed layouts. F08 low: Reusable components rely on viewport rules rather than container queries. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Programmatic focus on the first link computed to outline:none 0px; Lighthouse reports multiple footer targets only 18-19px high. F09 medium: Keyboard focus and touch-target affordances are insufficient. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | Homepage, section, latest-news and article screenshots clearly identify publication, section and clickable story hierarchy. |
support-core-task-successprimary-flow-completion | pass | medium | The homepage-to-article reading journey completed without an account wall; the article H1, summary and body are server-rendered. |
support-core-task-successclear-system-state-and-recovery | pass | medium | The invalid route presents a clear ERROR 404 message and an IR A LA PORTADA recovery action. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 29.4s, TBT 1,030ms, FCP 4.8s and performance 0.36; the independent trace measured 901ms TBT and a 951ms long task. F10 critical: Mobile loading and responsiveness are far outside good Core Web Vitals targets. |
be-fast-and-stablevisual-stability | issues | high | The layout observer measured CLS 0.616 on latest-news, dominated by a 0.604 shift at about 2.45s. F11 high: The latest-news mobile template shifts dramatically during load. |
be-fast-and-stableefficient-main-thread | issues | high | The independent trace recorded a 951ms longest task and 901ms total blocking time; Lighthouse measured 1,030ms TBT and 6.0s main-thread work. F29 high: Main-thread execution blocks interaction for long periods. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 335 requests and 12.92MB transferred, including 9.41MB images, 158 scripts and many VeryHigh parser-inserted stylesheets. F12 high: The homepage transfers an excessive resource payload and has a long render-blocking chain. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse reports 6.0s main-thread work and 3.24s script evaluation; one first-party bundle consumed about 2.03s scripting and 158 scripts were requested. F13 high: Heavy first- and third-party JavaScript dominates main-thread work. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found the football widget iframe without a title; the image audit found 21 images without alt text, and the homepage has no H1. F14 high: Important embedded and image content lacks accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured ratios of 3.21-3.84:1 for consent text/links and 3.44:1 for LIVE badges, below 4.5:1 for the rendered text sizes. F15 medium: Text in the consent interface and live badges fails minimum contrast. |
be-inclusivestructure-and-focus | issues | high | The homepage has no H1; Lighthouse found a UL with a direct DIV child, and the focus probe found no visible outline on the first focusable link. F16 medium: Homepage semantics and focus structure contain defects. |
be-inclusivelegible-text | pass | medium | Desktop/mobile article screenshots show readable serif headings, clear summaries and comfortable text wrapping on the representative story. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The live probe reports maximum-scale=2.5 and Lighthouse flags many 18-19px-high touch targets; article content also overflows by 13px. F17 low: The mobile viewport and target sizing constrain inclusive reflow. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured ERR_CONNECTION_REFUSED to localhost.sensic.net and a 400 response from an Incapsula resource. F18 medium: The homepage emits network errors during load. |
follow-best-practicessound-document-and-assets | issues | high | Image audit found 13 images without dimensions, 23 oversized, 54 without srcset, 33 legacy-format and no modern-format images; Lighthouse found invalid list children. F19 medium: Image delivery and document structure contain avoidable defects. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse best-practices was 0.50 and Inspector Issues recorded cookie-related problems across Dailymotion and TradingView integrations. F20 low: DevTools reports browser-platform hygiene issues. |
be-discoverabletitle-and-description | pass | medium | Homepage and article both expose descriptive titles and meta descriptions in raw and rendered HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | medium | 403 real links were present with no anchors lacking href, viewport metadata exists, and generic robots rules allow the public pages. |
be-discoverablecanonical-and-indexing-signals | issues | high | Fetching /sitemap.xml returned a full HTML page rather than XML, while robots.txt is extensive and relies on that indexing surface. F21 medium: The advertised sitemap endpoint does not return a sitemap. |
be-discoverablestructured-and-shareable-metadata | pass | medium | Article probe found NewsArticle and BreadcrumbList JSON-LD plus complete Open Graph title, description, image, URL and type. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers include HTTPS, HSTS, CSP, nosniff and framing protection, but cookies reports didomi_token and __adblocker without Secure and sessionActive without HttpOnly. F22 high: Cookie security is inconsistent despite strong transport headers. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 48 third-party origins and 12 known trackers; HAR attributes 274 requests and 12.68MB to third-party origins. F23 high: The homepage exposes a very large third-party tracking surface. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | medium | No permission prompt or authentication form was exercised on the public reading paths; the page source does not request geolocation/notifications on load. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive found both response headers absent, although CSP, HSTS, nosniff and X-Frame-Options were present. F24 medium: Referrer-Policy and Permissions-Policy are missing. |
be-resilientprogressive-enhancement | pass | medium | Discoverability captures show 100% content coverage without JavaScript for homepage and article, including title/H1/description where applicable. |
be-resilientresilient-runtime-behaviour | pass | medium | Representative menus/content loaded across desktop and mobile; no clipped open overlay was observed and the server-rendered core remained usable. |
be-resilientoffline-and-installable | not-applicable | medium | This public news publication is content-first rather than an installed app; server-rendered no-JS access is the relevant resilience bar. |
be-resilientnetwork-and-http-failure-states | pass | medium | The 404 route provides explicit failure text and a homepage recovery link instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | low | html lang is es, but CSS sampling found 122 physical left/right declarations and only 4 logical-property occurrences. F27 low: CSS is not robust to alternate writing directions. |
be-internationalisedlocale-aware-data | pass | medium | Rendered Spanish dates, temperatures, percentages and market values use Spanish conventions on the homepage. |
be-internationalisedtime-zone-correctness | pass | medium | Article structured data uses an explicit +02:00 offset and displayed publication context is consistent with the Spanish locale. |
be-trustworthyno-dark-patterns | issues | high | Lighthouse captured a near-full mobile dialog whose text says continuing navigation is treated as acceptance, while the primary content is obscured. F31 high: The consent wording and blocking presentation undermine freely informed choice. |
be-trustworthyhumane-error-handling | not-applicable | medium | No validation-oriented form was present in the selected public reading templates. |
be-trustworthytrustworthy-input-assistance | not-applicable | medium | No address, payment, sign-in or sign-up input flow was present in the selected public reading templates. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | medium | Subscription/account completion would require credentials or a purchase commitment and was excluded from this public, non-destructive audit. |
be-sustainableoptimised-assets | issues | high | Images account for 9.41MB; three animated GIFs alone transfer 3.82MB, 1.45MB and 0.92MB, with 23 images oversized and no modern formats detected. F25 high: Image assets are disproportionate for a text-led news homepage. |
be-sustainableno-wasteful-work | issues | high | The initial load issues 274 third-party requests; Lighthouse boot-up attributes work to analytics, consent, Crazy Egg and Dailymotion before a media interaction. F30 high: Background vendor and media work begins before it supports the reading task. |
be-sustainablethird-party-and-media-budget | issues | high | HAR measured 12.68MB across 274 third-party requests and Lighthouse shows Dailymotion, ad-tech and analytics work before the user requests those surfaces. F26 high: Third-party and media work is not proportionate to the initial reading task. |
be-agent-readystructured-agent-capabilities | not-applicable | medium | The publication exposes content, metadata and crawlable links but no agent-actuated capability that would warrant WebMCP tools. |
be-agent-readyon-device-inference | not-applicable | medium | No user-facing inference or summarisation task is offered on these editorial templates; adding on-device AI is an optional product choice. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten finite full-feed scroll cycles, heap rose from 24.34MB to 29.21MB while lazy content was exercised; no Detached constructor appeared among top constructors. This is bounded evidence, not proof of a leak. |
be-memory-efficientbounded-footprint | pass | medium | Heap summaries remained below 30MB self-size for the long latest-news page after repeated scroll; footprint increase tracked finite lazy loading. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Before/after heap summaries did not surface Detached DOM constructors among the largest populations; no unbounded timer/listener symptom was observed during the finite repeat test. |
Provenance
Canonical report: results/atomic/reports/0191-www_elconfidencial_com.json
Report SHA-256: 2a0bb47ba88c34a46dd5aef3931de5080a267245cefcb9e52fe7cb07ccc7a5e9
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_elconfidencial_com/2026-07-19T01-29-02-190Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_elconfidencial_com/2026-07-19T01-29-02-190Z
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.