Manifest position 246 · CrUX rank bucket 1000
https://www.imagefap.com
Coverage complete
Coverage-complete audit of five representative public templates. Detail/gallery item pages, upload after authentication, registration, account settings, forums, and transactional completion were not covered because they require volatile content selection or authenticated/destructive interaction.
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 | Under emulated dark preference, `color-scheme` remained `normal`, body text remained black, no relevant preference rules were found, and the dark capture remained light. F01 medium: The interface is hard-coded for a light colour scheme. |
respect-user-preferencesrespects-reduced-motion | pass | medium | Under emulated reduced motion, `getAnimations()` returned no active animations; no auto-advance motion was observed. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse failed the color-contrast audit; no `prefers-contrast` or forced-colors adaptation was found. F02 high: Text and essential controls do not consistently meet contrast requirements. |
implement-natural-interactionsview-transitions | issues | high | Recon shows a multi-page set of ordinary links; no active transition was observed and no View Transition integration was established for route changes. F03 low: Navigation swaps are abrupt and do not preserve visual continuity. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation is present, so there is no imperative scroll animation implementation to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The audited desktop-style MPA exposes no custom gesture-driven interaction. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Mobile content height reached 7,140 CSS px while the DOM/CSS probes found no verified sticky progress, scroll-state chrome, or equivalent position cue. F04 medium: Long listing pages provide little position-aware navigation guidance. |
provide-guided-navigationanchored-positioning | issues | high | The overlay probe found `#agego-overlay-container` covering 780x493 at z-index 2147483647; the page contains zero `<dialog>` and zero popover elements. F05 medium: The mandatory age gate is implemented as a custom top-layer div rather than a semantic dialog. |
provide-guided-navigationdirects-attention | pass | medium | Global navigation uses descriptive text links and browser focus remains visibly outlined. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | medium | The only full-viewport interruption detected was the clearly stated adult-age gate, which is contextually necessary for this site and exposes a close/confirmation path. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The overlay probe found `#agego-overlay-container` covering 780x493 at z-index 2147483647; the page contains zero `<dialog>` and zero popover elements. F05 medium: The mandatory age gate is implemented as a custom top-layer div rather than a semantic dialog. |
maximize-content-reduce-noisereduced-chrome | issues | high | The login DOM included locally personalised promotional copy linking back to the login URL, while the homepage loaded several ad networks and three visible ad-like regions. F22 high: Advertising competes with account tasks and is not always clearly distinguishable from site content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | All four tested templates lacked a viewport meta tag. At a requested 360px viewport, home rendered a 1,292px layout viewport and login/video rendered 1,000px layouts. F06 high: Mobile browsers receive a scaled-down desktop layout instead of a responsive layout. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | All four tested templates lacked a viewport meta tag. At a requested 360px viewport, home rendered a 1,292px layout viewport and login/video rendered 1,000px layouts. F06 high: Mobile browsers receive a scaled-down desktop layout instead of a responsive layout. |
adapt-to-the-form-factorinput-modality-aware | issues | high | On login, 38 of 44 visible interactive elements were under 24px in at least one dimension and ten text/password controls were unlabeled. Lighthouse also failed target-size. F07 high: Touch and form controls are too small and many controls lack usable labels. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | Titles, H1 headings and navigation directly identify gallery, video, category and sign-in purposes. |
support-core-task-successprimary-flow-completion | pass | medium | Anonymous users can reach category, gallery, video and search listings through real links/forms; account recovery links are present on sign-in. |
support-core-task-successclear-system-state-and-recovery | issues | high | Username/password were not `required`, empty submission produced no `:invalid` controls, and the page had no live region, alert, or status element. F08 high: Sign-in does not expose native required state or accessible recovery feedback before submission. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 8.28s, FCP 4.47s and TTI 8.30s (performance score 0.61), despite a separate warm trace showing no long tasks. F09 high: Measured mobile loading is slow. |
be-fast-and-stablevisual-stability | issues | high | Image audit found 79/100 missing dimensions, 58 missing srcset, 98 legacy-format images, and Lighthouse failed image aspect ratio/responsive sizing. F14 medium: Images are frequently unsized, distorted, and served without responsive variants. |
be-fast-and-stableefficient-main-thread | pass | medium | The DevTools trace recorded zero long tasks and 0ms total blocking time in the measured load. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 146 requests and 11.72MB transferred, including two GIF thumbnails of 5.19MB and 4.70MB. Parser-inserted classic scripts lacked async/defer and CSS was uncompressed/uncached. F10 high: The homepage transfers excessive image weight and blocks rendering on legacy resources. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse reported DevTools inspector issues and 1.35s potential unused-JS savings; the DOM had 92 inline event-handler elements and 16 target=_blank links without noopener/noreferrer. F15 medium: The page has browser hygiene issues despite avoiding console exceptions. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed image-alt, label and link-name. The image probe found 48 images without alt and the login probe found ten unlabeled text/password controls. F11 high: Core controls and media lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed the color-contrast audit; no `prefers-contrast` or forced-colors adaptation was found. F02 high: Text and essential controls do not consistently meet contrast requirements. |
be-inclusivestructure-and-focus | issues | high | The login page had no main/nav/header/footer landmarks, no H1, and only an H2, although browser-default focus outline was visible. F12 medium: Pages lack semantic landmarks and a consistent heading hierarchy. |
be-inclusivelegible-text | issues | high | All four tested templates lacked a viewport meta tag. At a requested 360px viewport, home rendered a 1,292px layout viewport and login/video rendered 1,000px layouts. F06 high: Mobile browsers receive a scaled-down desktop layout instead of a responsive layout. |
be-inclusivezoom-reflow-targets-and-media | issues | high | No viewport meta was present and Lighthouse failed meta-viewport and target-size; tested mobile pages rendered at 1,000-1,292 CSS px rather than 360px. F13 high: Zoom/reflow and mobile target requirements are not met. |
follow-best-practicesno-console-errors | pass | medium | Lighthouse `errors-in-console` passed with no captured console errors. |
follow-best-practicessound-document-and-assets | issues | high | Image audit found 79/100 missing dimensions, 58 missing srcset, 98 legacy-format images, and Lighthouse failed image aspect ratio/responsive sizing. F14 medium: Images are frequently unsized, distorted, and served without responsive variants. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported DevTools inspector issues and 1.35s potential unused-JS savings; the DOM had 92 inline event-handler elements and 16 target=_blank links without noopener/noreferrer. F15 medium: The page has browser hygiene issues despite avoiding console exceptions. |
be-discoverabletitle-and-description | pass | medium | Homepage raw HTML contains a descriptive title and meta description; discoverability confirmed both survive without JavaScript. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Raw HTML is crawlable (92% coverage), but no viewport meta exists, multiple links have no discernible name, no canonical was present, sitemap.xml returned 404, and no JSON-LD/Open Graph metadata was found. F16 medium: Search metadata is incomplete across public templates. |
be-discoverablecanonical-and-indexing-signals | issues | high | Raw HTML is crawlable (92% coverage), but no viewport meta exists, multiple links have no discernible name, no canonical was present, sitemap.xml returned 404, and no JSON-LD/Open Graph metadata was found. F16 medium: Search metadata is incomplete across public templates. |
be-discoverablestructured-and-shareable-metadata | issues | high | Raw HTML is crawlable (92% coverage), but no viewport meta exists, multiple links have no discernible name, no canonical was present, sitemap.xml returned 404, and no JSON-LD/Open Graph metadata was found. F16 medium: Search metadata is incomplete across public templates. |
be-private-and-securesecure-transport-and-headers | issues | high | All seven cookies lacked Secure; PHPSESSID also lacked HttpOnly and SameSite protection. CSP, frame protection, Referrer-Policy and Permissions-Policy were absent. F17 critical: Session and analytics cookies are not protected and key browser security headers are absent. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker probe found 18 third-party origins and Google Analytics/Tag Manager/DoubleClick; HAR attributed 121/146 requests and 11.52MB to non-main-origin hosts. F18 high: The first page load exposes users to a large advertising and analytics footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login template contains username/password fields, no WebAuthn/passkey affordance, and blank autocomplete attributes. F19 high: Authentication is password-only and lacks modern input assistance. |
be-private-and-securedefensive-browser-policies | issues | high | All seven cookies lacked Secure; PHPSESSID also lacked HttpOnly and SameSite protection. CSP, frame protection, Referrer-Policy and Permissions-Policy were absent. F17 critical: Session and analytics cookies are not protected and key browser security headers are absent. |
be-resilientprogressive-enhancement | pass | medium | Discoverability measured 92% raw/rendered content coverage, with title, H1 and description available without JavaScript. |
be-resilientresilient-runtime-behaviour | issues | high | Empty login submission exposed no native invalid state or live feedback; HAR also recorded blocked/aborted ad and image requests without an observed user-facing recovery state. F20 medium: Representative error and failure states are not actionable or accessible. |
be-resilientoffline-and-installable | not-applicable | high | This public media website is not presented as an installable app; offline media access is not a reasonable core requirement. |
be-resilientnetwork-and-http-failure-states | issues | high | Empty login submission exposed no native invalid state or live feedback; HAR also recorded blocked/aborted ad and image requests without an observed user-facing recovery state. F20 medium: Representative error and failure states are not actionable or accessible. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The document declares `lang="en-GB"`, and CSS inspection found logical-property usage. |
be-internationalisedlocale-aware-data | issues | high | The English page rendered a fixed English date while probes found no alternate locale surface or evidence that user-facing date formatting responds to locale. F21 low: Rendered dates are not demonstrably locale-aware. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling, event coordination, or user-facing time-of-day flow was present in the audited templates. |
be-trustworthyno-dark-patterns | issues | high | The login DOM included locally personalised promotional copy linking back to the login URL, while the homepage loaded several ad networks and three visible ad-like regions. F22 high: Advertising competes with account tasks and is not always clearly distinguishable from site content. |
be-trustworthyhumane-error-handling | issues | high | Login fields are not required and empty submission yielded no invalid controls or live error region. F23 high: Forms neither prevent nor explain common mistakes humanely. |
be-trustworthytrustworthy-input-assistance | issues | high | Both username and password reported an empty autocomplete value. F24 medium: Sign-in fields omit autofill tokens. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The login template contains username/password fields, no WebAuthn/passkey affordance, and blank autocomplete attributes. F19 high: Authentication is password-only and lacks modern input assistance. |
be-sustainableoptimised-assets | issues | high | The homepage transferred 11.72MB, 11.23MB as images; 88 below-fold images were not lazy-loaded, 98/100 used legacy formats, and two GIF thumbnails accounted for 9.88MB. F25 high: Media delivery is disproportionately wasteful even for an image-heavy service. |
be-sustainableno-wasteful-work | issues | high | The network capture started analytics, ad, age-verification and related requests during initial rendering, contributing 121 non-main-origin requests. F26 medium: Non-essential third-party work begins immediately on load. |
be-sustainablethird-party-and-media-budget | issues | high | Tracker probe found 18 third-party origins and Google Analytics/Tag Manager/DoubleClick; HAR attributed 121/146 requests and 11.52MB to non-main-origin hosts. The homepage transferred 11.72MB, 11.23MB as images; 88 below-fold images were not lazy-loaded, 98/100 used legacy formats, and two GIF thumbnails accounted for 9.88MB. F18 high: The first page load exposes users to a large advertising and analytics footprint. F25 high: Media delivery is disproportionately wasteful even for an image-heavy service. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing capability or tool intent was found for this media-browsing site. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model task is part of the representative journeys. |
be-memory-efficientno-leak-under-repeated-interaction | pass | low | Ten repeated age-overlay toggle attempts increased the separate-session heap summary by about 3.9% (12.75MB to 13.25MB), not evidence of unbounded retained growth; confidence is low because snapshots used separate browser sessions. |
be-memory-efficientbounded-footprint | pass | low | Heap summary reported 12.75MB self size and 190,531 nodes, proportionate to a media-heavy DOM. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | low | Detached-node constructors did not appear among dominant constructors before or after the repeated interaction; closure counts fell rather than accumulated. |
Provenance
Canonical report: results/atomic/reports/0246-www_imagefap_com.json
Report SHA-256: 395477c6141ac173ad821233d702bd7f3b3f1d2c79943d7aed6aedca4e30dca1
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_imagefap_com/2026-07-19T10-21-31-294Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_imagefap_com/2026-07-19T10-21-31-294Z
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.