Manifest position 395 · CrUX rank bucket 1000
https://www.gismeteo.ru
Coverage complete
Coverage-complete multi-template audit; no local source or fixes requested.
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 prefers-color-scheme: dark screenshot remains the same light grey/white palette as the normal capture; no site dark theme is applied. F04 medium: The site ignores the user’s dark colour-scheme preference |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion probe reported zero active animations under prefers-reduced-motion: reduce. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/high-contrast screenshot preserved text, controls, boundaries, and consent actions. |
implement-natural-interactionsview-transitions | issues | high | DOM/script inspection found no authored view-transition CSS or transition setup across the MPA links, while representative navigation is cross-document. F05 medium: Navigation changes are abrupt and do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation was present on the audited templates, so there is no implementation to assess. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull, drag, or gesture-driven core interaction was exposed in the audited paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Long article and forecast screenshots show no scroll progress or state-responsive chrome; this is covered as a lower-confidence quality issue? F03 high: Primary flow cannot be completed reliably on mobile |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or anchored popover was required or surfaced in the representative journeys. |
provide-guided-navigationdirects-attention | pass | high | The DOM and screenshots show descriptive forecast-period links, active contextual page labels, and clear map playback state. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Load screenshots show a modal dimming and obscuring the entire forecast/article/map before interaction; on mobile its rejection action is off-screen. F02 critical: Consent interstitial blocks the core weather and reading tasks |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inventory shows the consent overlay implemented as DIV role=dialog rather than a native dialog, and mobile dismissal remains broken. F02 critical: Consent interstitial blocks the core weather and reading tasks |
maximize-content-reduce-noisereduced-chrome | issues | high | Homepage screenshot is crowded by news modules, advertising and modal chrome around a compact weather card. F02 critical: Consent interstitial blocks the core weather and reading tasks |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Mobile screenshots on all four representative templates show a fixed 512px consent dialog beginning at x=249; its text and action buttons extend beyond the right viewport edge and cannot be reached. F01 critical: Consent dialog is unusable at a 360px viewport |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe over loaded stylesheets found no @container rules; the fixed-width consent component overflows narrow reuse conditions. F06 medium: Components rely on viewport layout rather than container responsiveness |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe focused the Новости link but computed outline-style was none; many primary links were only 20px high and forecast tabs 40px high, below a comfortable 44px target. F07 high: Keyboard focus and touch-target support are inadequate |
support-core-task-successclear-purpose-and-primary-action | pass | high | Titles, H1 content, weather cards, forecast-period links, and map controls clearly communicate each page purpose once visible. |
support-core-task-successprimary-flow-completion | issues | high | The homepage, weather detail, news article, and map journey all stop at the same horizontally clipped consent state at 360x800. F03 high: Primary flow cannot be completed reliably on mobile |
support-core-task-successclear-system-state-and-recovery | issues | high | The 360x800 404 screenshot clips the recovery sentence and link off the right edge, although the DOM contains a home link. F12 medium: The 404 recovery page overflows on mobile |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP of 10.8s home, 16.2s weather, 12.2s news, and 12.7s maps; trace LCP was 9.12s. F08 high: Largest Contentful Paint is extremely slow across every template |
be-fast-and-stablevisual-stability | pass | high | Lighthouse CLS remained 0–0.018 across four templates, within the good range. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reported 5.6s main-thread work and 3.4s JS execution on home, 11.2s and 6.2s on weather. F09 high: Advertising and unused JavaScript dominate delivery and main-thread work |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 146 requests/2.71MB and Lighthouse estimated 896KiB cache-lifetime savings on home. F09 high: Advertising and unused JavaScript dominate delivery and main-thread work |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR recorded 2.71MB across 146 requests, 2.22MB of script, with 143 requests and 2.65MB classified third-party; Lighthouse estimated 1,624KiB unused JS on home and 1,612KiB on weather. F09 high: Advertising and unused JavaScript dominate delivery and main-thread work |
be-inclusivenames-roles-labels | issues | high | Lighthouse found 21/16/11/15 required-parent ARIA failures across the templates and five unnamed buttons on maps. F11 high: ARIA structure and map control names are invalid |
be-inclusivesufficient-contrast | issues | high | Lighthouse found 34 contrast failures on home, 32 weather, 19 news, and 39 maps. F10 high: Text and controls fail colour contrast across all templates |
be-inclusivestructure-and-focus | issues | high | Lighthouse ARIA ownership failures and the focus probe with outline-style none show structure/focus divergence. F11 high: ARIA structure and map control names are invalid F07 high: Keyboard focus and touch-target support are inadequate |
be-inclusivelegible-text | pass | medium | Article/body text is readable at mobile scale, but clipping is isolated to the reported consent and 404 layout defects. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Viewport permits maximum-scale=5, but the 360px screenshots and target probe show clipped dialog/recovery content and sub-44px targets. F01 critical: Consent dialog is unusable at a 360px viewport F07 high: Keyboard focus and touch-target support are inadequate F12 medium: The 404 recovery page overflows on mobile |
follow-best-practicesno-console-errors | pass | medium | Lighthouse did not report the errors-in-console audit as failing on any of four templates. |
follow-best-practicessound-document-and-assets | pass | medium | The page has UTF-8, a viewport meta and modern WebP map images; the one missing image dimension is reported through delivery/sustainability evidence. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Every Lighthouse run found a deprecated API warning, five BFCache failure reasons, and DevTools inspector issues. F15 medium: Browser-platform hygiene is degraded |
be-discoverabletitle-and-description | pass | high | DOM probe found a descriptive title and meta description; Lighthouse SEO was 100 on all templates. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Real href links and viewport meta were present; robots.txt returned 200 and Lighthouse SEO scored 100. |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage returned 200 with canonical URL, ru/ru-BY/ru-KZ hreflang, indexable robots policy, and a current sitemap index. |
be-discoverablestructured-and-shareable-metadata | issues | high | Metadata probe found useful Open Graph tags and hreflang, but no JSON-LD on the weather homepage despite representing places and forecasts. F20 low: Entity pages lack structured data |
be-private-and-securesecure-transport-and-headers | issues | high | Headers evidence found no CSP, frame protection, or Permissions-Policy. Cookie evidence found eight cookies flagged insecure; FCCDCF is non-Secure, SameSite=None, and 390 days. F13 high: Security headers and cookie attributes are weak |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture saw 23 third-party origins; HAR attributed 143 of 146 requests and 2.65MB to third parties, including DoubleClick and Yandex analytics/ad traffic. F14 high: The page activates a very large tracking and advertising surface |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; public authentication entry points use VK ID and Yandex ID OAuth rather than an authored password form. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS and Referrer-Policy are present, but CSP/frame protection and Permissions-Policy are absent. F13 high: Security headers and cookie attributes are weak |
be-resilientprogressive-enhancement | pass | high | Discoverability capture found 75% raw-HTML coverage, no JS shell, and visible weather content in the crawler screenshot. |
be-resilientresilient-runtime-behaviour | pass | high | Forecast/navigation content renders server-side and representative templates expose stable native links; no cut-off authored menu was observed apart from the separately reported consent component. |
be-resilientoffline-and-installable | issues | high | The site links a web app manifest, but navigator.serviceWorker.getRegistrations() returned no registrations. F16 medium: App-like weather experience has no offline runtime |
be-resilientnetwork-and-http-failure-states | issues | high | Invalid URL returns a clear Russian 404 message and home link, but its mobile recovery layout is clipped. F12 medium: The 404 recovery page overflows on mobile |
be-internationalisedlang-dir-and-logical-properties | pass | high | The document declares lang=ru and exposes ru, ru-BY, and ru-KZ hreflang variants; Russian reading order renders correctly. |
be-internationalisedlocale-aware-data | pass | high | Dates, weekdays, units, decimal conventions, and forecast labels render in Russian on both domestic and international-location content. |
be-internationalisedtime-zone-correctness | pass | high | Weather pages are keyed to a named location and display local date/time context rather than an ambiguous global timestamp. |
be-trustworthyno-dark-patterns | pass | high | Desktop consent presents equally prominent Отказаться and Согласиться actions; the mobile layout failure is reported separately as usability, not deceptive intent. |
be-trustworthyhumane-error-handling | not-applicable | high | No authored data-entry form with validation was present in the representative weather, news, or map paths. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, sign-up, or comparable multi-field input flow was present; authentication uses external OAuth links. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, payment, or account-management flow was in the public representative scope. |
be-sustainableoptimised-assets | issues | high | Images evidence found five of five images without srcset, four below-fold map thumbnails without loading=lazy, and one image without dimensions; maps Lighthouse found two low-resolution images. F17 medium: Image delivery omits responsive and lazy-loading hints |
be-sustainableno-wasteful-work | issues | high | HAR shows extensive background advertising/analytics fetch and script work disproportionate to initial weather content. F18 high: Third-party code and media cost is disproportionate to weather content |
be-sustainablethird-party-and-media-budget | issues | high | Third-party transfers were 2.65MB of 2.71MB total, led by a 488KB prebid script and multiple advertising stacks, while first-party content was a small fraction. F18 high: Third-party code and media cost is disproportionate to weather content |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent-facing capability exposure is emerging and was not declared as an intent for this public weather/content site. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the audited forecast, article, or map templates required on-device language-model inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | low | After repeated consent settings attempts, heap self size rose 2.7% and node count 1.5%; this bounded delta does not establish unbounded retained growth. |
be-memory-efficientbounded-footprint | issues | high | The weather-detail baseline heap summary contained 938,696 nodes and 49,952,936 bytes self size before a representative interaction. F19 medium: Initial memory footprint is disproportionate |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Heap summaries did not report Detached* constructors among top retained constructors; object and closure populations did not grow across the pair. |
Provenance
Canonical report: results/atomic/reports/0395-www_gismeteo_ru.json
Report SHA-256: 49c9c61081bf3193a8e1ad798a74b24afd670a5245931635ef607a009f5a36e4
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_gismeteo_ru/2026-07-20T11-42-36-975Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_gismeteo_ru/2026-07-20T11-42-36-975Z
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.