Manifest position 785 · CrUX rank bucket 1000
https://www.crazygames.com
Coverage complete
Atomic audit completed for all 58 registered checks across representative home, category, search, game, login, and recovery surfaces.
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 | The CSS feature probe found no prefers-color-scheme rule and computed color-scheme was normal; light/default and dark-emulated captures use the same dark surface. F01 medium: The site uses a fixed dark palette rather than honoring the user’s color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, matchMedia was true and the page exposed zero active animations; no auto-advancing motion was visible. |
respect-user-preferencesrespects-contrast | pass | high | The forced-colors/prefers-contrast capture retained readable text, outlines, card boundaries, search, and navigation controls. |
implement-natural-interactionsview-transitions | issues | high | The rendered CSS/HTML probe found no view-transition usage even though the browser supports document.startViewTransition. F02 low: Route and state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked parallax, scrollytelling, or reveal animation was present on the representative routes, so there was no scroll-linked implementation to judge. |
implement-natural-interactionsphysical-gestures | pass | high | Representative carousels and page scrolling retained native wheel/touch scrolling behavior; CSS used overscroll behavior and no conflicting pointer-driven gesture surface was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The CSS probe found no scroll-state or scroll-driven timeline use; screenshots show a fixed top bar and full-height side rail occupying persistent viewport space. F25 low: Persistent navigation chrome does not adapt to scroll state. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored menu, or edge-positioned transient overlay requiring anchor positioning was present in the exercised states. |
provide-guided-navigationdirects-attention | pass | high | Category breadcrumbs, descriptive section headings, card labels, and the game-detail breadcrumb clearly preserve location and next-action context. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop screenshots on the home, category, game, and 404 routes show a centered consent wall covering the game grid or active game. F03 high: A large consent interstitial obscures the primary content on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The feature and login probes found zero dialog and popover elements while visible modal surfaces were present; the login email field had no role=dialog ancestor. F04 medium: Consent and login overlays are custom containers rather than semantic dialog/popover primitives. |
maximize-content-reduce-noisereduced-chrome | pass | high | Outside the consent state, the dark grid dedicates most of the viewport to game artwork and labels; header and side navigation remain compact. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The 360×800 search screenshot shows “Agree & Continue” cut off beyond the right edge and the modal consuming almost the whole viewport. F05 high: The consent dialog does not fit a 360 px viewport and clips its action row. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | The CSS feature probe found @container/container-type usage and the 360 px homepage reflowed the card grid without page-level horizontal overflow. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe measured top controls at 40×40, nav links at 59×34, and multiple focused buttons with outline-style none and no box shadow; Lighthouse also failed button-name. F06 medium: Several controls are undersized and some buttons lack a visible programmatic focus treatment. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport identifies searchable game categories and prominent game cards; /game/2048 loads the playable game above its details. |
support-core-task-successprimary-flow-completion | issues | high | Desktop screenshots on the home, category, game, and 404 routes show a centered consent wall covering the game grid or active game. F03 high: A large consent interstitial obscures the primary content on first load. |
support-core-task-successclear-system-state-and-recovery | pass | high | The synthetic missing route rendered a branded GAME OVER recovery page with popular-game alternatives instead of a blank or broken shell. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 3.46 s and CLS 0.578 with a performance score of 0.56; the game detail also measured CLS 0.243. F07 high: The homepage misses the good Core Web Vitals range in lab testing. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse recorded CLS 0.578 on home and 0.243 on /game/2048; the image audit found 99 of 100 images without width/height attributes. F08 high: Late layout movement is severe on the homepage and remains poor on game detail. |
be-fast-and-stableefficient-main-thread | issues | high | The trace summary found a 1,172.66 ms longest task and 1,173.35 ms total blocking time; Lighthouse reported 3.1 s main-thread work. F09 high: A very long main-thread task delays responsiveness during load. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse estimated 1,110 ms render-blocking savings and 2,287 KiB image-delivery savings; the HAR recorded 236 requests and 2.27 MB transferred in its capture. F10 medium: The initial dependency chain and image delivery are heavier than necessary. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 174 KiB unused JavaScript, 19 KiB unused CSS, and 39 KiB legacy JavaScript on home; game detail showed 465 KiB unused JavaScript. F11 medium: The homepage ships avoidable unused and legacy code. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed aria-prohibited-attr and button-name on the homepage; the DOM recon also found image-only links with empty text. F12 high: Some controls expose invalid or missing accessible names. |
be-inclusivesufficient-contrast | issues | high | Desktop Lighthouse failed the color-contrast audit on /game/2048. F13 medium: Game-detail text includes insufficient color contrast. |
be-inclusivestructure-and-focus | issues | high | Programmatically focused header and modal buttons computed to outline-style none with no box shadow; native anchor outlines were present. F14 medium: Keyboard focus is not consistently visible on button controls. |
be-inclusivelegible-text | pass | high | Desktop, mobile, dark, and forced-colors screenshots show readable headings and compact labels without clipping in the underlying site UI. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At 360×800 the consent actions clip horizontally; several controls measured only 34–40 px high, and Lighthouse failed its viewport scaling audit. F15 medium: Narrow-screen reflow and target sizing are not consistently inclusive. |
follow-best-practicesno-console-errors | pass | high | Lighthouse did not report its errors-in-console audit as failing on either home or game detail. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 99 of 100 images without width and height attributes; Lighthouse also failed unsized-images. F16 medium: Most image elements omit intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed valid-source-maps for large first-party JavaScript and inspector-issues on both representative Lighthouse runs. F17 low: Production diagnostics are incomplete and Chrome reports inspector issues. |
be-discoverabletitle-and-description | pass | high | Home and game detail expose unique descriptive titles and meta descriptions; the discoverability primitive found both in raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | The DOM contained real href links and a scaling viewport; robots permits public category/game routes and declares a sitemap index. |
be-discoverablecanonical-and-indexing-signals | pass | high | Home and game detail returned 200, exposed canonical URLs, had no accidental noindex, and robots.txt declares a sitemap index. |
be-discoverablestructured-and-shareable-metadata | pass | high | /game/2048 exposes matching Open Graph data plus VideoGame/WebApplication, ItemPage, breadcrumb, FAQ, and video JSON-LD. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers probe found no Content-Security-Policy; the cookie probe found three non-Secure first-party cookies and all five cookies using SameSite=None. F18 high: Transport is HTTPS, but CSP is absent and several cookies use weak attributes. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The consent copy states that 1,336 technology partners may process data; the tracker probe observed eight non-page origins and Sentry, while the HAR recorded 230 cross-origin requests. F19 medium: The consent and third-party surface is unusually broad for initial browsing. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login flow exposed email/password inputs, and a fetched-script probe found no PublicKeyCredential, navigator.credentials create/get, or passkey implementation. F20 medium: The account sign-in surface does not expose phishing-resistant passkey authentication. |
be-private-and-securedefensive-browser-policies | issues | high | The headers probe found no Referrer-Policy or Permissions-Policy. HSTS, nosniff, and SAMEORIGIN framing protection were present. F21 medium: Several browser-enforced defensive policies are missing. |
be-resilientprogressive-enhancement | pass | high | Raw HTML retained 51% of homepage, 76% of category, and 93% of game-detail content; title, H1, and description survived without JavaScript on all three. |
be-resilientresilient-runtime-behaviour | issues | high | The 360×800 search screenshot shows “Agree & Continue” cut off beyond the right edge and the modal consuming almost the whole viewport. F05 high: The consent dialog does not fit a 360 px viewport and clips its action row. |
be-resilientoffline-and-installable | pass | high | A valid standalone web-app manifest, active service-worker registration, and Workbox precache containing offline.html and an offline game were directly observed. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately invalid route rendered a branded recovery page with recommended games and a clear GAME OVER message. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The DOM reported lang=en and dir=ltr, while the CSS probe counted 329 physical left/right declarations versus only six logical-property uses. F22 medium: The document declares language/direction correctly but CSS remains dominated by physical directional properties. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative public routes displayed no dates, currencies, durations, or locale-sensitive numeric data. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public routes contained no event scheduling or time-zone-sensitive data. |
be-trustworthyno-dark-patterns | issues | high | Desktop screenshots on the home, category, game, and 404 routes show a centered consent wall covering the game grid or active game. F03 high: A large consent interstitial obscures the primary content on first load. |
be-trustworthyhumane-error-handling | not-applicable | high | The audited browsing, search, game, and first-step login surfaces contained no validation form with a user-triggerable invalid submission state. |
be-trustworthytrustworthy-input-assistance | issues | medium | The login probe found autocomplete=email on email but an empty autocomplete value on the password input. F23 medium: The sign-in password field does not advertise the expected autocomplete purpose. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The login flow exposed email/password inputs, and a fetched-script probe found no PublicKeyCredential, navigator.credentials create/get, or passkey implementation. F20 medium: The account sign-in surface does not expose phishing-resistant passkey authentication. |
be-sustainableoptimised-assets | issues | high | Lighthouse estimated 2,287 KiB image savings; the image audit found 25 below-fold images without lazy loading, 13 legacy-format images, and 99 missing intrinsic dimensions. F24 high: Image delivery wastes substantial bytes on the media-heavy homepage. |
be-sustainableno-wasteful-work | pass | high | The load trace showed three load-related long tasks but no continuing animation or idle background-task stream after the capture window; requests completed without chatty error retries. |
be-sustainablethird-party-and-media-budget | pass | high | The transferred media is substantial but proportionate to a visual game catalog, most bytes came from CrazyGames asset/build subdomains, and no autoplay video/audio appeared on browsing routes. |
be-agent-readystructured-agent-capabilities | not-applicable | high | CrazyGames exposes public game discovery and play, but no declared agent-facing transaction/tool surface; emerging WebMCP capability is therefore treated as out of scope. |
be-agent-readyon-device-inference | not-applicable | high | No summarization, generation, or other inference task is part of the representative game browsing and play journey. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 20 sidebar toggles, heap self size rose only 38,026 bytes (34,083,008 to 34,121,034) and heap node count decreased by 28, providing no retained-growth signal. |
be-memory-efficientbounded-footprint | pass | high | A settled homepage used about 34.1 MB heap self size, 28.9 MB JS heap used, and 2,575 DOM elements, proportionate to a dense game catalog. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Across the baseline/post snapshots, node count fell from 597,615 to 597,587 and no growth trend appeared after repeated sidebar toggling. |
Provenance
Canonical report: results/atomic/reports/0785-www_crazygames_com.json
Report SHA-256: 29e14a0ec72dcf0e16aa01dbf8bbc79dd096c08a30b5f0114f11634dfbdde072
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_crazygames_com/2026-07-23T00-47-45-452Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_crazygames_com/2026-07-23T00-47-45-452Z
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.