Manifest position 366 · CrUX rank bucket 1000
https://www.seznam.cz
Coverage complete
Coverage-complete representative audit. Dynamic editorial content and consent state may vary by request.
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 | Desktop screenshots under light and prefers-color-scheme: dark are pixel-identical in surface treatment; the rendered CSS declares color-scheme: light. F001 medium: The portal ignores the operating system dark theme. |
respect-user-preferencesrespects-reduced-motion | pass | high | evaluate under prefers-reduced-motion: reduce found no active animations. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/prefers-contrast screenshot retained readable controls and content. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found no view-transition CSS while the portal has tab, menu and content state changes. F002 low: Primary state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | CSS inspection found scroll-timeline/animation-timeline use rather than only scroll handlers. |
implement-natural-interactionsphysical-gestures | pass | high | Mobile portal uses native horizontal scrolling and platform controls without evidence of pointermove-driven gesture replacement. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Rendered DOM includes sticky-header search chrome and CSS scroll timelines that respond to position. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover or edge-positioned menu archetype was present in the representative surfaces, so there was no anchored overlay to assess. |
provide-guided-navigationdirects-attention | pass | high | Active search tabs, section headings and a direct 404 return action visibly orient the user. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and 360px screenshots show a fixed consent sheet covering the lower viewport before interaction; on mobile it hides the lead story. F003 high: The consent prompt obscures primary content on every fresh load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The homepage overlay was absent from dialog/[role=dialog]/aria-modal probes, while the settings DOM uses a custom .szn-cmp-dialog-container. F004 medium: The consent surface is custom chrome without dialog semantics. |
maximize-content-reduce-noisereduced-chrome | pass | high | Outside the consent layer, the portal prioritises search, weather and editorial content with restrained framing. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360x800 the search result layout reported scrollWidth 1232px, clientWidth 360px and 872px horizontal overflow. F005 high: Search results force a desktop-width layout on mobile. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | CSS inspection found 66 container-query rules and the homepage itself has no horizontal overflow at 360px. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found none/0px outlines on search tabs, submit buttons and article links; many controls are 28-32px high. Lighthouse also failed target-size. F006 high: Keyboard focus is invisible on many primary controls and targets are undersized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport clearly presents Seznam search and a prominent submit action. |
support-core-task-successprimary-flow-completion | pass | high | A representative query loaded a populated results page and timetable exposes an actionable route form. |
support-core-task-successclear-system-state-and-recovery | pass | high | A nonexistent route returns a clear Czech explanation, homepage return button and support links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 10.6s, FCP 8.6s, TBT 800ms and performance 33; the trace independently measured LCP 4.13s and TBT 302ms. F007 high: Cold-load performance is far outside the good range. |
be-fast-and-stablevisual-stability | issues | high | The 360px layout observer measured CLS 0.125 with a 0.096 shift around 6.9s; all 100 inspected images lacked width/height attributes. F008 medium: Late content and unsized images shift the mobile page. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded six long tasks (longest 163ms, TBT 302ms); mobile layout recorded tasks up to 206ms and Lighthouse TBT was 800ms. F009 high: Heavy scripting repeatedly blocks the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 480 requests and 16.7MB transferred, including 315 images/14.2MB and six redirects; many preview images lacked cache headers. F010 high: Resource delivery is excessively heavy and redirect-rich. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR recorded 452 third-party-origin requests and a 644KB client bundle plus 406KB assistant widget and 153KB tag manager; Lighthouse reported TTI 65.6s. F011 high: Non-critical and third-party code dominates initial load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed button-name, image-alt, link-name and frame-title; the image probe counted 61/100 images without alt, and DOM probes found unnamed buttons/links. F012 high: Many images and controls lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse accessibility scored 70 and failed the color-contrast audit on the rendered homepage. F013 high: Text and essential UI fail minimum colour contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed heading-order; the DOM begins with empty H1s then H6 before H2, and the focus probe found invisible focus on most tested links/buttons. F014 high: Heading structure and focus treatment do not provide a reliable reading/keyboard path. |
be-inclusivelegible-text | pass | high | Body and heading copy is generally readable with clear section grouping on desktop and mobile. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Search results overflow by 872px at 360px and Lighthouse failed target-size; the homepage also includes videos with no <track> elements. F015 medium: Reflow and target-size support fail on a primary path. |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed errors-in-console; HAR recorded aborted fetches and a 400 autologin request. F016 medium: The homepage emits runtime/network errors. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse failed image-aspect-ratio and image-size-responsive; 100/100 inspected images omitted dimensions and 30 were oversized. F017 medium: Image sizing and aspect-ratio hygiene is poor. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported one deprecation, invalid source maps, inspector issues and four BFCache failure reasons. F018 medium: Deprecated APIs, source-map defects and BFCache blockers remain. |
be-discoverabletitle-and-description | pass | high | Homepage and search results expose descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Real href links, viewport meta and permissive robots rules were directly observed. |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage/search canonical URLs, successful main fetch and declared robots sitemaps were observed with no accidental noindex. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage exposes consistent Open Graph title, description, URL, image, locale and type for its visible portal identity. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show CSP only frame-ancestors, with no script/style/default-src policy; X-Content-Type-Options, Referrer-Policy and Permissions-Policy are absent. HTTPS and HSTS are present. F019 high: The CSP is only a frame policy and key response defenses are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture saw 36 third-party origins including Google Tag Manager/Analytics; HAR attributed 452 requests and 16.45MB to non-main origins, before consent was resolved. F020 high: The fresh homepage has a very large analytics and third-party footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; login markup includes WebAuthn and correctly tokenised username/current-password/OTP fields. |
be-private-and-securedefensive-browser-policies | issues | high | All nine observed cookies were SameSite=None and several non-auth cookies were script-readable; Referrer-Policy and Permissions-Policy were absent. F021 medium: Cookie and browser-policy posture is overly permissive. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 92% rendered-word coverage in raw HTML and no empty JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | The consent/settings route provides a bilingual scripted failure fallback, and menus/forms remained within tested viewports. |
be-resilientoffline-and-installable | issues | high | The timetable has a web app manifest, but navigator.serviceWorker.controller was absent in the tested load and no offline fallback was exposed. F022 medium: The app-like timetable surface exposes a manifest but no demonstrated offline fallback. |
be-resilientnetwork-and-http-failure-states | pass | high | The tested 404 gives a useful explanation, return action and support links rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Homepage and timetable set html lang=cs; login offers 18 language choices and the tested layouts preserve reading order. |
be-internationalisedlocale-aware-data | pass | high | Visible Czech dates, temperatures, prices and locale-specific copy are formatted for the active Czech locale. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public portal, search, timetable-start and settings states exposed no cross-time-zone event creation or DST-sensitive editing flow. |
be-trustworthyno-dark-patterns | issues | high | The settings screen presents a dominant Agree button for tailored ads and a CZK 49/month alternative; the non-pay, non-targeted detailed choice is a lower-emphasis text link. F023 high: The consent choice strongly steers users toward tracking or payment. |
be-trustworthyhumane-error-handling | issues | high | Before/after screenshots of the empty submit are effectively unchanged and the origin/destination inputs are not marked required in DOM. F024 medium: Submitting the empty timetable form gives no visible field-specific guidance. |
be-trustworthytrustworthy-input-assistance | issues | high | Homepage search and timetable origin/destination use autocomplete=off; timetable email/comment fields omit useful tokens, although login correctly uses username/current-password/one-time-code. F025 medium: Several meaningful inputs disable or omit autofill assistance. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The login surface labels account creation, supplies username/password/OTP autocomplete and offers multiple federated identity methods including BankID/mojeID. |
be-sustainableoptimised-assets | issues | high | The homepage transferred 14.2MB across 315 image requests; 30/100 inspected images were oversized, 45 used legacy formats and 13 lacked srcset. F026 high: Image delivery is disproportionate and poorly responsive. |
be-sustainableno-wasteful-work | issues | high | A fresh load issued 480 requests, 452 to non-main origins, with video metadata, assistant and analytics traffic plus repeated long tasks. F027 high: The page performs extensive background work before user demand. |
be-sustainablethird-party-and-media-budget | issues | high | 16.45MB of 16.72MB transferred came from non-main origins; scripts included assistant/analytics and the DOM contained three video players. F028 high: Third-party and media cost is not proportionate to the first-view portal task. |
be-agent-readystructured-agent-capabilities | issues | high | Discoverability is strong (92% raw/rendered coverage), but no WebMCP or agentic-tool registration was found; Lighthouse agentic-browsing scored 45. F029 low: The search portal has no structured agent-facing capability surface. |
be-agent-readyon-device-inference | not-applicable | high | No clearly beneficial private on-device summarisation or generation task was established in the tested public flows; emerging inference use is not an obligation by itself. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten hamburger open/close cycles, heap self size rose only 0.30% (90.90MB to 91.17MB) and nodes 0.21%, not unbounded growth. |
be-memory-efficientbounded-footprint | issues | high | The heap summary contained 1,532,409 nodes and 90.9MB self size at baseline (post interaction 1,535,702 nodes/91.2MB), including 162k closures post-interaction. F030 medium: The initial memory footprint is high for a portal landing page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Post-interaction heap top constructors contained no Detached* population and aggregate growth stayed below 0.3%. |
Provenance
Canonical report: results/atomic/reports/0366-www_seznam_cz.json
Report SHA-256: a8ef7f8d6d5c58f6c3c969499dec2ea7fa201d14da1a4f0e6064d219a49e5baf
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_seznam_cz/2026-07-20T06-46-15-547Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_seznam_cz/2026-07-20T06-46-15-547Z
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.