Manifest position 236 · CrUX rank bucket 1000
https://www.tjk.org
Coverage complete
Atomic coverage complete: 58/58 checks judged across seven representative paths. Not covered: external betting/account origins, authenticated journeys, and destructive/real submissions because they are separate systems or could create real data.
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 | Dark media screenshot and computed style probe. F02 medium: The site does not adapt to the user’s dark color preference |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion emulation matched and no active CSS/Web Animations were present, so there is no non-essential animation to suppress. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors capture retained readable text, controls and consent actions. |
implement-natural-interactionsview-transitions | issues | high | Long tab/route changes are immediate and DOM/CSS inspection found no View Transition usage. F04 medium: Long pages provide no state-aware navigation or attention cue |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked decorative motion or script scroll handlers were found; the site does not implement the anti-pattern. |
implement-natural-interactionsphysical-gestures | pass | high | No custom pointer gesture surface was found in the representative templates; native scrolling and controls remain available. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Long homepage and race-program templates have static chrome with no scroll-state cue. F04 medium: Long pages provide no state-aware navigation or attention cue |
provide-guided-navigationanchored-positioning | issues | high | The footer contact menu uses absolute left/bottom positioning and hover-only display rather than anchored/popover positioning. F03 medium: Transient consent and menu UI is implemented without semantic overlay primitives |
provide-guided-navigationdirects-attention | issues | high | Hash-tab navigation changes content without transition, focus movement or location/progress cue. F04 medium: Long pages provide no state-aware navigation or attention cue |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Fresh-load screenshots show the consent panel obscuring core content. F01 high: Consent overlay obscures the primary content on every fresh load |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Custom consent/dropdown UI is present while semantic overlay primitive counts are zero. F03 medium: Transient consent and menu UI is implemented without semantic overlay primitives |
maximize-content-reduce-noisereduced-chrome | issues | high | At mobile size, dense site chrome and scaled desktop controls compete with content. F15 high: Text and controls become illegibly small on phones |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Four mobile layouts use a 980px layout viewport with no viewport meta. F05 high: Mobile pages render a scaled 980px desktop canvas instead of reflowing |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | No container-query behavior was found and reused shell/components stay fixed-width. F06 medium: Reusable components do not adapt to their containers |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focus probe shows outline-style none and Lighthouse fails target size. F07 high: Keyboard focus is not visibly indicated and targets are too small |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, race program, horse query and contact pages have recognizable titles/navigation and expose their main action or information directly. |
support-core-task-successprimary-flow-completion | pass | high | Representative race lookup, horse query and contact form surfaces loaded without an auth wall or dead-end detour; CAPTCHA is proportionate for submission. |
support-core-task-successclear-system-state-and-recovery | issues | high | Blank contact submission exposes no native invalid state or actionable error message. F08 high: The contact form does not expose humane validation or required-field recovery |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.7s and CLS 0.750. F09 high: Core Web Vitals are poor under Lighthouse mobile conditions |
be-fast-and-stablevisual-stability | issues | high | Lighthouse’s CLS 0.750 is far outside the good range; 38 images also lack dimensions. F09 high: Core Web Vitals are poor under Lighthouse mobile conditions |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded zero long tasks and 0ms TBT; Lighthouse TBT was about 20ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR shows 105 requests, 3.24MB and parser-inserted high-priority head dependencies. F10 high: The critical path is large and parser-blocked |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse identified 161KiB unused JS and 17KiB unused CSS. F11 medium: The page ships substantial unused JavaScript and CSS |
be-inclusivenames-roles-labels | issues | high | Lighthouse and probes show unnamed links, missing image alt and table-header failures. F12 high: Links, images and table data lack accessible names and relationships |
be-inclusivesufficient-contrast | issues | high | Lighthouse found 3.69:1 navigation contrast where 4.5:1 is required. F13 high: Text and navigation colors fail minimum contrast |
be-inclusivestructure-and-focus | issues | high | Homepage has no h1/landmarks and focus sampling found no visible outlines. F14 high: Pages lack landmarks, coherent headings and visible focus |
be-inclusivelegible-text | issues | high | Mobile captures scale dense 980px content to 36.7%. F15 high: Text and controls become illegibly small on phones |
be-inclusivezoom-reflow-targets-and-media | issues | high | Missing viewport metadata prevents proper mobile reflow and Lighthouse fails target-size. F05 high: Mobile pages render a scaled 980px desktop canvas instead of reflowing |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with no collected errors. |
follow-best-practicessound-document-and-assets | issues | high | Lighthouse flags quirks mode, image aspect/size problems; image audit found 38 missing dimensions. F16 high: Document and image asset hygiene is unsound |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse emitted a deprecated-API warning and the page loads a large legacy script stack. F16 high: Document and image asset hygiene is unsound |
be-discoverabletitle-and-description | pass | high | All representative pages have specific titles and the shared descriptive meta description is present in raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Viewport meta is absent and Lighthouse found javascript: anchors that are not crawlable. F05 high: Mobile pages render a scaled 980px desktop canvas instead of reflowing |
be-discoverablecanonical-and-indexing-signals | issues | high | Canonical/hreflang are absent, robots.txt returns an error page and sitemap URLs use HTTP. F17 medium: Indexing signals are inconsistent and stale |
be-discoverablestructured-and-shareable-metadata | issues | high | Organization/news page has no JSON-LD or Open Graph metadata. F18 medium: Entity and social-share metadata is absent |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS/nosniff pass, but CSP/HSTS and Secure/SameSite cookie posture fail. F19 high: Security headers and cookie attributes are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Known analytics trackers and large third-party request footprint occur on initial load. F20 high: Tracking code loads before the user has made a consent choice |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No authentication or browser-permission journey exists on the audited tjk.org surfaces; betting/auth is hosted on a separate external origin. |
be-private-and-securedefensive-browser-policies | issues | high | Clickjacking, referrer and permissions policies are absent. F19 high: Security headers and cookie attributes are incomplete |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 83% raw/rendered content coverage, no empty app shell, and core page content remains visible without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | Representative static, query and form templates loaded to stable usable states; forced-colors retained overlay actions and no cut-off critical menu was observed. |
be-resilientoffline-and-installable | not-applicable | high | This is a multi-page public information site rather than an installable app; no offline product intent is apparent. |
be-resilientnetwork-and-http-failure-states | pass | high | An unknown route renders a clear Turkish error, error code, support address and prominent homepage recovery action. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Turkish templates declare lang=en and use physical directional CSS. F21 high: Turkish pages declare English and use physical-direction CSS |
be-internationalisedlocale-aware-data | issues | high | Locale-specific race dates are rendered without correct document locale or machine-readable event metadata. F22 medium: Race date/time information is not explicitly locale or time-zone aware |
be-internationalisedtime-zone-correctness | issues | high | International race venue times have no explicit IANA timezone or unambiguous machine-readable timestamp in inspected markup. F22 medium: Race date/time information is not explicitly locale or time-zone aware |
be-trustworthyno-dark-patterns | pass | high | Consent presents equally prominent Accept and Reject actions with category controls; no confirmshaming, disguised ads or forced continuity was observed. |
be-trustworthyhumane-error-handling | issues | high | Blank form submission yields no constraints, invalid controls or announced recovery message. F08 high: The contact form does not expose humane validation or required-field recovery |
be-trustworthytrustworthy-input-assistance | issues | high | Contact identity fields omit autocomplete and multiple controls lack associated labels. F23 medium: Form inputs omit autocomplete and several programmatic labels |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription or account-management flow exists on the audited origin; betting is explicitly linked to another service and was not included. |
be-sustainableoptimised-assets | issues | high | Image audit found all 42 in legacy formats, 21 oversized and 30 below-fold images eager-loaded. F24 high: Images and third-party media consume a disproportionate resource budget |
be-sustainableno-wasteful-work | issues | high | Initial load ships unused code and duplicate analytics bundles without user interaction. F11 medium: The page ships substantial unused JavaScript and CSS |
be-sustainablethird-party-and-media-budget | issues | high | Initial transfer is 3.24MB with 3.14MB outside www origin and 2.62MB images. F24 high: Images and third-party media consume a disproportionate resource budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | No agent-facing intent is declared for this traditional public information site; emerging WebMCP capability is treated as an opportunity, not a defect. |
be-agent-readyon-device-inference | not-applicable | high | No on-device inference use case is necessary for the site’s current race information and institutional content. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 repeated homepage tab switches, retained heap rose only 82,782 bytes (0.76%) and closure count rose by 3, consistent with bounded warm-up rather than unbounded growth. |
be-memory-efficientbounded-footprint | pass | medium | Heap self-size was about 10.9MB for a dense 105-request information page, proportionate to its rendered content. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Before/after heap summaries show stable Object/Array/closure populations and no Detached* constructor among retained-size leaders. |
Provenance
Canonical report: results/atomic/reports/0236-www_tjk_org.json
Report SHA-256: e386ac6cd498376478931f46fdccd655e7308a58b92610c5f3b8a317b6a27e9b
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_tjk_org/2026-07-19T08-38-48-379Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_tjk_org/2026-07-19T08-38-48-379Z
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.