Manifest position 238 · CrUX rank bucket 1000
https://www.filgoal.com
Coverage complete
Atomic coverage complete across 58 checks and six representative paths. No local source was supplied; critique only.
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 | Computed style and dark screenshot under emulation show no preference-driven theme. FG-01 medium: No user-preference dark theme |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, getAnimations() returned no active animations on the primary page. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors/high-contrast screenshot retained visible text, borders and controls. |
implement-natural-interactionsview-transitions | pass | high | Live stylesheet inspection found view-transition-name usage and no jarring route swap was observed in the representative link journey. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling or scroll-linked reveal was present on the audited templates, so there is no scroll-linked motion implementation to judge. |
implement-natural-interactionsphysical-gestures | not-applicable | high | Core news, article and match tasks use ordinary links and document scrolling; no required custom swipe/pull gesture was found. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Long mobile captures retain a compact persistent navigation/footer and visible section context without obscuring the reading column. |
provide-guided-navigationanchored-positioning | pass | high | Stylesheet inspection found anchor-name usage; no detached or clipped tooltip/menu was observed at viewport edges. |
provide-guided-navigationdirects-attention | pass | high | Section tabs, breadcrumbs, article headings and match score hierarchy visibly identify location and next destinations. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Screenshots directly show stacked notification and consent interruptions on load. FG-03 critical: Two first-visit interruptions obscure the primary content |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM probe found zero dialog/popover primitives while overlay UI was visible. FG-02 medium: On-load overlays are not represented by native page primitives |
maximize-content-reduce-noisereduced-chrome | issues | high | Screenshots show ads, placeholders and side chrome consuming more space than primary editorial content. FG-04 high: Advertising and auxiliary chrome overwhelm editorial content |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, layout metrics reported scrollWidth=clientWidth=360 and zero horizontal overflow on home and article. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Stylesheet probe found no @container usage for reused cards/modules. FG-05 low: Components rely on viewport layout rather than container adaptation |
adapt-to-the-form-factorinput-modality-aware | issues | high | Direct focus/target probe found no visible focus outline and 151 undersized controls. FG-06 high: Keyboard focus and target sizing are inadequate |
support-core-task-successclear-purpose-and-primary-action | pass | high | After dismissing overlays, page titles, scores, section headings and article headlines make the sports-news purpose and reading destinations clear. |
support-core-task-successprimary-flow-completion | issues | high | First-visit overlays cover the reading/navigation flow on every content template sampled. FG-07 high: First-visit overlays obstruct the reading journey |
support-core-task-successclear-system-state-and-recovery | issues | high | Unknown route produced a completely empty 200 response with no recovery UI. FG-08 high: Unknown routes return an empty success response |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse and trace show severely slow LCP/TBT and poor homepage CLS. FG-09 critical: Core load metrics are far outside good ranges |
be-fast-and-stablevisual-stability | issues | high | Layout observers measured CLS 0.559/0.187 and image audit found missing dimensions. FG-10 high: Late content causes severe layout movement |
be-fast-and-stableefficient-main-thread | issues | high | Trace and Lighthouse recorded long tasks and 0.97-1.92s blocking time. FG-11 high: Third-party and page scripts block the main thread |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR/Lighthouse show heavy delivery, blocking CSS and failed dependency/LCP discovery insights. FG-12 high: Critical delivery is heavy and poorly prioritized |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | 60 scripts and 2.91MB script transfer, mostly third-party, dominate load. FG-13 high: Script and third-party code dominate the page load |
be-inclusivenames-roles-labels | issues | high | Lighthouse and direct probes found unnamed commands, links, frames and images. FG-14 high: Controls, links, frames and images lack accessible names |
be-inclusivesufficient-contrast | issues | high | Lighthouse failed color contrast on homepage and article. FG-15 medium: Text color contrast fails WCAG checks |
be-inclusivestructure-and-focus | issues | high | Heading order/accessibility tree failed and direct focus had outline:none. FG-16 high: Heading structure and focus treatment are broken |
be-inclusivelegible-text | issues | high | Visual review shows cramped desktop columns and fragmented long mobile reading flow. FG-17 medium: Dense narrow columns and long empty runs impair reading |
be-inclusivezoom-reflow-targets-and-media | issues | high | maximum-scale=1 disables zoom and target probe found 151 undersized controls. FG-18 high: The viewport disables effective user zoom |
follow-best-practicesno-console-errors | pass | high | Neither Lighthouse run reported errors-in-console or an uncaught-exception audit failure. |
follow-best-practicessound-document-and-assets | issues | high | Image audit and Lighthouse show missing dimensions, incorrect aspect ratios and low-resolution assets. FG-19 medium: Asset markup has widespread sizing and aspect-ratio problems |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found deprecated APIs, inspector issues and BFCache blockers. FG-20 high: Deprecated APIs and browser lifecycle blockers remain |
be-discoverabletitle-and-description | pass | high | Home, section and article probes expose descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse failed crawlable anchors and the direct probe found href=#/empty links. FG-21 medium: Some navigation links are unnamed or non-crawlable |
be-discoverablecanonical-and-indexing-signals | issues | high | Homepage canonical was absent and the empty error route incorrectly returned 200. FG-22 medium: Indexing signals are inconsistent on public routes |
be-discoverablestructured-and-shareable-metadata | pass | high | Home/article expose Open Graph/Twitter metadata and JSON-LD; article title/h1/description survive without JS. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS page still has mixed content, missing CSP/HSTS/nosniff and insecure SameSite=None cookies. FG-23 critical: Transport defenses and cookie attributes are unsafe |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Trackers/HAR show 51 third-party origins, seven trackers and 4.18MB third-party transfer. FG-24 high: The default third-party tracking footprint is excessive |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Notification solicitation appears immediately before user intent; public content has no auth requirement. FG-25 high: Notification solicitation appears before user intent |
be-private-and-securedefensive-browser-policies | issues | high | Header probe found no clickjacking, referrer or permissions policy defenses. FG-26 high: Browser-enforced defensive policies are absent |
be-resilientprogressive-enhancement | pass | high | Article raw HTML returned 200 with title, h1 and description; it is not a JS shell and remains content-bearing without JS. |
be-resilientresilient-runtime-behaviour | issues | high | Stacked overlay state competes for focus and viewport space at 360px. FG-27 high: Stacked third-party overlays create a fragile initial state |
be-resilientoffline-and-installable | issues | high | Service worker controller exists but no web app manifest is linked on this app-like mobile news experience. FG-28 medium: The app-like site is not installable |
be-resilientnetwork-and-http-failure-states | issues | high | Unknown route returns empty HTTP 200 with no state or recovery. FG-29 high: Failure routes degrade to a blank screen |
be-internationalisedlang-dir-and-logical-properties | issues | high | Arabic lang is present but dir is omitted, leaving direction implicit. FG-30 medium: Arabic pages omit explicit directionality |
be-internationalisedlocale-aware-data | pass | high | Representative home/match views render Arabic labels, Arabic-localized competition content and a consistent 24-hour time format. |
be-internationalisedtime-zone-correctness | issues | high | Upcoming 22:00 kickoff lacks visible time-zone context. FG-31 low: Match times do not state their time-zone context |
be-trustworthyno-dark-patterns | issues | high | Consent UI privileges acceptance and requires Manage options to avoid processing by 215 partners. FG-32 high: Consent choice architecture favors acceptance |
be-trustworthyhumane-error-handling | not-applicable | high | No user-authored form is part of the representative public news, article or match journey. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in or sign-up input appears in the audited public-content scope. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Checkout, subscription, authentication and account management are outside the sampled public editorial journey. |
be-sustainableoptimised-assets | issues | high | Image audit directly found legacy formats, absent srcset/lazy-loading and oversized files. FG-33 high: Images are not delivered efficiently |
be-sustainableno-wasteful-work | issues | high | Idle load performs 60 script, 36 fetch/XHR and six media requests with late long tasks. FG-34 high: Background advertising and analytics work is excessive |
be-sustainablethird-party-and-media-budget | issues | high | 4.18MB third-party transfer includes a 1.08MB video without user request. FG-35 high: Third-party media cost is disproportionate to the reading task |
be-agent-readystructured-agent-capabilities | not-applicable | high | No developer intent or agent-facing transactional capability was declared; this emerging opportunity is not required for the public editorial scope. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model feature is offered, and on-device inference is not necessary to complete the core reading task. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten representative menu/carousel activation attempts, heap self size was 65.0MB versus 64.0MB baseline (+1.5%); closures and native-node counts fell, with no unbounded-growth signal in this bounded run. |
be-memory-efficientbounded-footprint | issues | medium | Baseline heap was 64.0MB with 1,147,497 nodes before interaction. FG-36 medium: The idle homepage has a very large memory/DOM footprint |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Post-interaction summary showed closure count falling from 94,267 to 91,146 and native node count falling from 309,389 to 302,491; no Detached* constructor entered the reported top population. |
Provenance
Canonical report: results/atomic/reports/0238-www_filgoal_com.json
Report SHA-256: 0195c44e31715c8075d28a0d8be95834f3a69a647495fa3e739dfa37039b24f5
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_filgoal_com/2026-07-19T08-56-41-859Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_filgoal_com/2026-07-19T08-56-41-859Z
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.