Manifest position 258 · CrUX rank bucket 1000
https://simpcity.cr
Coverage complete
Coverage-complete audit of six representative paths. Authenticated-only account, posting, upload, and moderation flows were not covered because no credentials were provided.
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 | pass | high | The page is intentionally dark in normal and emulated dark mode; color-scheme is computed as dark and matching theme-color metadata is present. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion evaluate probe matched prefers-reduced-motion: reduce but still found two running animations with 14s and 22s durations. F-001 medium: Reduced-motion preference does not stop long-running decorative animation. |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast: more screenshot is visually unchanged, while Lighthouse identifies forum metadata down to 3.94:1, green labels at 2.77:1, and links indistinguishable from surrounding text. F-002 medium: High-contrast preference retains known low-contrast text and controls. |
implement-natural-interactionsview-transitions | issues | high | Rendered CSS contained no view-transition usage, and the representative forum, thread, and login route states swap directly. F-003 low: Route and state changes are abrupt rather than using view transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked animation is present; zero animation-timeline uses means there is no main-thread scroll animation anti-pattern on audited routes. |
implement-natural-interactionsphysical-gestures | pass | high | The audited forum uses native document scrolling and ordinary links; no custom pointer-driven gesture surface fights platform scrolling. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | CSS inspection found no scroll-state query or animation timeline; the captured page chrome remains a fixed, static band rather than giving position/progress feedback. F-004 low: Sticky navigation does not react to scroll state. |
provide-guided-navigationanchored-positioning | issues | high | The site exposes dropdown navigation, but CSS inspection found zero anchor-name, position-anchor, or position-try declarations. F-005 low: Dropdown positioning relies on legacy/custom behavior rather than anchor positioning. |
provide-guided-navigationdirects-attention | pass | high | Active navigation, page headings, breadcrumbs, and explicit logged-out messaging consistently identify location and moved attention. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | At 360x800, a 107px animated ad plus two large notice cards consume roughly the first 450px; the first actual forum row begins below the initial viewport. F-006 high: Promotional chrome and notices displace the primary forum content on mobile. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection found no dialog, popover, or details elements despite dropdown/navigation disclosure controls. F-007 low: Interactive menus and disclosures are custom rather than semantic platform primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | The mobile screenshot shows advertising and operational notices before the forum directory, leaving little room for the user’s core content. F-008 medium: Non-content chrome dominates the first mobile viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | scrollWidth and clientWidth are both 360 with 0px horizontal overflow; viewport meta is present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The page adapts at 360px, but rendered CSS contains no @container rules and the probe found zero size containers. F-009 low: Responsive behavior is viewport-only rather than component-aware. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse fails target-size for footer links at 20px high; the DOM probe also found the notice dismiss target at 17x21px and a 22px-wide disclosure target. F-010 medium: Several interactive targets are too small for reliable touch use. |
support-core-task-successclear-purpose-and-primary-action | pass | high | “SimpCity Forums” plus categorized forum rows communicate purpose; New Posts, Log in, category, and thread links expose next actions. |
support-core-task-successprimary-flow-completion | pass | high | Public category navigation reaches listings; the protected thread gives an explicit login state; login exposes username/password, verification, and passkey paths. |
support-core-task-successclear-system-state-and-recovery | pass | high | Protected content says login is required, and the unknown route presents a clear “page could not be found” state with Home, Help, FAQ, and rules links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP at 4.3s (score 0.42), although the trace run measured 1.58s, indicating materially variable load performance. F-011 high: Largest Contentful Paint is outside the good range. |
be-fast-and-stablevisual-stability | pass | high | Observed CLS was 0 on mobile and 0.00048 on desktop, with only two tiny shifts. |
be-fast-and-stableefficient-main-thread | pass | high | Trace total blocking time was 33ms with one 83ms task; layout observers saw one 79–85ms task, indicating a light main thread after load. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR records 6.71MB transferred, including 6.44MB of images; several multi-megabyte images lack cache headers. Lighthouse estimates 760ms savings from render-blocking resources. F-012 high: Resource delivery is dominated by large images and render-blocking styles. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 55KiB unused CSS with about 86% waste and 38KiB unused JS in core-compiled.js. F-013 medium: The page ships substantial unused CSS and JavaScript. |
be-inclusivenames-roles-labels | issues | high | The images primitive reports 7 of 48 images without alt text. F-014 medium: Some images have no text alternative. |
be-inclusivesufficient-contrast | issues | high | Lighthouse fails color contrast for repeated forum metadata (3.94–4.21:1) and green labels (2.77:1), and reports inline links relying only on color. F-015 high: Text and essential UI fail minimum contrast. |
be-inclusivestructure-and-focus | issues | high | The DOM probe found header, nav, and footer but no main; Lighthouse explicitly fails landmark-one-main. F-016 medium: The document has no main landmark. |
be-inclusivelegible-text | pass | high | Primary headings and body copy remain unclipped and readable at 360px and desktop; rows reflow rather than truncating core labels. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The 360px layout reflows without overflow, but Lighthouse target-size fails multiple footer controls at 20px high. F-017 medium: Zoom/reflow usability is weakened by undersized targets. |
follow-best-practicesno-console-errors | pass | high | Lighthouse “No browser errors logged to the console” passed. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive reports 37 images without dimensions, 11 oversized images, and 30 below-fold images without lazy loading; Lighthouse also finds a logo aspect-ratio mismatch. F-018 medium: Image dimensions, resolution, and aspect-ratio handling are unsound. |
follow-best-practicesbrowser-platform-hygiene | pass | high | BFCache audit passes, no deprecated-api failure was reported, and no notification/geolocation prompt appeared on load. |
be-discoverabletitle-and-description | pass | high | Title is “SimpCity Forums” and meta description is present in both raw and rendered HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse SEO identifies the support-thread link text “here” as non-descriptive. F-019 low: One prominent link uses non-descriptive text. |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt is available and permits the public site, but /sitemap.xml returned HTTP 403 during recon. Canonical metadata is otherwise present. F-020 medium: Sitemap discovery is inconsistent. |
be-discoverablestructured-and-shareable-metadata | issues | high | The probe found five Open Graph tags but zero JSON-LD blocks on a page representing a WebSite/Organization. F-021 low: The public forum home lacks structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show no HSTS and a CSP limited to upgrade-insecure-requests. Cookie audit found 8 insecure cookies and SameSite=None on all 8, including a 399-day storage cookie. F-022 critical: Cookie and transport defenses are materially incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR and script evidence show Clickadu requests carrying canvas/WebGL, plugin, platform, screen, language, and other fingerprint fields; 19 third-party requests transfer 776,551 bytes. F-023 high: Advertising requests collect a broad browser fingerprint without an evident consent step. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; login includes a WebAuthn/passkey form in addition to autocomplete-correct password fields. |
be-private-and-securedefensive-browser-policies | issues | high | Headers lack HSTS and Permissions-Policy; CSP has only upgrade-insecure-requests and therefore does not meaningfully restrict script/style origins. F-024 high: Defensive browser policies are incomplete. |
be-resilientprogressive-enhancement | pass | high | Raw HTML returned 200 with 100% rendered-word coverage; title, h1, and description all survive without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Navigation, notices, category rows, login, and error states render without clipped overlays or blank shells across audited routes. |
be-resilientoffline-and-installable | pass | high | A standalone manifest supplies 192/512 icons and start_url; an active service worker caches an explicit offline route and returns it when navigation fetch fails. |
be-resilientnetwork-and-http-failure-states | pass | high | An unknown route renders a clear error and recovery navigation instead of a blank page or infinite spinner. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The document declares en-US/ltr, but CSS inspection found 31 margin-left and 20 margin-right usages and no evidence of logical-property adaptation. F-025 low: The layout is hard-wired to physical directions. |
be-internationalisedlocale-aware-data | pass | high | Rendered times use semantic time elements with ISO datetime, a numeric timestamp, and locale-facing labels, enabling locale-aware client rendering. |
be-internationalisedtime-zone-correctness | pass | high | Time elements include unambiguous numeric timestamps and explicit +0100 offsets rather than ambiguous hand-written local dates. |
be-trustworthyno-dark-patterns | pass | high | Calls to action, advertising, login persistence, password recovery, and protected-route state are visibly labelled; no confirmshaming or disguised cancellation was observed. |
be-trustworthyhumane-error-handling | pass | high | The login fields are explicitly labelled, password recovery is adjacent, verification is visible before submission, and protected content explains why login is required. |
be-trustworthytrustworthy-input-assistance | pass | high | Username and password fields have labels and correct username/current-password autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The relevant account flow exposes password recovery and a WebAuthn/passkey form; no checkout/subscription commitment occurs in the audited public journey. |
be-sustainableoptimised-assets | issues | high | HAR shows 6.44MB of images, led by decorative/user embellishments of 2.85MB and 947KB; the images audit finds 42 legacy-format images and 11 oversized images. F-026 high: Image assets are grossly disproportionate to their rendered purpose. |
be-sustainableno-wasteful-work | issues | high | The page launches multiple asynchronous ad scripts and loads dozens of decorative images during initial navigation, even when they are below the fold. F-027 medium: Background advertising and decoration create avoidable work. |
be-sustainablethird-party-and-media-budget | issues | high | The initial page makes 84 requests and transfers 6.71MB, with 19 third-party requests and 776KB third-party bytes before interaction. F-028 high: The third-party and media budget is not proportionate to a forum index. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The public forum exposes content, navigation, forms, and raw HTML but no transactional capability that needs a WebMCP tool; agent actions are out of scope. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or generation task is part of the audited core forum journeys, so on-device inference is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | At the same 360x800 viewport, 10 menu open/close cycles changed self size from 43,433,977 to 43,801,080 bytes (under 1%) and no Detached constructor appeared in top populations. |
be-memory-efficientbounded-footprint | pass | medium | The mobile page heap is about 43.4MB with 160,757 nodes, proportionate to a long forum directory and stable after interaction. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached constructor appears in either summary’s top constructors, and the repeated menu exercise produced only bounded total growth. |
Provenance
Canonical report: results/atomic/reports/0258-simpcity_cr.json
Report SHA-256: 4ed7c1fd590c5b03fcb7bad754c255779406e5689110ad2536dc3b21ef6f4856
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/simpcity_cr/2026-07-19T12-19-29-487Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/simpcity_cr/2026-07-19T12-19-29-487Z
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.