Manifest position 810 · CrUX rank bucket 1000
https://an1.com
Coverage complete
Coverage-complete representative audit of seven paths/templates; source code, authenticated/account flows, actual APK installation, Russian route parity, and every pagination/category instance were not covered.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | pass | medium | Explicit light and dark captures re-tint the header, body, cards and text while preserving usability. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, the CSS probe found one rule that disables .btn transitions only below 992px, while modal, app-panel and other transitions remain defined. F01 medium: Reduced-motion support is only partial |
respect-user-preferencesrespects-contrast | issues | high | The prefers-contrast probe matched the emulated preference but found no prefers-contrast or forced-colors rules; axe also measured CTA contrast as low as 2.04:1. F02 medium: No high-contrast or forced-colors adaptation |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no view-transition CSS and the MPA does not declare cross-document view transitions, so catalog-to-detail navigation swaps instantly. F03 low: Route changes are abrupt |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface exists on the representative templates. |
implement-natural-interactionsphysical-gestures | issues | high | The homepage ships flickity.pkgd.min.js and absolutely positions carousel slides; no scroll-snap evidence was found. Hidden slides also retain focusable descendants. F04 low: Carousel interaction relies on custom Flickity positioning |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Mobile screenshots show long 3,000+ px listing/article pages, while CSS inspection found no scroll-state query or progress indicator. F05 low: Long pages have static chrome with no scroll-state feedback |
provide-guided-navigationanchored-positioning | issues | high | DOM/CSS inspection shows custom fixed .modal and manually positioned .submenu rules, with no anchor-name, position-anchor, or position-try usage. F06 low: Menus and overlays use legacy manual positioning |
provide-guided-navigationdirects-attention | pass | medium | Breadcrumbs on detail pages, active navigation labels, strong category cards and clear search results preserve orientation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Mobile captures of the game detail and article show a near-full-viewport consent dialog before any page content can be read; the persistent AN1 Store panel remains behind it. F07 high: Consent UI blocks the entire detail and article first view |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The detail probe found .fc-consent-root and .fc-dialog-overlay with no dialog element, role=dialog or aria-modal; site search/menu overlays also use custom .modal divs. F08 medium: Site overlays are custom div-based widgets |
maximize-content-reduce-noisereduced-chrome | pass | medium | Outside the separately reported consent/app panel, listing and article templates devote the viewport primarily to content with restrained framing. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | Layout captures on home, listing, detail, news and article at 360×800 all report scrollWidth=clientWidth=360 and zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found zero @container rules; game cards are reused in carousels, grids and search but are sized through global media queries. F09 low: Reusable cards adapt only at viewport breakpoints |
adapt-to-the-form-factorinput-modality-aware | issues | high | The controls probe measured each 1–5 rating link at 20×20 CSS px, and Lighthouse target-size failed. F10 medium: Rating targets are too small for touch |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The first viewport clearly states Games catalog and presents All Games / Mod Games actions; listing/search/detail headings are specific. |
support-core-task-successprimary-flow-completion | pass | medium | After choosing Do not consent, the detail page exposes a clear DOWNLOAD (320.5MB) link to the next download step. |
support-core-task-successclear-system-state-and-recovery | issues | high | The deliberately unknown path returned HTTP 200 and rendered the homepage with no error message, retry, search, or route recovery state. F11 high: Unknown URLs silently become the homepage |
be-fast-and-stablegood-core-web-vitals | pass | medium | Lighthouse measured LCP 2.4s, CLS 0 and TBT 0ms (performance 0.98); trace measured LCP 564ms and zero blocking time in the local run. |
be-fast-and-stablevisual-stability | pass | medium | Layout observers measured CLS 0 on home/listings and 0.019 on detail/article, within the good range. |
be-fast-and-stableefficient-main-thread | pass | medium | Trace and layout observers found zero long tasks and 0ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse estimated 402 KiB image-delivery savings; the image probe found 66/67 legacy-format images, 24 without srcset, 25 oversized, and 66 without explicit dimensions. F12 medium: Image delivery leaves substantial savings |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 47 KiB unused JavaScript and 16 KiB unused CSS; HAR shows a 62.7 KiB legacy general bundle plus Flickity on the initial path. F13 medium: Unused CSS and JavaScript ship on the homepage |
be-inclusivenames-roles-labels | issues | high | axe found focusable links inside aria-hidden carousel slides and no main landmark; Lighthouse accessibility scored 0.85. F14 high: Carousel and landmark semantics exclude keyboard and assistive-tech users |
be-inclusivesufficient-contrast | issues | high | axe measured white-on-green CTA contrast at 2.04:1 and white-on-orange at 2.67:1, below 4.5:1 for the rendered text sizes. F15 high: Primary CTA text fails WCAG contrast |
be-inclusivestructure-and-focus | pass | medium | Direct DOM, visual, layout, metadata, or workflow evidence across the representative paths showed the expected outcome for structure-and-focus. |
be-inclusivelegible-text | pass | medium | Screenshots show readable Montserrat text, comfortable line lengths on content pages, and no clipping at 360px. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse target-size failed and the live controls probe found multiple 20×20 rating targets, despite otherwise successful 360px reflow. F16 medium: Small controls undermine mobile accessibility |
follow-best-practicesno-console-errors | pass | medium | Lighthouse errors-in-console audit passed with an empty item list. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive reported 66 of 67 img elements without width/height attributes, weakening the document’s intrinsic layout contract even though observed CLS was currently low. F17 medium: Most images omit intrinsic dimensions |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported one back/forward-cache failure, so returning from a game detail can require a fresh page load. F18 low: The page is not eligible for BFCache |
be-discoverabletitle-and-description | pass | medium | Homepage, games, game detail and article probes all expose descriptive, route-specific titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse SEO found 12 links without descriptive text; the card ratings use links labelled only 1–5 and generic MORE links appear in listings. F19 medium: Many links have non-descriptive text |
be-discoverablecanonical-and-indexing-signals | issues | high | A prominently linked news article declares robots=noindex,nofollow, while an unknown URL returns 200 with homepage content. Both send misleading indexing signals. F20 high: Public article indexing and missing-route signals conflict |
be-discoverablestructured-and-shareable-metadata | issues | high | The detail and article probes found no JSON-LD, despite representing downloadable software and a news article; Open Graph is present but does not replace schema.org entities. F21 medium: Product and article pages omit structured data |
be-private-and-securesecure-transport-and-headers | issues | high | Headers evidence found no CSP or X-Content-Type-Options; both language and PHPSESSID cookies were not Secure and used SameSite=None despite HTTPS. F22 high: Core XSS defenses and cookie flags are missing |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The first-visit consent dialog states that identifiers and device data may be processed by 210 partners; denial is possible, but the default third-party surface is disproportionate to a download catalog. F23 high: Consent surface proposes data sharing with 210 partners |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No authentication flow or browser permission request exists on the audited public catalog paths. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive found no clickjacking protection, Referrer-Policy, Permissions-Policy, CSP frame-ancestors, or nosniff; only HSTS was present. F24 medium: Defensive response policies are largely absent |
be-resilientprogressive-enhancement | pass | medium | Discoverability evidence found 100% rendered-word coverage in raw HTML, title/H1/description present, and no empty JS shell. |
be-resilientresilient-runtime-behaviour | pass | medium | Representative menu/search/detail states rendered within 360px without clipping; denying consent restored the underlying detail action. |
be-resilientoffline-and-installable | issues | high | A manifest with start_url and standalone display is present, but probes found no controlling service worker, so this app-like catalog has no verified offline fallback. F25 medium: Installability metadata exists without an active offline controller |
be-resilientnetwork-and-http-failure-states | issues | high | The unknown route returned 200 and the normal homepage rather than a not-found state, making broken links look successful and offering no recovery context. F26 high: HTTP failure state is replaced with misleading success content |
be-internationalisedlang-dir-and-logical-properties | issues | high | The site links English and Russian variants and sets lang=en, but captured CSS extensively uses left/right, margin-left and border-left with no logical-property strategy evident. F27 low: Multilingual layout relies on physical direction properties |
be-internationalisedlocale-aware-data | not-applicable | high | Representative paths expose no user-facing dates, currencies, durations, or locale-sensitive numeric input requiring formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | Representative paths expose no events, appointments, or stored user times for which time-zone/DST handling applies. |
be-trustworthyno-dark-patterns | pass | medium | Consent presents Consent and Do not consent with equal visual weight, plus Manage options; the app panel is dismissible. |
be-trustworthyhumane-error-handling | pass | medium | The representative search flow accepts a plain query and returns a clear FOUND 14 APPS state without premature validation or blame. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | The only input is a search box; address, payment, sign-in and sign-up autofill tokens do not apply. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, account, or authentication flow exists on the audited public paths. |
be-sustainableoptimised-assets | issues | high | The image audit found 66 legacy PNG/JPG assets, 25 oversized renderings and 24 responsive images without srcset; images accounted for 598 KiB of the 786 KiB homepage transfer. F28 medium: Legacy and oversized images waste transfer |
be-sustainableno-wasteful-work | pass | medium | Trace found no long tasks or persistent work and HAR recorded only 60 requests / 786 KiB, proportionate aside from the separately reported image optimization gap. |
be-sustainablethird-party-and-media-budget | pass | medium | Homepage HAR found only 4 third-party requests / 6.4 KiB and no autoplay audio/video. Privacy breadth is reported separately. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent-facing capabilities are emerging and not an expressed surface of this public download/editorial catalog. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the representative paths requires on-device inference; absence is not a failure. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten attempted open/close menu cycles, retained summary growth was modest: +791 nodes and +108,550 bytes (~1.8%), with no evidence of unbounded growth. |
be-memory-efficientbounded-footprint | pass | medium | Baseline heap summary reported 99,551 nodes and 6.08 MB self size for a 1,504-node media catalog, proportionate to the rendered page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Before/after heap summaries showed only modest bounded growth; no Detached* constructor spike or accumulating listener/timer evidence was observed. |
Provenance
Canonical report: results/atomic/reports/0810-an1_com.json
Report SHA-256: d31c47c1c096d6ba3eb54e6b4308d869c7eaf7f2eb84713758386a76d5cf7cd6
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/an1_com/2026-07-23T04-23-13-420Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/an1_com/2026-07-23T04-23-13-420Z
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.