Manifest position 522 · CrUX rank bucket 1000

https://es.eporner.com

Coverage complete

Coverage-complete audit of the public age gate and representative support/legal templates. Explicit media content and authenticated account management were not entered; the legal age gate was respected.

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 / checkStatusConfidenceEvidence or reason
respect-user-preferences
respects-color-scheme
issueshighDOM/CSS probe found no color-scheme declaration or prefers-color-scheme rule; dark-emulation output is byte-identical in size to the default capture.
F01 medium: Theme is hard-coded rather than driven by the user’s color-scheme preference.
respect-user-preferences
respects-reduced-motion
issueshighUnder prefers-reduced-motion: reduce, the SVG still contains an indefinite 3-second animate element and no reduced-motion CSS is present.
F02 medium: The age-estimation indicator ignores reduced-motion.
respect-user-preferences
respects-contrast
issueshighThe platform probe found no prefers-contrast/forced-colors rules; the increased-contrast screenshot is visually unchanged, while Lighthouse also identifies a 3.83:1 text contrast failure.
F03 medium: The page has no high-contrast or forced-colors adaptation.
implement-natural-interactions
view-transitions
issueshighThe interaction video shows the registration surface appearing without a directional or same-document transition; CSS inspection found no view-transition usage.
F04 low: The primary state change is an abrupt custom-overlay swap.
implement-natural-interactions
scroll-driven-animations
not-applicablehighNo applicable feature or task was present.
implement-natural-interactions
physical-gestures
not-applicablehighNo applicable feature or task was present.
provide-guided-navigation
scroll-state-aware-chrome
issueshighThe 10,158px-high terms template has static header/chrome; CSS inspection found no scroll-state query, progress indicator, or scroll-driven state.
F05 low: Long policy pages provide no scroll progress or scroll-state-aware chrome.
provide-guided-navigation
anchored-positioning
not-applicablehighNo applicable feature or task was present.
provide-guided-navigation
directs-attention
passhighThe CTA overlay visibly dims the background and focus moves to the first registration input, making the change of attention apparent.
maximize-content-reduce-noise
no-intrusive-interruptions
issueshighTerms, privacy, and FAQ screenshots show a fixed banner covering the bottom lines of content; it says continued use accepts cookies and exposes only “[ X ]”.
F06 medium: The cookie notice persistently obscures mobile content and offers only dismissal/implied consent.
maximize-content-reduce-noise
semantic-dismissible-primitives
issueshighThe interaction frame shows a modal overlay, but the visible-state probe finds no dialog element or role=dialog; it is built with SimpleModal-style divs.
F07 high: The mandatory registration overlay is an ad-hoc modal without dialog semantics.
maximize-content-reduce-noise
reduced-chrome
issueshighFAQ begins with header plus a two-tile ad and ends under a cookie overlay; policy screenshots show content hidden behind persistent chrome.
F08 medium: Mobile support pages devote too much of the viewport to chrome, ads and overlays.
adapt-to-the-form-factor
responsive-no-horizontal-scroll
passhighLayout primitives report 0px horizontal overflow at 360x800 on both the entry and 10,158px terms page; viewport meta is present.
adapt-to-the-form-factor
component-level-responsiveness
issueshighCSS inspection found no @container/container-type usage across the reused age-card and content templates.
F09 low: Responsive behavior is only viewport-wide and lacks component-level adaptation.
adapt-to-the-form-factor
input-modality-aware
issueshighThe focus/geometry probe measured every footer link at 14px high; Lighthouse target-size reports less than the required 24px size/spacing.
F10 medium: Footer controls are too small for reliable touch input.
support-core-task-success
clear-purpose-and-primary-action
passhighThe first viewport plainly states the legal age gate and presents one visually dominant verification CTA plus a separate login action.
support-core-task-success
primary-flow-completion
issueshighThe age wall promises age verification and “no ID required,” but its CTA opens a “Register for free” account form before any age check, an undisclosed detour in the core journey.
F11 high: The “Get You Verified” action unexpectedly dead-ends at mandatory account registration.
support-core-task-success
clear-system-state-and-recovery
issueshighSubmitting the empty visible registration form reports only a password-length error, leaves all fields valid with no aria-invalid, and exposes no role=alert/live announcement.
F12 medium: Registration recovery state is incomplete and weakly associated.
be-fast-and-stable
good-core-web-vitals
passhighTrace reports LCP 1.41s, no long tasks and TBT 0; Lighthouse lab LCP is 2.2s with CLS 0 and performance score 96.
be-fast-and-stable
visual-stability
passhighBoth layout observers and Lighthouse report CLS 0; narrow screenshots show reserved, stable primary layout.
be-fast-and-stable
efficient-main-thread
passhighTrace and layout observers recorded no long tasks and total blocking time 0 during load.
be-fast-and-stable
efficient-resource-delivery
issueshighLighthouse identifies two synchronous scripts plus the stylesheet as render-blocking with up to 1,280ms estimated savings; the longest critical chain is 913ms.
F13 medium: Parser-blocking scripts and CSS delay the small age wall.
be-fast-and-stable
trim-unused-and-duplicate-code
issueshighLighthouse estimates 31KiB unused CSS (99.8%) and 35KiB unused JavaScript (84.9%) on this small gate.
F14 medium: The age wall ships mostly unused site-wide CSS and JavaScript.
be-inclusive
names-roles-labels
issueshighLighthouse flags the logo without alt; the registration form uses placeholder-only inputs with no labels, and the visible modal has no dialog role.
F15 high: Key images, modal structure and registration fields lack accessible names/relationships.
be-inclusive
sufficient-contrast
issueshighLighthouse measures #0a910a on #222 at 3.83:1, below the required 4.5:1 for the rendered 19.5px normal-weight text.
F16 medium: The green age-estimation text fails minimum contrast.
be-inclusive
structure-and-focus
issueshighLighthouse reports no main landmark and a UL containing a direct BR child; the DOM has only an H2 and no landmarks.
F17 medium: The age wall lacks a main landmark and H1, and its footer list is malformed.
be-inclusive
legible-text
issueshighThe terms screenshot shows dense 12.5px copy in a narrow column while the fixed cookie bar covers the current lines.
F18 medium: Long legal text is cramped and partially obscured on mobile.
be-inclusive
zoom-reflow-targets-and-media
issueshighThe 360px layouts do not overflow, but Lighthouse identifies multiple 14px-high footer targets with insufficient spacing.
F19 medium: Touch-target accessibility fails despite successful viewport reflow.
follow-best-practices
no-console-errors
passhighLighthouse best-practices scored 100 and reported no console-error or uncaught-exception audit failure.
follow-best-practices
sound-document-and-assets
issueshighThe entry image audit finds both images unsized; the FAQ audit finds all 23 images unsized and six missing alt values.
F20 low: Images lack intrinsic dimensions and some content images lack alternatives.
follow-best-practices
browser-platform-hygiene
passhighLighthouse best-practices scored 100; camera is not requested on load and remains behind an explicit Start camera action.
be-discoverable
title-and-description
issueshighDOM and Lighthouse show a title but no meta[name=description], producing an SEO audit failure.
F21 medium: The public age-verification entry has no meta description.
be-discoverable
crawlable-and-mobile-friendly
passhighReal href links, viewport metadata, permissive root robots rules and a valid sitemap were directly observed.
be-discoverable
canonical-and-indexing-signals
issueshighThe home probe finds no canonical or hreflang; an intentionally nonexistent URL returns HTTP 200 with the age wall.
F22 medium: The entry lacks canonical/localization signals and unknown URLs return false-success pages.
be-discoverable
structured-and-shareable-metadata
issueshighThe metadata probe found no Open Graph title/description/image and no JSON-LD.
F23 low: The public entry exposes no share-preview or structured metadata.
be-private-and-secure
secure-transport-and-headers
issueshighCSP only upgrades insecure requests; epcolor lacks Secure and uses SameSite=None, while EPRNS also uses SameSite=None.
F24 high: Transport is HTTPS, but CSP and cookie protections are insufficient.
be-private-and-secure
data-minimisation-and-third-parties
passhighTracker scan found no known tracker domains, secrets scan found no credentials, and the cold-load HAR is only 8 requests; the verification copy states image processing occurs on device.
be-private-and-secure
in-context-permissions-and-modern-auth
issueshighThe registration modal exposes social/password account options; source/probes show no WebAuthn/passkey affordance. Camera permission is at least deferred to an explicit button.
F25 medium: Account authentication offers federated/password paths but no phishing-resistant passkey path.
be-private-and-secure
defensive-browser-policies
issueshighHeader inspection finds no X-Content-Type-Options or Referrer-Policy; Permissions-Policy grants broad client-hint access and CSP lacks frame-ancestors/Trusted Types restrictions.
F26 medium: Defensive response policies are incomplete.
be-resilient
progressive-enhancement
passhighDiscoverability probes show 100% raw-HTML content coverage for the entry and terms page, with no JS shell.
be-resilient
resilient-runtime-behaviour
passhighThe exercised registration overlay remained centered and stable, and focus moved into the first form control after asynchronous loading.
be-resilient
offline-and-installable
not-applicablehighNo applicable feature or task was present.
be-resilient
network-and-http-failure-states
issueshighThe intentional nonexistent route returned HTTP 200 and the normal age-verification HTML instead of a 404/recovery page.
F27 medium: Unknown routes fail silently as a successful age-wall response.
be-internationalised
lang-dir-and-logical-properties
issueshighThe age wall and legal documents are English at es.eporner.com; the entry html lang is empty, while terms declares es despite English headings/body.
F28 high: Critical content is English on the Spanish host, and the entry has no language declaration.
be-internationalised
locale-aware-data
not-applicablehighNo applicable feature or task was present.
be-internationalised
time-zone-correctness
not-applicablehighNo applicable feature or task was present.
be-trustworthy
no-dark-patterns
issueshigh“Let’s Get You Verified” unexpectedly opens registration; support pages say continued use accepts cookies and offer only an X, with no reject choice.
F29 high: The age CTA conceals an account-creation requirement, and cookie consent is implied.
be-trustworthy
humane-error-handling
issueshighEmpty submit reports only a password-length message, uses no required attributes/aria-invalid, and does not expose the error as a live alert.
F30 high: Registration validation is neither field-complete nor accessibly announced.
be-trustworthy
trustworthy-input-assistance
issueshighLogin, password, confirmation and email fields all use autocomplete=off; none provide username, new-password or email tokens.
F31 medium: The signup form actively disables useful autofill.
be-trustworthy
safe-commercial-and-account-flows
issueshighThe gate forces registration before verification; the visible modal offers password/social registration but no passkey and no clearly labelled cancel action in the captured surface.
F32 medium: The account flow is disproportionate to the requested age check and lacks a modern, clearly reversible path.
be-sustainable
optimised-assets
issueshighThe FAQ image audit finds 23 unsized images, seven legacy-format assets and no responsive source data for content thumbnails; the entry uses an unsized GIF.
F33 low: Image delivery misses basic dimension and format efficiencies.
be-sustainable
no-wasteful-work
passhighThe entry makes 8 requests/277,872 bytes and trace/layout evidence recorded no long tasks or continuing main-thread load work.
be-sustainable
third-party-and-media-budget
passhighNo autoplay media or known trackers load on the gate; third-party-looking hosts are eporner.com subdomains and the total cold-load transfer is 278KB.
be-agent-ready
structured-agent-capabilities
not-applicablehighNo applicable feature or task was present.
be-agent-ready
on-device-inference
not-applicablehighNo applicable feature or task was present.
be-memory-efficient
no-leak-under-repeated-interaction
passmediumAfter one modal interaction the heap was 33,552,152 bytes/141,325 nodes; after ten attempts it was 33,798,066 bytes/143,707 nodes, only 0.7%/1.7% higher rather than repeated one-time growth.
be-memory-efficient
bounded-footprint
passmediumBaseline is 4.2MB; after loading the account and on-device age-model UI once, the retained heap plateaus near 33.8MB, proportionate to that feature.
be-memory-efficient
no-detached-dom-or-unbounded-listeners
passmediumHeap summaries show no Detached* constructor among top retained constructors and only small growth from one to ten repeated interactions.

Provenance

Canonical report: results/atomic/reports/0522-es_eporner_com.json
Report SHA-256: 95cff69e61c9c176841618781371aa7d21aab6c435c34e161ccf849c27e88ee3
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/es_eporner_com/2026-07-21T08-29-52-681Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/es_eporner_com/2026-07-21T08-29-52-681Z
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.