Tools & Wizards About Us
xe.co screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% 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

xe.co

Currency Exchange Rates and International Money Transfers

Page Load Speed

329 ms in total

First Response

17 ms

Resources Loaded

312 ms

Page Rendered

0 ms

xe.co screenshot

About Website

Click here to check amazing Xe content. Otherwise, check out these important facts you probably never knew about xe.co

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 xe.co

Key Findings

We analyzed Xe.co page load time and found that the first response time was 17 ms and then it took 312 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

xe.co performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value6,580 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.189

65/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

xe.co

17 ms

www.xe.com

62 ms

gtm.js

229 ms

9370dd39dc888ce1.css

35 ms

5b2da06775ad38c0.css

47 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 Xe.co, 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 (229 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 456.7 kB (64%)

Content Size

717.5 kB

After Optimization

260.8 kB

  • HTML
  • Images

In fact, the total size of Xe.co main page is 717.5 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. 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. HTML takes 427.5 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 316.7 kB

  • Original 427.5 kB
  • After minification 427.3 kB
  • After compression 110.9 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 316.7 kB or 74% of the original size.

Image Optimization

-48%

Potential reduce by 140.1 kB

  • Original 290.0 kB
  • After minification 149.9 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, Xe needs image optimization as it can save up to 140.1 kB or 48% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

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 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

xe.co

xe.co

17 ms

www.xe.com

www.xe.com

62 ms

gtm.js

gtm.js

229 ms

9370dd39dc888ce1.css

9370dd39dc888ce1.css

35 ms

5b2da06775ad38c0.css

5b2da06775ad38c0.css

47 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

116 ms

3366.59d5331013103e13.js

3366.59d5331013103e13.js

115 ms

5259-3bac440127a5c009.js

5259-3bac440127a5c009.js

143 ms

8687.6b4c819afb3d2652.js

8687.6b4c819afb3d2652.js

157 ms

9923.7d5c8cfccd1e4192.js

9923.7d5c8cfccd1e4192.js

141 ms

7202.e093ff4e43b271b9.js

7202.e093ff4e43b271b9.js

141 ms

3799.948a3680db1b5969.js

3799.948a3680db1b5969.js

160 ms

6953.b7bbe3d12b45da47.js

6953.b7bbe3d12b45da47.js

161 ms

webpack-6a3b695b2ddc1001.js

webpack-6a3b695b2ddc1001.js

161 ms

framework-ca706bf673a13738.js

framework-ca706bf673a13738.js

164 ms

main-d2bfb6e46077d9ca.js

main-d2bfb6e46077d9ca.js

174 ms

_app-7927399d635ad070.js

_app-7927399d635ad070.js

179 ms

1814-711876a5f5b0febc.js

1814-711876a5f5b0febc.js

172 ms

3595-a09ab626549e5fdd.js

3595-a09ab626549e5fdd.js

172 ms

865-0f5b59e772fdcc3a.js

865-0f5b59e772fdcc3a.js

174 ms

4538-928229537750bf79.js

4538-928229537750bf79.js

174 ms

1066-c139d7f41d9cc76e.js

1066-c139d7f41d9cc76e.js

176 ms

4127-a038c38e7451df18.js

4127-a038c38e7451df18.js

192 ms

6314-f67a877fdd4f2faa.js

6314-f67a877fdd4f2faa.js

191 ms

2944-db140d4520d91a25.js

2944-db140d4520d91a25.js

193 ms

349-517747c1f1c5a9d5.js

349-517747c1f1c5a9d5.js

194 ms

7192-7b3a96eb1e6e4402.js

7192-7b3a96eb1e6e4402.js

197 ms

1063-3f283bf3162f67ee.js

1063-3f283bf3162f67ee.js

198 ms

4297-f1c97e514701b18a.js

4297-f1c97e514701b18a.js

196 ms

5387-3c76586dd064fad2.js

5387-3c76586dd064fad2.js

196 ms

3363-9d7906a5413754cb.js

3363-9d7906a5413754cb.js

196 ms

1127-a289cf470d0291cc.js

1127-a289cf470d0291cc.js

198 ms

index-d9eb52e7576e61cc.js

index-d9eb52e7576e61cc.js

202 ms

_buildManifest.js

_buildManifest.js

203 ms

_ssgManifest.js

_ssgManifest.js

198 ms

Xe-App-iPhones__1_min_1.png

Xe-App-iPhones__1_min_1.png

173 ms

usd.static.svg

usd.static.svg

173 ms

eur.static.svg

eur.static.svg

175 ms

app_store_en.static.svg

app_store_en.static.svg

176 ms

google_play_en.static.svg

google_play_en.static.svg

175 ms

gbp.static.svg

gbp.static.svg

172 ms

cad.static.svg

cad.static.svg

118 ms

aud.static.svg

aud.static.svg

78 ms

jpy.static.svg

jpy.static.svg

79 ms

inr.static.svg

inr.static.svg

76 ms

nzd.static.svg

nzd.static.svg

65 ms

chf.static.svg

chf.static.svg

63 ms

zar.static.svg

zar.static.svg

65 ms

rub.static.svg

rub.static.svg

62 ms

bgn.static.svg

bgn.static.svg

61 ms

Accessibility Review

xe.co 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

xe.co 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

xe.co 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 Xe.co 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 Xe.co 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

xe.co

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