Manifest position 427 · CrUX rank bucket 1000
https://www.eenadu.net
Coverage complete
Atomic coverage complete: all 58 catalog checks received a conclusive judgement.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark/reduced-motion screenshot is visually identical to the light capture: white surfaces and light content cards remain; no usable dark theme is applied. F01 medium: No system-driven dark theme |
respect-user-preferencesrespects-reduced-motion | pass | medium | Evaluate probe under reduced-motion found no active document animations in the inspected state. |
respect-user-preferencesrespects-contrast | pass | medium | Lighthouse color-contrast audit scored 1.0 and the consent controls remained visually distinguishable. |
implement-natural-interactionsview-transitions | issues | high | UI probe found no page animation and no authored container CSS; DOM/CSS inspection found no View Transition or scroll-timeline usage despite carousel and route/state navigation. F02 low: Navigation and carousel state changes do not use declarative modern motion |
implement-natural-interactionsscroll-driven-animations | issues | high | UI probe found no page animation and no authored container CSS; DOM/CSS inspection found no View Transition or scroll-timeline usage despite carousel and route/state navigation. F02 low: Navigation and carousel state changes do not use declarative modern motion |
implement-natural-interactionsphysical-gestures | pass | medium | DOM/UI inspection found no custom pointer-drag handler or gesture that fought native scrolling on representative paths. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Screenshots and DOM show static desktop navigation/chrome; route changes and in-page navigation provide no directional transition, progress cue, or scroll-aware adaptation. F03 low: Navigation provides little state or attention guidance |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or viewport-edge anchored menu was present on the representative news, section, article, search, or error surfaces. |
provide-guided-navigationdirects-attention | issues | high | Screenshots and DOM show static desktop navigation/chrome; route changes and in-page navigation provide no directional transition, progress cue, or scroll-aware adaptation. F03 low: Navigation provides little state or attention guidance |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | First-load screenshots on homepage, article, search, and 410 show a large custom role=dialog consent wall obscuring the primary content; article capture additionally shows a blank white modal state. F04 high: Consent wall interrupts every primary path |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | First-load screenshots on homepage, article, search, and 410 show a large custom role=dialog consent wall obscuring the primary content; article capture additionally shows a blank white modal state. F04 high: Consent wall interrupts every primary path |
maximize-content-reduce-noisereduced-chrome | issues | high | Homepage and section screenshots devote substantial space to nav bars, side rails, ad placeholders, topic chips, and repeated modules, competing with headlines and article content. F05 medium: Dense chrome and advertising compete with news content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x800 viewport, layout reported scrollWidth 1200, clientWidth 360, and 840 px horizontal overflow; the screenshot shows only a clipped desktop slice. F06 critical: Mobile layout is a clipped 1200 px desktop canvas |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | At a 360x800 viewport, layout reported scrollWidth 1200, clientWidth 360, and 840 px horizontal overflow; the screenshot shows only a clipped desktop slice. F06 critical: Mobile layout is a clipped 1200 px desktop canvas |
adapt-to-the-form-factorinput-modality-aware | issues | high | Programmatic focus on the first visible link produced outline: none 0px. Lighthouse also reported target-size failures for tightly spaced links/buttons. F07 high: Keyboard focus is invisible and some touch targets collide |
support-core-task-successclear-purpose-and-primary-action | pass | medium | Homepage, section, and article screenshots clearly present Telugu news content, section labels, headlines, and real article links. |
support-core-task-successprimary-flow-completion | issues | high | First-load screenshots on homepage, article, search, and 410 show a large custom role=dialog consent wall obscuring the primary content; article capture additionally shows a blank white modal state. F04 high: Consent wall interrupts every primary path |
support-core-task-successclear-system-state-and-recovery | pass | medium | The invalid route redirects to /410 with a clear unavailable-content message and a populated list of current articles for recovery. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 4.5 s, FCP 3.4 s, CLS 0.295, Speed Index 5.9 s, and performance score 0.58; the trace corroborated load activity through 11.26 s. F08 high: Mobile loading and visual stability miss Core Web Vitals targets |
be-fast-and-stablevisual-stability | issues | high | Mobile Lighthouse measured LCP 4.5 s, FCP 3.4 s, CLS 0.295, Speed Index 5.9 s, and performance score 0.58; the trace corroborated load activity through 11.26 s. F08 high: Mobile loading and visual stability miss Core Web Vitals targets |
be-fast-and-stableefficient-main-thread | pass | medium | Trace measured 2 long tasks, 65.36 ms longest, and 21.63 ms total blocking time; Lighthouse TBT was 50 ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 205 requests and 5,018,815 transferred bytes, including 52 scripts/2.86 MB and multiple parser-inserted very-high-priority stylesheets; Lighthouse estimated 303 KiB unused JavaScript. F09 high: Heavy script and stylesheet delivery wastes the critical path |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR recorded 205 requests and 5,018,815 transferred bytes, including 52 scripts/2.86 MB and multiple parser-inserted very-high-priority stylesheets; Lighthouse estimated 303 KiB unused JavaScript. F09 high: Heavy script and stylesheet delivery wastes the critical path |
be-inclusivenames-roles-labels | issues | high | Search probe found an input with no associated label and a submit button with no accessible label text; the page title is also the generic homepage title. F10 medium: Search controls lack accessible names |
be-inclusivesufficient-contrast | pass | medium | Lighthouse color-contrast audit scored 1.0 with no failing nodes. |
be-inclusivestructure-and-focus | issues | high | Programmatic focus on the first visible link produced outline: none 0px. Lighthouse also reported target-size failures for tightly spaced links/buttons. F07 high: Keyboard focus is invisible and some touch targets collide |
be-inclusivelegible-text | pass | medium | Desktop section and article screenshots show readable Telugu text with clear card and article hierarchy. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At a 360x800 viewport, layout reported scrollWidth 1200, clientWidth 360, and 840 px horizontal overflow; the screenshot shows only a clipped desktop slice. Programmatic focus on the first visible link produced outline: none 0px. Lighthouse also reported target-size failures for tightly spaced links/buttons. F06 critical: Mobile layout is a clipped 1200 px desktop canvas F07 high: Keyboard focus is invisible and some touch targets collide |
follow-best-practicesno-console-errors | issues | high | Lighthouse reported a browser console error (third-party beacon HTTP 422) and a DevTools cookie inspector issue. F11 low: Third-party failures surface as browser errors and inspector issues |
follow-best-practicessound-document-and-assets | issues | high | Image audit found 18 oversized images, 47 without srcset, 3 below-fold images not lazy-loaded, 2 legacy-format images, and 1 missing alt. F12 medium: Responsive image delivery is incomplete |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported a browser console error (third-party beacon HTTP 422) and a DevTools cookie inspector issue. F11 low: Third-party failures surface as browser errors and inspector issues |
be-discoverabletitle-and-description | pass | medium | DOM recon found a descriptive title and meta description; Lighthouse SEO title and description audits scored 1.0. |
be-discoverablecrawlable-and-mobile-friendly | pass | medium | Real href links, viewport metadata, index/follow robots, and a valid robots.txt were observed; Lighthouse SEO scored 1.0. |
be-discoverablecanonical-and-indexing-signals | pass | medium | HTTP 200, canonical homepage URL, index/follow metadata, and sitemap directives in robots.txt were directly observed. |
be-discoverablestructured-and-shareable-metadata | pass | medium | Article DOM contains five JSON-LD scripts plus Open Graph title, URL, type, description, and image metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers audit found no Content-Security-Policy or Permissions-Policy. Cookie audit found 10 cookies marked insecure, including long-lived SameSite=None analytics/consent cookies. F13 high: Browser security policy and cookie flags are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Trackers audit observed 41 third-party origins and 7 known tracker domains. HAR attributed 190/205 requests and 4,988,164/5,018,815 bytes to third-party origins. F14 high: Advertising and tracking dominate network activity |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No authentication journey or browser-permission request exists on the audited public news surfaces. |
be-private-and-securedefensive-browser-policies | issues | high | Headers audit found no Content-Security-Policy or Permissions-Policy. Cookie audit found 10 cookies marked insecure, including long-lived SameSite=None analytics/consent cookies. F13 high: Browser security policy and cookie flags are incomplete |
be-resilientprogressive-enhancement | issues | high | Discoverability comparison found only 62% of rendered content words in raw server HTML, so a substantial portion of current content depends on JavaScript. F15 medium: A substantial share of current content is unavailable without JavaScript |
be-resilientresilient-runtime-behaviour | pass | medium | Representative listing and 410 recovery pages rendered usable content without clipped menus or blank runtime states at desktop size. |
be-resilientoffline-and-installable | pass | medium | Recon found manifest.json; the UI probe found an active service-worker controller, supporting installable/app-shell capability. |
be-resilientnetwork-and-http-failure-states | pass | medium | A deliberately invalid route produced a localized /410 recovery page with current-news links rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | HTML correctly declares lang=te, but rendered stylesheet evidence contains extensive physical direction rules (81 left, 30 right, 44 margin-left, 24 margin-right) and no demonstrated RTL/logical-property adaptation. F16 medium: Direction-sensitive CSS is not translation robust |
be-internationalisedlocale-aware-data | pass | medium | The document declares Telugu and rendered news timestamps and date content consistently for the publication locale. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited publication pages show local news timestamps but expose no cross-time-zone scheduling or recurring-event workflow. |
be-trustworthyno-dark-patterns | pass | medium | The consent dialog gives Consent and Do not consent equal visual weight, includes Manage options, and does not use confirmshaming copy. |
be-trustworthyhumane-error-handling | not-applicable | high | No data-entry or transactional form with validation was present; the only form is a single optional search field. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, sign-up, or other personal-data form was present on the representative public-news paths. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication, or account-management flow was exposed on the representative paths. |
be-sustainableoptimised-assets | issues | high | Image audit found 18 oversized images, 47 without srcset, 3 below-fold images not lazy-loaded, 2 legacy-format images, and 1 missing alt. F12 medium: Responsive image delivery is incomplete |
be-sustainableno-wasteful-work | issues | high | Trackers audit observed 41 third-party origins and 7 known tracker domains. HAR attributed 190/205 requests and 4,988,164/5,018,815 bytes to third-party origins. F14 high: Advertising and tracking dominate network activity |
be-sustainablethird-party-and-media-budget | issues | high | Trackers audit observed 41 third-party origins and 7 known tracker domains. HAR attributed 190/205 requests and 4,988,164/5,018,815 bytes to third-party origins. F14 high: Advertising and tracking dominate network activity |
be-agent-readystructured-agent-capabilities | not-applicable | high | Agent-facing capabilities are emerging and optional; this public news site exposes no agent action surface beyond crawlable content. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or generation feature is offered, so on-device inference has no current product task to support. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten bottom/top scroll cycles, heap totals were lower than baseline: 57,820,934 vs 58,042,271 bytes and 1,060,566 vs 1,068,632 nodes. |
be-memory-efficientbounded-footprint | issues | high | A single homepage state retained about 58 MB self-size across 1,068,632 heap nodes, a high baseline footprint for a news document even though repeated scrolling did not grow it. F17 medium: Baseline heap footprint is disproportionately large |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither baseline nor post-interaction heap summary listed Detached* constructors among retained-size leaders, and total nodes did not grow. |
Provenance
Canonical report: results/atomic/reports/0427-www_eenadu_net.json
Report SHA-256: 20cf4e2c8016ac4340ffda92d08e91a76f4ceec16ce25398662de1f6652bed53
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_eenadu_net/2026-07-20T18-08-04-689Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_eenadu_net/2026-07-20T18-08-04-689Z
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.