12.9 sec in total
3.2 sec
9.1 sec
599 ms
Click here to check amazing Xm content. Otherwise, check out these important facts you probably never knew about xm.direct
Visit xm.directWe analyzed Xm.direct page load time and found that the first response time was 3.2 sec and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
xm.direct performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value0
0/100
25%
Value18.9 s
0/100
10%
Value6,900 ms
0/100
30%
Value0.07
96/100
15%
Value32.0 s
0/100
10%
3243 ms
19 ms
3038 ms
97 ms
85 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Xm.direct, 5% (7 requests) were made to Apis.google.com and 5% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Xmindonesiatrade.com.
Page size can be reduced by 241.9 kB (20%)
1.2 MB
994.0 kB
In fact, the total size of Xm.direct main page is 1.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 610.3 kB which makes up the majority of the site volume.
Potential reduce by 2.7 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 2.7 kB or 53% of the original size.
Potential reduce by 55.7 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 images are well optimized though.
Potential reduce by 130.2 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 130.2 kB or 21% of the original size.
Potential reduce by 53.3 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.direct needs all CSS files to be minified and compressed as it can save up to 53.3 kB or 62% of the original size.
Number of requests can be reduced by 70 (55%)
127
57
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.xmindonesiatrade.com
3243 ms
FX72H-U393W-CNX6U-WRWHF-88HB7
19 ms
www.xmindonesiatrade.com
3038 ms
config.json
97 ms
gtm.js
85 ms
js
62 ms
analytics.js
91 ms
roundtrip.js
168 ms
destination
116 ms
uwt.js
113 ms
bat.js
161 ms
insight.min.js
156 ms
pixel.js
102 ms
destination
146 ms
collect
59 ms
rp.gif
73 ms
t2_9kokcyos_telemetry
71 ms
52015887.js
14 ms
adsct
204 ms
adsct
120 ms
adsct
201 ms
adsct
206 ms
adsct
149 ms
adsct
203 ms
adsct
131 ms
adsct
149 ms
52015887
94 ms
JRJZLHCGQJAIRP52AZ7GL2
20 ms
clarity.js
21 ms
0677960cd8.js
52 ms
DGOGWBODDRD7VMNVUJRIAB.js
6 ms
XMLogo-2021_homepage.svg
329 ms
cryptos-hp-icon-en.svg
326 ms
live-chat-icon-lite.svg
329 ms
livechat_24x24.svg
325 ms
whatsapp_24x24.svg
327 ms
XMBZNewWhatsappNumber1.png
354 ms
line_24x24.svg
339 ms
line-qr-code-bw.png
382 ms
helpcenter_24x24.svg
338 ms
home_page_competitions_card_icon.webp
374 ms
copy-trading-networking-icon-sm.webp
356 ms
copy-trading-networking-icon-lg.webp
354 ms
MT4-MT5-hp-xs.png
380 ms
MT4-MT5-hp-sm.png
403 ms
platforms.png
401 ms
wf-awards-customer-service.webp
423 ms
wf-awards-eu.webp
386 ms
wf-awards-australasia.webp
393 ms
wf-awards-latam.webp
392 ms
wf-awards-mddleeast.webp
397 ms
cfi-most-reliable-2023.webp
403 ms
metaquotes.webp
404 ms
verisign.webp
410 ms
unicef-cfc.webp
411 ms
iip-platinum.webp
413 ms
gptw-cy-2023.webp
414 ms
gptw-gr-2023.webp
414 ms
facebook-f.svg
420 ms
x-twitter.svg
421 ms
youtube.svg
425 ms
instagram.svg
422 ms
linkedin-in.svg
424 ms
tiktok.svg
429 ms
tp-logo-hp-footer.webp
431 ms
XM_logo_black_2021.svg
430 ms
flags-icons-sprite-alt.png
434 ms
events.js
239 ms
fbevents.js
173 ms
dablena.min.js
286 ms
ld.js
210 ms
ytc.js
209 ms
jquery.tosrus.min.css
812 ms
10201023.json
75 ms
syncframe
77 ms
Roboto-Regular-webfont.woff
113 ms
Roboto-Medium-webfont.woff
185 ms
Roboto-Light-webfont.woff
136 ms
Roboto-Thin-webfont.woff
184 ms
Roboto-Bold-webfont.woff
164 ms
Roboto-Black-webfont.woff
154 ms
bebasneue_bold-webfont.woff
138 ms
bebasneue_regular-webfont.woff
158 ms
bebasneue_book-webfont.woff
139 ms
bebasneue_bold-webfont.woff
181 ms
bebasneue_regular-webfont.woff
180 ms
bebasneue_book-webfont.woff
132 ms
popper_tippy.min.js
171 ms
main_homepage.js
150 ms
jquery_cookie.js
145 ms
cookie_popup.js
145 ms
url_parameters_affid_gid.js
152 ms
qrcode-with-logos_1_0_3.min.js
1021 ms
forms.js
150 ms
homepage-2023.webp
169 ms
copy-trading-homepage-bg.webp
170 ms
devices-icon-sm.svg
161 ms
platform.js
38 ms
popper_tippy.min.css
19 ms
textblocks.css
18 ms
tabs.css
15 ms
video.css
12 ms
footer.css
16 ms
forms.css
28 ms
alerts.css
29 ms
modals.css
99 ms
bubble_widget.css
33 ms
cb=gapi.loaded_0
12 ms
cb=gapi.loaded_1
34 ms
subscribe_embed
89 ms
postmessageRelay
90 ms
www-subscribe-embed_split_v0.css
5 ms
www-subscribe-embed_v0.js
14 ms
subscribe_button_branded_lozenge.png
26 ms
cb=gapi.loaded_0
12 ms
1005847222-postmessagerelay.js
51 ms
rpc:shindig_random.js
44 ms
cb=gapi.loaded_0
7 ms
cb=gapi.loaded_2
10 ms
border_3.gif
14 ms
subscribe_embed
197 ms
spacer.gif
14 ms
bubbleSprite_3.png
6 ms
bubbleDropR_3.png
11 ms
bubbleDropB_3.png
178 ms
ajax-loader.gif
83 ms
playlistItems
161 ms
playlistItems
192 ms
playlistItems
207 ms
www-subscribe-embed-card_v0.css
19 ms
www-subscribe-embed-card_v0.js
22 ms
playlistItems
143 ms
collect
33 ms
collect
33 ms
mqdefault.jpg
29 ms
mqdefault.jpg
41 ms
mqdefault.jpg
42 ms
mqdefault.jpg
43 ms
mqdefault.jpg
50 ms
c.gif
8 ms
xm.direct 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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
xm.direct best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
xm.direct SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xm.direct can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Xm.direct 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.direct
Open Graph description is not detected on the main page of Xm. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: