Manifest position 343 · CrUX rank bucket 1000
https://www.furaffinity.net
Coverage complete
All 58 atomic checks judged across six representative paths.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Dark and normal screenshots are visually identical, and the CSS probe found no prefers-color-scheme rule or color-scheme declaration. F001 medium: Theme is fixed rather than preference-aware. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion probe reported no running animations, so there is no non-essential motion to suppress. |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast screenshot is identical to the normal capture; the CSS probe found no prefers-contrast or forced-colors rules, while Lighthouse found contrast failures. F002 medium: High-contrast preferences are not handled. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no view-transition-name or @view-transition usage across this MPA’s browse, search, and detail navigation. F003 low: Cross-document navigation swaps abruptly. |
implement-natural-interactionsscroll-driven-animations | pass | high | CSS/runtime probe found no scroll-linked effects or animation-timeline; the page uses ordinary native scrolling. |
implement-natural-interactionsphysical-gestures | pass | high | Representative paths use native links, controls, and scrolling; no custom pointer-driven gesture layer was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Mobile layout measured a 9,374px document, but CSS inspection found no scroll-state container query or progress treatment and the header does not respond to position. F004 medium: Long feeds provide no scroll-state guidance. |
provide-guided-navigationanchored-positioning | pass | high | No first-party tooltip, popover, or manually positioned transient menu was present on the representative pages, so no overlay was observed drifting from an anchor. |
provide-guided-navigationdirects-attention | pass | high | Search and detail navigations land on clearly titled content regions and preserve standard browser navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Homepage mobile capture shows a large video ad covering the lower feed; search and login captures show a full-page consent dialog before the task. F005 high: Ads and consent obscure the core content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The page reports zero dialog, popover, and details elements while custom/third-party overlays handle advertising and consent. F006 medium: Overlay UI is not built from inspectable page-native semantics. |
maximize-content-reduce-noisereduced-chrome | issues | high | The first mobile viewport devotes large areas to the banner and ad; the ad overlays multiple submission cards. F007 medium: Advertising chrome competes with content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800 the layout primitive measured scrollWidth=clientWidth=360 with 0px overflow and a valid viewport meta. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection across reused gallery, navigation, and form components found no @container or container-type rules. F008 medium: Components rely on viewport rules rather than container context. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus/target probe found numerous links only 11px high; Lighthouse target-size failed. Native focus outlines were visible. F009 high: Many targets are too small for touch. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, Browse, Search, Login, and detail templates expose descriptive headings/actions and recognizable content. |
support-core-task-successprimary-flow-completion | pass | high | The public browse/search journey returned 2,369,120 matching submissions and a selected result loaded a complete detail page with download/gallery actions. |
support-core-task-successclear-system-state-and-recovery | issues | high | The intentional 404 returns status 404 and explains the error, but offers only policy links over HTTP and no home, browse, search, or retry action. F010 medium: The 404 page is a dead end. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 5.6s and CLS 0.453 (performance 0.53); trace corroborated FCP 2.55s/LCP 2.64s in a separate warm condition. F011 high: Lab Core Web Vitals are poor. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse measured CLS 0.453 with three shifts; all 100 inspected images lacked explicit width/height. F012 high: Late content causes substantial layout shift. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded one 50.76ms task and only 0.76ms TBT; Lighthouse TBT was 50ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR identified parser-inserted styles/scripts; DOM confirmed common.js in head and many body scripts without async/defer. Lighthouse estimates 910ms render-blocking savings. F013 medium: Render-blocking resources delay content. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 467KiB unused JavaScript and 69KiB unused CSS; HAR shows 764KiB script transfer including video, ad, prebid, and Prototype bundles. F014 high: The homepage ships avoidable legacy and unused code. |
be-inclusivenames-roles-labels | issues | high | Image audit found 100/100 images without alt; Lighthouse also failed image-alt and link-name. F015 critical: Core images and links lack accessible alternatives. |
be-inclusivesufficient-contrast | issues | high | Lighthouse color-contrast failed on the audited homepage. F016 high: Text contrast fails WCAG minimums. |
be-inclusivestructure-and-focus | issues | high | Homepage has no H1 and only one nav landmark; Lighthouse reports no main landmark. Focus outlines are visible, but structure is not logical for assistive navigation. F017 high: Document structure is incomplete. |
be-inclusivelegible-text | issues | high | The target probe measured many submission/author links at only 11px high; mobile screenshots show dense, truncated labels. F018 medium: Metadata links are cramped. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Although 360px layouts do not overflow and scaling is allowed, Lighthouse target-size failed and the probe found many sub-24px controls. F019 high: Small controls undermine mobile and zoom usability. |
follow-best-practicesno-console-errors | pass | high | Lighthouse did not report a console-error failure during the audited load. |
follow-best-practicessound-document-and-assets | issues | high | Doctype/UTF-8 are valid, but image audit found every image missing dimensions, 63 missing srcset, and 100 legacy-format images. F020 medium: Assets are structurally unsized and inefficient. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse flags missing source maps and legacy JavaScript; DOM shows Prototype 1.7.3 and several parser-inserted classic scripts. F021 medium: Legacy scripts and missing source maps reduce platform hygiene. |
be-discoverabletitle-and-description | pass | high | Homepage and representative templates have descriptive titles and the site supplies a meta description. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Discoverability found 100% raw-HTML content coverage; links use hrefs, viewport meta is present, and robots permits ordinary crawlers. |
be-discoverablecanonical-and-indexing-signals | issues | high | Homepage/detail probes found no canonical URL; /sitemap.xml returned 200 with an empty body. robots.txt is present. F022 medium: Canonical and sitemap signals are incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | high | The detail page has useful Open Graph tags but zero JSON-LD blocks and uses a generic site-wide meta description. F023 medium: Submission pages lack structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers audit found no HSTS or nosniff; CSP only sets frame-ancestors. Cookie FCCDCF lacks Secure and uses SameSite=None. F024 high: Transport protections and cookie flags are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Consent UI states data may be shared with 210 partners; tracker audit found seven third-party origins and Google Ads, while 44/74 requests and 1.07MB were third-party. F025 high: Advertising creates a broad third-party data surface. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Login exposes username/password fields; no WebAuthn/passkey source was found. No permission request was observed on load. F026 medium: Authentication is password-only. |
be-private-and-securedefensive-browser-policies | issues | high | Headers audit found no HSTS, Permissions-Policy, or X-Content-Type-Options; clickjacking and Referrer-Policy were present. F027 medium: Several browser-enforced policies are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 100% content coverage without JavaScript and no empty application shell. |
be-resilientresilient-runtime-behaviour | pass | high | The MPA uses server-rendered links/forms and representative browse/search/detail pages loaded to stable, usable states without a broken shell. |
be-resilientoffline-and-installable | not-applicable | high | The audited service is an intrinsically online community whose browse/search/account tasks require live server state; an offline/installable experience was judged out of scope. |
be-resilientnetwork-and-http-failure-states | issues | high | The 404 is a standalone legacy template with no navigation back to search/browse and policy links use http:// URLs. F028 medium: Failure recovery is not integrated with the primary journey. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang=en is correct, but CSS inspection counted 222 physical left/right declarations and no dir strategy was exposed. F029 medium: Layout is not prepared for bidirectional locales. |
be-internationalisedlocale-aware-data | issues | high | The global community page renders English-only relative/server dates, exposes no locale switch, and no locale-aware markup/API signal was found in the inspected page. F030 medium: Rendered dates are not demonstrably locale-aware. |
be-internationalisedtime-zone-correctness | issues | high | Detail footer prints “Server Time: Jul 19, 2026 07:32 PM” without a time-zone identifier or machine-readable datetime. F031 medium: Server-time output is ambiguous for global users. |
be-trustworthyno-dark-patterns | pass | high | The consent prompt presents equally prominent “Consent” and “Do not consent” actions plus management options; no disguised ads or forced continuity was observed in the scoped public paths. |
be-trustworthyhumane-error-handling | issues | high | Username/password inputs are not required and expose no inspected invalid-state semantics; the page gives no pre-submit assistance. F032 medium: Login fields do not expose modern validation semantics. |
be-trustworthytrustworthy-input-assistance | issues | high | Login username and password controls have empty autocomplete attributes. F033 high: Sign-in autofill is not enabled. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The public login route offers password plus recovery only and no passkey registration/authentication path was detected. F034 medium: Account entry lacks phishing-resistant authentication. |
be-sustainableoptimised-assets | issues | high | Image audit found 100 legacy-format images, 63 without srcset, and three oversized; Lighthouse estimates 412KiB image savings. F035 high: Image delivery wastes bytes. |
be-sustainableno-wasteful-work | issues | high | HAR shows 764KiB scripts, including 190KiB ad implementation, 186KiB video, and 111KiB prebid on the homepage. F036 medium: Non-core advertising/video code dominates transfer. |
be-sustainablethird-party-and-media-budget | issues | high | HAR reports 44 third-party requests and 1.07MB third-party transfer out of 1.63MB total; the ad obscures content. F037 high: Third-party cost is disproportionate to the initial task. |
be-agent-readystructured-agent-capabilities | issues | high | Raw HTML is crawler-visible, but robots.txt disallows GPTBot, ChatGPT-User, and CCBot; no WebMCP/agentic tool registration was observed. F038 medium: Public content is intentionally unavailable to major AI agents and exposes no structured tools. |
be-agent-readyon-device-inference | not-applicable | high | No scoped public task clearly benefits from built-in on-device summarisation or language-model inference; absence is not a failure for this emerging contextual check. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After a repeated menu-toggle interaction, heap node count decreased from 331,595 to 330,812 and self size from 18,274,673 to 18,226,256 bytes. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap was 18.27MB self size with 331,595 nodes, proportionate to the media listing and advertising stack in this single state. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The post-interaction heap did not grow in nodes or self size after repeated menu toggles, providing no retained-growth signal. |
Provenance
Canonical report: results/atomic/reports/0343-www_furaffinity_net.json
Report SHA-256: 32a8daf065e66ec7984788fb06493912d661298e6f3b3ff171a662a8e08983e9
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_furaffinity_net/2026-07-20T02-28-18-704Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_furaffinity_net/2026-07-20T02-28-18-704Z
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.