Manifest position 547 · CrUX rank bucket 1000
https://www.epicsports.in
Coverage complete
Coverage complete across 58 registered checks. The requested host redirects to https://live.epicsports.in/.
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 prefers-color-scheme: dark screenshot is visually identical to the light surface; the existing Night theme is only activated manually. F01 medium: The site does not follow the system dark-color preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe found seven running animations, including flare, four flashing border animations, blueFlow, and pulseGlow; no reduced-motion CSS rule was present. F02 medium: Continuous decorative animation continues when reduced motion is requested. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors and prefers-contrast screenshot keeps navigation, social actions, match tabs, borders, and text visible. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no view-transition-name or @view-transition usage across the multi-page home-to-article journey. F03 low: Page navigation swaps abruptly. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked parallax, reveal, carousel, or scrollytelling interaction exists on the representative templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, drag, pull-to-reveal, or other custom gesture surface exists; navigation uses links and scrolling. |
provide-guided-navigationscroll-state-aware-chrome | not-applicable | high | The header is not sticky or affixed, so there is no persistent scroll chrome whose state needs to react. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or viewport-edge menu requiring anchor positioning was present in the exercised states. |
provide-guided-navigationdirects-attention | pass | high | Screenshots show clear page headings, selected Today state, match-day tabs, and conventional same-origin links that preserve location. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots on all representative templates show no modal, consent wall, or full-viewport interstitial obscuring content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection shows #menubtn plus label.menublabel controls a fixed panel; there is no button, dialog, popover, or details primitive, and the input could not receive programmatic focus. F04 medium: The mobile navigation is an ad-hoc hidden checkbox and labels rather than a semantic control. |
maximize-content-reduce-noisereduced-chrome | issues | high | Desktop and mobile screenshots show four large promotional rows before match information, consuming roughly 340px of the first mobile viewport and repeating on home, article, and contact templates. F05 medium: Repeated social-channel promotions crowd the primary sports content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Layout probes on home, article, and contact at 360x800 all report scrollWidth 360, overflow 0, and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Desktop/mobile screenshots show header, social rows, content cards, and footer adapting from wide to narrow without clipping; no component is reused at conflicting container widths. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe focused links successfully but every sampled link computed outline: none and box-shadow: none. Control geometry also shows nav and social controls at 35px high. F06 high: Keyboard focus is invisible and several controls are below recommended target height. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home identifies today’s matches and day navigation; article has a specific match title; contact has a clear heading and email purpose. |
support-core-task-successprimary-flow-completion | pass | high | The home article link reaches a complete match-detail page, and the contact route provides a visible email address without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | The empty match state says there are no important matches, and a real 404 response renders a Page not found view with global navigation. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 2.6s on home and article and 3.8s on contact; article time-to-interactive was 12.8s. The direct trace corroborated home LCP at 2.10s under a separate desktop run. F07 medium: Key templates miss the good LCP threshold in lab tests. |
be-fast-and-stablevisual-stability | pass | high | Layout observers reported CLS 0 on all 360px routes; Lighthouse measured 0 on home/contact and 0.002 on article. |
be-fast-and-stableefficient-main-thread | pass | high | Direct trace had zero long tasks and 0ms TBT; Lighthouse TBT was 0ms on home/contact and 120ms on article, within the good lab threshold. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR plus DOM confirmation found two Font Awesome stylesheets in head and synchronous classic scripts for timer.js and widgets.365scores.com/main.js; Lighthouse flagged the network dependency tree. F08 medium: Parser-blocking styles and synchronous third-party scripts lengthen the critical path. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR recorded 22 script requests and 406,812 script bytes. Two major Font Awesome versions load together, while 365scores creates 21 requests and GTM is the largest script at 134,970 bytes. F09 medium: Third-party and duplicate code dominate the page load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found no main landmark on every template, malformed ul/li nesting, unnamed linked images on article/contact, and a contact image without alt text. Accessibility scores were 85, 81, and 73. F10 high: Landmarks, list semantics, alt text, and link names are inconsistent. |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured white on WhatsApp green at 1.98:1, Instagram at 4.33:1, share controls as low as 2.46:1, and article metadata at 3.84:1. F11 medium: Several action and metadata colors fail WCAG contrast. |
be-inclusivestructure-and-focus | issues | high | The active focus probe reports outline none and box-shadow none for every sampled visible link, while the global CSS resets outline to 0. F12 high: Keyboard users receive no visible location cue. |
be-inclusivelegible-text | pass | high | Desktop/mobile screenshots show readable 16px body text, clear headings, and no clipped or overlapping copy at 360px. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The control-size probe found primary nav, social icons, day tabs, and footer links at 35px or 15px high, below the commonly recommended 44px target. Reflow itself had no overflow. F13 medium: Some interactive targets are too short for reliable touch use. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured SyntaxError: Unexpected token ) on home, article, and contact mobile documents. F14 medium: Every tested template throws a JavaScript syntax error. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found all three home images missing a complete width/height pair, two oversized images, and no responsive source sets. Lighthouse found the article preview displayed at 2.36:1 despite a 3.00:1 source ratio. F15 medium: Images are distorted or missing intrinsic sizing. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices evidence found no deprecated-API, permission-on-load, paste-prevention, or vulnerable-library failure beyond the separately reported console error. |
be-discoverabletitle-and-description | issues | high | Article and contact pages reuse the homepage description about news, wallpapers, scoreboards, and TV lists instead of describing the match or contact route. F16 medium: Page descriptions are generic rather than template-specific. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | All prominent navigation/content links have href values, viewport metadata is present, and robots allows search crawling. |
be-discoverablecanonical-and-indexing-signals | pass | high | Home, article, and contact return successful content; canonical URLs are correct; live robots points to a 200 sitemap containing the article; no noindex was found. |
be-discoverablestructured-and-shareable-metadata | issues | high | The article NewsArticle JSON-LD says headline "Article headline", uses example.com image URLs, and contains an unresolved author-photo substitution; homepage BlogPosting data also contains unresolved template text. F17 high: Article structured data contains placeholders and inaccurate fields. |
be-private-and-securesecure-transport-and-headers | issues | high | Header inspection found no CSP or HSTS. All three analytics cookies lacked Secure and used SameSite=None, including a 400-day _ga cookie. F18 high: HTTPS is present but key defenses and cookie flags are missing. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | HAR recorded 33 of 41 requests and 606,421 of 702,185 transferred bytes as third-party. Tracker evidence found Google Analytics and Tag Manager plus ten third-party origins. F19 high: The page sends most requests and bytes to third parties without a visible privacy choice. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No authentication flow or browser permission request exists on the representative public content routes. |
be-private-and-securedefensive-browser-policies | issues | high | The main response has no X-Frame-Options or CSP frame-ancestors, no Referrer-Policy, and no Permissions-Policy. F20 medium: Clickjacking, referrer, and capability policies are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability captures show 100% raw-content coverage on home, 88% article, and 98% contact with title and H1 present without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | The CSS-driven mobile menu and content templates rendered without clipping at 360px; no fragile overlay or async blank state appeared. |
be-resilientoffline-and-installable | not-applicable | high | This is a server-rendered sports content site rather than an installed application; an offline/installable product experience is not part of the observed intent. |
be-resilientnetwork-and-http-failure-states | pass | high | A nonexistent URL returns HTTP 404 and a readable Page not found state while retaining the global navigation. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Rendered DOM reports lang=en and dir=ltr, but CSS evidence contains extensive float:left/right, margin-left/right, padding-right, and positioned left/right declarations rather than logical properties. F21 medium: The stylesheet is heavily tied to physical left/right directions. |
be-internationalisedlocale-aware-data | issues | high | The article renders "20 July 2026", "12:30 AM IST", 11:00 PM for UAE, and 10:00 PM for Saudi Arabia, with no semantic time elements and no page-owned Intl formatting signal. F22 medium: Match dates and times are hard-coded instead of formatted for the visitor. |
be-internationalisedtime-zone-correctness | issues | high | The match lists abbreviations or country flags for three hand-picked zones but no offset, zone identifier, conversion control, or user-local time; 7/19 elsewhere on the same page conflicts with 20 July. F23 medium: Time-zone presentation is incomplete and ambiguous. |
be-trustworthyno-dark-patterns | pass | high | Visual review found no confirmshaming, forced continuity, disguised advertisement, checkout trap, or preselected consent control. |
be-trustworthyhumane-error-handling | not-applicable | high | No form exists on the audited home, article, or contact routes; contact is provided as an email address. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No user input fields exist on the representative routes. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, consent, authentication, or account-management flow exists on the representative routes. |
be-sustainableoptimised-assets | issues | high | Image evidence found a 1600px logo displayed at 200px and a 2340px preview displayed around 178px, both without srcset; one content image remains JPEG. F24 medium: Oversized and non-responsive images waste transfer. |
be-sustainableno-wasteful-work | issues | high | The homepage says there are no important matches while 365scores makes 21 requests and transfers 257,559 bytes. F25 medium: An empty match state still loads a large external scores application. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 86% of transfer bytes, led by scores, tag manager, CDN icon assets, and analytics on a small content page. F26 medium: Third-party resources are disproportionate to visible content. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The site is a read-only content publication with no safe transactional capability for an agent to invoke; raw content and metadata were evaluated separately. |
be-agent-readyon-device-inference | not-applicable | high | No summarization or language-model feature is part of the observed product, so on-device inference is not needed for current task success. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten mobile-menu open/close cycles, retained self size changed from 9,182,323 to 9,237,022 bytes (0.6%) and node count from 184,164 to 184,587 (0.23%), not unbounded growth. |
be-memory-efficientbounded-footprint | pass | high | The loaded scores/content page retained about 9.2MB self size and 184k heap nodes, proportionate to its third-party widget load. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Before/after heap summaries show stable closure and object counts and no Detached constructor population in the reported summaries. |
Provenance
Canonical report: results/atomic/reports/0547-www_epicsports_in.json
Report SHA-256: 39d73d16e4fa41cd8d5db0e7c97fad46ef638cc4f959086e19984b8783e3e0ae
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_epicsports_in/2026-07-21T12-06-04-171Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_epicsports_in/2026-07-21T12-06-04-171Z
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.