traders-trust.com website review

About 721 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

34 files are served with short cache lifetimes, so returning visitors download them again (888 KiB).

Your mobile performance score is 22 (desktop: 41). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 5.4 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Facebook and LiveChat and others), adding 1.3 MB and 1.3 s of main-thread time.

Google Tag Manager costs a phone 787 ms of main-thread work and 670 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

20 long tasks block the main thread while loading, the longest for 400 ms. During a long task the page ignores taps.

8 images could be 371 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Facebook costs a phone 315 ms of main-thread work and 212 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The page has 1,771 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

LiveChat costs a phone 87 ms of main-thread work and 366 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 38 KiB of CSS is downloaded but never applied on this page.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 6.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 653 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.36 (75th percentile). Good is under 0.1.

Your largest element takes 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MetaTrader 4 — Official example interface”.

Visually, the page fills in at 13.2 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 18.1 s. Good is under 3.8 s.

Scripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.

The layout shifts by 0.384 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

9 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 507 ms to 599 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.3 s to 6.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.1 MB in 154 requests on a phone: scripts 2.1 MB (73), images 797 KiB (35) and fonts 71 KiB (2). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 29 characters: “Traders Trust - Forex Trading”. Between 30 and 65 characters leaves room to say what you do and for whom.

No XML sitemap at https://traders-trust.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 8 pages on traders-trust.com and 0 external pages.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://traders-trust.com/en/open-account, whose canonical is https://traders-trust.com/open-account. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://traders-trust.com/en/open-account has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 1 page linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://www.facebook.com/tr?id=761735350200022&ev=PageView&noscript=1.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 10 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.