5.3 sec in total
1.8 sec
3 sec
578 ms
Click here to check amazing XM Trader content for Hong Kong. Otherwise, check out these important facts you probably never knew about xm-trader.com
Forex, cfd trading on stocks, stock indices, oil and gold on MT4 and MT5. Trade forex online with XM™, a licensed forex broker.
Visit xm-trader.comWe analyzed Xm-trader.com page load time and found that the first response time was 1.8 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
xm-trader.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value21.0 s
0/100
25%
Value13.4 s
2/100
10%
Value2,060 ms
7/100
30%
Value0.007
100/100
15%
Value22.5 s
1/100
10%
1803 ms
151 ms
40 ms
146 ms
341 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Xm-trader.com, 4% (3 requests) were made to Xm.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Xm.com.
Page size can be reduced by 753.0 kB (50%)
1.5 MB
739.9 kB
In fact, the total size of Xm-trader.com main page is 1.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. HTML takes 667.7 kB which makes up the majority of the site volume.
Potential reduce by 543.3 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 543.3 kB or 81% of the original size.
Potential reduce by 48.0 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. XM Trader images are well optimized though.
Potential reduce by 72.8 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 72.8 kB or 30% of the original size.
Potential reduce by 88.9 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Xm-trader.com needs all CSS files to be minified and compressed as it can save up to 88.9 kB or 78% of the original size.
Number of requests can be reduced by 19 (35%)
54
35
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of XM Trader. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.xm.com
1803 ms
gtm.js
151 ms
0677960cd8.js
40 ms
jquery.tosrus.min.css
146 ms
popper_tippy.min.js
341 ms
main_homepage.js
345 ms
jquery_cookie.js
344 ms
cookie_popup.js
345 ms
url_parameters_affid_gid.js
345 ms
qrcode-with-logos_1_0_3.min.js
731 ms
forms.js
360 ms
GVsXEo
26 ms
FX72H-U393W-CNX6U-WRWHF-88HB7
136 ms
flags-icons-sprite-alt.png
273 ms
XMLogo-2021_homepage.svg
269 ms
live-chat-icon-lite.svg
293 ms
livechat_24x24.svg
264 ms
telegram_24x24.svg
283 ms
XMCYTelegramQRcode.png
282 ms
helpcenter_24x24.svg
287 ms
homepage-2023.webp
346 ms
MT4-MT5-hp-xs.png
323 ms
MT4-MT5-hp-sm.png
325 ms
devices-icon-sm.svg
315 ms
platforms.png
344 ms
cfi-Awards-2024-broker.webp
335 ms
cfi-Awards-2024-service.webp
341 ms
colwma-2024.webp
353 ms
wf-awards-customer-service.webp
353 ms
wf-awards-eu.webp
359 ms
wf-awards-australasia.webp
361 ms
metaquotes.webp
362 ms
verisign.webp
370 ms
unicef-cfc.webp
368 ms
iip-platinum.webp
376 ms
gptw-cy-2024-lg.webp
378 ms
gptw-gr-2024.webp
377 ms
gptw_w_cy_2024_careers.webp
385 ms
facebook-f.svg
435 ms
x-twitter.svg
394 ms
youtube.svg
395 ms
instagram.svg
393 ms
config.json
196 ms
popper_tippy.min.css
190 ms
textblocks.css
290 ms
tabs.css
166 ms
video.css
213 ms
footer.css
185 ms
forms.css
277 ms
alerts.css
219 ms
modals.css
217 ms
bubble_widget.css
227 ms
Roboto-Regular-webfont.woff
474 ms
Roboto-Medium-webfont.woff
220 ms
Roboto-Light-webfont.woff
235 ms
Roboto-Thin-webfont.woff
464 ms
Roboto-Bold-webfont.woff
270 ms
Roboto-Black-webfont.woff
441 ms
bebasneue_bold-webfont.woff
311 ms
bebasneue_regular-webfont.woff
421 ms
bebasneue_book-webfont.woff
416 ms
bebasneue_bold-webfont.woff
415 ms
bebasneue_regular-webfont.woff
413 ms
bebasneue_book-webfont.woff
409 ms
linkedin-in.svg
403 ms
tp-logo-hp-footer.webp
399 ms
XM_logo_black_2021.svg
398 ms
xm-trader.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
xm-trader.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
xm-trader.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xm-trader.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Xm-trader.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
xm-trader.com
Open Graph data is detected on the main page of XM Trader. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: