Manifest position 787 · CrUX rank bucket 1000

https://resultadosegundavuelta.onpe.gob.pe

Coverage complete

All 58 catalog checks were judged. The live deployment currently serves index HTML for hashed assets, causing a blank SPA; a successful Lighthouse snapshot also supplied evidence about the last renderable build.

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	Under prefers-color-scheme: dark the blank surface remains #f8f8f8; computed color-scheme is normal and the CSS contains no dark-mode media rule. F011 medium: The page has no system-driven dark theme.
respect-user-preferences `respects-reduced-motion`	issues	high	The reduced-motion probe matched reduce but found no prefers-reduced-motion CSS; global scroll-behavior remains smooth. F012 medium: Reduced-motion preference is not handled.
respect-user-preferences `respects-contrast`	issues	high	The rendered CSS applies outline:0!important to every element; no forced-colors/prefers-contrast rule was found and computed outlines are none. F013 medium: Global CSS suppresses focus outlines and contains no high-contrast adaptation.
implement-natural-interactions `view-transitions`	issues	high	No View Transition API usage or transition evidence is present; navigation either fails or swaps without a rendered continuity cue. F029 low: Modern navigation/interaction guidance is not implemented for this results SPA.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	This check is contextual and the inspected public results surface has no matching interaction or flow.
implement-natural-interactions `physical-gestures`	not-applicable	high	This check is contextual and the inspected public results surface has no matching interaction or flow.
provide-guided-navigation `scroll-state-aware-chrome`	issues	high	The long results experience provides no evidenced scroll-state-aware chrome or progress affordance. F030 low: Modern navigation/interaction guidance is not implemented for this results SPA.
provide-guided-navigation `anchored-positioning`	issues	high	The successful Lighthouse DOM shows an Angular Material menu trigger, with no native popover/CSS anchor positioning evidence. F031 low: Modern navigation/interaction guidance is not implemented for this results SPA.
provide-guided-navigation `directs-attention`	issues	high	No rendered navigation attention cues survive in the current app; the blank route offers no orientation. F032 low: Modern navigation/interaction guidance is not implemented for this results SPA.
maximize-content-reduce-noise `no-intrusive-interruptions`	pass	high	Desktop/mobile screenshots and Lighthouse DOM show no load-time interstitial obscuring content.
maximize-content-reduce-noise `semantic-dismissible-primitives`	pass	high	The successful Lighthouse DOM uses semantic button/menu roles through Angular Material and shows no ad-hoc modal overlay finding.
maximize-content-reduce-noise `reduced-chrome`	pass	high	The successful Lighthouse result view prioritizes the results surface; no advertising interstitial or excessive frame was found.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	Raw-CDP layout at 360x800 reports scrollWidth=clientWidth=360 and horizontalOverflowPx=0 with a valid viewport meta.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	DOM CSS includes max-width media queries while computed container-type is normal and no @container rule appears in captured CSS. F014 low: The CSS evidence shows viewport breakpoints but no component/container responsiveness.
adapt-to-the-form-factor `input-modality-aware`	issues	high	The global rule * { outline: 0 !important } removes focus indication from all controls; Lighthouse also found an unnamed menu button. F015 high: Keyboard focus is globally hidden.
support-core-task-success `clear-purpose-and-primary-action`	issues	high	The 20-second evaluate probe reports empty body text, zero headings, zero links, zero buttons and an empty app-root. F002 critical: No purpose, result, or next action is visible in the live page.
support-core-task-success `primary-flow-completion`	issues	high	Repeated desktop and mobile screenshots, DOM probes after 20 seconds, and direct requests show an empty <app-root>. Hashed JS, CSS and image URLs return the 16,591-byte index HTML with content-type text/html and CloudFront x-cache: Error, so the SPA cannot mount. F001 critical: The election-results application is currently a blank page, so its primary task cannot be completed.
support-core-task-success `clear-system-state-and-recovery`	issues	high	After 20 seconds the viewport remains blank and contains no recovery control or status message. F003 high: Asset failure produces no loading, error, retry, or fallback state.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured LCP 12,722 ms, FCP 4,874 ms, CLS 0.094 and TBT 72 ms, scoring performance 0.60. Current raw-CDP traces cannot paint the broken app at all. F008 high: The last successful Lighthouse render was slow: LCP 12.7 s and FCP 4.9 s.
be-fast-and-stable `visual-stability`	pass	high	Lighthouse measured CLS 0.094, within the good threshold, and the raw blank-state layout observer measured 0.
be-fast-and-stable `efficient-main-thread`	pass	high	Lighthouse measured TBT 72 ms; raw-CDP trace and layout observers recorded no long tasks in the current state.
be-fast-and-stable `efficient-resource-delivery`	issues	high	HAR hygiene flags missing cache headers for hashed JS/font assets; direct asset responses return index HTML instead of the requested MIME type. F009 medium: Static delivery is misconfigured and useful cache headers are absent on hashed assets.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	Lighthouse estimated 629 KiB unused JavaScript, including 517 KiB from main and about 127 KiB across GTM/gtag, plus 37 KiB unused CSS (90%). F010 medium: The successful build shipped substantial unused code.
be-inclusive `names-roles-labels`	issues	high	Lighthouse button-name identifies button#sidebarToggle with no visible text, aria-label, aria-labelledby or title. F016 medium: The menu toggle lacks an accessible name.
be-inclusive `sufficient-contrast`	pass	high	Lighthouse color-contrast audit passed on the successfully rendered mobile results view.
be-inclusive `structure-and-focus`	issues	high	Lighthouse landmark-one-main failed; captured CSS sets outline:0!important on every element. F017 high: The successful render had no main landmark, and focus visibility is removed globally.
be-inclusive `legible-text`	pass	high	Lighthouse accessibility was 0.92 and heading order passed; no text clipping finding was reported in the successful render.
be-inclusive `zoom-reflow-targets-and-media`	pass	high	The mobile Lighthouse viewport rendered at 412x823; viewport allows scaling and raw layout at 360px had no overflow.
follow-best-practices `no-console-errors`	issues	high	Lighthouse errors-in-console records blocked region1.analytics.google.com connections and failed analytics fetches caused by CSP. F018 medium: The application emits CSP and fetch errors.
follow-best-practices `sound-document-and-assets`	issues	high	JS/CSS/SVG paths currently return HTML. Lighthouse also flagged five unsized images, creating layout-shift risk. F019 high: Static assets are unsafely deployed and several images lack intrinsic dimensions.
follow-best-practices `browser-platform-hygiene`	issues	high	Lighthouse reports the large main bundle has no source map and records CSP inspector issues; BFCache itself passed. F020 low: Production debugging and inspector hygiene are incomplete.
be-discoverable `title-and-description`	issues	high	DOM has title ONPE - PRESENTACIÓN DE RESULTADOS and no meta[name=description]; Lighthouse meta-description failed. F021 medium: The title exists but the page has no meta description.
be-discoverable `crawlable-and-mobile-friendly`	issues	high	Raw HTML has no content links; Lighthouse found a pseudoLink anchor without href, and /robots.txt returns the SPA HTML with 52 syntax errors. F022 high: Core navigation and content are not crawlable.
be-discoverable `canonical-and-indexing-signals`	issues	high	The SEO probe found no canonical; /sitemap.xml and /robots.txt both return index HTML with status 200. F023 medium: Canonical, sitemap and valid robots signals are absent.
be-discoverable `structured-and-shareable-metadata`	issues	high	The SEO probe found zero Open Graph tags and zero JSON-LD blocks. F024 low: Election-result pages expose no structured data or social preview metadata.
be-private-and-secure `secure-transport-and-headers`	issues	high	Cookie audit found _ga and _ga_THMBN2T4BS without Secure, both SameSite=None and 400-day expiry. Header audit flags unsafe-inline/unsafe-eval. F025 medium: Analytics cookies are missing Secure and use SameSite=None for 400 days; CSP also permits unsafe-inline and unsafe-eval.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	HAR reports 9/15 requests and 289,128/316,075 transferred bytes third-party (91.5%); tracker audit identifies GTM and DoubleClick. F026 medium: Tracking dominates the network before any useful result appears.
be-private-and-secure `in-context-permissions-and-modern-auth`	not-applicable	high	This check is contextual and the inspected public results surface has no matching interaction or flow.
be-private-and-secure `defensive-browser-policies`	pass	high	Headers include HSTS preload, nosniff, SAMEORIGIN plus frame-ancestors, strict-origin-when-cross-origin and a restrictive Permissions-Policy.
be-resilient `progressive-enhancement`	issues	high	Raw HTML contains only an empty app-root; crawler evidence reports three raw content tokens and no h1, while the current JS assets fail to load as executable JavaScript. F004 high: Core election results are unavailable without successful JavaScript execution.
be-resilient `resilient-runtime-behaviour`	issues	high	Both / and /main/resumen remain empty when the hashed bundles are unavailable; no runtime shell survives. F005 high: The runtime has a single point of failure at application bootstrap.
be-resilient `offline-and-installable`	issues	high	The page probe found no manifest URL and sw=false. F006 low: The app has no manifest, service-worker controller, or offline fallback.
be-resilient `network-and-http-failure-states`	issues	high	Static asset failures are returned as HTTP 200 HTML and the page gives no failure state after 20 seconds. F007 high: Network and deployment failures collapse to a blank screen.
be-internationalised `lang-dir-and-logical-properties`	pass	high	The document declares lang=es; the public interface is Spanish and Lighthouse html-has-lang passed.
be-internationalised `locale-aware-data`	pass	high	The successful Lighthouse render presents the intended Spanish election-results locale; no conflicting locale formatting was observed.
be-internationalised `time-zone-correctness`	not-applicable	high	This check is contextual and the inspected public results surface has no matching interaction or flow.
be-trustworthy `no-dark-patterns`	pass	high	No purchase, subscription, consent wall, disguised ad or forced-continuity flow appears in the inspected results experience.
be-trustworthy `humane-error-handling`	not-applicable	high	This check is contextual and the inspected public results surface has no matching interaction or flow.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	This check is contextual and the inspected public results surface has no matching interaction or flow.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	This check is contextual and the inspected public results surface has no matching interaction or flow.
be-sustainable `optimised-assets`	pass	high	The visible application assets identified by Lighthouse are predominantly SVG and local WOFF2; no raster image oversizing finding was reported.
be-sustainable `no-wasteful-work`	issues	high	Third-party analytics accounts for 91.5% of captured bytes, while Lighthouse estimates 629 KiB unused JS and 37 KiB unused CSS. F027 medium: Most transferred bytes and much of the shipped code do not support the visible task.
be-sustainable `third-party-and-media-budget`	issues	high	GTM/gtag transferred 288,557 bytes while the current app showed no content; known trackers include GTM and DoubleClick. F028 medium: The third-party budget is disproportionate to a public results page.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	Agent-facing capability is emerging and no declared agent surface exists; absence is an opportunity, not a defect.
be-agent-ready `on-device-inference`	not-applicable	high	Agent-facing capability is emerging and no declared agent surface exists; absence is an opportunity, not a defect.
be-memory-efficient `no-leak-under-repeated-interaction`	not-applicable	high	The current app cannot mount and therefore exposes no real representative interaction to repeat; fabricating one would not test the product.
be-memory-efficient `bounded-footprint`	pass	high	Baseline heap summary is proportionate at 119,336 nodes and 4,827,050 self-size bytes for the current state.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	Baseline heap top constructors contain no Detached* population; the current failed mount has no repeating interaction or growing DOM.

Provenance

Canonical report: results/atomic/reports/0787-resultadosegundavuelta_onpe_gob_pe.json
Report SHA-256: abb6418f5551cdf0aed832e6de7a5952227354d571368642b9f5054801489db1
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/resultadosegundavuelta_onpe_gob_pe/2026-07-23T01-11-14-329Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/resultadosegundavuelta_onpe_gob_pe/2026-07-23T01-11-14-329Z
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.