Manifest position 629 · CrUX rank bucket 1000
https://www.cricbuzz.com
Coverage complete
Coverage-complete audit of six representative paths. Video/gallery templates and authenticated/purchase completion were not covered because they duplicate media/listing patterns or require credentials/payment; login entry was inspected without solving CAPTCHA.
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 | The dark/reduced/contrast capture remains the same light rgb(236, 240, 241) surface with black text as the light capture; computed color-scheme is normal and inspected CSS has no prefers-color-scheme rule. F01 high: The site does not honour the user’s dark theme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Emulated reduced-motion capture reported zero active homepage animations after consent rejection; no autoplay carousel motion was observed. |
respect-user-preferencesrespects-contrast | issues | high | Under prefers-contrast: more the CSS probe found no prefers-contrast or forced-colors rules; Lighthouse reports 3.92:1 for GET APP and lower ratios in consent controls. F02 medium: High-contrast preferences are not explicitly supported and existing contrast failures remain. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection across representative pages found no view-transition declarations; navigation uses ordinary links and abrupt document/state replacement. F03 low: Route and state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | Context reviewed across all representative paths. |
implement-natural-interactionsphysical-gestures | pass | high | The mobile score/video rails use native horizontal layout with CSS scroll-snap present; no custom pointermove gesture layer was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Desktop captures show a static header and the CSS probe found no scroll-state container queries or scroll-driven progress treatment across a long 8,636px homepage. F04 low: Navigation chrome does not react to scroll state. |
provide-guided-navigationanchored-positioning | issues | high | The site exposes several dropdown navigation menus, while CSS inspection found no anchor-name, position-anchor, or fallback position rules. F05 low: Dropdown/menu positioning does not use anchor positioning. |
provide-guided-navigationdirects-attention | pass | high | Mobile navigation keeps a persistent bottom bar with Home visibly active, while live-score pages expose a descriptive H1 and contextual navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The initial 1440x1000 screenshot is dimmed behind a centered consent dialog; users must choose before reading scores or news. Reject is available and visually equal, which limits severity. F06 medium: A full-screen consent interruption obscures all content on first load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The CMP is a div with role=dialog rather than <dialog>; across inspected pages there are zero dialog, popover, or details elements despite menus and disclosures. F07 low: Transient UI relies on custom role-based markup instead of native overlay primitives. |
maximize-content-reduce-noisereduced-chrome | issues | high | Mobile first viewports contain an install banner, top ad, in-feed video ad, GET APP promo, and fixed bottom navigation; the HAR records 81 third-party requests before the core page settles. F08 high: Advertising and app-promotion chrome competes heavily with cricket content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout metrics report zero horizontal overflow at 360px for homepage and article; screenshots show a purpose-built mobile layout and viewport meta is present. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Desktop/mobile layouts do adapt, but inspected CSS across reused cards contains no @container rules. F09 low: Responsive layouts are viewport-driven rather than component-driven. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focused logo link reports outline none; structured probes found 12–30 visible controls below 24px on representative pages, and Lighthouse flags 56x14px sponsored controls on the article. F10 medium: Some controls have weak focus treatment or undersized targets. |
support-core-task-successclear-purpose-and-primary-action | pass | high | First viewports immediately expose current scores, article headline/content, schedule dates, and clearly labelled primary navigation. |
support-core-task-successprimary-flow-completion | pass | high | The public core journeys from homepage to live score, schedule and article all loaded with usable content and stable onward links without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | The invalid route shows “Nothing to show”, explains unavailability, and offers direct links to home, live scores, schedule, archives, news and photos. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse reports homepage LCP 3.4s, CLS 0.155, TBT 300ms and article LCP 2.7s, CLS 0.22, TBT 340ms; performance scores are 0.68 and 0.69. F11 high: Lab Core Web Vitals miss the good range on primary pages. |
be-fast-and-stablevisual-stability | issues | high | The layout observer measured CLS 0.110 on the mobile homepage and 0.191 on the mobile article; Lighthouse measured 0.155 and 0.22 respectively. F12 high: Late content causes visible cumulative layout shift, especially on mobile article pages. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measures 300–340ms TBT and 18.9–19.7s Time to Interactive; the custom post-load trace saw no long tasks, indicating the main cost is concentrated during load. F13 medium: Third-party work delays interactivity despite a clean short trace window. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 140 requests and 2,218,614 transferred bytes, including 69 scripts; 81 third-party requests transferred 1,627,042 bytes. Parser-inserted stylesheets and high-priority script chains start at navigation. F14 high: The critical load has a long, third-party-heavy dependency surface. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 769 KiB unused JavaScript and 36 KiB unused CSS; top waste includes Taboola, GPT, GTM, CleverTap, and k-words scripts. F15 high: Large amounts of shipped JavaScript and CSS are unused on initial load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse finds the logo and carousel links have no discernible name; login inspection finds an email input with no label, aria-label, id/name, required state, or autocomplete. F16 high: Important links and the email input lack accessible names/labels. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reports 3.92:1 for 14px GET APP controls and lower ratios in consent UI; article ad attribution also measures about 4.14:1 at small text sizes. F17 high: Text and controls fail WCAG contrast minimums. |
be-inclusivestructure-and-focus | issues | high | Lighthouse flags an H3 Featured Videos heading that skips hierarchy on the homepage; the first logo link is focusable but computed outline is none. F18 medium: Heading order and keyboard focus are inconsistent. |
be-inclusivelegible-text | pass | high | Desktop and 360px article screenshots show unclipped body copy with comfortable line length, spacing and clear headline hierarchy. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Every inspected page uses maximum-scale=1.0 and user-scalable=no; Lighthouse fails meta-viewport and also flags small article targets. Layout otherwise reflows without horizontal overflow at 360px. F19 high: The viewport prevents user zoom. |
follow-best-practicesno-console-errors | issues | high | The homepage probe captured CORS failure for Amazon APS and HTTP 400 from prebid-server; Lighthouse independently fails errors-in-console. F20 medium: Advertising integrations emit console/network errors on load. |
follow-best-practicessound-document-and-assets | issues | high | Document doctype and UTF-8 charset are valid, but the image audit found one image missing dimensions and eight 400–640px team images rendered at only 24px. F21 low: Some image assets are not proportionately sized. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports deprecated Topics API use from sdk.k-words.io, cookie inspector issues, and a BFCache eviction caused by an advertising frame redirect. F22 medium: Deprecated and inspector issues remain in third-party code. |
be-discoverabletitle-and-description | pass | high | Homepage, article, live score and schedule expose unique descriptive titles and meta descriptions; Lighthouse title/description audits pass. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | robots.txt says User-agent: * followed by Disallow: /, while only named crawlers such as Googlebot receive exceptions. The site is public and has a current sitemap, so generic and many AI/search crawlers cannot crawl it. F23 high: The default robots policy blocks all unspecified crawlers. |
be-discoverablecanonical-and-indexing-signals | pass | high | Representative pages return 200, expose canonical URLs, and a current sitemap enumerates key templates; the invalid route carries noindex. |
be-discoverablestructured-and-shareable-metadata | pass | high | Probes found 6–10 JSON-LD blocks plus Open Graph and Twitter metadata on representative entity pages. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS, nosniff, and SAMEORIGIN are present, but CSP is missing; all 11 observed first-party cookies lack Secure and many use SameSite=None, including long-lived analytics/ad identifiers. F24 high: Security headers and cookie attributes are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture found 31 third-party origins and 12 known tracker domains; HAR shows 81 third-party requests transferring 1.63 MB, including Taboola, DoubleClick, GTM, Criteo, CleverTap, Amazon Ads, and ScorecardResearch. F25 high: The default page has an unusually broad tracking footprint. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; sign-in offers passwordless email plus Google and Apple rather than a password-only flow. |
be-private-and-securedefensive-browser-policies | issues | high | Headers inspection found no CSP, Referrer-Policy, or Permissions-Policy; HSTS max-age is only 86400 seconds. Clickjacking and nosniff protections are present. F26 medium: Several browser-enforced defensive policies are missing. |
be-resilientprogressive-enhancement | pass | high | No-JavaScript/raw HTML retains 85% of homepage, 53% of article and 71% of live-score rendered words; none is an empty JS shell and article H1/meta survive. |
be-resilientresilient-runtime-behaviour | pass | high | Consent dialog remained within desktop/mobile viewports, representative pages settled without clipping, and live content continued to expose navigation and state. |
be-resilientoffline-and-installable | not-applicable | high | Context reviewed across all representative paths. |
be-resilientnetwork-and-http-failure-states | pass | high | A deliberately invalid route renders a useful recovery state with multiple actionable destinations instead of a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | All representative pages declare html lang=en; LTR is correct for the rendered English content and inspected shared CSS includes logical inline properties. |
be-internationalisedlocale-aware-data | issues | high | The server identified the visitor as GB, but the schedule and article render US-style JUL 23 and “Tue, Jul 21, 2026 • 6:10 PM” with no locale control or locale-specific formatting signal. F27 medium: Dates and times are not adapted to the visitor locale. |
be-internationalisedtime-zone-correctness | issues | high | The schedule displays dates/times for a global audience without a timezone label or user-zone affordance; the article timestamp similarly gives 6:10 PM without a zone. F28 medium: Match and publication times lack explicit time-zone context. |
be-trustworthyno-dark-patterns | pass | high | Consent presents equal “Do not consent” and “Consent” actions; sign-in consent is unchecked by default and sponsored recommendations are labelled. |
be-trustworthyhumane-error-handling | issues | high | The email, agreement, and CAPTCHA controls are not programmatically required; Continue is disabled with no inline explanation or aria-live error state, and the blank-state probe found no :invalid or role=alert feedback. F29 medium: The sign-in form hides requirements behind a disabled action. |
be-trustworthytrustworthy-input-assistance | issues | high | The email field is type=text and has empty autocomplete, name and id values, with only “Email Id” as a placeholder. F30 medium: The sign-in email field does not support autofill semantics. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Sign-in clearly identifies privacy/terms consent, offers passwordless/social choices, and does not preselect consent; no purchase commitment occurs on this entry step. |
be-sustainableoptimised-assets | issues | high | Image audit found eight team images naturally 400–640px wide but displayed at 24px; although the image CDN often negotiates WebP, source URLs request 0x0 originals. F31 medium: Small icons are sourced from much larger images. |
be-sustainableno-wasteful-work | issues | high | 69 script requests transfer 1.53 MB, while Lighthouse estimates 769 KiB unused JS and TTI near 19 seconds; several auction/tracking calls also fail. F32 high: Large background advertising and analytics stacks run during the initial experience. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 81 of 140 requests and 1,627,042 of 2,218,614 transferred bytes (73%); the largest scripts are Taboola, DoubleClick, GTM, CleverTap, and ad bidders. F33 high: Third parties dominate the page’s network budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Context reviewed across all representative paths. |
be-agent-readyon-device-inference | not-applicable | high | Context reviewed across all representative paths. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 carousel/scroll cycles, heap self size rose only 142,790 bytes (0.39%) and V8 node count by 469 (0.08%), with no unbounded retained-growth signal. |
be-memory-efficientbounded-footprint | issues | high | Performance metrics show about 10,474 DOM nodes, 1,713 event listeners and 28.2 MB JS heap used after consent rejection; the heap snapshot contains 617,337 V8 nodes and 36.3 MB self size. F34 medium: The homepage has a heavy steady-state DOM/listener footprint for a content surface. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after heap summaries show no Detached* constructor among retained populations and only small bounded growth after repeated interaction. |
Provenance
Canonical report: results/atomic/reports/0629-www_cricbuzz_com.json
Report SHA-256: 9d88900387b26d05b4bf32fad5e9473c1f9061c49b68f20f0ff23213ee189b25
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_cricbuzz_com/2026-07-22T00-59-57-519Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_cricbuzz_com/2026-07-22T00-59-57-519Z
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.