Manifest position 693 · CrUX rank bucket 1000

https://timesofindia.indiatimes.com

Coverage complete

Coverage-complete audit of four representative public templates plus a 404 recovery path. Excluded authenticated account, subscription/checkout, and internal editorial surfaces because they require credentials or a commercial commitment.

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-emulated screenshot is pixel-identical in appearance and byte size to the default capture, and the CSS probe found no prefers-color-scheme rule. F01 medium: The site does not adapt to the user’s dark color-scheme preference.
respect-user-preferences `respects-reduced-motion`	issues	high	The reduced-motion probe confirmed the media query matched but found seven running animations with 1–2 second durations. F02 medium: Animations continue while reduced motion is requested.
respect-user-preferences `respects-contrast`	issues	high	The CSS probe found neither prefers-contrast nor forced-colors handling; Lighthouse also found 28 low-contrast elements on the homepage. F03 low: No explicit high-contrast or forced-colors adaptation was found.
implement-natural-interactions `view-transitions`	issues	high	The full CSS probe found no view-transition rules or declarations across the rendered homepage. F04 low: Page and route changes do not use View Transitions.
implement-natural-interactions `scroll-driven-animations`	pass	high	DOM/CSS probe found no scroll-linked animation or custom scroll animation implementation to move onto the main thread.
implement-natural-interactions `physical-gestures`	pass	high	Screenshots and DOM inspection showed conventional native scrolling and controls, with no custom gesture surface fighting platform behavior.
provide-guided-navigation `scroll-state-aware-chrome`	issues	high	The CSS probe found no scroll-state container query or animation timeline despite a 24,163px homepage and persistent navigation chrome. F05 low: Navigation chrome does not expose scroll-state-aware behavior.
provide-guided-navigation `anchored-positioning`	issues	high	The DOM/CSS probe found a large city overlay but no anchor-name, position-anchor, or position-try usage. F06 low: Large menus and overlays are manually positioned rather than anchored.
provide-guided-navigation `directs-attention`	pass	high	Section labels, breadcrumbs, headline hierarchy, and real links visibly preserve orientation across home, section, article, and liveblog templates.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	Desktop and mobile screenshots of the homepage, section, article, and liveblog all open with a near/full-viewport consent layer over the primary content. F07 high: A consent interstitial obscures all editorial content on every tested content template.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	The DOM probe identifies role=dialog divs and a large fixed div, but no native dialog element for the modal flow. F08 medium: The blocking consent UI is implemented as custom div-based dialog chrome.
maximize-content-reduce-noise `reduced-chrome`	issues	high	The homepage probe counted 1,995 controls and the mobile document is 24,163px tall; the first content view is additionally hidden by consent UI. F09 high: The news feed is crowded by controls, promotional chrome, and ad infrastructure.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	pass	high	Layout primitives at 360x800 reported zero horizontal overflow on home, section, and article, all with a viewport meta tag.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	The CSS probe found no @container rules across a homepage with many reused card and navigation components. F10 low: No component-level container-query adaptation was found.
adapt-to-the-form-factor `input-modality-aware`	issues	high	Programmatic focus on the first visible link computed to outline:none; the probe counted 453 controls below 24px in one dimension, and Lighthouse found 8 article target-size failures. F11 high: Keyboard focus and touch target support are weak.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	Raw HTML and rendered pages expose prominent news headlines and section/article titles; crawler coverage is 90–98%.
support-core-task-success `primary-flow-completion`	issues	high	After activating “Do not consent” and waiting 3 seconds, the captured homepage remained dimmed behind a completely blank blocking panel. F12 critical: Rejecting tracking can leave a blank modal that still blocks the page.
support-core-task-success `clear-system-state-and-recovery`	issues	high	The post-rejection screenshot shows an empty white panel with no loading indicator, error message, close, retry, or back action. F13 high: The failed consent transition has no state explanation or recovery action.
be-fast-and-stable `good-core-web-vitals`	issues	high	Lighthouse measured homepage LCP 10.3s, CLS 0.257 and TBT 350ms; the article measured LCP 5.5s, TBT 410ms and 31.2s time to interactive. F14 high: Synthetic mobile performance is outside good Core Web Vitals ranges.
be-fast-and-stable `visual-stability`	issues	high	Lighthouse measured CLS 0.257 and identified layout-shift culprits; the images audit found all 100 homepage images missing a complete width/height pair. F15 high: The homepage shifts substantially during load.
be-fast-and-stable `efficient-main-thread`	issues	high	Lighthouse reported 350–410ms TBT and 13.2–31.2s time to interactive, while the HAR recorded 77 scripts totaling 2.28MB transferred. F16 medium: Heavy script work delays interactivity.
be-fast-and-stable `efficient-resource-delivery`	issues	high	HAR: 187 requests and 4.09MB transferred, including 2.28MB scripts; 178 requests and 3.84MB were classified off the main origin. Confirmed candidate ad scripts are async, so the issue is volume and dependency cost rather than parser blocking. F17 high: The homepage delivers an excessive request and byte payload.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	The HAR largest scripts include Taboola 330KB, Google ad code 202KB, gtag 177KB, prebid 147KB and GTM 131KB before accounting for their follow-on requests. F18 high: Third-party code dominates the load.
be-inclusive `names-roles-labels`	issues	high	The images primitive found 51 of 100 homepage images without alt; the DOM probe found the text search input had zero associated labels. F19 high: The homepage has many unnamed images and an unlabeled search field.
be-inclusive `sufficient-contrast`	issues	high	Lighthouse found 28 homepage contrast failures and 3 article failures. F20 high: Text and controls fail minimum contrast.
be-inclusive `structure-and-focus`	issues	high	The homepage has multiple H1s including consent headings, Lighthouse found article heading-order failures, and the first focused link computed with no outline. F21 high: Heading structure and focus visibility are inconsistent.
be-inclusive `legible-text`	pass	high	Article and feed text remains readable and reflows at 360px without horizontal overflow; screenshots show clear typographic hierarchy behind the consent layer.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	The viewport declares maximum-scale=1; Lighthouse failed meta-viewport and found 8 target-size failures on the article. F22 high: The viewport restricts zoom and several targets are undersized.
follow-best-practices `no-console-errors`	issues	high	Lighthouse failed errors-in-console on both the homepage and article. F23 medium: Both tested templates log browser errors.
follow-best-practices `sound-document-and-assets`	issues	high	The article failed charset placement and image aspect-ratio checks; the image audits found 100/100 homepage and 17/18 article images missing complete dimensions. F24 high: Document and image hygiene is inconsistent.
follow-best-practices `browser-platform-hygiene`	issues	high	Lighthouse reported one deprecated API warning and failed inspector-issues on the article. F25 medium: Deprecated APIs and DevTools issues remain on the article template.
be-discoverable `title-and-description`	pass	high	DOM and discoverability evidence found descriptive titles and meta descriptions in raw and rendered HTML on home, article, and liveblog.
be-discoverable `crawlable-and-mobile-friendly`	issues	high	Lighthouse found 25 non-descriptive homepage links and failed the zoom-restricting viewport; robots permits core content and raw HTML coverage remains high. F26 medium: Mobile and link semantics undermine otherwise strong discoverability.
be-discoverable `canonical-and-indexing-signals`	pass	high	Homepage exposes canonical URL, returns 200, robots allows core paths, and robots lists current and archive sitemaps.
be-discoverable `structured-and-shareable-metadata`	pass	high	Homepage DOM contains WebSite JSON-LD plus complete Open Graph title, URL, image, description, site name, and type.
be-private-and-secure `secure-transport-and-headers`	issues	high	All 17 observed cookies were reported insecure; many use SameSite=None, while nosniff is missing and HSTS lasts only one day. HTTPS, CSP and X-Frame-Options are present. F27 high: Cookie and header hardening is incomplete.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	The tracker probe saw 39 third-party origins and 11 known tracker endpoints; HAR classified 178/187 requests and 3.84MB off the main origin. F28 high: The page contacts an unusually broad tracking and advertising ecosystem before a consent choice.
be-private-and-secure `in-context-permissions-and-modern-auth`	pass	high	No notification or geolocation prompt appeared on load across repeated captures; authentication was not required for the representative public reading journey.
be-private-and-secure `defensive-browser-policies`	issues	high	The headers primitive found no Referrer-Policy, Permissions-Policy, or X-Content-Type-Options; CSP frame-ancestors and X-Frame-Options are present. F29 medium: Referrer-Policy, Permissions-Policy, and nosniff are missing.
be-resilient `progressive-enhancement`	pass	high	Discoverability primitive found 98% homepage, 90% article, and 95% liveblog content in raw HTML with no JS shell.
be-resilient `resilient-runtime-behaviour`	issues	high	After rejection the blocking panel remains blank over live content, demonstrating fragile asynchronous overlay state. F30 high: The consent overlay enters a broken persistent top-layer state.
be-resilient `offline-and-installable`	not-applicable	high	The audited surface is a public, continuously updated news publication rather than an installed app flow. A manifest exists, but offline installability is not required for the representative reading task.
be-resilient `network-and-http-failure-states`	pass	high	A deliberately missing route returned a real HTTP 404 and a useful Page Not Found message with category recovery links.
be-internationalised `lang-dir-and-logical-properties`	pass	high	DOM reports html lang=en and the CSS probe found logical inline properties; language edition links are present.
be-internationalised `locale-aware-data`	pass	high	The header renders an English India-specific date/time and exposes explicit language/edition choices rather than ambiguous numeric-only formatting.
be-internationalised `time-zone-correctness`	pass	high	The header labels the updated time explicitly as IST, avoiding an ambiguous local timestamp.
be-trustworthy `no-dark-patterns`	pass	high	Consent and refusal are equally prominent, plainly labelled actions in both desktop and mobile screenshots; the broken rejection transition is separately reported as a reliability issue.
be-trustworthy `humane-error-handling`	pass	high	The only visible text form is search, which has no required fields or validation failure state; no premature validation or blame language was observed.
be-trustworthy `trustworthy-input-assistance`	pass	high	The search input intentionally uses autocomplete=off for free-form news queries and does not obstruct paste or text entry in the inspected DOM.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	No checkout, subscription purchase, consented account-management, or authenticated flow was entered in this public reading-scope audit.
be-sustainable `optimised-assets`	issues	high	Homepage: 75/100 oversized, 92 missing srcset, 97 below-fold images not lazy, and 100 missing complete dimensions; article: 14/18 oversized. F31 high: Images are broadly oversized, dimensionless, and not responsive.
be-sustainable `no-wasteful-work`	issues	high	The HAR records 187 requests, 77 scripts, 27 fetch/XHR requests, and large analytics/ad/WASM dependencies while a consent wall blocks reading. F32 high: Background advertising and analytics work is disproportionate to initial reader value.
be-sustainable `third-party-and-media-budget`	issues	high	HAR classified 3.84MB of 4.09MB transferred and 178 of 187 requests off the main origin; trackers found 39 third-party origins. F33 high: Third-party bytes consume nearly the entire transfer budget.
be-agent-ready `structured-agent-capabilities`	issues	high	Discoverability is strong (90–98% raw HTML coverage), but Lighthouse agentic-browsing scored 0.49 on home and 0.67 on article and reported llms.txt guidance failures; no WebMCP registration was found in the DOM probe. F34 low: The public news experience exposes content but no structured agent capability layer.
be-agent-ready `on-device-inference`	not-applicable	high	No user task in the representative public news-reading paths requires on-device generative inference; adding it without a defined product need would add risk and complexity.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	medium	Baseline and post-scroll heap summaries rose from 47.46MB to 49.87MB (about 5%) after ten top-to-bottom cycles, not evidence of unbounded growth in this bounded exercise.
be-memory-efficient `bounded-footprint`	pass	medium	Heap summary measured 47.46MB baseline and 49.87MB post-interaction; substantial but proportionate to the unusually large news feed in this bounded capture.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	medium	Neither heap summary surfaced Detached* constructors among top retained populations, and closure growth was modest (35,323 to 35,675) across the bounded exercise.

Provenance

Canonical report: results/atomic/reports/0693-timesofindia_indiatimes_com.json
Report SHA-256: 130c48a43424b93370d0d5445e487d9a546b99b3bd171eb9fe1ffe087b5c0811
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/timesofindia_indiatimes_com/2026-07-22T10-41-16-565Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/timesofindia_indiatimes_com/2026-07-22T10-41-16-565Z
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.