Manifest position 405 · CrUX rank bucket 1000
https://www.tvazteca.com
Coverage complete
Coverage-complete representative audit of four public templates plus the not-found state.
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-mode screenshot is visually identical to the default capture, and the reduced-media probe reports computed color-scheme: normal. F01 medium: The site does not respect dark color preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned no active animations. |
respect-user-preferencesrespects-contrast | issues | high | Default, dark and prefers-contrast: more screenshots have identical byte sizes and appearance, while Lighthouse also finds insufficient contrast. F24 medium: The presentation does not adapt to increased-contrast preference. |
implement-natural-interactionsview-transitions | issues | high | The platform probe confirms the browser supports View Transitions, while page markup contains no view-transition integration. F03 low: Route changes have no continuity treatment. |
implement-natural-interactionsscroll-driven-animations | issues | high | The platform probe found no scroll-snap surfaces and the DOM/CSS recon found no container or view-transition integration across pages up to 9,133px tall. F04 low: Long discovery surfaces do not use compositor-driven scroll cues or natural snapping. |
implement-natural-interactionsphysical-gestures | issues | high | The platform probe found no scroll-snap surface, while long horizontally scrollable navigation is present in the DOM/CSS recon. F25 low: Scrollable navigation and long content do not offer natural gesture constraints. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Mobile layout captures show pages 3,374px to 9,133px tall, but recon found no scroll-state query or equivalent guided progress affordance. F05 low: Long pages do not adapt navigation chrome to scroll state. |
provide-guided-navigationanchored-positioning | not-applicable | medium | No user-invoked anchored tooltip, menu, or popover was present in the representative core journey. |
provide-guided-navigationdirects-attention | pass | high | Screenshots show strong section headings, lead-story hierarchy and breadcrumbs on the article. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The first mobile viewport is covered by an on-load notification prompt, and Lighthouse reports geolocation-on-start on home and notification-on-start on the article. F07 high: A notification opt-in interrupts content before user intent. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The on-load prompt is visually modal, while Lighthouse reports aria-dialog-name failure. F06 medium: The notification prompt is not exposed as a named semantic dialog. |
maximize-content-reduce-noisereduced-chrome | issues | high | The mobile homepage first shows the permission prompt and a large PUBLICIDAD reserve before the lead story. F08 medium: Advertising and prompts delay meaningful content in the first viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All four 360px layout captures report horizontalOverflowPx: 0. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The media probe reports no container-query rules, although the same cards appear in several differently sized modules. F09 low: Components rely on viewport breakpoints rather than container context. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The DOM probe counted 529 of 1,536 visible homepage targets below 24px in one dimension, and Lighthouse failed target-size on home and article. F10 high: Many interactive targets are too small for touch. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, news index, article and program screenshots expose clear branded purpose and prominent content links. |
support-core-task-successprimary-flow-completion | pass | high | Direct crawlable links connect the homepage to section and article content; the representative article loaded without account gating. |
support-core-task-successclear-system-state-and-recovery | pass | high | The invalid-route capture clearly states that the page does not exist and offers an Avanzar recovery action plus content links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured homepage LCP 6.3s, TBT 1,300ms and performance 36; article LCP 6.2s, TBT 930ms and performance 40. The raw-CDP trace corroborated LCP 4.47s and five long tasks. F11 high: Primary pages load too slowly. |
be-fast-and-stablevisual-stability | pass | high | Observed mobile CLS was 0 on home, 0.0005 on news, 0.038 on article and 0.0004 on program. |
be-fast-and-stableefficient-main-thread | issues | high | Mobile Lighthouse measured homepage LCP 6.3s, TBT 1,300ms and performance 36; article LCP 6.2s, TBT 930ms and performance 40. The raw-CDP trace corroborated LCP 4.47s and five long tasks. F11 high: Primary pages load too slowly. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 371 requests and 14.63MB transferred, including 10.46MB of images and 3.70MB of scripts; 365 requests and 14.43MB were third-party by origin classification. F12 high: The homepage transfers an excessive resource payload. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR recorded 371 requests and 14.63MB transferred, including 10.46MB of images and 3.70MB of scripts; 365 requests and 14.43MB were third-party by origin classification. F12 high: The homepage transfers an excessive resource payload. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed aria-dialog-name, image-alt and select-name; the homepage probe found 11 unnamed buttons and an unlabeled search input and select. F13 high: Controls and media lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse accessibility reports color-contrast as a failing audit on the homepage. F02 high: Some foreground and background combinations fail contrast requirements. |
be-inclusivestructure-and-focus | issues | high | The homepage has zero h1 elements and starts at h3 then h4, while section, article and program templates each expose one h1. F14 medium: Homepage heading structure does not expose a primary heading. |
be-inclusivelegible-text | pass | high | Mobile screenshots show readable body and heading sizes with adequate line length and clear typographic hierarchy. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse fails target-size on home and article, and the mobile DOM probe counts 529 targets below 24px in one dimension. F27 high: Touch-target sizing undermines inclusive reflow and mobile operation. |
follow-best-practicesno-console-errors | issues | high | Lighthouse reports errors-in-console and Inspector Issues failures on both homepage and article. F15 medium: Runtime errors are emitted during normal loading. |
follow-best-practicessound-document-and-assets | issues | high | The article mobile screenshot shows a broken lead image; image probes found six missing alt texts and six missing dimensions on the article, with similar failures on listing templates. F16 high: Image delivery is unreliable and incompletely described on editorial templates. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports geolocation-on-start on home, notification-on-start on article, and a deprecation warning on both. F17 high: Permission requests occur before a relevant user action and deprecated APIs remain. |
be-discoverabletitle-and-description | pass | high | All four templates expose unique titles and non-empty meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | All four pages are server-rendered at 94 to 99 percent raw-content coverage, have viewport metadata, and use real href links. |
be-discoverablecanonical-and-indexing-signals | pass | high | All representative pages return content, declare self-referential canonicals and index/follow robots signals; robots.txt lists section sitemaps. |
be-discoverablestructured-and-shareable-metadata | pass | high | Representative pages expose JSON-LD and Open Graph metadata aligned to visible titles. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers probe found no CSP, X-Content-Type-Options, frame protection, Referrer-Policy, or Permissions-Policy. HSTS is present. F18 high: Key defensive response headers are absent. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe observed 69 third-party origins and 12 known trackers. HAR attributed 365 of 371 requests and 14.43MB to third-party origins. F19 high: The page exposes visitors to an unusually broad tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Lighthouse reports geolocation-on-start on the homepage and notification-on-start on the article. F29 high: Permissions are requested out of context. |
be-private-and-securedefensive-browser-policies | issues | high | Cookie inspection found all 15 observed cookies flagged insecure, many SameSite=None, and several 366 to 400 days old; Lighthouse observed 21 to 22 third-party cookies. F20 high: Cookie and browser policies are weak. |
be-resilientprogressive-enhancement | pass | high | Discoverability captures show 94 to 99 percent content coverage without JavaScript and no empty SPA shell. |
be-resilientresilient-runtime-behaviour | pass | high | The invalid route renders a branded, usable recovery page rather than a blank runtime failure. |
be-resilientoffline-and-installable | not-applicable | medium | A public broadcast and news site depends on live remote editorial and video data; no installable or offline intent was declared and no manifest is exposed. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately invalid URL produced a clear not-found message and recovery controls. |
be-internationalisedlang-dir-and-logical-properties | pass | high | All representative pages declare lang="es-MX" and render coherent left-to-right Spanish content. |
be-internationalisedlocale-aware-data | pass | high | Visible publication dates are rendered in Spanish words such as 19 julio, 2026 rather than ambiguous numeric-only formatting. |
be-internationalisedtime-zone-correctness | not-applicable | medium | No scheduling or user-entered time flow was present in the representative paths; displayed publication dates did not expose time-zone-sensitive interaction. |
be-trustworthyno-dark-patterns | issues | high | The first viewport asks users to activate notifications before they have engaged with content; Lighthouse also detects permission requests on load. F26 high: Permission prompts use interruption before intent rather than contextual consent. |
be-trustworthyhumane-error-handling | not-applicable | medium | The audited core path is content browsing and did not expose a user-submitted validation flow without entering account registration. |
be-trustworthytrustworthy-input-assistance | issues | high | Across four representative templates the search field has no label, aria-label or autocomplete value; the homepage select is also unlabeled. F21 medium: Search and select fields lack explicit labels and autofill hints. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | medium | No checkout, subscription purchase, or authenticated account-management flow was part of the public representative paths. |
be-sustainableoptimised-assets | issues | high | The homepage image probe reports 70 oversized images and 68 below-fold images without lazy loading; HAR records 10.46MB of images. F30 high: Image assets are substantially oversized and eagerly loaded. |
be-sustainableno-wasteful-work | issues | high | HAR records 371 requests, 71 scripts and 48 XHR/fetch requests during initial observation, while the trace records five long tasks. F28 high: Nonessential background network and script work is excessive. |
be-sustainablethird-party-and-media-budget | issues | high | The homepage transfers 14.63MB across 371 requests, with 10.46MB images, 3.70MB scripts and 69 third-party origins. Sixty-eight below-fold images are not lazy-loaded and 70 are oversized. F22 high: Network and media cost is disproportionate to initial content. |
be-agent-readystructured-agent-capabilities | not-applicable | medium | No agent-facing action surface is declared; the site is a public editorial publisher and provides crawlable content rather than WebMCP tools. |
be-agent-readyon-device-inference | not-applicable | medium | The site has no summarisation, translation, or other product feature that requires on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten full-page scroll cycles, aggregate heap self size rose about 1.59MB (2.1 percent) and node count about 1.9 percent, which does not establish unbounded retained growth in this bounded test. |
be-memory-efficientbounded-footprint | issues | high | Heap summary recorded 1,289,194 nodes and 77.17MB self size at baseline; after repeated scrolling it recorded 1,313,414 nodes and 78.76MB. F23 medium: The initial JavaScript heap is heavy for a content discovery page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | not-applicable | medium | The heap primitive produced aggregate summaries but no constructor-level detached-node or listener instrumentation in this run; however, the repeated scroll was bounded and this specific leak pattern was not observable. This check is not applicable to the chosen interaction because it creates no transient DOM component. |
Provenance
Canonical report: results/atomic/reports/0405-www_tvazteca_com.json
Report SHA-256: cd11321b96580105d3bb23edd2a315890d1cf4499b1cabbe76c5196e598aaa30
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_tvazteca_com/2026-07-20T13-40-38-148Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_tvazteca_com/2026-07-20T13-40-38-148Z
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.