Manifest position 248 · CrUX rank bucket 1000

https://www.sondakika.com

Coverage complete

Atomic coverage complete across 58/58 checks and five representative paths.

Attempts

1 / 3

Judged checks

58 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	The dark-mode probe reported colorScheme "normal" and a white body background; the dark screenshot retains the light consent surface and page palette. F01 medium: The site does not adapt to the user’s dark color-scheme preference.
respect-user-preferences `respects-reduced-motion`	pass	high	Reduced-motion emulation found zero active animations, so no non-essential motion remained.
respect-user-preferences `respects-contrast`	pass	high	Forced-colors/high-contrast screenshot retains visible text, borders and controls.
implement-natural-interactions `view-transitions`	issues	high	The active probe found browser support but no authored view-transition usage; navigation remains a hard document swap. F02 low: Page and route changes have no authored View Transitions.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	No scroll-linked animation or parallax surface was present to implement or test.
implement-natural-interactions `physical-gestures`	not-applicable	high	No gesture-driven carousel, swipe, pull-to-refresh or comparable custom gesture was present.
provide-guided-navigation `scroll-state-aware-chrome`	issues	high	The 22,394px homepage has no authored container/scroll-state signal and no visible reading or feed-position cue. F03 low: The long news feed provides no scroll-state progress or responsive chrome.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No tooltip or edge-sensitive anchored popover was exposed in the representative paths.
provide-guided-navigation `directs-attention`	issues	high	The navigation probe found no authored View Transition, scroll marker, or scroll snap behavior on a very long feed. F04 low: Navigation does not visibly direct attention after state or route changes.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	Mobile screenshots of the homepage, article and currency utility show the consent dialog obscuring all primary content before interaction. F05 high: A full-screen consent interstitial blocks every audited page on first load.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	The DOM probe found 0 <dialog>, 0 popover, 0 details, and four role=dialog elements. F06 medium: Consent overlays are custom role=dialog structures rather than native dialog primitives.
maximize-content-reduce-noise `reduced-chrome`	pass	high	Beyond the consent layer, layouts devote the viewport to headlines, article content and utility data rather than decorative app framing.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	All four representative 360px layouts reported 0px horizontal overflow and a viewport meta tag.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	The active probe found no authored @container usage across reusable news cards and navigation components. F07 low: No component-level container-query adaptation was found.
adapt-to-the-form-factor `input-modality-aware`	issues	high	Programmatic focus on the first link produced outline:none and no box-shadow; the probe listed many 15–20px-high links. F08 high: Keyboard focus is invisible and multiple controls have small hit areas.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	Headings and navigation clearly identify breaking news, category, article and currency purposes.
support-core-task-success `primary-flow-completion`	pass	high	Homepage links use real hrefs and the representative article loaded with headline, metadata and content in raw HTML.
support-core-task-success `clear-system-state-and-recovery`	pass	high	The unknown route returns a clear Turkish 404 state with explanation, search and category recovery links.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured homepage LCP 9.3s and CLS 0.38; article LCP was 19.4s with 550ms TBT. F09 critical: Core Web Vitals are poor on primary templates.
be-fast-and-stable `visual-stability`	issues	high	The mobile layout observer measured CLS 0.391, including a single 0.38675 shift; Lighthouse independently measured 0.38. F10 high: The homepage shifts substantially after load.
be-fast-and-stable `efficient-main-thread`	issues	high	The trace recorded a 997ms long task and 947ms TBT; Lighthouse reported 18.5s main-thread work on the homepage. F11 high: Heavy JavaScript blocks the main thread.
be-fast-and-stable `efficient-resource-delivery`	issues	high	HAR recorded 149 requests and 3.59MB transferred; Lighthouse estimated 540–1180ms render-blocking savings and 513–890KiB cache savings. F12 high: Resource delivery is heavy and includes render-blocking and weak-cache opportunities.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	Lighthouse estimated 1,001KiB unused JS on the homepage, 1,335KiB on the article, and 61KiB unused CSS. F13 high: Large amounts of unused JavaScript and CSS ship on primary pages.
be-inclusive `names-roles-labels`	issues	high	Lighthouse failed link-name on the representative article, and the DOM probe found an empty anchor without text, aria-label, or an image alt. F14 high: Some article links lack accessible names.
be-inclusive `sufficient-contrast`	issues	high	Lighthouse failed the color-contrast audit on both homepage and article templates. F15 high: Text/background combinations fail minimum contrast.
be-inclusive `structure-and-focus`	issues	high	The probe found multiple H1s, hundreds of H2s, no <main>, and focus with outline:none; Lighthouse also reported malformed article list structure. F16 high: Heading/landmark structure and keyboard focus are not reliable.
be-inclusive `legible-text`	pass	high	Representative mobile screenshots show readable body copy and headings without clipping or horizontal overflow.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	The target probe found many navigation links only 15–20px tall, despite successful narrow-viewport reflow. F17 medium: Several interactive targets are too short for reliable touch use.
follow-best-practices `no-console-errors`	issues	high	Lighthouse failed errors-in-console on both homepage and article. F18 medium: Primary pages log browser console errors.
follow-best-practices `sound-document-and-assets`	issues	high	The image audit found 7 missing dimensions, 26 oversized images, 63 without srcset and 93 legacy-format images; Lighthouse found incorrect aspect ratios. F19 medium: Image dimensions, aspect ratios, and formats are not consistently sound.
follow-best-practices `browser-platform-hygiene`	issues	high	Lighthouse failed notification-on-start, deprecated APIs, inspector issues and BFCache (five reasons) on the homepage. F20 high: The page requests notification permission on load and has platform hygiene failures.
be-discoverable `title-and-description`	pass	high	Homepage and article have descriptive titles and meta descriptions.
be-discoverable `crawlable-and-mobile-friendly`	pass	high	Real href links, viewport metadata and permissive robots were observed; raw content coverage is high.
be-discoverable `canonical-and-indexing-signals`	pass	high	Pages returned 200 with canonicals; robots and sitemap files were fetched and no accidental noindex was found.
be-discoverable `structured-and-shareable-metadata`	issues	high	The article probe returned "invalid" for its application/ld+json block, despite correct title, description and canonical signals. F21 medium: The representative article’s JSON-LD is not parseable as JSON.
be-private-and-secure `secure-transport-and-headers`	issues	high	Headers found no CSP or HSTS; cookie audit found all 33 cookies flagged, including 30 without Secure and pervasive SameSite=None; article Lighthouse found one insecure request. F22 critical: Transport protections and cookie attributes are unsafe.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	Tracker capture found 35 third-party origins and five known tracker domains; the consent copy names 619 partners and HAR shows 149 requests. F23 critical: The page has an excessive tracking and third-party data footprint.
be-private-and-secure `in-context-permissions-and-modern-auth`	issues	high	Lighthouse failed notification-on-start on both homepage and article. Authentication was not exercised because login is a separate portal. F24 high: Notification permission is requested at page startup rather than in context.
be-private-and-secure `defensive-browser-policies`	issues	high	The header audit found no frame protection, X-Content-Type-Options, Referrer-Policy or Permissions-Policy, in addition to missing CSP and HSTS. F25 critical: Browser-enforced defensive policies are absent.
be-resilient `progressive-enhancement`	pass	high	Raw HTML contains 90% of homepage and 68% of article rendered content, including title/H1/description; neither is a JS shell.
be-resilient `resilient-runtime-behaviour`	pass	high	Representative templates loaded and reflowed without horizontal clipping, and the consent overlay remained within viewport bounds.
be-resilient `offline-and-installable`	pass	high	A valid manifest is linked and returned for this app-capable news site; offline content was not required for the core public reading path.
be-resilient `network-and-http-failure-states`	pass	high	The tested unknown URL renders an actionable 404 with search and route links rather than a blank shell.
be-internationalised `lang-dir-and-logical-properties`	issues	high	The probe confirmed lang=tr, but found 0 logical-property tokens and 34 physical left/right padding or margin tokens in page HTML/CSS. F26 medium: The Turkish language is declared, but physical CSS directions dominate.
be-internationalised `locale-aware-data`	issues	high	Article time elements use non-ISO datetime values such as 19.07.2026 09:44:00, and the currency template exposes locale data without a table structure. F27 medium: Visible date/currency data is not exposed in robust locale-aware semantics.
be-internationalised `time-zone-correctness`	issues	high	The datetime attributes are local dotted date strings with no UTC offset or IANA zone, so DST/zone interpretation is not deterministic. F28 medium: Article timestamps are ambiguous about offset and time zone.
be-trustworthy `no-dark-patterns`	pass	high	Consent presents equally prominent Consent and Do not consent actions and a manage-options path; no forced continuity was observed.
be-trustworthy `humane-error-handling`	not-applicable	high	No user-data form with validation was present on the audited public templates.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	The only public text input observed was optional 404 search; no address, payment or account input was in scope.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	No checkout, subscription or account-management flow exists on the audited public host; login is a separate portal.
be-sustainable `optimised-assets`	issues	high	Of 100 images, 93 use legacy formats, 63 lack srcset and 26 are oversized; Lighthouse estimates up to 448KiB image savings on the article. F29 high: Image delivery wastes bytes across a content-heavy news page.
be-sustainable `no-wasteful-work`	issues	high	HAR recorded 39 scripts and 35 third-party origins; trace TBT was 947ms and Lighthouse reported 18.5s main-thread work. F30 high: Background and third-party work is disproportionate to reading news.
be-sustainable `third-party-and-media-budget`	issues	high	The homepage transferred 3.59MB across 149 requests, including 1.79MB of scripts and 35 third-party origins. F31 high: Third-party scripts dominate a multi-megabyte page load.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	The public news-reading site exposes no transactional agent capability requiring WebMCP; crawlable content remains available in raw HTML.
be-agent-ready `on-device-inference`	not-applicable	high	No user task on these public templates requires on-device inference; absence is an emerging opportunity, not a failure.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	After ten full-page scroll cycles, heap node count fell from 720,065 to 662,127 and self size from 39.3MB to 37.1MB rather than growing.
be-memory-efficient `bounded-footprint`	issues	high	The baseline heap had 720,065 heap nodes and 39.3MB self size, while the DOM probe counted 13,996 elements for a news listing. F32 medium: The homepage has a large initial memory and DOM footprint.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	The repeated-scroll post snapshot had 57,938 fewer nodes overall; no accumulating population was signaled in this bounded exercise.

Provenance

Canonical report: results/atomic/reports/0248-www_sondakika_com.json
Report SHA-256: 307888db058c50152a99869e057abef1588c4dad2f70e4c1f96aeefb63be40de
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_sondakika_com/2026-07-19T10-43-32-709Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_sondakika_com/2026-07-19T10-43-32-709Z
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.