Manifest position 109 · CrUX rank bucket 1000
https://www.cronista.com
Coverage complete
Coverage-complete audit across five representative templates and global transport/network conditions.
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-condition screenshot is visually identical to the light design, and the CSS probe found no prefers-color-scheme rule on any representative template. F01 medium: The site does not honor the user’s dark-color preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, eight animations remained running, including 15–24 second ticker animations and pulsing elements. F02 medium: Long-running motion continues when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors and high-contrast screenshot preserved visible text, controls, and outlines; CSS probes found forced-colors/prefers-contrast handling on four templates. |
implement-natural-interactionsview-transitions | issues | high | CSS probes found no View Transition support on the homepage or representative article, despite cross-document navigation being a primary interaction. F03 low: Primary template changes are abrupt on key routes. |
implement-natural-interactionsscroll-driven-animations | pass | high | Section and markets CSS probes found scroll-timeline/animation-timeline support, while no evidence showed scroll-event-driven animation work. |
implement-natural-interactionsphysical-gestures | pass | high | Representative CSS contained scroll-snap and logical/intrinsic layout support, with no observed custom pointer handling fighting native scrolling. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The article is over 15,800 CSS pixels tall, but the captured template exposes no reading progress or scroll-aware article chrome. F04 low: Long pages do not provide scroll-state guidance. |
provide-guided-navigationanchored-positioning | pass | high | Section, markets, and login CSS probes found anchor positioning declarations; no clipped overlay was observed at representative viewport edges. |
provide-guided-navigationdirects-attention | pass | high | Breadcrumbs, clearly labelled section links, persistent mobile navigation, and scroll-snap affordances provide orientation across tested templates. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a full-page dimmer and large consent panel before interaction, with an additional Google sign-in prompt on desktop. F05 high: A consent wall obscures every audited page on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM probes found one large fixed overlay but zero dialog or popover elements; its modal behavior is implemented as nested divs. F06 medium: The blocking consent UI is custom chrome rather than a semantic dialog. |
maximize-content-reduce-noisereduced-chrome | issues | high | The first viewport combines a full consent wall, a separate Google sign-in prompt, subscription chrome, ticker, bottom navigation, and a chat control. F07 medium: Competing fixed chrome crowds the news content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All five 360×800 layout captures reported zero horizontal overflow and a valid viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | CSS probes found container-query support on all five representative templates, and mobile captures reflowed to 360px without clipping. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focus probes found 3–4 visible controls below 24px in one dimension, including a 132×15 edition button and 18×22 modal close control. F08 medium: Several controls have undersized hit areas. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home, section, article, markets, and login views expose recognizable branding, descriptive titles, and direct content or sign-in actions. |
support-core-task-successprimary-flow-completion | pass | high | Server-rendered article content is reachable directly and representative navigation uses real links; no account wall blocked article discovery in DOM/discoverability evidence. |
support-core-task-successclear-system-state-and-recovery | issues | high | Requesting a deliberately nonexistent URL ended at https://www.cronista.com/ with no 404 heading or recovery explanation. F09 medium: Unknown URLs silently redirect to the homepage. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured FCP 17.6s, LCP 26.7s, TBT 300ms, and a 0.49 performance score; a separate trace measured LCP 3.03s under a less-throttled condition. F10 high: Cold-load performance is far outside the good range. |
be-fast-and-stablevisual-stability | pass | high | Observed mobile CLS was 0.0039–0.049 across five templates, and Lighthouse measured CLS 0.023, all in the good range. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reported 4.1s main-thread work and 2.2s JavaScript execution; Clickio, React, and Permutive were leading contributors. F11 high: JavaScript startup consumes substantial main-thread time. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 109 requests and 3.19MB transferred; 2.24MB was script, and the 568KB first-party default bundle took 2.31s. F12 high: Critical delivery is dominated by a large script and vendor chain. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR measured 58 third-party requests and 1.77MB third-party transfer, including duplicate analytics tags, reCAPTCHA, consent, identity, and advertising scripts. F13 medium: Third-party code dominates the load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed image-alt and link-name; the image primitive found 2 missing alts on home and 10 on the article, while DOM probes found unlabeled search inputs. F14 high: Accessible names and alternatives are incomplete. |
be-inclusivesufficient-contrast | issues | high | Lighthouse color-contrast failed with 201 affected nodes. F15 high: Many text elements fail minimum color contrast. |
be-inclusivestructure-and-focus | issues | high | The homepage h1 is empty, article markup contains several empty headings, and focused menu links were observed with outline: none. F16 medium: Heading and focus semantics are inconsistent. |
be-inclusivelegible-text | pass | high | Desktop and mobile screenshots show readable editorial typography and reflow; no text clipping or horizontal overflow was observed. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Viewport permits scaling, all five mobile templates reflow without overflow, and no video requiring captions appeared on the audited paths. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured a React Internal Server Error, a first-party content API 500, CORS errors, and failed resources. F17 medium: The page logs runtime and network errors. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found 87/100 homepage images and 28/39 article images without width/height, mostly legacy formats; Lighthouse also found aspect-ratio and low-resolution failures. F18 medium: Image markup and sizing are unsound at scale. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed the valid-source-maps audit for large first-party JavaScript. F19 low: Large first-party scripts lack usable source maps. |
be-discoverabletitle-and-description | pass | high | All five probes found titles and descriptions; the article title and description accurately describe its visible content. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Real href links dominate navigation, viewport meta is present, and robots.txt allows public content while declaring targeted disallows. |
be-discoverablecanonical-and-indexing-signals | pass | high | Representative pages returned content, declared matching canonicals and index/follow, and robots.txt lists current sitemap feeds. |
be-discoverablestructured-and-shareable-metadata | pass | high | Home, section, article, and markets pages expose JSON-LD plus Open Graph title/image metadata matching visible entities. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP is only upgrade-insecure-requests; HSTS and nosniff are missing, and all seven observed cookies were flagged, including one non-Secure cookie. F20 high: Transport protections and cookie attributes are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 32 third-party origins and six known tracker domains; HAR attributed 58 requests and 1.77MB to third parties. F21 high: The first load exposes users to an extensive tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No browser permission prompt appeared on load; the login surface uses federated Google identity rather than exposing a password-only form. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence found no HSTS, frame protection, Referrer-Policy, Permissions-Policy, or X-Content-Type-Options, while CSP lacks a source policy and frame-ancestors. F22 high: Browser-enforced defenses are largely absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability evidence found 92% raw-HTML content coverage on home and 83% on the article, with title, h1, and description present without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Core news content remained rendered despite vendor and one feed failure; templates use anchor-position and container-query support where overlays/layout adapt. |
be-resilientoffline-and-installable | issues | high | All templates expose service-worker capability but no manifest link; offline behavior is not presented as a user-facing capability. F23 low: The app-like news experience has no install manifest or verified offline fallback. |
be-resilientnetwork-and-http-failure-states | issues | high | A nonexistent path redirected to the homepage, and the live homepage also produced a first-party API 500 with no visible recovery state. F24 medium: HTTP failure handling is misleading. |
be-internationalisedlang-dir-and-logical-properties | pass | high | All templates declare lang=es and ltr, use logical CSS properties, and the homepage exposes eight hreflang alternates. |
be-internationalisedlocale-aware-data | pass | high | Rendered dates, Argentine currency, decimal separators, and market values are localized in Spanish across article and markets templates. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited news and spot-market views do not schedule user events or accept partial times; displayed publication/market dates do not expose a cross-time-zone transaction. |
be-trustworthyno-dark-patterns | issues | high | The blocking panel headline says “Accept cookies to browse for free” although a reject action exists, while consent text describes device identification and 1,719 partners. F25 high: Consent copy frames tracking acceptance as required for free browsing. |
be-trustworthyhumane-error-handling | pass | high | No user-submittable validation form was exposed on the representative public and federated-login paths; search controls did not show premature error states. |
be-trustworthytrustworthy-input-assistance | pass | high | Search fields use appropriate search semantics and autocomplete=off for query UI; no address, payment, password, or signup field requiring missing autofill tokens was exposed. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Persistent chrome advertises “Suscribite x $999” without a visible billing period or renewal terms in the same decision context. F26 medium: The subscription call to action omits the commitment period. |
be-sustainableoptimised-assets | issues | high | The homepage image audit found 93 legacy-format images, 87 missing dimensions, 16 missing srcset, and 9 oversized images. F27 medium: Most image assets use legacy formats or lack responsive metadata. |
be-sustainableno-wasteful-work | issues | high | The load made 109 requests and ran analytics, ads, identity, recaptcha, push, chat, and measurement code before the user engaged. F28 high: Background and startup work is disproportionate to a news homepage. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties transferred 1.77MB of the 3.19MB total and accounted for 58 requests; scripts represented 2.24MB overall. F29 high: Third-party transfer exceeds half of the page load. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing workflow was found; this emerging capability is optional for the publication, whose content is already 83–92% available in raw HTML. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the audited publication paths requires built-in inference; absence is an opportunity, not a defect under the contextual emerging principle. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll cycles, the heap summary was 47.70MB versus a 47.38MB baseline, a 0.68% difference consistent with bounded settling rather than unbounded retention. |
be-memory-efficientbounded-footprint | pass | high | The page used about 41MB JS heap, 2,959 DOM elements, and a 47.38MB snapshot footprint; substantial but proportionate to the dense news page and stable after exercise. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after heap summaries showed no Detached* constructor among leading populations and only 0.4% node-count difference after repeated scrolling. |
Provenance
Canonical report: results/atomic/reports/0109-www_cronista_com.json
Report SHA-256: 53d8e3bba66188051e11dc39afef0ec673faa6f2b2aeced61493147c9b9afa5c
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_cronista_com/2026-07-18T11-54-49-118Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_cronista_com/2026-07-18T11-54-49-118Z
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.