Manifest position 593 · CrUX rank bucket 1000
https://www.protothema.gr
Coverage complete
Atomic coverage complete across 58 checks and five representative paths. The fresh-load consent wall was evaluated as part of the real experience; content DOM/raw HTML remained inspectable.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Under emulated prefers-color-scheme: dark, body remained rgb(255,255,255) on rgb(0,0,0), color-scheme computed as normal, and the dark screenshot was byte-identical to light. F01 medium: The site ignores the user’s dark-color preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, eight animations remained, including three 30s infinite animations and one 6s infinite animation; CSS contained no prefers-reduced-motion rule. F02 high: Long-running motion continues under reduced-motion. |
respect-user-preferencesrespects-contrast | issues | high | Stylesheet probe found no prefers-contrast or forced-colors handling, while Lighthouse found 3.68:1 low-contrast text. F03 medium: High-contrast preferences are unsupported. |
implement-natural-interactionsview-transitions | issues | high | Same-document news navigation and content state are present, but fetched CSS/JS contained no view-transition usage. F04 low: Content navigation does not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, or entry/exit reveal that needed scroll-linked animation was observed on representative news templates. |
implement-natural-interactionsphysical-gestures | pass | medium | CSS probe found scroll-snap support and no evidence that core article/list scrolling was replaced by a custom pointer-driven surface. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The header is wired to a JavaScript stickit plugin, while fetched CSS contained no scroll-state container query or declarative scroll progress treatment. F05 low: Sticky navigation is driven by a JavaScript plugin rather than scroll-state-aware CSS. |
provide-guided-navigationanchored-positioning | issues | high | The site exposes menus and a consent overlay, but CSS contains no anchor-name or position-anchor support; the overlay is a manually layered fixed div. F06 low: Menus/overlays do not use anchor positioning. |
provide-guided-navigationdirects-attention | pass | medium | Persistent labelled section navigation, article cards, headings, and a distinct current content hierarchy provide clear destinations and attention cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Every fresh load is fully obscured by a long consent dialog describing 1,726 partners; desktop and 360px screenshots show no news content until a choice is made. F07 high: A full-screen consent wall blocks every primary content path. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The consent modal uses role=dialog on nested divs rather than <dialog>, and the page contains zero dialog, popover, or details primitives. F08 medium: role=dialog exists, but there are zero <dialog>, popover, or details elements. |
maximize-content-reduce-noisereduced-chrome | issues | high | The homepage has 475 visible interactive elements and a 41,385px mobile document, while a full-viewport consent layer dominates the initial experience. F09 medium: 475 visible controls and a 41,385px mobile document accompany the blocking consent layer. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | At 360x800 the homepage and article both reported scrollWidth=clientWidth=360, zero horizontal overflow, and a valid viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Fetched first-party stylesheets contain no @container rules despite cards/components being reused across the 41,385px responsive homepage. F10 low: No @container rule was found in first-party styles. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Keyboard focus was visible, but 90 of 475 visible interactive elements measured below 24px in at least one dimension. F11 medium: 90 visible controls measured below 24px in width or height. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The title, section navigation, all-news link, and descriptive story links clearly identify a breaking-news publication and expose the next reading action. |
support-core-task-successprimary-flow-completion | issues | high | The primary reading journey is needlessly interrupted before any content can be read by the full-viewport consent dialog on every tested route. F07 high: A full-screen consent wall blocks every primary content path. |
support-core-task-successclear-system-state-and-recovery | pass | medium | A fabricated route returned a real HTTP 404 after redirect, used a descriptive 404 title, and retained navigation links back into the site. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse performance was 0.57 with LCP 15.5s, Speed Index 9.3s, TBT 290ms, and TTI 18.4s; the independent trace measured LCP 4.99s. F12 critical: Lighthouse LCP was 15.5s, performance 57, Speed Index 9.3s, and TTI 18.4s. |
be-fast-and-stablevisual-stability | pass | medium | CLS was 0.052 in Lighthouse and 0.041 on the 360px layout run, both within the good threshold. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 290ms TBT and 18.4s time to interactive; the trace also captured a 72ms long task. F13 high: Lighthouse TBT was 290ms and TTI 18.4s; trace found a 72ms long task. |
be-fast-and-stableefficient-resource-delivery | issues | high | The load transferred 3.34MB in 126 requests; 54 scripts transferred 1.68MB, and parser-inserted high-priority stylesheets were present. F14 high: 126 requests/3.34MB, including 54 scripts/1.68MB and parser-blocking styles. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 603KiB unused JavaScript and 49KiB unused CSS; repeated Google tag bundles dominate the waste list. F15 high: Lighthouse estimates 603KiB unused JS and 49KiB unused CSS. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found unnamed social links, unnamed mainLink overlays, and nine images lacking alt; the independent probe counted 174 unnamed visible interactive elements. F16 high: Lighthouse found unnamed social/mainLink anchors and missing-alt images; probe counted 174 unnamed controls. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found repeated 3.68:1 text contrast failures for Games, tabs, and timestamps against white. F17 high: Lighthouse measured 3.68:1 for navigation, tabs, and timestamps. |
be-inclusivestructure-and-focus | issues | high | Focus styling was visible, but the homepage H1 is empty and Lighthouse found skipped heading levels including H3/H4 starts. F18 medium: The H1 is empty and Lighthouse found H3/H4 level skips. |
be-inclusivelegible-text | pass | medium | Article titles and body copy use readable Greek text, descriptive line wrapping, and no horizontal clipping at 360px. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport permits scaling and reflows without horizontal overflow, but 90 visible targets are below 24px and the detected video has no captions track. F19 medium: 90 targets are under 24px and the detected video has no captions track. |
follow-best-practicesno-console-errors | pass | medium | Lighthouse logged no browser console errors. |
follow-best-practicessound-document-and-assets | issues | high | The doctype and charset are valid, but 95 of 100 inspected images lack explicit dimensions and 93 lack srcset; six lacked alt. F20 medium: 95/100 images lack dimensions and 93/100 lack srcset. |
follow-best-practicesbrowser-platform-hygiene | pass | medium | No console errors or permission prompts on load were observed; Lighthouse best-practices completed without a deprecated-API or paste-prevention finding in the inspected evidence. |
be-discoverabletitle-and-description | pass | medium | Homepage and article expose unique descriptive titles and meta descriptions in rendered and raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | medium | Lighthouse passed crawlable anchors, robots.txt validity, crawlability, and viewport; the mobile layout has no overflow. |
be-discoverablecanonical-and-indexing-signals | pass | medium | Homepage and article return 200, declare self-canonicals, are index/follow, and robots/sitemap endpoints are available. |
be-discoverablestructured-and-shareable-metadata | pass | medium | The article contains NewsArticle JSON-LD and matching Open Graph title, description, URL, author, image, and update time. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and HSTS are present, but CSP and X-Content-Type-Options are absent; four analytics cookies are not Secure and all eight observed cookies were flagged insecure by the cookie audit. F21 high: No CSP or nosniff; four analytics cookies are not Secure. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The load contacted 22 third-party origins and seven known tracker domains; 74 third-party requests transferred 2.37MB before a consent choice. F22 high: 22 third-party origins, seven known trackers, and 2.37MB third-party bytes were observed before choice. |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No notification/geolocation permission prompt fired on load; authentication is not part of the representative public-news journey. |
be-private-and-securedefensive-browser-policies | issues | high | CSP/frame-ancestors or X-Frame-Options, Referrer-Policy, Permissions-Policy, and nosniff are all absent; only HSTS is present. F23 high: No CSP/frame-ancestors, X-Frame-Options, Referrer-Policy, Permissions-Policy, or nosniff. |
be-resilientprogressive-enhancement | pass | medium | Raw HTML preserved 96% of homepage and 93% of article rendered content; both titles/descriptions survive without JavaScript and the article H1 does too. |
be-resilientresilient-runtime-behaviour | pass | medium | The responsive pages retained navigation and content structure at 360px with no overflow; the consent overlay fit the viewport and exposed explicit choices. |
be-resilientoffline-and-installable | not-applicable | high | A valid standalone manifest exists, but this live breaking-news publication is intrinsically network-current; an offline app experience was not treated as required. |
be-resilientnetwork-and-http-failure-states | pass | medium | An unknown route resolves to an HTTP 404 page with a descriptive title and retained navigation rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The Greek site declares html lang=el, uses logical CSS properties, and provides a visible English-site switch; Greek is left-to-right so an explicit dir is not required. |
be-internationalisedlocale-aware-data | pass | medium | Rendered dates use Greek relative-time strings and machine-readable ISO datetime values; a dedicated English edition is linked. |
be-internationalisedtime-zone-correctness | pass | medium | Article metadata and visible time elements carry unambiguous ISO offsets such as +03:00 and updated_time values. |
be-trustworthyno-dark-patterns | issues | high | The first screen is a dense consent wall naming 1,726 partners; tracking requests and analytics cookies are already present before the user chooses, undermining an informed, honest default. F24 high: The wall names 1,726 partners while trackers/cookies activate before a user choice. |
be-trustworthyhumane-error-handling | pass | medium | The public content flow has no required form; Lighthouse found form controls labelled and the 404 state uses a clear title with recovery navigation. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, or sign-up data-entry flow is present in the representative public-news paths. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription purchase, authentication, or account-management flow was exposed on the representative public-news paths. |
be-sustainableoptimised-assets | issues | high | Of 100 inspected images, 93 lack srcset, 95 lack dimensions, 17 use legacy formats, and seven are oversized; images transferred 1.11MB. F25 high: 93 images lack srcset, 17 are legacy format, and seven are oversized. |
be-sustainableno-wasteful-work | issues | high | The initial load makes 126 requests and ships 1.68MB of scripts; Lighthouse estimates 603KiB unused JavaScript. F26 high: 126 requests, 1.68MB scripts, and 603KiB estimated unused JS. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 74 requests and 2.37MB, including 1.12MB from Google Tag Manager alone, disproportionate for the initial text-news view. F27 high: Third parties transfer 2.37MB; Google Tag Manager origins alone transfer 1.12MB. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The site publishes crawler-readable HTML and JSON-LD but declares no agent-facing transactional capability; WebMCP was not treated as required for this public news surface. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the representative paths requires on-device inference, and no built-in language-model API use was found. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten full-document scroll cycles, the post heap was smaller than baseline: 959,239 vs 997,826 nodes and 52.18MB vs 53.60MB self size. |
be-memory-efficientbounded-footprint | issues | high | A fresh homepage heap contains 997,826 nodes and 53.60MB self size, a large footprint for a document whose core task is reading news. F28 medium: Heap summary reports 997,826 nodes and 53.60MB self size. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | No Detached* constructor appeared among the top heap constructors, and node count fell by 38,587 after repeated scrolling rather than growing. |
Provenance
Canonical report: results/atomic/reports/0593-www_protothema_gr.json
Report SHA-256: ec5d81eb43ecd9e1af858aa042a2a9cc024c5f26b4ad8541651d8b50bc1cf522
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_protothema_gr/2026-07-21T19-34-42-914Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_protothema_gr/2026-07-21T19-34-42-914Z
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.