Manifest position 36 · CrUX rank bucket 1000
https://jp.pornhub.com
Coverage complete
Coverage-complete report-mode audit. Anonymous browsing was exercised after essential-only consent and age confirmation. /video, /categories, /login and a deliberate missing path redirected to home; account creation, payment, upload, and authenticated management were not committed.
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 | Light and dark captures are byte-identical (141,208 bytes), and the CSS probe found no prefers-color-scheme or color-scheme rule. The site is usable but hard-coded dark rather than preference-driven. F01 medium: Hard-coded dark theme ignores the user color-scheme preference |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce the home page exposed zero active animations; no auto-advance was visible in the consent/age state. |
respect-user-preferencesrespects-contrast | pass | high | Controls and text remained visible in the prefers-contrast: more capture, including outlined consent and age-gate actions. |
implement-natural-interactionsview-transitions | issues | medium | Shared-session CSS inspection found no view-transition usage; route/state changes in the gate-flow video are abrupt. F02 low: Route and state changes are abrupt |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, entry reveal, or other scroll-linked motion was observed on the audited templates. |
implement-natural-interactionsphysical-gestures | pass | medium | The audited browsing surfaces use native scrolling and ordinary controls; no custom pointer-driven gesture that fights platform behavior was found. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The long home feed has a 5,348px scroll height, but CSS inspection found no scroll-state query, progress indicator, or shrinking/reactive header. F03 low: Long-feed chrome does not respond to scroll state |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, context menu, or popover surface requiring anchored positioning was exposed in the representative anonymous paths. |
provide-guided-navigationdirects-attention | issues | high | Home and redirected listing/category states have no h1 and no directional transition; focus probes land on an unnamed button with outline-style none. F04 medium: Navigation does not reliably guide attention or focus |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | medium | The initial consent and age gates cover content, but both are purpose-specific, clearly explained, and provide direct essential-only/enter/exit choices rather than an unrelated promotion. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The age/consent overlays are custom div structures: the shared-session probe found 0 dialog, popover, details, and role=dialog elements. F05 medium: Consent and age gates do not use semantic modal primitives |
maximize-content-reduce-noisereduced-chrome | issues | high | The home feed interleaves repeated advertising/removal upsells and 49 of 150 visible controls are under 24px, crowding the primary content. F06 high: Advertising and upsell chrome crowds the content feed |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All five 360x800 layout captures reported scrollWidth=clientWidth=360 and horizontalOverflowPx=0; viewport metadata is present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | CSS inspection across home and detail found no @container/container-type usage; reused cards rely only on page-level layout rules. F07 low: Reusable cards do not use component-level responsiveness |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe reported outline-style none on the first focusable control, and 49/150 home controls plus 33/76 detail controls measured under 24px. F08 high: Focus visibility and target sizes are inadequate |
support-core-task-successclear-purpose-and-primary-action | pass | high | The required age gate clearly states the site purpose and offers explicit enter/exit actions; the detail page exposes its title and player immediately after entry. |
support-core-task-successprimary-flow-completion | pass | medium | An anonymous user can accept essential cookies, confirm age, browse the feed, and reach a video detail with title and player controls. |
support-core-task-successclear-system-state-and-recovery | issues | high | A deliberate nonexistent URL resolves to the home feed without a visible not-found explanation or recovery state, making the failure indistinguishable from success. F09 medium: Missing routes do not expose a clear recovery state |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured home LCP 4.4s/CLS 0.697 and video LCP 6.1s/CLS 0.609; the trace measured video LCP at 21.8s in its longer capture. F10 high: Core Web Vitals are outside good thresholds |
be-fast-and-stablevisual-stability | issues | high | Lighthouse attributed CLS 0.608 primarily to the late cookie banner and also found unsized advertising media; the mobile layout primitive independently observed CLS 0.101. F11 high: Cookie and ad insertion causes severe layout shift |
be-fast-and-stableefficient-main-thread | pass | high | Trace summaries found no >50ms long tasks and 0ms trace TBT; Lighthouse TBT remained 50ms home and 160ms detail despite 2.2-2.9s total main-thread work. |
be-fast-and-stableefficient-resource-delivery | issues | high | Home loaded 172 requests/5.20MB with at least seven parser-inserted VeryHigh-priority stylesheets and multiple parser scripts; video loaded 132 requests/3.08MB. F12 high: Network delivery is heavy and render-blocking |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse failed unused CSS and unused JavaScript on both templates; home ships 40 scripts and detail 50 scripts. F13 medium: Large amounts of unused CSS and JavaScript ship on entry |
be-inclusivenames-roles-labels | issues | high | Lighthouse found untitled ad iframes on home and unnamed player buttons on detail; the detail image audit also found one image without alt. F14 high: Player controls and ad frames lack accessible names |
be-inclusivesufficient-contrast | pass | high | Neither Lighthouse run reported a color-contrast failure, and text/controls stayed legible in the increased-contrast capture. |
be-inclusivestructure-and-focus | issues | high | Home has no h1 and only a header landmark; Lighthouse found heading-order issues on detail, while focused controls can have outline-style none. F15 high: Heading, landmark, and keyboard-focus structure is weak |
be-inclusivelegible-text | pass | medium | Japanese gate copy and content titles are readable at desktop and mobile widths without clipping or horizontal overflow. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Mobile reflow succeeds, but dozens of controls are under 24px and the primary video elements expose no caption tracks. F16 high: Small targets and missing caption tracks limit comparable media access |
follow-best-practicesno-console-errors | issues | high | Lighthouse logged a null addEventListener exception; shared-session CDP captured repeated null.style TypeErrors from generated-lib.js. F17 medium: The page throws runtime exceptions |
follow-best-practicessound-document-and-assets | issues | high | Doctype/UTF-8 are valid, but image audits found 3 missing dimensions on home and 7 on detail, including the detail poster. F18 medium: Images lack intrinsic dimensions |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found deprecated Cast-control CSS, deprecated unload listeners, BFCache blockers, and inspector issues. F19 medium: Deprecated APIs and BFCache blockers remain |
be-discoverabletitle-and-description | issues | high | All inspected paths use the generic title “Pornhub” and omit meta descriptions; even the specific video page lacks a descriptive document title. F20 high: Titles are generic and meta descriptions are missing |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The viewport is mobile-friendly, but pages declare noindex,nofollow and home contains 18 javascript: links; Lighthouse failed crawlable anchors/robots. F21 high: Robots policy and JavaScript links prevent crawling |
be-discoverablecanonical-and-indexing-signals | issues | high | The video detail and redirected templates canonicalize to the home URL while also declaring noindex,nofollow, preventing stable page-level indexing signals. F22 high: Canonical and indexing signals collapse detail pages to home |
be-discoverablestructured-and-shareable-metadata | issues | high | The video detail exposes neither JSON-LD nor Open Graph metadata despite representing a rich media entity. F23 medium: Video pages lack structured and social metadata |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/HSTS are present, but CSP and nosniff are missing; the rp cookie is not Secure and uses SameSite=None. F24 high: Transport protection is incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Home made 101 third-party requests totaling 2.15MB across 11 origins, including Google Tag Manager and DoubleClick, even in the initial consent state. F25 high: The initial page has a large tracking footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No geolocation/notification prompt appeared on load, and the initial controls include a passkey continuation banner rather than a password-only prompt. |
be-private-and-securedefensive-browser-policies | issues | high | Clickjacking protection and HSTS exist, but CSP, Referrer-Policy, Permissions-Policy, and nosniff are absent. F26 high: Key browser-enforced defensive policies are absent |
be-resilientprogressive-enhancement | pass | medium | Raw responses contain 475-501KB of HTML, are not JS shells, preserve title and the video h1, and expose 32-36% rendered-word overlap without JavaScript. |
be-resilientresilient-runtime-behaviour | issues | high | Public /video, /categories, and /login navigation attempts resolve back to the home URL in the shared session without an explanatory state. F27 medium: Primary navigation routes silently fall back to home |
be-resilientoffline-and-installable | not-applicable | high | This media-streaming site is intrinsically network-dependent; no product intent indicating installability/offline playback was found. |
be-resilientnetwork-and-http-failure-states | issues | high | The deliberate nonexistent path silently becomes the homepage rather than showing a useful not-found/retry/recovery state. F28 medium: HTTP/network failure recovery is not explicit |
be-internationalisedlang-dir-and-logical-properties | issues | medium | html lang=ja is correct, but CSS inspection found no logical properties and 14 physical left/right declarations on home (130 on detail), while visible UI mixes untranslated English. F29 medium: Japanese localization is not layout-robust |
be-internationalisedlocale-aware-data | pass | medium | Visible counts and age text are localized (for example “6 年前”), and the page consistently declares Japanese. |
be-internationalisedtime-zone-correctness | not-applicable | high | No schedules, absolute timestamps, recurring events, or cross-zone date entry appeared in the representative paths. |
be-trustworthyno-dark-patterns | issues | medium | After essential-only consent, a persistent banner asks users to “Accept All Cookies”; the feed repeatedly inserts paid destinations and “remove ads” upsells among content. F30 medium: Post-consent nagging and paid destinations reduce trust |
be-trustworthyhumane-error-handling | not-applicable | high | The representative anonymous task exposes search but no required user-editable form with an invalid submission state; no safe validation workflow was available without account creation. |
be-trustworthytrustworthy-input-assistance | pass | medium | The visible search input has an accessible label and no address/payment/sign-up fields requiring autocomplete tokens were rendered; passkey continuation is offered separately. |
be-trustworthysafe-commercial-and-account-flows | pass | medium | Anonymous browsing does not force a subscription or payment commitment; login remains optional and the initial UI advertises passkey continuation. |
be-sustainableoptimised-assets | issues | high | Home has 33 images without srcset and 22 legacy-format images; detail has 16 without srcset, 13 legacy images, and one oversized avatar. F31 medium: Images are not responsively or format optimized |
be-sustainableno-wasteful-work | issues | high | The initial home state issues 172 requests and 5.20MB, including 38 XHR/fetch requests and duplicated GTM payloads before the primary content is used. F32 medium: Entry load performs wasteful background work |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 101 requests/2.15MB; TrafficJunky alone transfers about 939KB and GTM about 468KB, disproportionate before a user starts media. F33 high: Third-party scripts and ads exceed a proportionate entry budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing task or structured WebMCP capability is expected for this public adult-media browsing surface. |
be-agent-readyon-device-inference | not-applicable | high | No summarization, language-model, or other inference feature is part of the observed product experience. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 cookie-customization open/back cycles the collected heap was 39.39MB versus 37.41MB baseline (+5.3%); garbage collection completed and no unbounded pattern was demonstrated in this bounded run. |
be-memory-efficientbounded-footprint | pass | medium | The home page retained about 37.4MB in the baseline heap; this is substantial but proportionate to a script/ad-heavy media homepage and remained under 40MB after exercise. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither heap summary surfaced Detached* constructors among the largest retained constructor groups, and the ten-cycle run did not show explosive node growth. |
Provenance
Canonical report: results/atomic/reports/0036-jp_pornhub_com.json
Report SHA-256: 8ddbab1b8d6eb5dbf71cd40e7de6ff10f687f0f7037d89b2cf121dac23579a71
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/jp_pornhub_com/2026-07-17T23-49-08-392Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/jp_pornhub_com/2026-07-17T23-49-08-392Z
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.