Website review, no card needed
fortrade.com website review
Visit site (opens in a new tab)Reviewed 30 October 202636 issues · 85 checks
This review found 36 issues worth fixing on fortrade.com, 15 of them high impact, across 85 checks. The most urgent: google Tag Manager adds 5.9 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.5 s |
| May 16, 2026 | 4.6 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.5 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.4 s |
| Jun 27, 2026 | 4.5 s |
| Jul 4, 2026 | 4.6 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.7 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.5 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.7 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 5.0 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 5.0 s |
| Sep 26, 2026 | 4.9 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.8 s |
| Oct 24, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 427 ms |
| May 16, 2026 | 493 ms |
| May 23, 2026 | 501 ms |
| May 30, 2026 | 501 ms |
| Jun 6, 2026 | 498 ms |
| Jun 13, 2026 | 471 ms |
| Jun 20, 2026 | 449 ms |
| Jun 27, 2026 | 399 ms |
| Jul 4, 2026 | 358 ms |
| Jul 11, 2026 | 341 ms |
| Jul 18, 2026 | 332 ms |
| Jul 25, 2026 | 334 ms |
| Aug 1, 2026 | 329 ms |
| Aug 8, 2026 | 323 ms |
| Aug 15, 2026 | 318 ms |
| Aug 22, 2026 | 329 ms |
| Aug 29, 2026 | 332 ms |
| Sep 5, 2026 | 336 ms |
| Sep 12, 2026 | 328 ms |
| Sep 19, 2026 | 318 ms |
| Sep 26, 2026 | 329 ms |
| Oct 3, 2026 | 338 ms |
| Oct 10, 2026 | 345 ms |
| Oct 17, 2026 | 350 ms |
| Oct 24, 2026 | 351 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.9 s
4.5 s
5.2 s
Speed
Google Tag Manager adds 5.9 s
5.9 sGoogle Tag Manager costs a phone 5.9 s of main-thread work and 4.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 15.6 s
A phone's processor spends 15.6 s on main-thread work while loading, 9.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.1 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cookiebot and TikTok and others), adding 4.7 MB and 7.5 s of main-thread time.
Reduce unused JavaScript
600 ms · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Cookiebot adds 873 ms
873 msCookiebot costs a phone 873 ms of main-thread work and 40 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 796 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
343 KiB29 files are served with short cache lifetimes, so returning visitors download them again (343 KiB).
Legacy JavaScript
150 ms · 83 KiBPolyfills for old browsers add 83 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
14 KiB14 KiB could be saved by minifying JavaScript.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 92 ms
92 msYour server sent the HTML in 92 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user LCP: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.8 s
3.8 sReal visitors see the first content after 3.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.5 s
2.5 sReal visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 6.5 s
6.5 sScripts block taps and scrolling for 6.5 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 41.6 s
41.6 sThe page becomes fully interactive after 41.6 s. Good is under 3.8 s.
Largest Contentful Paint: 6.0 s
6.0 sYour largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
Real-user INP: 443 ms
443 msReal visitors wait 443 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.5 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Tap response (INP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 427 ms to 351 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 8.9 MB in 310 requests
8.9 MBYour homepage downloads 8.9 MB in 310 requests on a phone: scripts 5.5 MB (112), images 1.8 MB (80) and media 1.3 MB (1). Under 2 MB keeps phones on slow connections fast.
4 images below the first screen load straight away
4 images further down the page (296 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.51 g of CO₂e: 301.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 92 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Online CFD Trading Platform | Trade Forex Pairs, Stocks & Indices | Fortrade”.
2 H1 headlines
There are 2 <h1> headlines (“Elevate Your Trading Experience” and “Start Trading in 3 Easy Steps”). One clear main headline is easier for people and search engines.
Meta description is long (191 characters)
Your meta description is 191 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.fortrade.com/sitemap.xml, so Google discovers your pages only by following links.
33 internal links, 39 external
The homepage links to 33 pages on fortrade.com and 39 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.fortrade.com/.
Structured data in place
Structured data found: Organization.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.fortrade.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (853 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share a meta description
https://www.fortrade.com/product-cat/currencies, https://www.fortrade.com/product-cat/stocks, https://www.fortrade.com/product-cat/commodities, https://www.fortrade.com/product-cat/digitalcurrencies, https://www.fortrade.com/product-cat/indices and https://www.fortrade.com/product-cat/us-treasuries use the same meta description. A description written for each page earns more clicks.
4 pages without an H1
https://www.fortrade.com/product-cat/currencies, https://www.fortrade.com/product-cat/stocks, https://www.fortrade.com/product-cat/commodities and https://www.fortrade.com/product-cat/indices have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.fortrade.com/trading-conditions took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5549254&tm=gtm002&Ver=2&mid=e3b00170-7a98-4db0-9ea0-fea6fe1eb2e1&bo=1&sid=cd7b86c0d45c11f1a4398130863710c3&vid=cd7bc4b0d45c11f1a409230bad204b5b&vids=1&msclkid=N>m_ta.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
30 of 31 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 859 words of copy
The homepage carries about 859 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start Trading” and “Download the App”.
14 calls to action
The homepage has 14 calls to action, for example “Start Trading”, “Get Free Demo” and “Contact us”.
Social proof on the page
Social proof on the homepage: 120 testimonial or review blocks and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
24 cookies set on arrival
24Opening the homepage sets 24 cookies (measured from a US location before any click).
32 other companies contacted
Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at fortrade.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Founded
- 2013
- Headquarters
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on fortrade.com, including 18 speed issues, 5 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.