Manifest position 456 · CrUX rank bucket 1000
https://liquipedia.net
Coverage complete
Coverage complete: all 58 catalog checks have conclusive outcomes. Five representative public templates plus search and missing-page recovery were exercised; authenticated editing/account flows and the many game-specific templates sharing the sampled MediaWiki structure were not covered.
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 | Dark/default screenshots and CSS probe show an automatic dark theme and prefers-color-scheme/color-scheme support. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce the animation probe returned zero active animations versus one 200 ms animation normally. |
respect-user-preferencesrespects-contrast | issues | high | CSS inspection found prefers-color-scheme but no prefers-contrast handling; the prefers-contrast screenshot was pixel-identical in size to the default capture. F03 medium: No explicit high-contrast preference adaptation was found |
implement-natural-interactionsview-transitions | pass | high | Rendered CSS contains view-transition declarations and representative route/content changes remain coherent. |
implement-natural-interactionsscroll-driven-animations | pass | high | CSS inspection found scroll-timeline/animation-timeline support and layout captures showed no scroll overflow failure. |
implement-natural-interactionsphysical-gestures | pass | medium | Mobile captures show native scrolling and platform controls without a custom pointer-only primary interaction. |
provide-guided-navigationscroll-state-aware-chrome | pass | medium | Long mobile pages retain compact, stable navigation chrome and native scrolling across templates. |
provide-guided-navigationanchored-positioning | pass | high | CSS inspection found anchor-positioning declarations; navigational menus remain attached in representative screenshots. |
provide-guided-navigationdirects-attention | pass | high | Heading, breadcrumb, active wiki color, and search redirect clearly preserve context across the selected paths. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots across all five representative templates show a large fixed consent panel covering roughly half the viewport before any interaction. On mobile it masks the event/team content while presenting 1,192 vendors. F01 high: Consent wall obscures the primary content on every fresh visit |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM probe found zero dialog, role=dialog, or aria-modal elements while screenshots show a modal-like overlay; focus and dismissal therefore rely on third-party ad-hoc markup. F02 medium: The consent wall is not exposed as a dialog |
maximize-content-reduce-noisereduced-chrome | pass | high | After the separately reported consent interruption, page chrome is compact and content occupies the main viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | All five 360 px layout captures report scrollWidth=clientWidth=360 and horizontalOverflowPx=0 with a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Rendered CSS inspection found no @container or container-type despite reusable wiki cards appearing in multiple widths. Mobile reflow works, but components are coupled to viewport breakpoints. F04 low: Reusable cards adapt only at the page/viewport level |
adapt-to-the-form-factorinput-modality-aware | pass | high | Focus probe shows visible browser outlines or 4 px focus rings on primary links, search, select, and submit controls; mobile controls are touch-sized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Landing H1 says “Your home for esports”, exposes game selection/search, and detail pages lead with specific entity headings. |
support-core-task-successprimary-flow-completion | pass | high | The search URL for Natus Vincere resolves end-to-end to the matching team entity page without a dead end. |
support-core-task-successclear-system-state-and-recovery | pass | high | The invented page shows a clear empty-page explanation with search/log recovery links rather than a blank shell. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 4.4 s, TBT 1,100 ms, max potential FID 820 ms, and time-to-interactive 23.9 s (performance score 0.53). The first-party trace was faster but still recorded 165 ms TBT. F05 high: Throttled mobile load misses the LCP and responsiveness bar |
be-fast-and-stablevisual-stability | pass | high | CLS was 0.0002 on home and below 0.0014 on sampled detail pages; all home images reserve width and height. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reported 3.5 s main-thread work and 2.2 s JavaScript execution. The trace found a 215 ms long task and mobile layouts repeatedly observed roughly 220 ms tasks. F06 high: Third-party and application scripts block the main thread |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 119 requests and 3.51 MB transferred; ten first-party CSS/JS/font resources lacked useful cache headers. Lighthouse estimated 1,027 KiB cache savings and 450 ms render-blocking savings. DOM confirmation shows index.js is a deferred-by-spec module, but three stylesheets remain parser-blocking. F07 medium: Resource delivery has avoidable cache and render-path costs |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 1,160 KiB unused JavaScript and 54 KiB unused CSS. HAR attributes 2.50 MB to 40 scripts, with 2.53 MB of all transfer bytes from third parties. F08 high: The page ships a large amount of unused and third-party JavaScript |
be-inclusivenames-roles-labels | pass | high | Lighthouse accessibility scored 0.96 with no name/role/label failure; card images use deliberate empty alt next to text labels. |
be-inclusivesufficient-contrast | issues | high | Lighthouse accessibility found two text-block links distinguished from surrounding text only by colour, despite an otherwise strong 0.96 accessibility score. F09 medium: Some inline links rely on colour alone |
be-inclusivestructure-and-focus | pass | high | DOM has one H1, sequential H2 sections and header/main/footer landmarks; focus probe shows visible indicators. |
be-inclusivelegible-text | pass | high | Desktop/mobile screenshots show readable line lengths, scalable text, clear headings, and no clipping in the underlying content. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Viewport allows initial-scale without maximum-scale; 360 px reflow has no horizontal overflow and controls remain usable. |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed the errors-in-console audit on the landing page. HAR also recorded a missing commons.jpg and aborted third-party requests. F10 medium: Browser errors are emitted during load |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse reported a deprecated API and a low-resolution image; HAR returned 404 for /static/images/wikis/commons.jpg. The document itself has valid HTML doctype and UTF-8 charset. F11 medium: Asset and platform diagnostics are not clean |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed deprecations and inspector-issues audits and reported legacy JavaScript savings of 40 KiB. F12 medium: Chrome reports platform hygiene issues |
be-discoverabletitle-and-description | pass | high | Home and discoverability captures confirm descriptive title/meta description in raw and rendered HTML across templates. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | The home probe found no href-less anchors, viewport meta is present, and representative content is exposed as real links. |
be-discoverablecanonical-and-indexing-signals | pass | high | Home has a canonical URL; robots advertises sitemap_index.xml; missing wiki pages correctly emit noindex,nofollow. |
be-discoverablestructured-and-shareable-metadata | pass | high | Home exposes JSON-LD plus Open Graph title, description, URL and image matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | Header inspection confirms HTTPS and two-year preload HSTS, but no Content-Security-Policy and no X-Content-Type-Options: nosniff. F13 high: HTTPS is strong, but essential response defenses are absent |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 35 third-party origins and ten known tracker domains. HAR recorded 72 third-party requests and 2.53 MB third-party transfer, including advertising and Amplitude session replay. F14 high: The default page has an unusually broad tracking footprint |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | The audited public content and search paths request no device permissions and contain no authentication step, so passkey/password behavior is outside these representative journeys. |
be-private-and-securedefensive-browser-policies | issues | high | Headers lacked clickjacking protection, Referrer-Policy, and Permissions-Policy. Cookie audit found 13 of 14 cookies without Secure and several SameSite=None analytics cookies lasting 365-400 days. F15 high: Browser-enforced policy coverage is incomplete and analytics cookies are weakly scoped |
be-resilientprogressive-enhancement | pass | high | No-JS discoverability retains 73-90% content words, title, H1 and meta description on all four representative templates; none is a JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Menus, breadcrumbs and content remain within the 360 px viewport on all sampled long pages, with no horizontal clipping. |
be-resilientoffline-and-installable | not-applicable | high | Liquipedia is a public reference website rather than an installed app; offline installability is not required for the selected content and search journeys. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately missing wiki page presents an explanatory state, search option, related logs and correct noindex policy. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The root language is en and rendered CSS uses logical inline properties; default LTR direction is correctly inherited. |
be-internationalisedlocale-aware-data | pass | medium | Tournament markup and rendered event content use MediaWiki timestamp/content structures rather than locale-specific URLs or image text. |
be-internationalisedtime-zone-correctness | pass | medium | Event pages retain structured server-rendered schedule content and avoid ambiguous state in the sampled tournament path. |
be-trustworthyno-dark-patterns | issues | high | The initial consent panel foregrounds Accept and Advanced Settings while claiming processing by 1,192 vendors; rejecting non-essential processing requires a deeper flow. F16 high: Consent offers Accept but no equally direct Reject action |
be-trustworthyhumane-error-handling | not-applicable | high | The representative search form has no required or constraint-validated input, so there is no invalid submission state to recover from. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, or sign-up input flow appears in the audited public paths. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication, or account-management flow appears in the audited public scope. |
be-sustainableoptimised-assets | issues | high | Image audit found 64 legacy-format images, 61 without srcset, 26 below-fold images loaded eagerly, and one oversized image. Lighthouse estimated 431 KiB image-delivery savings. F17 high: Landing imagery is not delivered responsively or in modern formats |
be-sustainableno-wasteful-work | issues | high | The initial HAR transfers 2.53 MB from third parties and the trace/Lighthouse show heavy scripting before interaction, including ad bidding and session replay. F18 high: Advertising and analytics perform substantial work before the user asks for it |
be-sustainablethird-party-and-media-budget | issues | high | Of 3.51 MB transferred, 2.53 MB came from third parties; the largest files include ad, tag-manager, bidder, consent, and session-replay scripts rather than core esports content. F19 high: Third-party scripts dominate the page budget |
be-agent-readystructured-agent-capabilities | issues | high | robots.txt blocks GPTBot, ClaudeBot, ChatGPT-User, Amazonbot, meta-externalagent and others from all paths, while discoverability captures show 73-90% of representative content is available in raw HTML. No WebMCP capability surface was detected. F20 medium: High-value public content is intentionally unavailable to major AI agents |
be-agent-readyon-device-inference | not-applicable | high | The audited reference/search experience has no task that requires on-device generative inference; absence is not a quality failure. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten representative select changes, heap self-size rose only ~0.41 MB (0.9%) and nodes ~0.3% between independent snapshots, not evidence of unbounded retained growth. |
be-memory-efficientbounded-footprint | pass | high | Heap self-size was about 45 MB for a content-rich page with advertising; DOM probe counted 1,741 elements, proportionate to the long card index. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after constructor summaries showed no growing Detached* population and only small bounded object/closure changes after repeated selection. |
Provenance
Canonical report: results/atomic/reports/0456-liquipedia_net.json
Report SHA-256: 0e1880eaa3d142d7f7f616352d2243b7ab9b216ef89f4a231b3f5261170d09d9
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/liquipedia_net/2026-07-20T22-51-12-577Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/liquipedia_net/2026-07-20T22-51-12-577Z
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.