Manifest position 167 · CrUX rank bucket 1000
https://pornone.com
Coverage complete
Coverage complete. Visual paths were consistently fronted by a jurisdictional biometric age gate; underlying server-rendered templates were inspected without bypassing it.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The CSS probe found no prefers-color-scheme rule; the page defaults localStorage to dark-theme rather than following the OS. The dark emulation produced the same fixed-dark age-gate rendering. F01 medium: System color preference is ignored |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce matched, the probe still found 13 running animations, including twelve infinite 1-second ping animations; the CSS contains no reduced-motion query. F02 medium: Reduced-motion preference does not stop continuous animation |
respect-user-preferencesrespects-contrast | issues | high | The contrast probe confirmed prefers-contrast: more while finding no prefers-contrast or forced-colors rules; Lighthouse separately found 17 color-contrast failures. F03 medium: No high-contrast or forced-colors adaptation |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection across the MPA templates found no view-transition-name or @view-transition usage, so moving from listing to detail is an abrupt document swap. F04 low: Route changes have no continuity cue |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | Applicability judged from recon and representative templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | Applicability judged from recon and representative templates. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The home page is over 15,000 CSS pixels tall, but CSS inspection found no scroll-state container queries or progress/orientation treatment. F05 low: Long listings provide no scroll-state-aware orientation |
provide-guided-navigationanchored-positioning | issues | high | Rendered DOM includes manually fixed ad and playlist overlays, while the CSS probe found no anchor positioning or fallback positions. F06 low: Custom overlays are manually fixed rather than viewport-aware |
provide-guided-navigationdirects-attention | issues | high | The listing/detail inspection found no directional transition, highlight, scroll marker, or other attention cue after route or in-page navigation. F07 low: Navigation does not visibly direct attention after a move |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The rendered DOM contains a fixed 410px video ad with z-index 9999 and webExperienceManager pop-under code bound to video links. This is additional to the jurisdictional age gate. F08 high: Fixed ad and pop-under code competes with core content |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Screenshots show a full-screen age-verification gate, but DOM inspection found a fixed div with no dialog role, aria-modal, labelled relationship, or native dialog/popover semantics. F09 high: The mandatory age gate is an inaccessible custom modal |
maximize-content-reduce-noisereduced-chrome | issues | high | The home probe counted 396 interactive elements and an iframe; rendered DOM also injects slider/native ad chrome around the content grid. F10 medium: Ad chrome and hundreds of controls overwhelm the listing |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360px visual viewport, layout metrics reported a 369px document width and 9px horizontal overflow on both home and detail. F11 medium: Mobile listing and detail templates overflow horizontally |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found no @container/container-type usage despite cards and ad widgets being reused in grids and side surfaces at different widths. F12 low: Reusable cards adapt only through viewport breakpoints |
adapt-to-the-form-factorinput-modality-aware | issues | high | The home probe found 18 visible interactive elements below 24px in at least one dimension; Lighthouse also reports accessibility failures. F13 medium: Some interactive targets are too small |
support-core-task-successclear-purpose-and-primary-action | pass | high | Recon shows descriptive titles/headings and direct video-card links; the age gate itself has one visually dominant action. |
support-core-task-successprimary-flow-completion | issues | high | All visual captures were replaced by a mandatory “AI face check” gate linking to an external partner. No non-biometric verification option, exit, or alternative access route is offered. F14 high: Core content has a biometric-only access path in this region |
support-core-task-successclear-system-state-and-recovery | issues | high | The first viewport exposes only “Start age verification”; it has no cancel, help, retry explanation, unsupported-camera path, or alternative verification control. F15 medium: The age gate offers no recovery or alternative state |
be-fast-and-stablegood-core-web-vitals | pass | high | Lighthouse home measured LCP 2.458s, CLS 0.043 and TBT 11ms; trace measured LCP 1.439s with no long tasks. |
be-fast-and-stablevisual-stability | pass | high | Observed CLS remained 0.043 on home and 0.057 on detail, both below the 0.1 good threshold. |
be-fast-and-stableefficient-main-thread | pass | high | Home/detail traces reported zero long tasks and zero total blocking time; Lighthouse TBT was 11ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse transferred 2,943 KiB and estimated 1,270 KiB cache savings; HAR recorded 71 requests, while image delivery and render-blocking audits also failed. F16 medium: Resource delivery is heavier and less cacheable than needed |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 170 KiB unused JavaScript and 11 KiB unused CSS on home, while third-party scripts dominate request cost. F17 medium: Unused JavaScript and CSS ship on the entry path |
be-inclusivenames-roles-labels | issues | high | Lighthouse found an aria-allowed-attr failure; the image audit found 20 images without alt text, and the custom gate has no modal role or accessible modal state. F18 high: Accessible names, roles, and alternatives are incomplete |
be-inclusivesufficient-contrast | issues | high | Lighthouse found 17 failing contrast nodes on home and 4 on login. F19 high: Text and controls fail minimum contrast |
be-inclusivestructure-and-focus | issues | high | The home outline starts with four H2 sections before its H1; Lighthouse found four positive tabindex values on login, forcing an authored order that can diverge from reading order. F20 medium: Heading and focus order are not logical |
be-inclusivelegible-text | pass | high | Age-gate screenshots at desktop/mobile show readable sizing, line lengths and spacing without clipping. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The detail probe found two videos with zero track elements, and the home probe found 18 sub-24px interactive targets. F21 high: Video has no caption track and small targets remain |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no logged errors. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse found an incorrectly stretched RTA image and unsized images; the image audit found 12 missing dimensions and 15 oversized resources. F22 medium: Image dimensions and aspect ratios are unsound |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse logged a Cookie issue in DevTools; login also had three BFCache failure reasons. Source maps, paste prevention, prompts, and deprecated APIs otherwise passed. F23 medium: Browser hygiene issues remain |
be-discoverabletitle-and-description | pass | high | Home, login and detail DOM each contain unique descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable anchors, and the probe counted 16 javascript: links, including live cards and “Show More”. F24 medium: Sixteen links are not crawlable |
be-discoverablecanonical-and-indexing-signals | pass | high | HTTP status, canonical and 12 hreflang links pass on representative pages; robots.txt points to live sitemap indexes and does not block core pages. |
be-discoverablestructured-and-shareable-metadata | pass | high | Detail includes VideoObject and BreadcrumbList JSON-LD plus Open Graph metadata matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but headers inspection found no CSP, HSTS, nosniff, clickjacking, Referrer-Policy, or Permissions-Policy. All 10 observed cookies lacked Secure and several use SameSite=None. F25 high: Transport defenses and cookie flags are missing |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker capture found 9 third-party origins, including Google Tag Manager/Analytics and multiple ad networks; analytics cookies last about 400 days and are set without Secure. F26 high: Tracking and ad third parties load before meaningful consent |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login form exposes username/current-password fields and no WebAuthn/passkey flow. Permission prompts did not fire on load, but the relevant authentication path is not phishing-resistant. F27 medium: Authentication is password-only |
be-private-and-securedefensive-browser-policies | issues | high | The response has neither clickjacking protection nor CSP frame-ancestors, HSTS, Referrer-Policy, Permissions-Policy, or origin-isolation policy. F28 high: Browser-enforced defensive policies are absent |
be-resilientprogressive-enhancement | pass | high | Discoverability found server-rendered content with 81% raw/rendered word coverage on home and 68% on detail, not an empty JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | DOM inspection shows custom fixed overlays with very high z-indexes and manual jQuery hide/state handling; the ad slider is positioned off-screen then animated in. F29 medium: Ad and playlist overlays rely on fragile manual positioning/state |
be-resilientoffline-and-installable | not-applicable | high | Applicability judged from recon and representative templates. |
be-resilientnetwork-and-http-failure-states | pass | high | A fabricated route returns HTTP 404 and renders a clear “Page not found” message with search and Home recovery controls. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Pages expose lang and 12 hreflang variants, but CSS inspection found no logical properties and extensive physical left/right positioning. F30 medium: Localized routes exist, but layout CSS is not writing-mode ready |
be-internationalisedlocale-aware-data | pass | high | The site exposes 12 locale variants and renders localized route labels and compact/segmented view counts; no hand-rolled date input was found on tested paths. |
be-internationalisedtime-zone-correctness | not-applicable | high | Applicability judged from recon and representative templates. |
be-trustworthyno-dark-patterns | issues | high | Rendered source calls webExperienceManager.bindTo([“.vidLinkFX”]) with under:true, so selecting core video links can also open an advertising tab/window. F31 high: Video links are wired to pop-under advertising |
be-trustworthyhumane-error-handling | issues | high | The login control is type=button and calls document.forms[0].submit(); although required fields make checkValidity false, form.submit() bypasses constraint validation and submit events. F32 medium: Login bypasses native required-field validation |
be-trustworthytrustworthy-input-assistance | pass | high | Login uses autocomplete=username and autocomplete=current-password with associated labels. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The account path is password-only, while regional entry requires a third-party AI face check without a non-biometric alternative in the gate. F33 high: Account access and age assurance lack safer alternatives |
be-sustainableoptimised-assets | issues | high | The image audit found 46 images without srcset, 18 legacy-format images, 15 oversized images, and 17 below-fold images not lazy-loaded. F34 medium: Images are not consistently optimized for their slots |
be-sustainableno-wasteful-work | issues | high | HAR/trackers evidence shows analytics, Cloudflare insight, live-cam, ad-network, and autoplay-ad media requests before the user reaches content. F35 medium: Background analytics and advertising work is disproportionate |
be-sustainablethird-party-and-media-budget | issues | high | Nine third-party origins and fixed injected video advertising add network, CPU, and privacy cost to a media-heavy page that already has a 2.9 MiB load. F36 high: Third-party ad/media budget is disproportionate |
be-agent-readystructured-agent-capabilities | not-applicable | high | Applicability judged from recon and representative templates. |
be-agent-readyon-device-inference | not-applicable | high | Applicability judged from recon and representative templates. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten full-page scroll cycles, heap summary grew only 0.8% (13.44MB to 13.55MB), while same-session used heap fell from 7.12MB to 5.77MB and DOM nodes stayed 1,922. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap was 13.44MB for a media listing with 1,922 DOM elements, proportionate to the rendered page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Heap summaries contain no Detached* constructor in the top populations; repeated scroll kept DOM count fixed and did not increase same-session used heap. |
Provenance
Canonical report: results/atomic/reports/0167-pornone_com.json
Report SHA-256: 7b36a0ba1973c925112591f86f033131bfa4fb3b183b711173ed1a9437d3a6b7
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/pornone_com/2026-07-25T22-35-10-540Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/pornone_com/2026-07-25T22-35-10-540Z
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.