Manifest position 809 · CrUX rank bucket 1000
https://www.tokyomotion.net
Coverage complete
Atomic coverage complete across 58 checks and four representative public templates plus an error-state probe.
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 | Screenshot under dark preference and computed styles show color-scheme: normal and the same light rgb(236,236,236) body surface. F01 high: Honours prefers-color-scheme: a usable dark mode exists and is driven by the user's preference (color-scheme / prefers-color-scheme / light-dark()), not hard-coded light only. |
respect-user-preferencesrespects-reduced-motion | pass | high | The reduced-motion probe matched the emulated preference and found zero active animations on the entry page. |
respect-user-preferencesrespects-contrast | issues | high | Axe found 118 serious color-contrast failures; the high-contrast capture provides visual corroboration. F02 high: Honours prefers-contrast / forced-colors: controls, text and scrollbars remain visible under high-contrast preferences. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found no authored view-transition CSS, and route changes are full abrupt document navigations. F03 high: State and route changes use View Transitions (including same-document, cross-document and scroll-driven/staggered) rather than instant, jarring swaps. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, entry reveal, or other scroll-linked motion was present on the representative pages, so there is no scroll-driven effect to implement. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No carousel, swipe, pull-to-reveal, or other gesture-driven control was present in the representative browsing and signup surfaces. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The long listing pages use static navigation chrome; CSS/DOM inspection found no scroll-state or progress treatment to orient users. F04 medium: Sticky/affixed UI reacts to scroll state and position (e.g. the new scroll-state(scrolled) query, shrinking headers, progress indicators) so chrome responds to position instead of static or JS-driven toggling. |
provide-guided-navigationanchored-positioning | issues | high | Language and login overlays are Bootstrap-style div modals; the probe found zero popover/dialog elements and no anchor-positioning implementation. F05 high: Tooltips, popovers and menus use CSS anchor positioning (with fallback positions) so they stay attached and reposition correctly rather than being manually positioned. |
provide-guided-navigationdirects-attention | issues | medium | Route and modal navigation provides no directional transition, highlight, or authored view-transition cue for the moved context. F06 medium: Navigation and in-page jumps guide attention (highlight effects, scroll/carousel markers, directional transitions, drill-down and drawer navigation) so the user can follow where focus moved. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The rendered DOM/CSS contains fixed, z-index 9999 third-party video-ad slider chrome and the screenshots show advertising competing with the content. F07 high: No intrusive pop-ups, interstitials or banners that obscure content on load; overlays are dismissible and content-first. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The page uses custom div-based .modal overlays and manual Bootstrap dismissal; zero dialog, popover, or details elements were found. F08 high: Overlays and rich controls use the right primitive: popover (with declarative light-dismiss) for transient UI, dialog for modal flows, details for disclosure, native-but-branded selects and pickers, rather than ad-hoc divs. |
maximize-content-reduce-noisereduced-chrome | issues | medium | First-viewport screenshots show dense toolbars, filters, ad placements, and borders competing with the video content. F09 medium: Minimise non-content chrome and borders so the content is the focus, not the application frame; expressive/decorative visuals serve the content rather than crowd it. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360px, home, videos, and video-detail overflow by 540-555px (scroll widths 900-915px). F10 high: Layout adapts to narrow viewports with no horizontal overflow and no fixed pixel widths forcing a desktop layout on mobile; viewport meta present; fluid scaling and intrinsic sizing rather than brittle breakpoints. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | CSS inspection found zero container-query rules; reused listing components retain a desktop-width layout and cause mobile overflow. F11 medium: Components adapt to their container with container queries (incl. anchored container queries) and content/state-based styling where reused at different sizes, not only global viewport breakpoints. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focused navigation link computed to outline none 0px, and the target probe found multiple visible controls only 19px tall. F12 high: Touch targets are adequately sized and hover-only affordances have a non-hover fallback, and keyboard focus is visible, so the UI works for touch, pointer and keyboard alike. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The title, primary Videos/Photos navigation, current content grids, and descriptive thumbnail links make the browsing purpose and next action clear. |
support-core-task-successprimary-flow-completion | pass | high | The representative browse journey proceeded from home to the videos listing and a video detail URL without an account wall or dead end. |
support-core-task-successclear-system-state-and-recovery | issues | high | Submitting the empty signup exposed no validation messages, invalid controls, alerts, or recovery guidance; an unknown route falls through to Chrome’s bare HTTP 404 page. F13 high: Loading, empty, success, error, offline, and partial-completion states are visible and actionable; users can retry, undo, cancel, go back, or continue without losing context. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.1s and CLS 0.107, outside good thresholds, despite TBT 0ms. F14 high: Core Web Vitals are in the good range: LCP is fast, interaction latency (INP) is low, and CLS is minimal; work is prioritised and deferred sensibly. |
be-fast-and-stablevisual-stability | issues | high | The mobile video detail layout observer measured CLS 0.172 with a dominant late shift of 0.143. F15 high: No cumulative layout shift from late content (images, banners, fonts) that arrives without reserved space. |
be-fast-and-stableefficient-main-thread | pass | high | The trace recorded one 61.81ms long task and only 11.81ms total blocking time; Lighthouse reported 0ms TBT. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR shows six parser-inserted VeryHigh-priority stylesheets plus a synchronous parser-inserted jQuery 1.11.1 script in the critical path. F16 high: Critical resources are delivered efficiently: cache headers are useful, render-blocking chains are short, fonts do not block or shift text, HTTP delivery is modern, and network dependency trees do not delay the main content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | 56 of 58 requests and 868,870 of 886,697 transferred bytes were classified as third-party, including multiple ad scripts and legacy jQuery. F17 high: The page does not ship large unused or duplicated JavaScript/CSS, avoidable legacy bundles, or third-party code that dominates the load without user value. |
be-inclusivenames-roles-labels | issues | high | Axe found an unnamed search link and three untitled iframes; the signup probe also found unlabelled search/select controls. F18 high: Interactive elements have accessible names, correct roles, and form fields have labels; images have alt text where meaningful; canvas/expressive content is exposed to assistive technology. |
be-inclusivesufficient-contrast | issues | high | Axe reported 118 serious color-contrast failures on the home page. F19 high: Text and essential UI meet WCAG colour-contrast minimums against their background. |
be-inclusivestructure-and-focus | issues | high | There is no h1 or main landmark, list semantics fail axe, and keyboard focus on the sampled navigation link has no visible outline. F20 high: Heading and landmark structure is logical, focus order follows reading order, keyboard focus is always visible, and interactive state survives DOM moves. |
be-inclusivelegible-text | issues | medium | The 360px page remains 915px wide, forcing lateral panning and cramped scaled content rather than readable reflow. F21 medium: Text is legible and inclusively rendered: comfortable line layout, precise alignment, stable rendering across mixed fonts, no clipping or cramped wrapping that harms comprehension. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Axe reports a critical meta-viewport text-scaling failure and Lighthouse reports target-size failure; major pages also fail narrow reflow. F22 high: The experience remains usable when zoomed or reflowed, touch targets are large enough, media has captions or equivalents where needed, and the viewport does not prevent user scaling. |
follow-best-practicesno-console-errors | issues | medium | Lighthouse errors-in-console failed with one recorded console error. F23 medium: The page loads without console errors or uncaught exceptions. |
follow-best-practicessound-document-and-assets | issues | high | Although doctype and UTF-8 are valid, all 25 inspected images lack width/height and srcset, and all use legacy GIF/JPEG formats. F24 high: Valid doctype and charset, images sized with correct aspect ratio, no deprecated APIs misused, and CSS/HTML are well structured and not needlessly repetitive. (HTTPS, CSP and permission hygiene are judged under be-private-and-secure, not here.) |
follow-best-practicesbrowser-platform-hygiene | issues | medium | Lighthouse failed inspector-issues and BFCache audits; the page also loads jQuery 1.11.1 and legacy Font Awesome 4.1. F25 medium: The page uses the platform cleanly: no deprecated APIs, no avoidable BFCache blockers, no broken source maps or inspector issues, no stale vulnerable libraries, no paste-prevention on inputs, and no notification/geolocation prompts on load. |
be-discoverabletitle-and-description | pass | high | The entry page has the descriptive title “Free Porn Videos - TOKYO Motion” and meta description “Free Japanese Porn Videos”. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The viewport disables text scaling per axe, and all language-option links resolve to the non-crawlable same-page # URL. F26 high: Links are crawlable (real href), there is a viewport meta tag, robots does not block indexing, and link text is descriptive. |
be-discoverablecanonical-and-indexing-signals | issues | high | The canonical is malformed as /https%3A%2F%2Fwww.tokyomotion.net and /sitemap.xml returns HTTP 404, despite index/follow robots. F27 high: Public pages expose the indexing signals search engines need: successful HTTP status, canonical URL when appropriate, hreflang for localized variants, robots/sitemap consistency, and no accidental noindex/noarchive policy. |
be-discoverablestructured-and-shareable-metadata | issues | high | The video/content homepage exposes zero JSON-LD blocks and no Open Graph metadata despite representing rich media entities. F28 high: Where the page represents an article, product, organization, event, place or other rich entity, structured data and share-preview metadata accurately describe the visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP, HSTS, nosniff, framing protection, Referrer-Policy, and Permissions-Policy are all absent; all four cookies lack Secure and use SameSite=None. F29 critical: Served over HTTPS with a sensible Content-Security-Policy and secure, SameSite cookies; no mixed content or obvious transport/header smells. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The load contacts 14 third-party origins including known Google trackers and opaque ad/tracking domains; third parties account for 868,870 transferred bytes. F30 critical: No over-collection of user data, no leaky third parties, and analytics/background data collection is minimised and batched rather than chatty or session-wide by default. |
be-private-and-securein-context-permissions-and-modern-auth | issues | medium | The public signup/login surface offers password-only authentication with no passkey/WebAuthn affordance and omits sign-in autocomplete tokens. F31 medium: Permission prompts are requested in context (not on load), and authentication uses modern, phishing-resistant methods (passkeys / WebAuthn) where relevant rather than passwords alone. |
be-private-and-securedefensive-browser-policies | issues | high | Header inspection found no HSTS, clickjacking defense, Referrer-Policy, Permissions-Policy, or CSP frame-ancestors protection. F32 critical: Browser-enforced defenses are configured where appropriate: HSTS, clickjacking protection (frame-ancestors / X-Frame-Options), Trusted Types for XSS-sensitive apps, origin isolation, privacy-preserving third-party cookie posture, and sensible Referrer-Policy / Permissions-Policy. |
be-resilientprogressive-enhancement | pass | high | Raw HTML returned 200 with 78% rendered-content coverage, title and description present, and no empty JS shell. |
be-resilientresilient-runtime-behaviour | issues | medium | Representative long pages render 540-555px beyond the mobile viewport, so runtime content and overlay positioning are not robust at a common edge condition. F33 medium: The page behaves robustly at runtime: overlays and menus never get cut off, DOM state survives moves, background work and async dependencies are sequenced and conditional rather than fragile, and initial visibility state is detected correctly. |
be-resilientoffline-and-installable | issues | medium | The media application provides no web app manifest or installable metadata; no offline fallback was exposed. F34 medium: Where the site is an app, it is installable (web app manifest) and offers an offline fallback and works on flaky networks. (Contextual: a brochure or intrinsically-online site may reasonably not need this.) |
be-resilientnetwork-and-http-failure-states | issues | high | A missing route displays Chrome’s generic HTTP ERROR 404 page with no branded explanation, navigation, search, or recovery links. F35 high: HTTP errors, network failures, timeouts and stale data states are handled intentionally: users see useful recovery options rather than blank screens, infinite spinners, broken shells, or misleading success states. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The page declares lang=en while prominently rendering Japanese titles and offers RTL languages through # links without a page direction strategy. F36 high: Correct lang and dir attributes, logical CSS properties (inline/block) rather than physical left/right, and translation-ready markup so the layout and reading order survive other languages and writing modes. |
be-internationalisedlocale-aware-data | not-applicable | medium | No dates, currencies, localized numbers, durations requiring formatting, or other locale-sensitive data were present in the audited public templates. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited templates expose no events, schedules, timestamps, recurring intervals, or other user-facing time-zone-sensitive concepts. |
be-trustworthyno-dark-patterns | issues | medium | Opaque third-party advertising scripts and fixed high-z-index ad chrome compete with content without an evident consent or preference surface. F37 medium: No deceptive design: no confirmshaming, forced continuity, disguised ads, or nagging consent walls; honest defaults; clear pricing and consent; easy reversal/cancel; predictable, declaratively-wired actions; and no hidden-text tricks (hidden content stays deep-linkable and indexable rather than used to deceive). |
be-trustworthyhumane-error-handling | issues | high | Empty signup submission produced no browser validation message, :invalid fields, alert role, or visible error state. F38 high: Forms prevent and recover from mistakes humanely: validate after interaction (not prematurely), give clear required-field feedback, announce errors accessibly, and signal invalid fields visibly rather than blaming the user. |
be-trustworthytrustworthy-input-assistance | issues | high | Signup username, password, confirmation, and email fields all have empty autocomplete values; login fields do too. F39 high: Input is assisted, not obstructed: correct autocomplete tokens so address, payment, sign-in and sign-up fields autofill, and inputs are highlighted/sized to help the user rather than trip them up. |
be-trustworthysafe-commercial-and-account-flows | issues | medium | Account creation and login are password-only, omit autocomplete/passkey support, and expose no modern reauthentication affordance. F40 medium: Checkout, subscription, consent, authentication and account-management flows are clear, reversible, and proportionate: pricing and commitments are visible, cancellation is findable, sensitive actions re-authenticate when appropriate, and users are not tricked into continuity. |
be-sustainableoptimised-assets | issues | high | All 25 audited images lack srcset and modern formats; 20 below-fold images are not lazy-loaded. F41 high: Images and decorative assets are optimised and served at appropriate resolutions; decorative pseudo-element imagery and heavy decorative images are resolution-optimised rather than oversized. |
be-sustainableno-wasteful-work | issues | high | The initial page performs 58 requests, 56 third-party, with duplicate ad-provider scripts and analytics before user interaction. F42 high: Background work and fetching are not wasteful: background processing is efficient and de-prioritised, and the lightest technique that achieves the result is preferred over heavy or redundant work. |
be-sustainablethird-party-and-media-budget | issues | high | Third-party resources consume 868,870 of 886,697 transferred bytes; scripts are 409KB and fonts 212KB on the entry page. F43 high: Third-party scripts, fonts, video, audio, animation and heavy media are proportionate to the user value they provide; autoplay or background media is avoided unless essential and resource use is cached or deferred where possible. |
be-agent-readystructured-agent-capabilities | not-applicable | high | This public video-browsing site exposes no transactional or productivity capability that needs WebMCP tooling; agent capability exposure is an emerging optional surface. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, translation, or other inference task was present where on-device AI would improve the audited core journey. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After ten login-modal open/close cycles, the heap summary rose from 9,023,564 to 10,511,868 bytes and from 167,313 to 187,182 nodes; this is a leak signal requiring retained-path confirmation. F44 medium: Repeating a representative interaction (open/close a modal, navigate a route and back, infinite-scroll a list) about 10 times does not grow retained heap without bound; what is allocated during the interaction is released when it ends. |
be-memory-efficientbounded-footprint | pass | medium | The baseline heap was about 9.0MB across 167,313 nodes, proportionate to this media listing and far below a browser-memory pressure level. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither heap summary listed a Detached* constructor among retained-size leaders, and repeated modal cycling did not surface a detached-DOM population in the summary. |
Provenance
Canonical report: results/atomic/reports/0809-www_tokyomotion_net.json
Report SHA-256: 95b37b4b59b94234d66a401f8de4e561771c204fffd1595617bc601d76bc2e09
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_tokyomotion_net/2026-07-23T04-15-18-836Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_tokyomotion_net/2026-07-23T04-15-18-836Z
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.