Manifest position 21 · CrUX rank bucket 1000
https://loteriadehoy.com
Coverage complete
Coverage-complete audit of four representative public templates plus an HTTP failure state. Excludes the separate secure.loteriadehoy.com account origin and exhaustive lottery-template 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 | The dark preference matched, but body remained rgb(255,255,255), color-scheme was normal, and the preference screenshot was identical to light mode. F01 medium: No system-driven dark theme |
respect-user-preferencesrespects-reduced-motion | pass | high | The preference matched and document.getAnimations() returned no active animations, so there was no non-essential motion to suppress. |
respect-user-preferencesrespects-contrast | issues | high | The page did not expose contrast-specific styling and Lighthouse found multiple WCAG contrast failures, including teal buttons at 2.95:1. F08 high: Core text and buttons fail WCAG contrast |
implement-natural-interactionsview-transitions | issues | medium | The multi-page navigation has no view-transition-name or View Transition CSS; route changes are abrupt full-document swaps. F02 low: Navigation changes are abrupt |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, entry reveal, carousel, or other scroll-linked motion exists on the representative pages. |
implement-natural-interactionsphysical-gestures | pass | medium | Interactions use native links and buttons; no custom pointermove, swipe, or pull gesture was exposed in the representative paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | On pages up to 22,963 CSS px tall, the chrome provides no scroll progress or position-aware cue; the platform probe found no scroll-state/timeline styling. F03 medium: The long results template is visually noisy and hard to orient within |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or viewport-edge menu requiring anchored positioning appeared in the representative paths. |
provide-guided-navigationdirects-attention | issues | medium | Navigation swaps abruptly and the very long results page lacks progress, current-section, or other attention cues. F02 low: Navigation changes are abrupt F03 medium: The long results template is visually noisy and hard to orient within |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No modal, consent wall, or interstitial obscured primary content on load; advertising occupied bounded page regions. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The FAQ disclosure uses no details elements; after one interaction all sampled question buttons reported aria-expanded=true, making state semantics unreliable. F04 medium: FAQ disclosure state is not semantic or reliable |
maximize-content-reduce-noisereduced-chrome | issues | medium | The results template is 22,963 CSS px tall and adds a persistent right rail of logos plus repeated social controls and advertising around the result content. F03 medium: The long results template is visually noisy and hard to orient within |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All four layouts reported scrollWidth 360, innerWidth 360, viewport meta present, and zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | medium | Hero actions change from a row on desktop to a stacked mobile layout, while result/detail/help templates fit at 360 px without overflow. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Many links expose outline:none when focused, result buttons are 38 px tall, and hundreds of empty hash links add unnamed keyboard stops. F05 high: Keyboard and touch affordances are weak |
support-core-task-successclear-purpose-and-primary-action | pass | high | The home page clearly offers result categories, and result/detail/help pages state their purpose with prominent headings and actions. |
support-core-task-successprimary-flow-completion | pass | high | The core information journey is reachable without login: home links to results, results expose dated outcomes, and a lottery detail explains schedules. |
support-core-task-successclear-system-state-and-recovery | issues | high | A missing route returns a bare Apache 404 with no site navigation, search, home link, or recovery action. F12 medium: HTTP failures provide no recovery path |
be-fast-and-stablegood-core-web-vitals | issues | high | Trace LCP was 973 ms and TBT 6 ms, but Lighthouse measured CLS 0.265, outside the good range. F06 high: Image sizing causes poor visual stability |
be-fast-and-stablevisual-stability | issues | high | Lighthouse measured CLS 0.265; all 100 result-page images and all 33 home images lacked explicit width/height. F06 high: Image sizing causes poor visual stability |
be-fast-and-stableefficient-main-thread | pass | high | The trace recorded one 56.25 ms long task and only 6.25 ms total blocking time over a 5.8 s capture. |
be-fast-and-stableefficient-resource-delivery | issues | high | The results page made 205 requests, loaded 173 images, and shipped seven parser-inserted high-priority stylesheets; 88 below-fold images were eager. F07 high: The results page eagerly ships excessive assets and unused code |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 85 KiB unused JS and 37 KiB unused CSS, including 95% of Bootstrap CSS and 86% of datatables.js. F07 high: The results page eagerly ships excessive assets and unused code |
be-inclusivenames-roles-labels | issues | high | All 100 result images lacked alt, 310 of 409 links had no text, Lighthouse found unnamed links, and the date input had no label. F09 high: Result imagery and controls lack accessible names and structure |
be-inclusivesufficient-contrast | issues | high | Lighthouse found repeated failures: primary teal buttons at 2.95:1, orange Register at 2.47:1, and heading teal at 2.8:1. F08 high: Core text and buttons fail WCAG contrast |
be-inclusivestructure-and-focus | issues | high | The homepage jumps from H5 to H1 to H6, Lighthouse flags heading order, and many focusable links have no visible outline or accessible name. F05 high: Keyboard and touch affordances are weak F09 high: Result imagery and controls lack accessible names and structure |
be-inclusivelegible-text | pass | medium | Body text wraps within the viewport with readable line lengths and no clipping on the sampled templates. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Reflow itself succeeds and scaling is allowed, but prominent result controls are only 38 px tall and dense unnamed icon links create poor touch/keyboard targets. F05 high: Keyboard and touch affordances are weak |
follow-best-practicesno-console-errors | pass | high | Lighthouse reported no browser errors logged to the console. |
follow-best-practicessound-document-and-assets | issues | high | Doctype and UTF-8 are valid, but 100/100 result images lack dimensions and Lighthouse flags a low-resolution ad asset. F06 high: Image sizing causes poor visual stability |
follow-best-practicesbrowser-platform-hygiene | issues | high | The page is excluded from BFCache by cache-control:no-store and Lighthouse recorded DevTools cookie issues. F10 medium: Caching policy disables back/forward cache |
be-discoverabletitle-and-description | issues | high | Descriptions exist, but titles are keyword-stuffed: 1,073 characters on the results page and similarly excessive on home, rather than concise unique descriptions. F11 high: Search and sharing metadata is malformed and keyword-stuffed |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Viewport and robots are valid, but 312 of 409 result links use href="#" and 310 links have empty text, undermining crawlable descriptive navigation. F11 high: Search and sharing metadata is malformed and keyword-stuffed |
be-discoverablecanonical-and-indexing-signals | issues | high | Pages return 200 and allow search indexing, but no canonical is present and /sitemap.xml returns an Apache 404. F11 high: Search and sharing metadata is malformed and keyword-stuffed |
be-discoverablestructured-and-shareable-metadata | issues | high | No JSON-LD exists; og:url and og:image are malformed with a single slash, and the generic keyword-stuffed og:title does not accurately summarize the result page. F11 high: Search and sharing metadata is malformed and keyword-stuffed |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS and nosniff are absent; PHPSESSID is neither Secure nor HttpOnly and has SameSite=None. F13 high: Baseline browser defenses and session-cookie flags are missing |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Seven third-party origins include Analytics and DoubleClick; analytics cookies last 400 days and 213,552 transferred bytes were third-party. No exposed secret was found. F14 medium: Tracking runs broadly on load with long-lived identifiers |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | medium | No permission prompt or authentication form appeared on the audited public pages; authentication is hosted on a separate secure subdomain outside this run. |
be-private-and-securedefensive-browser-policies | issues | high | X-Frame-Options is present, but HSTS, CSP/frame-ancestors, Referrer-Policy and Permissions-Policy are absent, while cookies use SameSite=None. F13 high: Baseline browser defenses and session-cookie flags are missing |
be-resilientprogressive-enhancement | pass | high | Raw HTML preserves 99% of rendered content on home and results, including title, H1 and description; neither page is a JS shell. |
be-resilientresilient-runtime-behaviour | issues | medium | Layouts remain in bounds, but FAQ disclosure state is inconsistent: all sampled questions report aria-expanded=true after one question is activated. F04 medium: FAQ disclosure state is not semantic or reliable |
be-resilientoffline-and-installable | not-applicable | high | This is a server-rendered lottery-results content site rather than an installed app; no manifest or controlling service worker exists, and installability is not needed for the core task. |
be-resilientnetwork-and-http-failure-states | issues | high | The representative HTTP failure state is a bare server 404 with no branded explanation, navigation, or retry/home recovery. F12 medium: HTTP failures provide no recovery path |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang="es" and the Spanish left-to-right content reads and lays out correctly on all sampled pages. |
be-internationalisedlocale-aware-data | pass | medium | Dates are rendered in natural Spanish, for example “17 de julio de 2026”, rather than an ambiguous numeric-only format. |
be-internationalisedtime-zone-correctness | not-applicable | high | The site shows local Venezuelan daily draw schedules and dates, with no cross-time-zone events, user-entered times, or DST-sensitive coordination. |
be-trustworthyno-dark-patterns | pass | medium | No confirmshaming, forced consent, preselected purchase, disguised control, or forced-continuity flow appeared on the audited public pages. |
be-trustworthyhumane-error-handling | not-applicable | medium | The audited public flow has only a date selector and no required multi-field form or validation-error flow to exercise. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | The only public input sampled is a date/results selector; address, payment, sign-in, and sign-up autofill assistance is not applicable on these pages. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | medium | No checkout, subscription, consent, or account-management flow exists on the audited public origin; login/register lead to a separate secure subdomain. |
be-sustainableoptimised-assets | issues | high | Images are predominantly WebP, but 100 result images omit dimensions, 74 omit responsive sources, and 88 below-fold images load eagerly. F07 high: The results page eagerly ships excessive assets and unused code |
be-sustainableno-wasteful-work | issues | high | The page eagerly fetches 173 images and ships largely unused Bootstrap, icon, and DataTables code despite a light main thread. F07 high: The results page eagerly ships excessive assets and unused code |
be-sustainablethird-party-and-media-budget | issues | high | Nine third-party requests transfer 213,552 bytes; Google Tag Manager alone transfers 179,180 bytes and multiple advertising/analytics origins run on load. F14 medium: Tracking runs broadly on load with long-lived identifiers |
be-agent-readystructured-agent-capabilities | not-applicable | high | This public results-content site exposes no transactional agent capability that needs WebMCP; raw content is already machine-readable, while robots policy explicitly limits major AI crawlers. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, or language task on this simple results site warrants on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten menu cycles, heap self size rose from 12,337,567 to 12,648,725 bytes (2.5%) rather than showing unbounded growth; live DOM remained stable. |
be-memory-efficientbounded-footprint | pass | medium | The sampled server-rendered page used about 12.3–12.6 MB heap self size with 978 live elements, proportionate to its long content page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Ten menu cycles left the live DOM at 978 nodes, created no intervals, and added only three transitionend listeners total rather than accumulating per cycle. |
Provenance
Canonical report: results/atomic/reports/0021-loteriadehoy_com.json
Report SHA-256: 298a0515b2b4e2543cd1851537765795fe370ac200cfd337d70775b473fe4eeb
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/loteriadehoy_com/2026-07-17T21-48-52-337Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/loteriadehoy_com/2026-07-17T21-48-52-337Z
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.