Tools & Wizards About Us
xmbroker.direct screenshot

Report Summary

  • 0

    Performance

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

xmbroker.direct

Page Load Speed

9.1 sec in total

First Response

2 sec

Resources Loaded

6.6 sec

Page Rendered

466 ms

xmbroker.direct screenshot

About Website

Visit xmbroker.direct now to see the best up-to-date Xmbroker content for Indonesia and also check out these interesting facts you probably never knew about xmbroker.direct

Visit xmbroker.direct

Key Findings

We analyzed Xmbroker.direct page load time and found that the first response time was 2 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

xmbroker.direct performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value16.0 s

0/100

10%

TBT (Total Blocking Time)

Value2,590 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

www.xmindonesiatrade.com

2010 ms

FX72H-U393W-CNX6U-WRWHF-88HB7

19 ms

www.xmindonesiatrade.com

1883 ms

config.json

44 ms

gtm.js

62 ms

Our browser made a total of 150 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Xmbroker.direct, 7% (11 requests) were made to D.adroll.com and 5% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Xmindonesiatrade.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 241.1 kB (19%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xmbroker.direct main page is 1.3 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. 80% 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 670.2 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 40.4 kB

  • Original 61.9 kB
  • After minification 61.8 kB
  • After compression 21.5 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 40.4 kB or 65% of the original size.

Image Optimization

-11%

Potential reduce by 55.6 kB

  • Original 484.7 kB
  • After minification 429.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. Obviously, Xmbroker needs image optimization as it can save up to 55.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 91.7 kB

  • Original 670.2 kB
  • After minification 670.2 kB
  • After compression 578.5 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 91.7 kB or 14% of the original size.

CSS Optimization

-62%

Potential reduce by 53.3 kB

  • Original 86.2 kB
  • After minification 85.8 kB
  • After compression 32.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. Xmbroker.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.

Requests Breakdown

Number of requests can be reduced by 79 (63%)

Requests Now

126

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xmbroker. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.xmindonesiatrade.com

www.xmindonesiatrade.com

2010 ms

FX72H-U393W-CNX6U-WRWHF-88HB7

FX72H-U393W-CNX6U-WRWHF-88HB7

19 ms

www.xmindonesiatrade.com

www.xmindonesiatrade.com

1883 ms

config.json

config.json

44 ms

gtm.js

gtm.js

62 ms

0677960cd8.js

0677960cd8.js

112 ms

js

js

200 ms

analytics.js

analytics.js

68 ms

roundtrip.js

roundtrip.js

81 ms

destination

destination

195 ms

uwt.js

uwt.js

117 ms

bat.js

bat.js

188 ms

insight.min.js

insight.min.js

51 ms

pixel.js

pixel.js

180 ms

destination

destination

178 ms

jquery.tosrus.min.css

jquery.tosrus.min.css

956 ms

popper_tippy.min.js

popper_tippy.min.js

331 ms

main_homepage.js

main_homepage.js

330 ms

jquery_cookie.js

jquery_cookie.js

366 ms

cookie_popup.js

cookie_popup.js

324 ms

url_parameters_affid_gid.js

url_parameters_affid_gid.js

412 ms

qrcode-with-logos_1_0_3.min.js

qrcode-with-logos_1_0_3.min.js

415 ms

forms.js

forms.js

410 ms

insight_tag_errors.gif

insight_tag_errors.gif

446 ms

collect

collect

272 ms

fs.js

fs.js

309 ms

flags-icons-sprite-alt.png

flags-icons-sprite-alt.png

323 ms

XMLogo-2021_homepage.svg

XMLogo-2021_homepage.svg

325 ms

cryptos-hp-icon-en.svg

cryptos-hp-icon-en.svg

322 ms

live-chat-icon-lite.svg

live-chat-icon-lite.svg

357 ms

livechat_24x24.svg

livechat_24x24.svg

391 ms

whatsapp_24x24.svg

whatsapp_24x24.svg

382 ms

XMBZNewWhatsappNumber1.png

XMBZNewWhatsappNumber1.png

382 ms

line_24x24.svg

line_24x24.svg

389 ms

line-qr-code-bw.png

line-qr-code-bw.png

387 ms

helpcenter_24x24.svg

helpcenter_24x24.svg

394 ms

homepage-2023.webp

homepage-2023.webp

426 ms

home_page_competitions_card_icon.webp

home_page_competitions_card_icon.webp

498 ms

copy-trading-homepage-bg.webp

copy-trading-homepage-bg.webp

428 ms

copy-trading-networking-icon-sm.webp

copy-trading-networking-icon-sm.webp

427 ms

copy-trading-networking-icon-lg.webp

copy-trading-networking-icon-lg.webp

426 ms

MT4-MT5-hp-xs.png

MT4-MT5-hp-xs.png

498 ms

MT4-MT5-hp-sm.png

MT4-MT5-hp-sm.png

445 ms

devices-icon-sm.svg

devices-icon-sm.svg

488 ms

platforms.png

platforms.png

488 ms

wf-awards-customer-service.webp

wf-awards-customer-service.webp

446 ms

wf-awards-eu.webp

wf-awards-eu.webp

461 ms

wf-awards-australasia.webp

wf-awards-australasia.webp

473 ms

wf-awards-latam.webp

wf-awards-latam.webp

496 ms

wf-awards-mddleeast.webp

wf-awards-mddleeast.webp

504 ms

cfi-most-reliable-2023.webp

cfi-most-reliable-2023.webp

514 ms

metaquotes.webp

metaquotes.webp

598 ms

verisign.webp

verisign.webp

528 ms

unicef-cfc.webp

unicef-cfc.webp

526 ms

iip-platinum.webp

iip-platinum.webp

526 ms

config.json

config.json

186 ms

events.js

events.js

298 ms

rp.gif

rp.gif

217 ms

t2_9kokcyos_telemetry

t2_9kokcyos_telemetry

128 ms

fbevents.js

fbevents.js

139 ms

dablena.min.js

dablena.min.js

200 ms

ld.js

ld.js

163 ms

ytc.js

ytc.js

132 ms

52015887.js

52015887.js

42 ms

JRJZLHCGQJAIRP52AZ7GL2

JRJZLHCGQJAIRP52AZ7GL2

156 ms

adsct

adsct

262 ms

adsct

adsct

262 ms

adsct

adsct

260 ms

adsct

adsct

240 ms

adsct

adsct

309 ms

adsct

adsct

245 ms

adsct

adsct

259 ms

adsct

adsct

320 ms

Roboto-Regular-webfont.woff

Roboto-Regular-webfont.woff

327 ms

Roboto-Medium-webfont.woff

Roboto-Medium-webfont.woff

360 ms

Roboto-Light-webfont.woff

Roboto-Light-webfont.woff

297 ms

52015887

52015887

154 ms

Roboto-Thin-webfont.woff

Roboto-Thin-webfont.woff

278 ms

Roboto-Bold-webfont.woff

Roboto-Bold-webfont.woff

239 ms

Roboto-Black-webfont.woff

Roboto-Black-webfont.woff

242 ms

bebasneue_bold-webfont.woff

bebasneue_bold-webfont.woff

282 ms

bebasneue_regular-webfont.woff

bebasneue_regular-webfont.woff

280 ms

bebasneue_book-webfont.woff

bebasneue_book-webfont.woff

244 ms

10201023.json

10201023.json

59 ms

bebasneue_bold-webfont.woff

bebasneue_bold-webfont.woff

270 ms

bebasneue_regular-webfont.woff

bebasneue_regular-webfont.woff

222 ms

bebasneue_book-webfont.woff

bebasneue_book-webfont.woff

228 ms

syncframe

syncframe

44 ms

gptw-cy-2023.webp

gptw-cy-2023.webp

216 ms

gptw-gr-2023.webp

gptw-gr-2023.webp

255 ms

facebook-f.svg

facebook-f.svg

215 ms

x-twitter.svg

x-twitter.svg

252 ms

youtube.svg

youtube.svg

213 ms

clarity.js

clarity.js

20 ms

DGOGWBODDRD7VMNVUJRIAB.js

DGOGWBODDRD7VMNVUJRIAB.js

3 ms

out

out

26 ms

sendrolling.js

sendrolling.js

25 ms

out

out

25 ms

out

out

29 ms

out

out

25 ms

out

out

27 ms

out

out

30 ms

out

out

26 ms

out

out

29 ms

out

out

31 ms

instagram.svg

instagram.svg

183 ms

linkedin-in.svg

linkedin-in.svg

184 ms

tiktok.svg

tiktok.svg

184 ms

tp-logo-hp-footer.webp

tp-logo-hp-footer.webp

203 ms

event

event

213 ms

pixel

pixel

86 ms

Pug

Pug

76 ms

tap.php

tap.php

71 ms

sd

sd

114 ms

XM_logo_black_2021.svg

XM_logo_black_2021.svg

186 ms

pixel

pixel

34 ms

bounce

bounce

41 ms

sync

sync

35 ms

in

in

42 ms

rum

rum

48 ms

platform.js

platform.js

28 ms

popper_tippy.min.css

popper_tippy.min.css

42 ms

textblocks.css

textblocks.css

86 ms

tabs.css

tabs.css

42 ms

video.css

video.css

87 ms

footer.css

footer.css

37 ms

forms.css

forms.css

39 ms

alerts.css

alerts.css

44 ms

modals.css

modals.css

174 ms

bubble_widget.css

bubble_widget.css

42 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

17 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

33 ms

subscribe_embed

subscribe_embed

83 ms

postmessageRelay

postmessageRelay

199 ms

www-subscribe-embed_split_v0.css

www-subscribe-embed_split_v0.css

4 ms

www-subscribe-embed_v0.js

www-subscribe-embed_v0.js

10 ms

subscribe_button_branded_lozenge.png

subscribe_button_branded_lozenge.png

23 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

cb=gapi.loaded_2

cb=gapi.loaded_2

8 ms

border_3.gif

border_3.gif

20 ms

subscribe_embed

subscribe_embed

49 ms

spacer.gif

spacer.gif

17 ms

bubbleSprite_3.png

bubbleSprite_3.png

14 ms

bubbleDropR_3.png

bubbleDropR_3.png

11 ms

bubbleDropB_3.png

bubbleDropB_3.png

12 ms

1005847222-postmessagerelay.js

1005847222-postmessagerelay.js

6 ms

rpc:shindig_random.js

rpc:shindig_random.js

38 ms

www-subscribe-embed-card_v0.css

www-subscribe-embed-card_v0.css

21 ms

www-subscribe-embed-card_v0.js

www-subscribe-embed-card_v0.js

23 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

19 ms

Accessibility Review

xmbroker.direct accessibility score

81

Accessibility Issues

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

High

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

xmbroker.direct best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

xmbroker.direct SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xmbroker.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 Xmbroker.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.

Social Sharing Optimization

xmbroker.direct

Open Graph description is not detected on the main page of Xmbroker. 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: