Manifest position 724 · CrUX rank bucket 1000
https://www.sozcu.com.tr
Coverage complete
Atomic coverage complete across homepage, section, article, and recovery templates.
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 | A dark-scheme capture is visually identical to the light capture; the probe reports color-scheme: normal and body background rgb(255,255,255). F01 medium: No dark theme is provided |
respect-user-preferencesrespects-reduced-motion | issues | high | With prefers-reduced-motion: reduce active, the probe still found sticky-animation with a 7000ms duration. F02 low: Reduced-motion preference does not remove all non-essential animation |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse found 15 contrast failures and the root exposes no color-scheme/high-contrast adaptation. F15 high: Text contrast fails in multiple places |
implement-natural-interactionsview-transitions | issues | high | Article CSS inspection found no view-transition rules while navigation is a multi-page route change. F03 low: Route changes are abrupt |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | Applicability was assessed during representative-path recon. |
implement-natural-interactionsphysical-gestures | not-applicable | high | Applicability was assessed during representative-path recon. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long homepage has 29,834 CSS px of content, but CSS inspection found no scroll-timeline/container-scroll-state behavior and the fixed header provides no progress cue. F04 low: Sticky chrome does not communicate scroll position |
provide-guided-navigationanchored-positioning | not-applicable | high | Applicability was assessed during representative-path recon. |
provide-guided-navigationdirects-attention | pass | high | The article presents a breadcrumb, dominant headline, byline, and clearly grouped share controls. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a modal dimming and blocking the homepage and article before any reading interaction. F05 critical: Consent wall obscures every primary page on load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM evidence found four DIV elements with role=dialog rather than native dialog/popover primitives, with multiple hidden H1/H2 trees injected into the page. F06 medium: Consent UI is a custom dialog stack |
maximize-content-reduce-noisereduced-chrome | issues | high | The blocking consent chrome consumes the central viewport and dims all editorial content. F05 critical: Consent wall obscures every primary page on load |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360px viewport both homepage and article report scrollWidth 507px and horizontalOverflowPx 147. F07 high: Mobile pages overflow by 147px |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The live stylesheet probe found zero container query rules while reusable cards/tickers appear at substantially different widths. F08 low: Components rely on viewport sizing only |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focusing the first 20 controls produced outline-style none and no box shadow for each sampled link. F09 high: Keyboard focus is not visible |
support-core-task-successclear-purpose-and-primary-action | pass | high | Section breadcrumb, news headline, summary and byline clearly communicate the article purpose. |
support-core-task-successprimary-flow-completion | issues | high | The representative homepage-to-article journey cannot reach readable content without first resolving a blocking consent modal; the manage screen offers no one-click reject-all. F10 high: Reading is blocked behind consent |
support-core-task-successclear-system-state-and-recovery | pass | high | The 404 state names the error, explains likely causes, and offers a homepage recovery action plus news links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Trace LCP was 7.37s; Lighthouse LCP was 4.28s with performance 60 and TBT 376ms. F11 high: Largest content appears too late |
be-fast-and-stablevisual-stability | pass | high | Observed CLS was 0.051 mobile and Lighthouse CLS 0.0076, both within the good threshold. |
be-fast-and-stableefficient-main-thread | issues | high | Trace found two ~121-123ms long tasks and Lighthouse TBT was 376ms. F11 high: Largest content appears too late |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR shows 5,467,900 transferred bytes, 121 third-party requests, 2.05MB script, 3.04MB images, and multiple parser-inserted critical resources. F12 high: The homepage transfers 5.47MB across 160 requests |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR attributes 4.98MB to third-party origins and shows repeated analytics/tag-manager payloads; Lighthouse TTI is 33.7s. F13 high: Third-party and advertising code dominates the load |
be-inclusivenames-roles-labels | issues | high | Lighthouse found one unnamed button, two unnamed links, and one untitled frame; the probe also sampled icon-only anchors. F14 high: Interactive controls lack accessible names |
be-inclusivesufficient-contrast | issues | high | Lighthouse reported 15 color-contrast failures on the loaded homepage. F15 high: Text contrast fails in multiple places |
be-inclusivestructure-and-focus | issues | high | Focus probes show no visible outline; the consent system injects several H1s and many H2 vendor headings alongside page headings. F16 high: Focus treatment and heading structure are polluted by consent UI |
be-inclusivelegible-text | pass | high | Article headline and summary use a clear hierarchy, generous size, and readable measure behind the consent layer. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At 360px, both tested templates overflow 147px, and the mobile consent copy/buttons extend beyond the visible layout. F17 high: The mobile/reflow view is clipped |
follow-best-practicesno-console-errors | pass | high | Lighthouse recorded zero console-error items. |
follow-best-practicessound-document-and-assets | issues | high | Image inspection found 90/100 without width/height, 93 without srcset, 90 legacy-format images, and 5 oversized images. F18 medium: Most images lack intrinsic dimensions and responsive sources |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported one deprecated API and notification permission requested on page load. F19 medium: Deprecated APIs and an unsolicited notification prompt are present |
be-discoverabletitle-and-description | pass | high | Both templates expose unique descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found two non-crawlable anchors and one robots.txt error; the mobile layout also overflows despite a viewport meta tag. F20 medium: Some links are not crawlable and robots validation fails |
be-discoverablecanonical-and-indexing-signals | issues | high | Discoverability reported titlePresentInRaw=false and h1PresentInRaw=false for the article, with only 48% rendered-token coverage. F21 medium: Article raw HTML omits key indexing signals under the crawler path |
be-discoverablestructured-and-shareable-metadata | pass | high | Article exposes NewsArticle, VideoObject, BreadcrumbList, canonical and complete Open Graph metadata matching visible content. |
be-private-and-securesecure-transport-and-headers | issues | high | Header inspection found no CSP, HSTS, nosniff, frame protection, Referrer-Policy, or Permissions-Policy; 14 cookies were flagged insecure. F22 high: Baseline security headers and secure cookie flags are missing |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence saw 50 third-party origins and 15 known trackers; HAR recorded 121 third-party requests and 4.98MB before the consent choice. F23 critical: Tracking starts before consent across a very large vendor surface |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Lighthouse notification-on-start failed on the public homepage. F24 high: Notification permission is requested on page load |
be-private-and-securedefensive-browser-policies | issues | high | The main response lacked HSTS, clickjacking protection, Referrer-Policy, Permissions-Policy, and CSP. F25 high: Browser-enforced defensive policies are absent |
be-resilientprogressive-enhancement | issues | high | Article discoverability found only 48% content overlap and no title/H1 in raw HTML, although rendered content exists. F26 high: Crawler/no-JS article delivery is incomplete |
be-resilientresilient-runtime-behaviour | pass | high | The tested consent and 404 states render deterministically and the error path remains navigable. |
be-resilientoffline-and-installable | issues | high | DOM probes found no manifest link; the public news site exposes service-worker capability but no installability metadata in tested pages. F27 low: No installable/offline entry point is exposed |
be-resilientnetwork-and-http-failure-states | pass | high | The missing-page state is explicit and offers recovery rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | html lang is tr and live styles include logical properties; Turkish content reading order is correct. |
be-internationalisedlocale-aware-data | pass | high | Currency values use Turkish separators and article times expose machine-readable ISO datetime values. |
be-internationalisedtime-zone-correctness | pass | high | Published, created, and modified timestamps are unambiguous ISO values with +03:00 offsets. |
be-trustworthyno-dark-patterns | issues | high | Initial UI emphasizes “İzin ver”; manage options exposes “Tümünü kabul et” and “Seçimleri onayla” but no one-click reject-all, while describing 286 partners. F28 critical: Consent choices are asymmetric |
be-trustworthyhumane-error-handling | not-applicable | high | Applicability was assessed during representative-path recon. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | Applicability was assessed during representative-path recon. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Applicability was assessed during representative-path recon. |
be-sustainableoptimised-assets | issues | high | One SVG response transfers 2,497,929 bytes; image inspection reports 90 legacy formats and 93 images without responsive sources. F29 high: Asset delivery is wasteful for an editorial homepage |
be-sustainableno-wasteful-work | issues | high | The first load makes 160 requests, including 121 third-party requests and 35 fetch/XHR requests, before a consent decision. F30 high: Background advertising and analytics work is disproportionate |
be-sustainablethird-party-and-media-budget | issues | high | HAR attributes 4.98MB of 5.47MB to third-party origins and 44 script requests overall. F31 high: Third-party payload exceeds the first-party payload by an order of magnitude |
be-agent-readystructured-agent-capabilities | not-applicable | high | Applicability was assessed during representative-path recon. |
be-agent-readyon-device-inference | not-applicable | high | Applicability was assessed during representative-path recon. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | After ten bottom/top traversals, heap summary rose from 52.6MB/916,348 nodes to 67.1MB/1,195,198 nodes; in-page used JS heap rose about 12MB even as element count fell. F32 medium: Memory grows materially after repeated feed traversal |
be-memory-efficientbounded-footprint | issues | medium | Baseline heap summary contains 916,348 nodes and 52.6MB self size before sustained interaction. F33 medium: Initial heap footprint is heavy for a news listing |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | No Detached* constructor entered either top-constructor summary; this gives medium-confidence evidence against a large detached-DOM population, though deeper listener tracing is still advisable. |
Provenance
Canonical report: results/atomic/reports/0724-www_sozcu_com_tr.json
Report SHA-256: fb437cf74b5e727206799de221adbfb7bde01227198e925d97fc3419dd52b567
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_sozcu_com_tr/2026-07-22T16-01-49-156Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_sozcu_com_tr/2026-07-22T16-01-49-156Z
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.