Manifest position 631 · CrUX rank bucket 1000
https://goal7.co
Coverage complete
58/58 atomic checks recorded with no blocked, not-run, missing, unknown or duplicate rows.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Dark-emulated and normal screenshots are pixel-identical; computed colorScheme is "normal". F01 medium: Dark preference leaves the page unchanged |
respect-user-preferencesrespects-reduced-motion | issues | high | The homepage chat transitions are disabled, but standings CSS contains an infinite blinkText animation with no reduced-motion override. F02 medium: Reduced motion is only partially honoured |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse fails color-contrast; authored CSS has no forced-colors or prefers-contrast adaptation. F03 high: Contrast preferences and minimum contrast are not robust |
implement-natural-interactionsview-transitions | issues | high | The DOM/CSS probe found no authored view-transition rules across the sampled templates. F04 low: Route and state changes are abrupt |
implement-natural-interactionsscroll-driven-animations | pass | high | DOM/CSS inspection across four templates found no scroll-linked animation or custom scroll-handler effect to implement inefficiently. |
implement-natural-interactionsphysical-gestures | pass | high | Representative pages use native scrolling and ordinary links; no custom swipe/pull/pointer gesture fights the platform. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Screenshots and CSS show a fixed-size 1000px header/menu and no scroll-state query or progress cue. F05 low: Navigation chrome does not respond to scroll state |
provide-guided-navigationanchored-positioning | issues | high | CSS positions submenu at fixed top/left values and sends .htmltooltip to -1000px; no anchor positioning or fallback positions are authored. F06 medium: Dropdowns and tooltips use brittle absolute coordinates |
provide-guided-navigationdirects-attention | pass | high | Navigation exposes current/active green states and destination pages retain consistent headers and explicit section headings. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Initial-load screenshots on home, live, analysis and standings show content directly with no blocking interstitial. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The probe finds zero dialog/popover elements while #chatOverlay/#chatPanel implement modal-like behavior with divs. F07 medium: The chat overlay is an ad-hoc modal |
maximize-content-reduce-noisereduced-chrome | issues | high | The first viewport devotes substantial space to a branded stadium header, two navigation rows and promotional/social controls before the results. F08 medium: Dense chrome competes with the core scores |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At viewport 360x800 the layout reports no viewport meta, a 1021px layout viewport and body min-width:1000px; text and controls are miniaturized. F09 critical: Mobile receives a scaled-down 1000px desktop layout |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The probe found no @container rules; tables and wrappers use fixed widths from 880px to 1000px across templates. F10 high: Components do not adapt to their containers |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse fails target-size; sampled navigation links are about 16px high and several hidden/custom links report no visible outline. F11 high: Touch targets and some focus states are inadequate |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage and live page immediately label schedules/results in Thai and expose direct navigation to today, tomorrow and live scores. |
support-core-task-successprimary-flow-completion | pass | high | The representative flow from homepage navigation to live scores and match analysis completed without an account wall or dead end. |
support-core-task-successclear-system-state-and-recovery | issues | high | The exercised unknown route returned a generic page/state without a clearly documented retry or return path in the captured DOM. F12 medium: The error route gives no useful recovery state |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse reports LCP 10.1s and CLS 0.211; performance score is 0.60. F13 high: Lab Core Web Vitals are poor |
be-fast-and-stablevisual-stability | issues | high | Lighthouse reports CLS 0.211 and the image audit finds 30 images without dimensions. F14 high: The page shifts during load |
be-fast-and-stableefficient-main-thread | pass | high | Trace records only two long tasks, 72.68ms longest and 36.6ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR records 115 requests, 3.39MB transferred and ten parser-blocking CSS/JS candidates; Lighthouse LCP is 10.1s. F15 high: Critical delivery is delayed by a wide dependency surface |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The DOM ships jQuery 1.8-era assets and repeated CSS rules; HAR includes 64 third-party requests and 1.41MB third-party bytes. F16 medium: Legacy and third-party code dominates avoidable work |
be-inclusivenames-roles-labels | issues | high | Lighthouse fails image-alt, link-name, select-name, table header and main-landmark audits; image probe finds 90 images without alt. F17 critical: Many controls and images lack accessible names |
be-inclusivesufficient-contrast | issues | high | Lighthouse color-contrast audit fails on the homepage. F18 high: Text does not consistently meet contrast minimums |
be-inclusivestructure-and-focus | issues | high | Lighthouse fails heading order and main landmark; focus probe finds custom/hidden links without visible outlines. F19 high: Document structure and focus semantics are incomplete |
be-inclusivelegible-text | issues | high | The 360px screenshots show the entire 1000px table scaled to the phone, making labels and scores extremely small. F20 critical: Mobile text is rendered at an unreadably small scale |
be-inclusivezoom-reflow-targets-and-media | issues | high | No viewport meta is present; fixed minimum widths force scale-to-fit and Lighthouse fails target-size. F21 critical: The page does not reflow at mobile width |
follow-best-practicesno-console-errors | pass | high | Lighthouse did not report the errors-in-console audit as a failure during the captured load. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse reports no HTML doctype, incorrect image aspect ratios and low-resolution images; image probe finds 30 missing dimensions. F22 high: Document and image fundamentals are invalid |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports inspector issues, three BFCache failure reasons, and the page depends on very old jQuery/UI assets. F23 medium: Browser platform hygiene has known failures |
be-discoverabletitle-and-description | pass | high | Discoverability probe confirms title, h1 and meta description are present in raw HTML and rendered output. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse fails crawlable anchors and the viewport meta is absent; many image-only anchors have no descriptive text. F24 high: Some links are not crawlable and the page is not mobile friendly |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt allows crawling but declares four sitemap URLs on goal5.co rather than goal7.co. F25 high: Robots points to the wrong domain sitemap |
be-discoverablestructured-and-shareable-metadata | issues | high | The homepage represents an organization and live sports data, but the probe found no JSON-LD and no Open Graph metadata. F26 medium: Rich entity/share metadata is absent |
be-private-and-securesecure-transport-and-headers | issues | high | Headers probe finds no CSP/HSTS/nosniff; PHPSESSID lacks Secure, HttpOnly and SameSite protection. F27 critical: Session cookies and response defenses are insecure |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Trackers probe finds Google Tag Manager/Analytics plus eight third-party origins; HAR records 64 third-party requests and 1.41MB. F28 high: Tracking and advertising footprint is excessive by default |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No authentication or permission-request surface appeared in the representative public content paths. |
be-private-and-securedefensive-browser-policies | issues | high | Headers probe reports missing clickjacking protection, Referrer-Policy and Permissions-Policy in addition to CSP/HSTS gaps. F29 high: Browser-enforced defenses are not configured |
be-resilientprogressive-enhancement | pass | high | Discoverability probe reports 100% raw-HTML content coverage, isJsShell=false and visible title/h1/description without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Four representative templates loaded and remained usable; no cut-off open overlay or fragile loading crash was observed. |
be-resilientoffline-and-installable | not-applicable | high | This public scores/content site is not presented as an installable application; offline installation is contextual. |
be-resilientnetwork-and-http-failure-states | issues | high | The unknown-route exercise did not expose an actionable recovery state; live data surfaces provide no captured retry/offline affordance. F30 medium: Failure recovery is not intentionally presented |
be-internationalisedlang-dir-and-logical-properties | issues | high | The recon probe reports htmlLang as empty and Lighthouse fails html-has-lang; CSS relies heavily on left/right physical properties. F31 high: The Thai document does not declare its language |
be-internationalisedlocale-aware-data | issues | high | Rendered dates/times are plain text with no <time> semantics or documented locale formatting in the inspected DOM. F32 medium: Locale-sensitive schedule data lacks explicit semantics |
be-internationalisedtime-zone-correctness | issues | high | Live and scheduled match tables show bare HH:MM values for worldwide events without a visible zone or machine-readable timestamp. F33 high: Global match times do not state a time zone |
be-trustworthyno-dark-patterns | pass | high | No consent wall, forced continuity, confirmshaming, checkout or cancellation obstruction appeared in the exercised paths. |
be-trustworthyhumane-error-handling | issues | high | The page probe finds repeated radio groups with zero associated labels and submit controls with no accessible label. F34 high: Interactive vote controls are not labelled for humane validation |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No personal, address, payment, sign-in or sign-up fields are present; only score-vote controls were observed. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, authentication or account-management flow exists in the audited site surfaces. |
be-sustainableoptimised-assets | issues | high | Image probe finds 99/100 legacy-format images, 18 oversized images, 27 below-fold images not lazy-loaded and 30 without dimensions. F35 high: Image delivery is highly wasteful |
be-sustainableno-wasteful-work | issues | high | HAR records 115 requests including analytics, advertising and large banners before interaction. F36 medium: The initial load performs excessive non-core work |
be-sustainablethird-party-and-media-budget | issues | high | Third parties transfer 1.41MB; multiple animated GIF banners are among the largest resources, including a 441KB GIF. F37 high: Third-party and animated media exceed a proportionate budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | The public sports-content site exposes no transactional agent-facing capability; this emerging opportunity is not required. |
be-agent-readyon-device-inference | not-applicable | high | No summarization/generation feature is offered, so on-device inference is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten synchronous chat open/close cycles, heap self size was 19,731,434 bytes versus 19,730,406 baseline and node count was lower, showing no retained-growth signal. |
be-memory-efficientbounded-footprint | issues | high | Heap summary reports about 294k nodes and 19.7MB self size for the initial homepage state. F38 medium: The initial page has a large DOM/heap footprint |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Heap constructor summaries did not report a growing Detached* population after repeated chat toggles; node count did not increase. |
Provenance
Canonical report: results/atomic/reports/0631-goal7_co.json
Report SHA-256: 67c51c9b763e37e3149929c55b05e9be002019e3f2900f26631a356304641c2a
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/goal7_co/2026-07-22T01-20-22-021Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/goal7_co/2026-07-22T01-20-22-021Z
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.