Manifest position 344 · CrUX rank bucket 1000
https://www.erome.com
Coverage complete
Atomic coverage complete across public landing, listing, login, FAQ, 404 and one localized listing. Authenticated upload/profile/account surfaces were not covered because no test credentials were supplied.
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 | medium | Desktop screenshots under default and prefers-color-scheme: dark are byte-identical, and the CSS probe found no color-scheme declaration or prefers-color-scheme rule. F01 low: The interface does not adapt its theme to the user’s color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned none and scroll behavior remained auto; there is no nonessential motion to suppress. |
respect-user-preferencesrespects-contrast | pass | high | The forced-colors/prefers-contrast screenshot preserves readable text, controls, selected tabs and focus boundaries; Lighthouse contrast passed. |
implement-natural-interactionsview-transitions | issues | high | The full stylesheet probe found no view-transition rules; the public listing navigates with ordinary full-page anchors. F02 low: Route and state changes use abrupt swaps rather than View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | The audited pages contain no scroll-linked animation to implement or migrate. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The representative public paths use native scrolling and ordinary activation, with no gesture-driven control. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The 5,016px mobile listing keeps static chrome and exposes no scroll-state/container or progress signal in the stylesheet probe. F03 low: The long feed has no scroll-position feedback or state-aware chrome. |
provide-guided-navigationanchored-positioning | issues | medium | DOM/CSS inspection found no anchor-name, position-anchor, or position-try rules, while navigation is implemented as custom/legacy menu chrome. F04 low: Menus and overlays use legacy manual positioning rather than anchored positioning. |
provide-guided-navigationdirects-attention | pass | high | The mobile screenshot clearly marks Explore, HOT as the selected tab, and card destinations with consistent visual grouping. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Desktop/mobile load screenshots show content immediately with no full-screen modal, consent wall, or blocking interstitial. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Rendered DOM contains a Bootstrap-style div.modal with role=dialog and no dialog, popover, or details elements. F05 medium: Transient and modal UI is built from generic divs instead of modern semantic primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | On mobile, content cards begin directly below compact navigation and dominate the 5,016px page; no application frame obscures the feed. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout at 360x800 reports scrollWidth=clientWidth=360 and horizontalOverflowPx=0 on Explore and Login. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The Explore stylesheet probe found no @container rules even though reusable feed cards and navigation appear at several widths. F06 low: Responsive components rely only on viewport styling rather than container-aware behavior. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The login focus probe reported outline:none and no box shadow for navigation links, the menu button, password field, submit button and footer links; several controls are 13–34px high. F07 high: Keyboard focus is not visibly indicated and several controls are too short for comfortable touch use. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The Explore H1, HOT/NEW tabs and immediately visible media grid make the public browsing purpose and next action clear. |
support-core-task-successprimary-flow-completion | pass | high | The server-rendered Explore listing exposes 134 real href links and public browsing works without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | The 404 route returns HTTP 404 with a Page not found explanation and alternative content; required login fields expose native validation messages. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 4.7s, Speed Index 16.4s and a 10.53s root-document response, despite a separate trace measuring LCP 1.53s; the variance itself indicates unreliable delivery. F08 high: Explore can load slowly under lab conditions. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout measured CLS 0.0019 on Explore and 0.0089 on Login, both well within the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded one 50.56ms task and only 0.56ms total blocking time; layout observers recorded no long tasks. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse reported about 110KiB cache-lifetime savings and 310ms render-blocking savings; the HAR captured 58 requests and 759,455 transferred bytes. F09 medium: Caching and render-critical delivery leave avoidable load cost. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 213KiB unused JavaScript, 31KiB unused CSS and 43KiB legacy JavaScript savings. F10 medium: The listing ships substantial unused and legacy code. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found two missing-alt images in the disclaimer; DOM inspection found the required captcha input has no associated label. F11 high: Some images and the CAPTCHA input lack accessible alternatives or labels. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast passed and the forced-colors screenshot remains legible. |
be-inclusivestructure-and-focus | issues | high | Focus probing found no visible outline on most links/buttons/inputs, while the login DOM visually says Login but exposes no H1/H2/H3. F12 high: Keyboard users cannot reliably see focus, and the login page lacks a semantic heading. |
be-inclusivelegible-text | pass | high | Mobile screenshots show unclipped headings, labels and card text with usable wrapping across 360px. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Viewport permits scaling, both tested paths reflow at 360px with no overflow, and Lighthouse target-size passed; no autoplay media is present on the listing. |
follow-best-practicesno-console-errors | pass | high | Lighthouse recorded zero browser console errors on Explore. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 18 images without width/height and 22 without srcset; Lighthouse also failed unsized-images. F13 medium: Many images omit intrinsic dimensions and responsive sources. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found an unload listener in libraries.js and four BFCache failure reasons. F14 medium: Deprecated unload handling prevents clean browser lifecycle behavior. |
be-discoverabletitle-and-description | pass | high | Home and Explore have descriptive unique titles and a nonempty meta description in rendered/server HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | All 134 Explore anchors have hrefs, viewport meta is present, robots.txt allows the audited routes, and Lighthouse crawlability/link text passed. |
be-discoverablecanonical-and-indexing-signals | issues | high | The live page declares x-default and en hreflang as https://dev.erome.com/explore; /sitemap.xml returned 503 during recon while robots allows the public site. F15 high: Locale indexing signals point English and default users at development hosts, and the sitemap was unavailable. |
be-discoverablestructured-and-shareable-metadata | issues | high | The Explore DOM probe found zero Open Graph tags and zero JSON-LD blocks despite a public media listing with named content. F16 medium: Public content pages lack social preview and structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show no CSP or nosniff; both Google Analytics cookies were set without Secure and all four cookies use SameSite=None. F17 high: Transport is HTTPS, but CSP and cookie protections are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture saw 31 non-page origins, including Google Tag Manager/Analytics plus ad-provider and tsyndicate requests; analytics cookies persist for 400 days. F18 high: The page exposes a broad advertising and analytics network surface. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No notification/geolocation prompt fired on load; sign-in offers Google, Reddit and Twitter federation in addition to email. |
be-private-and-securedefensive-browser-policies | issues | high | The main response lacks clickjacking protection, Referrer-Policy and Permissions-Policy in addition to CSP; only HSTS is present. F19 high: Several browser-enforced defenses are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 100% raw/rendered content coverage, with title, H1 and description available without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Public navigation and the mobile menu render within the viewport; the server-rendered feed remains usable without fragile client state. |
be-resilientoffline-and-installable | issues | high | A valid standalone manifest is present, but navigator.serviceWorker.getRegistration() returned null. F20 low: The app-like feed advertises installability but has no offline runtime. |
be-resilientnetwork-and-http-failure-states | pass | high | The HTTP 404 path provides a clear recovery page and the intermittent 503 response provides an explicit Service Unavailable message rather than a broken shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The English page advertises 16 localized alternates and Spanish correctly uses lang=es, but stylesheet inspection counted 313 left, 214 right and zero logical-property declarations. F21 medium: Localized pages are not built to adapt cleanly to bidirectional writing modes. |
be-internationalisedlocale-aware-data | pass | high | The Spanish alternate renders lang=es and a localized title (Inicio - Vídeo y Foto Porno Gratis), while the English page uses lang=en. |
be-internationalisedtime-zone-correctness | not-applicable | high | No dates, event times, schedules, or other time-zone-sensitive data appear on the representative public paths. |
be-trustworthyno-dark-patterns | issues | high | The first mobile row presents CAM GIRLS, AI CUM SLUT and AI JERK OFF as site chrome; DOM shows these route through /o/menu-* advertising redirects with no ad label. F22 high: Prominent advertising links are styled as first-party navigation without being identified as ads. |
be-trustworthyhumane-error-handling | pass | high | Empty required login fields are invalid only on validation and expose clear native “Please fill in this field” messages; password paste is not blocked. |
be-trustworthytrustworthy-input-assistance | issues | high | The required email and password inputs both expose an empty autocomplete value. F23 medium: Sign-in fields omit standard autocomplete assistance. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, paid continuity, or authenticated account-management flow was reachable in the public scope. |
be-sustainableoptimised-assets | issues | high | The image audit found 41 legacy-format images, no modern-format images, and 22 missing srcset. F24 medium: The image-heavy feed does not use modern responsive image delivery consistently. |
be-sustainableno-wasteful-work | pass | high | The 5-second trace shows negligible blocking work and the 759KB listing load contains no autoplay audio/video. |
be-sustainablethird-party-and-media-budget | issues | high | The page contacted 31 non-page origins and known trackers during a 759KB load before the user opened any media. F25 medium: Advertising and analytics consume a disproportionate share of the lightweight listing shell. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent or transactional tool surface was found; this emerging capability is contextual. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or inference task is part of the representative public experience; on-device AI is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten bottom/top feed cycles, heap self-size decreased from 8,332,814 to 8,323,607 bytes and DOM node count remained 1,142 in the same-window probe. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap is 8.33MB self-size for a 100-image feed, proportionate to the page content. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Baseline/post summaries show no Detached* constructor among top retained constructors; same-window DOM nodes remained 1,142 after ten cycles. |
Provenance
Canonical report: results/atomic/reports/0344-www_erome_com.json
Report SHA-256: 6eaf81cea09862e67605f1a9972cf24c06ba477d94bfc108cec704ec3bc51d87
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_erome_com/2026-07-20T02-38-29-583Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_erome_com/2026-07-20T02-38-29-583Z
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.