Manifest position 808 · CrUX rank bucket 1000
https://es.erome.com
Coverage complete
Coverage-complete representative audit. The album route intermittently returned 503, which is recorded as a product finding rather than an audit blocker because all atomic checks were judged with direct evidence.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Home screenshots are pixel-identical in default and prefers-color-scheme: dark, and the rendered CSS exposes no preference-driven theme signal. The dark palette is usable, but it does not respond to the user preference. F-01 low: Theme is fixed rather than preference-driven. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, matchMedia was active and document.getAnimations() returned no active animations; no non-essential motion remained to suppress. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/prefers-contrast screenshot retained visible text, tabs, cards, and controls; Lighthouse contrast audit also passed. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found no view-transition CSS; navigation is conventional full-page replacement. F-02 low: Route and state changes have no View Transition treatment. |
implement-natural-interactionsscroll-driven-animations | pass | high | CSS/runtime probe found no animation-timeline and no active animations; the page uses native scrolling rather than main-thread scroll-linked animation. |
implement-natural-interactionsphysical-gestures | pass | high | Representative pages use native scrolling and ordinary links; DOM/CSS inspection found no custom pointer-driven gesture surface fighting platform behavior. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The Explore page is 4,978 CSS px tall, while screenshots and CSS inspection show fixed/static navigation with no scroll-state query or progress affordance. F-03 low: Long-feed navigation chrome is not scroll-state aware. |
provide-guided-navigationanchored-positioning | issues | high | The platform probe found three role=dialog controls, zero native dialogs/popovers, and no anchor-name or position-anchor CSS. F-04 low: Overlay controls use legacy custom dialogs without anchor positioning. |
provide-guided-navigationdirects-attention | pass | high | Explore provides an H1, active Popular/New tab treatment, persistent navigation, and the 404 recovery page presents clear recommendation cards. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Desktop and mobile first-load captures show content immediately with no overlay obscuring the page. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Rendered DOM contains three role=dialog elements but zero <dialog> and zero [popover] elements. F-05 medium: Overlays are custom role=dialog elements rather than native dialog/popover primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | Explore devotes the viewport primarily to the media grid; navigation is compact and does not frame every item with excessive chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, Explore and Login each reported scrollWidth=clientWidth=360 and zero horizontal overflow; both include a scalable viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found no @container rules, although the card grid is reused across listing and 404 contexts. F-06 low: Responsive components rely on global layout rules only. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe focused visible nav links and the menu button; computed outline style was none and box-shadow was none. F-07 high: Keyboard focus is not visibly indicated on primary navigation. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Landing page says “Compartir Fotos y Vídeos” with clear sign-in choices and Explore; the listing labels itself Explorar and foregrounds content. |
support-core-task-successprimary-flow-completion | issues | high | A representative album chosen from Explore returned a full-page 503 Service Unavailable during the mobile capture, preventing content viewing. F-08 high: The core Explore-to-album journey intermittently dead-ends at the CDN. |
support-core-task-successclear-system-state-and-recovery | issues | high | The captured 503 state only says no server is available and “We’ll be back soon”; it has no retry, back, Explore, or status link. F-09 high: Service-unavailable states provide no recovery action. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.6s, FCP 2.8s, Speed Index 5.0s, and performance 0.71 on Explore; the independent trace measured LCP 1.77s in a warmer/faster run, showing variability. F-10 high: Mobile LCP is outside the good range. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observer measured CLS 0.00138 on Explore and 0 on Login; Lighthouse measured CLS 0.00028. |
be-fast-and-stableefficient-main-thread | pass | high | Trace and layout observers found zero long tasks and 0ms TBT; Lighthouse measured about 20ms TBT. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse estimated 1,700ms savings from render-blocking resources. HAR and DOM confirm parser-inserted classic libraries.js/main.js without async/defer, plus three blocking stylesheets. F-11 high: Parser-blocking resources delay rendering. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 213KiB unused JS and 31KiB unused CSS; ad-provider.js was 92% unused and the two first-party stylesheets were 87-94% unused. F-12 medium: Most shipped CSS and substantial JavaScript are unused on the primary listing. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found two images without alt text in the disclaimer; the login probe found captcha and search inputs without labels or aria-labels. F-13 high: Some images and inputs lack accessible alternatives. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed and forced-colors capture retained high-visibility content and control boundaries. |
be-inclusivestructure-and-focus | issues | high | Lighthouse passed heading order and main landmark, but the direct focus walk found no outline or box-shadow on visible navigation controls. F-14 high: Focus visibility fails despite otherwise reasonable heading structure. |
be-inclusivelegible-text | pass | high | Desktop and mobile captures show readable headings, labels, and card metadata without text clipping at sampled breakpoints. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Mobile reflow had zero overflow, viewport allows scaling, and Lighthouse target-size/meta-viewport audits did not fail. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no logged browser errors. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found 16 images missing dimensions and 20 missing srcset; Lighthouse also flagged the unsized vertical logo and a low-resolution logo. F-15 medium: Several images omit intrinsic dimensions or responsive sizing. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported a deprecated unload listener and four BFCache failure reasons, including the unload handler and Cache-Control: no-store. F-16 medium: Deprecated unload handling and no-store policy block BFCache. |
be-discoverabletitle-and-description | pass | high | Explore has a descriptive unique title and populated Spanish meta description; Lighthouse passed both audits. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse passed crawlable anchors, robots.txt, link text, and viewport checks; DOM contains 134 anchors and a viewport meta tag. |
be-discoverablecanonical-and-indexing-signals | issues | high | Canonical, hreflang, robots meta, and successful status were present, but /sitemap.xml returned 404 while robots.txt only disallowed /cams/. F-17 low: The large public site has no sitemap endpoint. |
be-discoverablestructured-and-shareable-metadata | issues | high | The metadata probe found zero JSON-LD blocks and zero Open Graph/Twitter tags on Explore. F-18 medium: Listing pages expose no structured data or social-preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers evidence shows no CSP or nosniff. Cookie evidence found analytics cookies without Secure, SameSite=None, and 400-day expiry; session/XSRF cookies also use SameSite=None. F-19 high: Transport is HTTPS, but CSP and cookie posture are weak. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture observed 35 non-host origins and active Google Tag Manager/Analytics. HAR shows GTM as the largest resource at 153KB plus two ad-network scripts. F-20 high: Tracking and ad code load by default with a broad origin footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The sign-in form contains email/password/captcha, no autocomplete=webauthn, and no evidence of WebAuthn, although third-party OAuth choices are available. F-21 medium: Email authentication is password-only and does not offer passkeys. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence found no X-Frame-Options or CSP frame-ancestors, no Referrer-Policy, and no Permissions-Policy; HSTS was the one strong defense present. F-22 high: Clickjacking and privacy-enforcement headers are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability capture found 100% rendered-content coverage in raw HTML, no empty SPA shell, and title/H1/description present without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | The SSR listing and navigation rendered coherently at desktop/mobile and the sampled menu/header remained within viewport bounds. |
be-resilientoffline-and-installable | issues | high | /manifest.json declares standalone display and icons, while the service-worker probe found zero registrations and no controller. F-23 medium: The app advertises installability but has no service worker or offline fallback. |
be-resilientnetwork-and-http-failure-states | issues | high | The album capture produced a generic English 503 page with no retry or preserved navigation, unlike the useful 404 page that retains content recommendations. F-24 high: Network/service failure falls through to an unbranded, non-actionable error document. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The page correctly declares lang=es and 17 hreflang variants, but CSS inspection counted 1,436 physical left/right/width/height declarations versus only two logical-property uses; dir is implicit LTR. F-25 medium: Localized markup is correct, but CSS is overwhelmingly physical-direction based. |
be-internationalisedlocale-aware-data | not-applicable | high | No locale-sensitive data surface was present in the representative paths. |
be-internationalisedtime-zone-correctness | not-applicable | high | No temporal workflow was present in the representative paths. |
be-trustworthyno-dark-patterns | pass | high | Sampled landing, Explore, Login, FAQ, and 404 surfaces show direct labels, visible password recovery, and no confirmshaming, forced continuity, or preselected consent. |
be-trustworthyhumane-error-handling | issues | high | Invalid login submission focused email but exposed English “Please fill in this field” messages on a Spanish page, with no aria-invalid, aria-describedby, role=alert, or aria-live region. F-26 medium: Form errors rely on browser bubbles and are not localized or announced inline. |
be-trustworthytrustworthy-input-assistance | issues | high | The email and password controls have empty autocomplete values, captcha is unlabeled, and the only explicit autocomplete setting disables search autofill. F-27 medium: Sign-in inputs omit autofill tokens. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The sampled sign-in surface clearly labels methods, exposes password recovery and registration, and makes no pricing/subscription commitment; no checkout was present. |
be-sustainableoptimised-assets | issues | high | Images evidence found 37 legacy-format images, zero modern-format images, 20 missing srcset, and 16 missing dimensions. F-28 medium: The media listing does not use modern responsive image delivery consistently. |
be-sustainableno-wasteful-work | issues | high | GTM (153KB), ad-provider.js (52KB), and tsyndicate (24KB) are among the largest transfers; Lighthouse reports 45-92% of these scripts unused. F-29 medium: Large non-core scripts consume bandwidth despite little route usage. |
be-sustainablethird-party-and-media-budget | issues | high | HAR recorded 459KB across 59 requests; three analytics/ad scripts account for roughly half the transfer, while tracker capture identified GTM and Analytics. F-30 medium: Third-party scripts dominate more of the initial budget than the content needs. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No WebMCP or agent tool surface was expected for the sampled content-browsing routes. |
be-agent-readyon-device-inference | not-applicable | high | No on-device inference use case was present in the sampled routes. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten bottom/top feed traversals, heap changed from 147,187 to 147,743 nodes (+0.38%) and 8,294,059 to 8,300,828 bytes (+0.08%); closure count stayed exactly 6,288. |
be-memory-efficientbounded-footprint | pass | high | Explore heap was about 8.3MB self-size with 147k nodes for a 100-image feed, proportionate to the rendered surface and stable after exercise. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after heap summaries show stable closures (6,288), arrays (3,409), and sets (30), with no Detached* constructor among top retained constructors. |
Provenance
Canonical report: results/atomic/reports/0808-es_erome_com.json
Report SHA-256: 2faac8b7450654e5e069d9f310e2e1a89ee60377eb365f2639edd89febb1d5d0
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/es_erome_com/2026-07-23T04-05-24-945Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/es_erome_com/2026-07-23T04-05-24-945Z
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.