Manifest position 302 · CrUX rank bucket 1000
https://www.tradingview.com
Coverage complete
Coverage-complete audit of seven representative public paths. Authenticated account, broker order execution, payment completion and every localized/template variant were outside scope.
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 CSS capability probe found 0 prefers-color-scheme rules, and the DOM reported color-scheme: light. The dark-emulated capture was pixel-identical to the default capture rather than being selected from the operating-system preference. F01 medium: System dark preference does not select a dark theme |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, getAnimations() reported a running 3.5 s hero animation and twenty 1 s skeleton animations; the CSS probe found 0 prefers-reduced-motion rules. F02 high: Reduced-motion users still receive continuous animation |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot preserves high-contrast text, buttons and consent controls. |
implement-natural-interactionsview-transitions | pass | high | CSS inspection found 12 view-transition references and the app uses stateful route/application changes. |
implement-natural-interactionsscroll-driven-animations | pass | high | CSS inspection found animation-timeline rules; no scroll-handler jank was observed in layout evidence. |
implement-natural-interactionsphysical-gestures | pass | high | CSS inspection found scroll-snap and overscroll-behavior rules, and the mobile layouts remained native-scrollable without overflow. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Screenshots show stable sticky application chrome and CSS includes scroll timelines/state-oriented rules without obstructing content. |
provide-guided-navigationanchored-positioning | pass | high | Rendered CSS contains anchor-name, position-anchor and position-try declarations (3 each), supporting attached fallback positioning. |
provide-guided-navigationdirects-attention | pass | high | The landing CTA hierarchy, market breadcrumbs/tabs and chart selection states clearly indicate location and next action. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The 360x800 screenshot shows the cookie banner occupying roughly the bottom 84 px and overlaying the hero on every fresh visit. It is dismissible and offers balanced choices, but still interrupts the first view. F03 medium: Consent banner consumes a large part of the mobile first viewport |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | high | The observed consent control uses native buttons and no modal flow was falsely represented; chart controls expose toolbar/role semantics. |
maximize-content-reduce-noisereduced-chrome | pass | high | Marketing pages prioritize the hero/content; dense chart chrome directly serves the primary analytical task rather than decoration. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800 both homepage and chart reported scrollWidth 360, clientWidth 360 and 0 horizontal overflow; both adapt visually. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Rendered CSS contains 108 @container rules and 637 logical/intrinsic-style declarations; mobile captures show distinct adapted layouts. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Lighthouse found multiple 16–20 px-high broker and footer targets below the 24 px minimum and reported the target-size audit as failing. F04 medium: Some touch targets are too small or tightly spaced |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport states the research-to-trade proposition and presents a single prominent “Get started for free” action; market, symbol and pricing pages have descriptive H1s. |
support-core-task-successprimary-flow-completion | pass | high | An unauthenticated user can move from market listing to symbol detail and use the full AAPL chart; pricing clearly exposes sign-up and plan choices without a credit card claim. |
support-core-task-successclear-system-state-and-recovery | pass | high | Chart state states market closed and last-update time; the deliberate unknown route gives clear back/home recovery actions instead of a broken shell. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 8.9 s, FCP 7.4 s, TBT 530 ms and time-to-interactive 20.7 s (performance 0.45). The raw-CDP trace was faster locally but still found long tasks; the chart trace had LCP 3.76 s and 232 ms TBT. F06 high: Cold mobile load is slow and main-thread heavy |
be-fast-and-stablevisual-stability | pass | high | Homepage and chart mobile layout observers measured CLS 0.0061 and 0.0084 respectively, both well inside the good range. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured LCP 8.9 s, FCP 7.4 s, TBT 530 ms and time-to-interactive 20.7 s (performance 0.45). The raw-CDP trace was faster locally but still found long tasks; the chart trace had LCP 3.76 s and 232 ms TBT. F06 high: Cold mobile load is slow and main-thread heavy |
be-fast-and-stableefficient-resource-delivery | issues | high | The homepage HAR recorded 464 requests including 194 stylesheets and 131 scripts; the chart recorded 977 requests, 458 stylesheets and 465 scripts, with 6.29 MB transferred. Parser-inserted VeryHigh-priority stylesheets form a long blocking candidate list. F07 high: Critical delivery fans out into hundreds of CSS and JavaScript requests |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 524 KiB of unused JavaScript, including 153 KiB from the ad script, 87 KiB from toast-layer, 73 KiB from Google identity and 136 KiB across two tag-manager bundles. F08 high: Large unused and third-party JavaScript ships on initial load |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed image-alt; the images probe found 91/100 sampled homepage images and 87/100 symbol-page images without alt. The chart has 20 canvases with no fallback text and 35 of 193 buttons without text, aria-label or title. F09 high: Images, canvas content and controls are not consistently exposed to assistive technology |
be-inclusivesufficient-contrast | pass | high | Lighthouse did not report a color-contrast failure, and forced-colors capture preserved readable high-contrast content/control boundaries. |
be-inclusivestructure-and-focus | issues | high | The rendered chart contained no h1–h6 elements. A focus probe across the landing page found most sampled controls with outline-style none, while only one sampled control displayed a 2 px focus outline. F10 high: The chart application has no heading structure and focus indication is inconsistent |
be-inclusivelegible-text | pass | high | Representative pages use clear hierarchy and readable line lengths; mobile hero copy wraps cleanly without clipping. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The live meta viewport is width=device-width, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, user-scalable=no; Lighthouse failed the meta-viewport accessibility audit. F05 high: The viewport explicitly prevents user zoom |
follow-best-practicesno-console-errors | issues | high | Lighthouse logged a Google Identity FedCM NetworkError and a not-signed-in error. It also found an unload event listener, which is deprecated and contributes to two BFCache failure reasons. F11 medium: Initial load logs errors and uses a deprecated unload listener |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found width and height attributes absent on all 100 sampled images on both the homepage and symbol page. Observed CLS was low in this run, but the markup does not reserve intrinsic image space. F12 medium: Rendered images omit intrinsic dimensions |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse logged a Google Identity FedCM NetworkError and a not-signed-in error. It also found an unload event listener, which is deprecated and contributes to two BFCache failure reasons. F11 medium: Initial load logs errors and uses a deprecated unload listener |
be-discoverabletitle-and-description | issues | high | Discoverability measured 1% raw-to-rendered content coverage for /chart/, classified it as a JS shell, and found that the rendered dynamic title was absent from raw HTML. Homepage, ideas and symbol pages were substantially server-rendered. F13 high: The public chart route is nearly empty to non-JavaScript crawlers |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse SEO was 0.85 and flagged the link text “More”; its mobile accessibility audit also failed because viewport zoom is disabled. Robots and sitemap otherwise expose public routes. F14 low: A generic link label and zoom restriction weaken mobile/crawlable navigation |
be-discoverablecanonical-and-indexing-signals | pass | high | Public pages returned content, expose canonical links, homepage has 20 hreflang links, robots permits normal public routes and sitemap.xml indexes template-specific sitemaps. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage, markets and symbol pages expose Open Graph metadata and JSON-LD; the AAPL detail has five JSON-LD blocks aligned with visible entity data. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS and frame-ancestors none are present, but CSP includes unsafe-inline in default-src; Permissions-Policy is absent; two non-auth cookies lacked Secure and all four observed cookies used SameSite=None. F15 medium: Browser security policy and cookie flags can be tightened |
be-private-and-securedata-minimisation-and-third-parties | issues | high | On a fresh profile while the consent banner was visible, trackers identified Tag Manager, DoubleClick and Google Ads. The HAR attributed 3.11 MB of 3.34 MB to non-main origins, including about 564 KB for tag-manager/ad scripts, before the user accepted. F16 high: Tracking and advertising code loads before a consent choice |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No notification or geolocation prompt appeared on load; the observed signed-out experience uses Google FedCM/identity integration and exposes auth only after user action. |
be-private-and-securedefensive-browser-policies | issues | high | HTTPS, HSTS and frame-ancestors none are present, but CSP includes unsafe-inline in default-src; Permissions-Policy is absent; two non-auth cookies lacked Secure and all four observed cookies used SameSite=None. F15 medium: Browser security policy and cookie flags can be tightened |
be-resilientprogressive-enhancement | issues | high | The rendered chart exposes thousands of characters of symbol and market data, but raw HTML contains only 67 text characters and 1% of rendered content words. The crawler screenshot is effectively an empty shell. F17 high: The core chart route has no useful no-JavaScript baseline |
be-resilientresilient-runtime-behaviour | pass | high | Menus/toolbars rendered without clipping on desktop and mobile, repeated Indicators open/close returned to zero dialogs, and the chart remained usable. |
be-resilientoffline-and-installable | not-applicable | high | TradingView’s live market chart is intrinsically online; an app manifest icon resource exists but offline trading/data is not a credible core promise, so this specific PWA/offline check is contextual and not applicable. |
be-resilientnetwork-and-http-failure-states | pass | high | The deliberate unknown route presents a clear “page not found” explanation with Head back and Head to homepage recovery actions. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Pages declare lang=en and dir=ltr; homepage offers a language selector, 20 hreflang variants and CSS has far more logical than physical declarations. |
be-internationalisedlocale-aware-data | pass | high | Pricing rendered GBP for the observed UK locale; values use localized separators and narrow no-break spaces, while machine-readable time elements carry ISO values. |
be-internationalisedtime-zone-correctness | pass | high | Chart state explicitly labels UTC/GMT+1 update times and machine-readable time elements use unambiguous Z timestamps. |
be-trustworthyno-dark-patterns | pass | high | Pricing discloses monthly equivalent, annual billing, annual savings, trial lengths and a pay-now alternative; consent presents equally direct accept and decline controls. |
be-trustworthyhumane-error-handling | pass | high | The exercised public paths contained no mandatory form before the task; the invalid-route state uses neutral language and actionable recovery rather than blame. |
be-trustworthytrustworthy-input-assistance | pass | high | No data-entry form was required in the representative public research flow; the pricing billing-cycle radios have explicit labels and predictable controls. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Pricing clearly shows £0 forever, billing cadence, trial duration, savings and annual commitment before sign-up; no forced continuity was observed in the accessible entry flow. |
be-sustainableoptimised-assets | issues | high | The homepage image probe found two hero assets over 2x display width, 55 below-fold images without lazy loading, 22 without responsive sources and 20 legacy-format assets. The symbol page found 11 oversized images. F18 medium: Some imagery is oversized and below-fold assets load eagerly |
be-sustainableno-wasteful-work | issues | high | The chart HAR made 977 requests and transferred 6.29 MB, overwhelmingly application scripts; the homepage fetched a 192 KB month-long economic calendar payload and multiple analytics endpoints during initial rendering. F19 medium: Initial routes perform disproportionate background and conditional work |
be-sustainablethird-party-and-media-budget | issues | high | Lighthouse reported a 6,859 KiB page payload led by a 3.65 MB WebM video, while advertising, analytics and identity scripts added hundreds of KiB before interaction. Lighthouse reported a 6,859 KiB page payload led by a 3.65 MB WebM video, while advertising, analytics and identity scripts added hundreds of KiB before interaction. F20 medium: Heavy media and third parties dominate the landing-page budget F20 medium: Heavy media and third parties dominate the landing-page budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | No developer intent or public agent-execution surface is declared. This emerging capability is optional; server-rendered public content was assessed separately under discoverability. |
be-agent-readyon-device-inference | not-applicable | high | No summarization or language-model task is presented as a core page capability, so absence of on-device inference is not a quality failure. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten Indicators open/close cycles in one chart session, used JS heap decreased from 113.4 MB to 103.9 MB and DOM nodes changed only 3485 to 3494. Separate heap captures varied, so the same-session metric was used for the verdict. |
be-memory-efficientbounded-footprint | pass | high | The chart baseline heap summary was about 99.0 MB self size with 1.72 M heap nodes, substantial but proportionate to a multi-canvas real-time chart; same-session used heap settled near 104 MB. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The repeated modal-like interaction left only 9 additional live DOM elements and no open dialogs; used heap fell after settling, providing no evidence of accumulating listeners/timers in this window. |
Provenance
Canonical report: results/atomic/reports/0302-www_tradingview_com.json
Report SHA-256: d68a4cd52c0e85b886c4aa4b1a021dc8920696eda673555253d782b780e87202
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_tradingview_com/2026-07-19T19-52-11-479Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_tradingview_com/2026-07-19T19-52-11-479Z
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.