Manifest position 854 · CrUX rank bucket 1000
https://www.conectate.com.do
Coverage complete
Atomic coverage complete: all 58 catalog checks were directly judged or given a check-specific applicability rationale.
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-emulated screenshot is pixel-identical in layout and light surfaces to the default capture; the CSS feature probe found no prefers-color-scheme rule or color-scheme declaration. F01 medium: The site does not adapt to the user’s dark colour-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion emulation found no active animations/autoplay and CSS contains several reduced-motion guards. |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast: more screenshot is an effectively blank brown viewport, while the default capture contains navigation and the consent dialog. F02 high: The rendered interface does not survive increased-contrast emulation. |
implement-natural-interactionsview-transitions | issues | medium | The CSS/platform probe found no view-transition rules; representative pages are separate full document loads and the cinema accordion uses legacy Bootstrap collapse. F03 low: Navigation and state changes use abrupt legacy swaps rather than View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | The CSS probe found no animation-timeline usage and no active scroll-linked animation or scroll-handler effect to migrate. |
implement-natural-interactionsphysical-gestures | pass | high | Representative paths rely on native document scrolling and standard controls; no custom pointermove/swipe implementation that fights platform gestures was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | Desktop and mobile captures show a fixed, full-height header; the CSS feature probe found no scroll-state/container query or progress affordance on long pages. F04 low: The fixed navigation chrome does not respond to scroll position. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or free-floating popover requiring edge-aware anchor positioning was present on the representative paths; fixed navigation and in-flow accordions were assessed separately. |
provide-guided-navigationdirects-attention | pass | high | Descriptive navigation labels, category headings and the cinema selector provide clear destinations and maintain normal browser history. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop, mobile, category, article, search and 404 screenshots all open behind a viewport-blocking consent dialog. On mobile it occupies nearly the entire 360×800 viewport. F05 high: A consent interstitial obscures the full page before the user can read any content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection found event and consent overlays implemented as div[role=dialog], with no native dialog or popover element. F06 medium: Site overlays are custom div-based dialogs rather than native top-layer primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | Outside the separately reported consent wall, cinema and editorial screenshots devote the viewport primarily to content/cards rather than decorative application framing. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360×800 viewport the article layout reports scrollWidth 1165px, horizontal overflow of 805px, innerWidth 1165px and CLS 0.447. F07 critical: The representative article breaks mobile reflow with a desktop-width layout. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The CSS feature probe found no @container rules; the WordPress and cinema templates use global Bootstrap/grid breakpoints despite components appearing in main and sidebar contexts. F08 low: Reusable cards and navigation adapt only through legacy viewport layout rules. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Programmatically focusing the visible “Loterías” link produced outline "none" and box-shadow "none". F09 high: Keyboard focus is not visibly indicated on the primary navigation. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Titles/descriptions are specific across home, tourism, article and cinema templates; the cinema path opens with a clear “Seleccione un Cine” control. |
support-core-task-successprimary-flow-completion | issues | high | The consent wall appears before the homepage, category, article, search and 404 paths, preventing immediate access to articles, lottery information and recovery content. F10 high: Every primary content journey begins with a blocking consent detour. |
support-core-task-successclear-system-state-and-recovery | pass | high | Search results return a populated content listing and a nonexistent route returns an actual HTTP 404 with a branded recovery page. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured FCP 5.2s, LCP 5.6s, Speed Index 14.6s and Time to Interactive 20.2s (performance score 0.57). The raw-CDP trace corroborated an LCP of 2.34s under its lighter desktop condition. F11 high: Cold-load performance is outside the good Core Web Vitals range. |
be-fast-and-stablevisual-stability | issues | high | The article mobile layout observer recorded CLS 0.447, dominated by a 0.445 shift around 5 seconds. F12 high: The article template has severe mobile layout shift. |
be-fast-and-stableefficient-main-thread | pass | high | The raw-CDP trace recorded no >50ms long tasks and 0ms TBT; Lighthouse TBT was 200ms, below the poor threshold. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR captured 108 requests and 2.43MB. It identified eight parser-inserted VeryHigh-priority stylesheets plus synchronous head scripts, and many first-party CSS/JS assets without useful cache headers. F13 high: The critical path is crowded by blocking styles/scripts and weak caching. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 787KiB unused JavaScript and 99KiB unused CSS; examples include Taboola, ad stacks, Facebook, Chart.js, mediaelement and WordPress block/dashicon CSS. F14 high: Most shipped frontend code is unused on the homepage. |
be-inclusivenames-roles-labels | issues | high | Lighthouse and the DOM accessibility probe identified the Facebook, Twitter and Instagram icon-only anchors as focusable but unnamed. F15 medium: Social links have no accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured the footer link at 2.69:1 and several consent controls between 1.06:1 and 2.8:1, below the 4.5:1 text requirement. F16 medium: Text in the footer and consent interface fails WCAG contrast minimums. |
be-inclusivestructure-and-focus | issues | high | The homepage authored DOM has no content h1, while the loaded page exposes consent/vendor headings as multiple h1/h2 elements; the first visible navigation link has no focus indicator. F17 high: The content heading structure is displaced by the consent UI and visible focus is absent. |
be-inclusivelegible-text | pass | high | Representative desktop/mobile cinema and editorial captures use readable line height, clear headings and unclipped text where the template reflows. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At 360px the article is 1165px wide with 805px horizontal overflow, forcing two-dimensional scrolling and preventing normal zoom/reflow use. F18 critical: The article cannot reflow at a standard mobile width. |
follow-best-practicesno-console-errors | pass | high | Lighthouse recorded no browser console errors or uncaught exceptions. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found 4/8 images without dimensions, 5/8 without srcset, 5 legacy-format images and 3 below-fold images not lazy-loaded. Lighthouse also found low-resolution rendered images. F19 medium: Images and assets are not consistently sized for sound rendering. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse found no deprecated APIs and no BFCache blocker; no notification or geolocation prompt appeared on load. |
be-discoverabletitle-and-description | issues | high | Rendered DOM summaries show descriptive title/description pairs on home, category and article paths, but the representative ?s=playa search result has no meta description. F20 medium: Search results omit a meta description. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse passed crawlable links, descriptive link text, viewport and robots audits; robots.txt allows public content. |
be-discoverablecanonical-and-indexing-signals | issues | high | The WordPress home/category/article pages expose canonical URLs, but the separately rendered cinema listing DOM has no rel=canonical despite returning indexable content. F21 medium: The cinema template omits a canonical link. |
be-discoverablestructured-and-shareable-metadata | issues | high | Home and WordPress article templates contain JSON-LD, while the cinema listing has no JSON-LD and no canonical in its rendered head. F22 medium: The cinema listing lacks structured/share metadata despite representing a rich entity collection. |
be-private-and-securesecure-transport-and-headers | issues | high | The header primitive found no CSP, HSTS or X-Content-Type-Options. The FCCDCF cookie is not Secure, uses SameSite=None and lasts 390 days. F23 high: Transport is HTTPS, but key security headers and cookie flags are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe found 26 third-party origins and five known trackers. The HAR attributed 76 requests and 2.07MB to third parties, while the consent UI lists 210 partners. F24 high: The page has a disproportionate tracking and third-party footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt fired on any audited load and no authentication flow exists on this host; no client-side secret was detected. |
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. F25 high: Browser-enforced defensive policies are incomplete. |
be-resilientprogressive-enhancement | pass | high | Raw HTML returned 200 and retained 75% of rendered content vocabulary with title/description present; the site is not a JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Representative menu, accordion and page loads completed without console exceptions; the consent dialog remained within both desktop and mobile viewports. |
be-resilientoffline-and-installable | not-applicable | high | This is primarily a public content portal rather than an app-like workflow. A manifest exists, but offline installability is not required for the representative reading/search journeys. |
be-resilientnetwork-and-http-failure-states | pass | high | A fabricated missing URL returned HTTP 404 rather than a soft-404 or blank shell, with branded recovery content behind the global consent layer. |
be-internationalisedlang-dir-and-logical-properties | not-applicable | high | The portal is deliberately scoped to Dominican Spanish; representative content, navigation and lottery/cinema data target one locale and writing direction. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited scope is deliberately single-locale Dominican Spanish and does not offer locale switching or multi-currency user data entry. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative content is local to the Dominican Republic and exposes no cross-time-zone scheduling workflow. |
be-trustworthyno-dark-patterns | pass | high | The consent UI offers “Do not consent” and “Consent” with equal visual weight and also exposes management/close controls; no forced continuity or disguised commercial flow was observed. |
be-trustworthyhumane-error-handling | pass | high | The only primary form is a non-required GET search; it does not prematurely mark input invalid or expose a blame-oriented validation flow. |
be-trustworthytrustworthy-input-assistance | pass | high | The search control uses type=search and an aria-label; there are no address, payment, sign-in or sign-up fields requiring autofill tokens. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication or account-management flow exists on the representative www host paths. |
be-sustainableoptimised-assets | issues | high | Five of eight inspected images use legacy JPG/PNG, five lack responsive sources, three below-fold images are eager, and Lighthouse found low-resolution images scaled beyond their natural size. F26 medium: Image delivery wastes bytes and underserves some displays. |
be-sustainableno-wasteful-work | issues | high | The initial load makes 108 requests; large Taboola, DoubleClick, AdSense, prebid, Facebook, Chart.js and mediaelement payloads contribute to 787KiB estimated unused JS. F27 high: Advertising and plugin work is fetched eagerly regardless of immediate user value. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 2,071,584 of 2,432,957 transferred bytes (85%) and 76 of 108 requests, led by ad and recommendation vendors. F28 high: Third-party scripts dominate the page’s transfer budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The audited surface is a read-only editorial portal with no transactional agent-facing capability; emerging WebMCP tooling is not a required user outcome here. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model interaction is part of the site’s stated user journey; on-device inference is therefore an optional emerging opportunity. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 20 menu-trigger clicks, heap self-size rose only 62,681 bytes (0.19%); closures fell by 2 and arrays were unchanged, with no unbounded retained-growth signal. |
be-memory-efficientbounded-footprint | pass | high | The loaded advertising-heavy page retained about 32.2MB in the V8 snapshot; this is material but bounded and proportionate to the observed third-party stack. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The before/after summaries show no Detached* constructor among top retained constructors, stable closure count and negligible total growth after repeated menu interaction. |
Provenance
Canonical report: results/atomic/reports/0854-www_conectate_com_do.json
Report SHA-256: 2094738062605b55b61b14f4e370984d460ca81c0b028df87fd21cfda146ac12
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_conectate_com_do/2026-07-23T10-54-48-134Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_conectate_com_do/2026-07-23T10-54-48-134Z
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.