Manifest position 452 · CrUX rank bucket 1000
https://movie.eroterest.net
Coverage complete
Coverage-complete audit. Default headless Chrome was blocked with 403, so raw CDP evidence was repeated with a regular Chrome user-agent override; Lighthouse and raw fetches corroborated the accessible site response.
Attempts
2 / 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/reduce/contrast screenshot is visually identical to the light screenshot: white content surfaces and the fixed blue chrome do not retint. F01 medium: No user-preference-driven dark theme |
respect-user-preferencesrespects-reduced-motion | pass | high | CDP under prefers-reduced-motion: reduce found no active CSS/Web Animations or autoplay media on the five templates. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse reports 191 color-contrast failures, and the prefers-contrast: more capture does not increase contrast or otherwise adapt controls. F02 high: High-contrast usability is not preserved |
implement-natural-interactionsview-transitions | issues | high | CDP CSS inspection found no view-transition rules across the homepage and four route archetypes; navigation uses immediate document/hash swaps. F03 low: Route and state changes swap abruptly |
implement-natural-interactionsscroll-driven-animations | pass | high | DOM/CSS inspection found no scroll-linked effects and no JS scroll-animation behavior; the site does not implement the anti-pattern this check guards against. |
implement-natural-interactionsphysical-gestures | pass | high | Interaction inspection found native page scrolling and links/forms, with no custom pointermove/swipe handlers fighting platform gestures. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Long listing pages reach thousands of pixels, but CDP inspection and screenshots show static/fixed chrome with no scroll-state feedback or progress cue. F04 low: Navigation chrome does not respond to scroll position |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, anchored menu, or edge-positioned overlay exists on the five representative templates. |
provide-guided-navigationdirects-attention | pass | high | Selected search tabs and ranking-date navigation retain visible active-state changes and descriptive labels after navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Initial desktop/mobile screenshots show no popup, consent wall, or full-viewport interstitial obscuring content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No modal, transient popover, disclosure widget, or custom overlay exists on the representative templates. |
maximize-content-reduce-noisereduced-chrome | issues | high | The first desktop viewport reserves roughly 170px of blank advertising space before the search/list, while mobile devotes much of the first screen to login, ad, tabs, controls, and fixed navigation. F05 medium: Large ad slots and dense application chrome crowd the content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All five templates measured scrollWidth equal to innerWidth at 360px and screenshots show usable reflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | not-applicable | high | The observed cards occur in one consistent page container rather than being reused in independently sized containers; viewport reflow is covered separately. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The mobile CDP probe found 38 controls below 24px in at least one dimension on home and 44 on popular; focused search controls had outline-width 0 while only some anchors retained the UA outline. F06 high: Many targets are too small and focus is inconsistent |
support-core-task-successclear-purpose-and-primary-action | pass | high | Titles, descriptions, the “動画一覧” section, and prominent keyword search make the site purpose and next action explicit. |
support-core-task-successprimary-flow-completion | pass | high | The representative search journey reached a successful OL results page with a specific title and 1,747,596-result count, without an account wall. |
support-core-task-successclear-system-state-and-recovery | issues | high | A request to an unknown route returns a bare “404 Not Found” response with no site navigation, search, retry, or route back to the primary task. F07 medium: Failure states do not explain recovery |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured FCP and LCP at 4.35s (performance 0.73), outside the 2.5s good LCP range, although CLS and TBT were good. F08 high: Largest content appears too late |
be-fast-and-stablevisual-stability | pass | high | Lighthouse measured CLS 0.000163, well within the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Lighthouse measured total blocking time 0ms on the homepage load. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse identified 11 render-blocking resources with about 2.36s estimated savings, inefficient cache lifetimes, font-display delay, and a 42-request/521KiB load. F09 high: Render-blocking and cache policy delay content |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 48KiB unused CSS and 59KiB unused JavaScript on the homepage, alongside old general-purpose UI libraries. F10 low: The page ships avoidable unused CSS and JavaScript |
be-inclusivenames-roles-labels | issues | high | The CDP probe found the primary search text input and actress/password fields without labels; Lighthouse also reports five untitled iframes, an unnamed link, and invalid ARIA-required children. F11 high: Forms, frames, and media lack complete accessible names |
be-inclusivesufficient-contrast | issues | high | Lighthouse reports 191 failing color-contrast nodes across the dense listing UI. F12 high: Text and essential UI fail contrast requirements |
be-inclusivestructure-and-focus | issues | high | All five templates have zero <main> landmarks and start visible content at H3; Lighthouse reports heading-order and list-item structure failures, while several controls suppress focus outlines. F13 high: Heading, landmark, and focus structure is incomplete |
be-inclusivelegible-text | issues | high | Mobile screenshots show crowded 14px tags, tightly packed explanatory copy, and multiple rows of controls/content in narrow cards. F14 medium: Dense small text reduces reading comfort |
be-inclusivezoom-reflow-targets-and-media | issues | high | Although all templates reflow without horizontal overflow and permit scaling, dozens of controls are under 24px and Lighthouse reports five iframes without titles. F15 high: Touch and embedded-media accessibility is incomplete |
follow-best-practicesno-console-errors | issues | high | Lighthouse logged net::ERR_CONNECTION_REFUSED for a do-gasource.eroterest.net WebP resource. F16 medium: A production asset fails to load |
follow-best-practicessound-document-and-assets | issues | high | CDP found one or two images per audited template without width/height attributes; Lighthouse also reports malformed list/ARIA structure. F17 medium: Image sizing and document structure are unsound |
follow-best-practicesbrowser-platform-hygiene | issues | high | Rendered markup loads jQuery 3.4.1, jQuery UI 1.12.1, Bootstrap 4.4.1, and touch-punch 0.2.3; Lighthouse reports inspector issues and three BFCache blockers caused by no-store/cookie mutation. F18 medium: Stale dependencies and cache policy weaken platform hygiene |
be-discoverabletitle-and-description | pass | high | All five templates expose descriptive, route-specific titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Rendered probes found real href links, a scaling viewport meta tag, index,follow on public templates, and no 360px overflow; robots.txt allows the public routes. |
be-discoverablecanonical-and-indexing-signals | issues | high | All public templates return 200 and index,follow but expose no canonical URL; /sitemap.xml returns 404 while robots.txt is present. F19 medium: Canonical and sitemap signals are missing |
be-discoverablestructured-and-shareable-metadata | issues | high | The homepage raw HTML contains no JSON-LD/microdata, Open Graph, or Twitter Card metadata despite representing searchable video entities. F20 medium: Public entities lack structured and social metadata |
be-private-and-securesecure-transport-and-headers | issues | high | The 200 response sets PHPSESSID, uidhash, and uidhash3 without Secure, HttpOnly, or SameSite; PHPSESSID is retained for roughly five years and identifiers for roughly six years. F21 critical: Session and persistent identifiers lack cookie protections |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Every audited template contacts nine third-party origins, and the site creates multi-year uidhash identifiers plus localStorage synchronization during initial load. F22 high: Persistent identifiers and third parties load without minimisation evidence |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The account entry route offers only a password/passphrase input with no label, autocomplete token, required state, or WebAuthn/passkey alternative; no permission prompt fired on load. F23 high: Authentication relies on an unlabeled passphrase field |
be-private-and-securedefensive-browser-policies | issues | high | The successful document response has no CSP, HSTS, nosniff, frame protection, Referrer-Policy response header, or Permissions-Policy. F24 high: Core browser-enforced defenses are absent |
be-resilientprogressive-enhancement | pass | high | A regular-UA raw fetch returned 108,558 bytes of server-rendered HTML with the title, description, links, search form, and result content; core discovery is present without JS. |
be-resilientresilient-runtime-behaviour | pass | high | Five routes loaded with zero custom-CDP runtime exceptions; no cut-off dialog/menu or fragile overlay state was present. |
be-resilientoffline-and-installable | not-applicable | high | This is a public content index/aggregator rather than an app-like installable workflow; offline installation is not necessary for the primary search task. |
be-resilientnetwork-and-http-failure-states | issues | high | The representative 404 response is plain text only, with no navigation, search, retry, or explanation. F25 medium: HTTP failure handling collapses to a dead end |
be-internationalisedlang-dir-and-logical-properties | pass | high | Every audited template declares html lang="ja" and follows Japanese left-to-right document order; no bidirectional content surface was present. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited templates contain no user-facing currencies, localized dates, durations, calendars, or locale-sensitive numeric entry. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited templates expose no events, schedules, or user-facing timestamps requiring time-zone/DST handling. |
be-trustworthyno-dark-patterns | issues | high | The first desktop result grid begins with a promotional card using the same image/card placement and red headline treatment as content, without a clear ad label; large ad slots also precede results. F26 high: Advertising is visually blended with result content |
be-trustworthyhumane-error-handling | issues | high | The login passphrase and actress/search text controls are unlabeled and required=false; no aria-invalid/error-announcement structure was found in the rendered form states. F27 high: Forms lack native validation and accessible feedback hooks |
be-trustworthytrustworthy-input-assistance | issues | high | The login passphrase, search, and actress-name fields all expose an empty autocomplete value. F28 medium: Input fields omit autocomplete assistance |
be-trustworthysafe-commercial-and-account-flows | issues | high | The only observed account-entry method is a passphrase field, with no passkey, recovery, or reauthentication affordance visible on the representative login route. F29 high: Account entry lacks modern, proportionate authentication support |
be-sustainableoptimised-assets | issues | high | Homepage/list templates serve 32–54 images with no srcset in the sampled DOM; Lighthouse estimates image-delivery savings and CDP found missing intrinsic dimensions. F30 medium: Images are not responsively delivered |
be-sustainableno-wasteful-work | pass | high | Lighthouse measured 0ms TBT and no autoplay media; sampled pages settle without continuous animation or long-running foreground work. |
be-sustainablethird-party-and-media-budget | issues | high | The homepage loads 42 requests/521KiB and five iframes across nine third-party origins before the user selects a result. F31 medium: Third-party and embedded-media cost is high for the first view |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing action or transaction surface exists; this emerging capability is not required for a read/search content aggregator. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation/generation task is part of the primary search journey, so built-in AI would add complexity without established user value. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 cycles across the three homepage tabs and forced GC, DOM element count stayed 1,085, Performance Nodes fell by 3, JSEventListeners stayed 13, and no listeners were added; retained JS heap rose 264KiB only. |
be-memory-efficientbounded-footprint | pass | high | The post-GC homepage used 1.41MiB JS heap at baseline with 2,882 Performance Nodes, proportionate to a 1,085-element listing and five embeds. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Across 10 tab cycles, DOM elements stayed constant, Performance Nodes changed -3, JSEventListeners stayed at 13, and the addEventListener probe recorded zero additions. |
Provenance
Canonical report: results/atomic/reports/0452-movie_eroterest_net.json
Report SHA-256: 59a7232a92497507127c9db0c488a4977b1e0f2f5667fa597d686a51c3bf8a27
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/movie_eroterest_net/2026-07-26T11-13-04-322Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/movie_eroterest_net/2026-07-26T11-13-04-322Z
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.