Manifest position 201 · CrUX rank bucket 1000
https://pikabu.ru
Coverage complete
Coverage-complete audit of four representative public templates/states plus a 404 recovery state.
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 | Light and dark emulation produce fully retinted usable surfaces. |
respect-user-preferencesrespects-reduced-motion | pass | high | Under reduce, all 100 sampled animations were paused. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/high-contrast capture keeps text, controls, borders, and focusable UI visible. |
implement-natural-interactionsview-transitions | pass | high | CSS inspection found @view-transition navigation:auto and 0.25s root transitions; route video captured navigation. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, or entry/exit reveal behavior was observed on the representative templates, so there is no scroll-linked animation implementation to judge. |
implement-natural-interactionsphysical-gestures | pass | medium | The feed uses native vertical scrolling; no custom element onscroll handlers were found. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | DOM evidence reports a sticky header, but platform-probe.json and CSS inspection found no scroll-state or scroll-timeline rules; the header remains a fixed 64px chrome region. F01 low: The sticky site chrome does not adapt as the user scrolls. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or viewport-edge menu was exposed on the representative anonymous-user paths. |
provide-guided-navigationdirects-attention | pass | high | Screenshots show a current-section underline, clear topic chips, and article heading hierarchy. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop screenshots show a roughly 200px top ad/empty ad slot before navigation and content; themes-desktop.png shows a full-width banner dominating the first viewport. F02 medium: Advertising displaces the primary feed before users reach content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No transient overlay or modal flow appeared on load or in the representative anonymous browsing paths. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop screenshots devote the top 200px to advertising and a 300px right rail to sign-in/promotional chrome, leaving a narrow 541px content column. F03 medium: Non-content chrome and advertising consume too much of the first viewport. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360px viewport, layout evidence reports scrollWidth 900, clientWidth 360, and 540px horizontal overflow. Mobile screenshots show most navigation and content clipped off-screen. F04 critical: The desktop layout is forced into mobile viewports. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | platform-probe.json found zero container rules, while the 360px layout remains 900px wide and cards/right rail retain desktop dimensions. F05 high: Components do not adapt to their available container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The accessibility probe found 40 sampled controls below 24px in one dimension; focused login buttons and inputs computed to outline: none. Lighthouse target-size scored 0. F06 high: Keyboard focus and touch target support are inconsistent. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage and themes screenshots immediately identify a social feed and expose clear content/navigation actions. |
support-core-task-successprimary-flow-completion | pass | high | Anonymous users can browse the feed, open a story, navigate themes, and return without a dead end; authoring clearly explains authentication is required. |
support-core-task-successclear-system-state-and-recovery | issues | high | After activating “Войти” with empty fields, login-invalid.png is visually unchanged: fields have no visible required message, invalid state, or recovery instruction. F07 high: Empty login submission gives no visible recovery feedback. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 17.5s, TBT 2,590ms, Speed Index 8.5s, and time-to-interactive 19.8s; the trace also measured 980.52ms blocking time. F08 critical: Load and interaction readiness are far outside good ranges. |
be-fast-and-stablevisual-stability | pass | high | Layout observer measured CLS 0 and Lighthouse CLS is 0. |
be-fast-and-stableefficient-main-thread | issues | high | Trace evidence found 7 long tasks, a 482.9ms maximum, and 980.52ms total blocking time; mobile layout observation found tasks up to 506ms. F09 high: Long JavaScript tasks block the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR evidence records 145 requests and 3.53MB transferred; parser-discovered app/vendor scripts are high priority, and the main document took 1.41s. F10 high: The critical path ships a large parser-discovered script chain. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 1,041KiB unused JavaScript and 98KiB unused CSS; HAR shows 2.36MB of transferred script across 31 requests. F11 high: Large amounts of unused code are delivered on initial load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse button-name and link-name audits scored 0; the probe found 10 unlabeled visible inputs, and images evidence reports 12 missing alt attributes. F12 high: Controls, fields, links, and images lack accessible names or alternatives. |
be-inclusivesufficient-contrast | issues | high | Lighthouse color-contrast scored 0. The forced-colors screenshot remains operable, but normal-theme combinations still fail automated contrast analysis. F13 high: Some text and essential UI fail minimum contrast. |
be-inclusivestructure-and-focus | issues | high | The focus probe computed outline:none for login buttons and both username/password fields, while the homepage has no h1 and Lighthouse accessibility scored 0.58. F14 high: Focus indication is removed from important interactive controls. |
be-inclusivelegible-text | pass | high | Desktop feed/story text has comfortable line length and readable spacing in both themes. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The 360px capture exposes a 900px layout and 540px overflow; Lighthouse target-size scored 0. F15 critical: The page does not reflow at a narrow/zoom-equivalent viewport. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit scored 1. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive reports 27 of 27 images without both width and height attributes, 17 below-fold images not lazy-loaded, and 6 oversized images. F16 medium: Image sizing and asset structure leave avoidable layout/resource risk. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports one deprecation warning, inspector issues, and two BFCache failure reasons. F17 medium: The page has deprecations, inspector issues, and BFCache blockers. |
be-discoverabletitle-and-description | pass | high | DOM probe found a descriptive title and meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse crawlable-anchors scored 0; the DOM includes empty links, while the 360px viewport clips navigation and content despite a valid viewport meta tag. F18 medium: Some links are not crawlable and the public templates are not mobile-friendly. |
be-discoverablecanonical-and-indexing-signals | pass | high | Main document returned 200, canonical points to https://pikabu.ru/, robots allows public content, and sitemap endpoint is present in captured evidence. |
be-discoverablestructured-and-shareable-metadata | issues | high | The homepage probe found Open Graph tags but no JSON-LD. A public story/article archetype should expose Article and author/date metadata matching visible content. F19 medium: Rich content lacks structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | cookies.json reports 33 cookies without Secure, including PHPSESS, and widespread SameSite=None; headers show HTTPS/HSTS but no X-Content-Type-Options. F20 critical: Cookies are not consistently protected despite HTTPS. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 36 third-party origins and Google/DoubleClick trackers; HAR counted 139 third-party requests and 3.29MB transferred, including multiple analytics/ad cookie-sync chains. F21 high: The page loads a large, chatty third-party tracking surface by default. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The visible sign-in surface offers password, Yandex ID, and VK ID; platform/DOM evidence found no WebAuthn or passkey affordance. F22 medium: Public authentication relies on passwords or federated providers without a passkey path. |
be-private-and-securedefensive-browser-policies | issues | high | headers.json shows missing X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. CSP contains upgrade-insecure-requests and frame-ancestors but no script/style/default source restrictions. F23 high: Browser-enforced defensive headers are incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison found 100% content coverage without JavaScript and no empty JS shell. |
be-resilientresilient-runtime-behaviour | pass | medium | Representative feed, story, themes, and auth-gated route rendered stable states; no cut-off overlay was observed at desktop. |
be-resilientoffline-and-installable | issues | high | platform-probe.json found a registered service worker but no manifest link, and /manifest.json returned 404. F24 medium: The app-like social experience has a service worker but no install manifest. |
be-resilientnetwork-and-http-failure-states | pass | high | A nonexistent route presents a clear 404 message and a return-home recovery link. |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=ru and dir=ltr, matching the visible Russian content. |
be-internationalisedlocale-aware-data | pass | high | Rendered relative times are grammatically localized in Russian and use machine-readable time elements. |
be-internationalisedtime-zone-correctness | pass | high | Time elements include explicit ISO offsets such as +03:00 rather than ambiguous local strings. |
be-trustworthyno-dark-patterns | issues | high | First-viewport screenshots show large promotional banners and an inline job promotion presented as page content without an obvious “Advertisement” label. F25 medium: Advertising is visually dominant and not consistently identified as advertising. |
be-trustworthyhumane-error-handling | issues | high | The empty-submit screenshot shows no visible field-level error, while the accessibility probe finds placeholder-only unlabeled inputs. F26 high: Login validation does not explain empty required fields. |
be-trustworthytrustworthy-input-assistance | issues | high | The username uses autocomplete=username, but the password field has no current-password token; several account recovery fields have empty or generic autocomplete values. F27 medium: Sign-in autocomplete metadata is incomplete. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authenticated account-management, or cancellation flow was accessible without credentials; the visible sign-in surface is judged by the other trust/auth checks. |
be-sustainableoptimised-assets | issues | high | Images evidence found 6 oversized images, 10 without srcset, 4 legacy-format images, and 17 below-fold images not lazy-loaded. F28 medium: Images are not consistently resolution- or delivery-optimized. |
be-sustainableno-wasteful-work | issues | high | HAR shows 52 fetch/XHR requests and many ad/analytics sync redirects; the trace records 980.52ms blocking time and Lighthouse finds more than 1MB unused JS. F29 high: Startup performs substantial non-essential ad and analytics work. |
be-sustainablethird-party-and-media-budget | issues | high | 139 of 145 HAR requests are classified off the main origin and account for 3.29MB of 3.53MB transferred; tracker evidence lists 36 third-party origins. F30 high: Third-party code dominates the page budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The public content site exposes no declared agent-facing task/tool surface; emerging WebMCP capability is treated as an opportunity, not a failure. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the audited anonymous flows requires on-device inference; absence of built-in AI is not a quality failure. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten bottom/top feed-scroll cycles, heap self size fell from 62.8MB to 56.9MB and node count fell from 1,068,025 to 979,967; no aggregate retained growth was observed. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap summary reports 1,068,025 nodes and 62.8MB self size. The post-scroll snapshot did not grow, but the one-state footprint remains large. F31 medium: The initial memory footprint is high for a text-first feed. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The repeated interaction reduced total node and heap counts rather than accumulating them; no unbounded aggregate listener/DOM signal was observed. |
Provenance
Canonical report: results/atomic/reports/0201-pikabu_ru.json
Report SHA-256: 5c18d58c5b87a8cc4f5c7554eba75ea2d365dcb6ef89408d0d4a359c11e196a6
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/pikabu_ru/2026-07-19T03-29-54-140Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/pikabu_ru/2026-07-19T03-29-54-140Z
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.