Tools & Wizards About Us
moneyxe.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

moneyxe.com

Xe: Currency Exchange Rates and International Money Transfers

Page Load Speed

895 ms in total

First Response

38 ms

Resources Loaded

312 ms

Page Rendered

545 ms

moneyxe.com screenshot

About Website

Welcome to moneyxe.com homepage info - get ready to check Money Xe best content right away, or after learning these important things about moneyxe.com

Get the best currency exchange rates for international money transfers to 200 countries in 100 foreign currencies. Send and receive money with best forex rates.

Visit moneyxe.com

Key Findings

We analyzed Moneyxe.com page load time and found that the first response time was 38 ms and then it took 857 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

moneyxe.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value4,600 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.14

79/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

moneyxe.com

38 ms

www.xe.com

46 ms

gtm.js

121 ms

ae1764fd752018c2.css

29 ms

5b2da06775ad38c0.css

36 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Moneyxe.com, 94% (47 requests) were made to Xe.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (172 ms) relates to the external source Xe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 317.0 kB (60%)

Content Size

529.4 kB

After Optimization

212.3 kB

  • HTML
  • Images

In fact, the total size of Moneyxe.com main page is 529.4 kB. 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 427.8 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 317.0 kB

  • Original 427.8 kB
  • After minification 427.6 kB
  • After compression 110.8 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 317.0 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 101.5 kB
  • After minification 101.5 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. Money Xe images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 37 (77%)

Requests Now

48

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

moneyxe.com

moneyxe.com

38 ms

www.xe.com

www.xe.com

46 ms

gtm.js

gtm.js

121 ms

ae1764fd752018c2.css

ae1764fd752018c2.css

29 ms

5b2da06775ad38c0.css

5b2da06775ad38c0.css

36 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

65 ms

3366.59d5331013103e13.js

3366.59d5331013103e13.js

36 ms

5259-3bac440127a5c009.js

5259-3bac440127a5c009.js

98 ms

8687.6b4c819afb3d2652.js

8687.6b4c819afb3d2652.js

64 ms

9923.f16e196f137cb15c.js

9923.f16e196f137cb15c.js

35 ms

7202.e093ff4e43b271b9.js

7202.e093ff4e43b271b9.js

107 ms

3799.948a3680db1b5969.js

3799.948a3680db1b5969.js

107 ms

6953.b7bbe3d12b45da47.js

6953.b7bbe3d12b45da47.js

108 ms

webpack-92f3d634140ae7f6.js

webpack-92f3d634140ae7f6.js

109 ms

framework-ca706bf673a13738.js

framework-ca706bf673a13738.js

111 ms

main-d2bfb6e46077d9ca.js

main-d2bfb6e46077d9ca.js

111 ms

_app-515f98d24bb929c3.js

_app-515f98d24bb929c3.js

151 ms

1814-711876a5f5b0febc.js

1814-711876a5f5b0febc.js

119 ms

3595-a09ab626549e5fdd.js

3595-a09ab626549e5fdd.js

117 ms

865-0f5b59e772fdcc3a.js

865-0f5b59e772fdcc3a.js

118 ms

4538-928229537750bf79.js

4538-928229537750bf79.js

118 ms

1066-c139d7f41d9cc76e.js

1066-c139d7f41d9cc76e.js

117 ms

4127-47b66b1ea1a14fda.js

4127-47b66b1ea1a14fda.js

162 ms

6314-5789ada16cd69dbc.js

6314-5789ada16cd69dbc.js

162 ms

2944-05df2242144220f4.js

2944-05df2242144220f4.js

162 ms

349-a82227679de2e4e6.js

349-a82227679de2e4e6.js

162 ms

5546-f3fca3b72ab4ef60.js

5546-f3fca3b72ab4ef60.js

160 ms

1063-9db8b17df103b6f0.js

1063-9db8b17df103b6f0.js

163 ms

4297-f1c97e514701b18a.js

4297-f1c97e514701b18a.js

165 ms

5387-a12a9428e3fb272f.js

5387-a12a9428e3fb272f.js

164 ms

3363-87d2b7dab90a41bc.js

3363-87d2b7dab90a41bc.js

167 ms

1127-e67fac0ca30e3b63.js

1127-e67fac0ca30e3b63.js

166 ms

index-87944101689a9132.js

index-87944101689a9132.js

166 ms

_buildManifest.js

_buildManifest.js

168 ms

_ssgManifest.js

_ssgManifest.js

172 ms

Xe-App-iPhones__1_min.png

Xe-App-iPhones__1_min.png

101 ms

usd.static.svg

usd.static.svg

156 ms

eur.static.svg

eur.static.svg

153 ms

app_store_en.static.svg

app_store_en.static.svg

163 ms

google_play_en.static.svg

google_play_en.static.svg

158 ms

gbp.static.svg

gbp.static.svg

153 ms

cad.static.svg

cad.static.svg

152 ms

aud.static.svg

aud.static.svg

122 ms

jpy.static.svg

jpy.static.svg

123 ms

inr.static.svg

inr.static.svg

108 ms

nzd.static.svg

nzd.static.svg

105 ms

chf.static.svg

chf.static.svg

83 ms

zar.static.svg

zar.static.svg

85 ms

rub.static.svg

rub.static.svg

84 ms

bgn.static.svg

bgn.static.svg

83 ms

Accessibility Review

moneyxe.com accessibility score

98

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

moneyxe.com best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

moneyxe.com SEO score

97

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Social Sharing Optimization

moneyxe.com

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