Tools & Wizards About Us
xe.co screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

xe.co

Xe: Currency Exchange Rates and International Money Transfers

Page Load Speed

1.4 sec in total

First Response

21 ms

Resources Loaded

771 ms

Page Rendered

566 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 21 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

xe.co performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,650 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.162

72/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

xe.co

21 ms

www.xe.com

64 ms

style.css

40 ms

8326554781.js

158 ms

4f3cedd0a4bbba24d5f4.css

41 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Xe.co, 93% (55 requests) were made to Xe.com and 2% (1 request) were made to Cdn.optimizely.com. The less responsive or slowest element that took the longest time to load (394 ms) relates to the external source Images.ctfassets.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 85.5 kB (31%)

Content Size

278.8 kB

After Optimization

193.3 kB

  • HTML
  • Images

In fact, the total size of Xe.co main page is 278.8 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. 60% of websites need less resources to load. Images take 169.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 85.5 kB

  • Original 109.2 kB
  • After minification 109.2 kB
  • After compression 23.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 85.5 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 46 (81%)

Requests Now

57

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 57 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 40 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

xe.co

xe.co

21 ms

www.xe.com

www.xe.com

64 ms

style.css

style.css

40 ms

8326554781.js

8326554781.js

158 ms

4f3cedd0a4bbba24d5f4.css

4f3cedd0a4bbba24d5f4.css

41 ms

polyfills-65824a8976c152b3b01b.js

polyfills-65824a8976c152b3b01b.js

58 ms

124.86c7d2962d81c3c2d5c0.js

124.86c7d2962d81c3c2d5c0.js

58 ms

125.172e836012d869715710.js

125.172e836012d869715710.js

45 ms

138.c25de8be7150ce9a4b2e.js

138.c25de8be7150ce9a4b2e.js

57 ms

140.bce13fa561e1b576436c.js

140.bce13fa561e1b576436c.js

45 ms

webpack-bb7331e854cbf4b7e52b.js

webpack-bb7331e854cbf4b7e52b.js

42 ms

framework.349d8128c43083da4feb.js

framework.349d8128c43083da4feb.js

51 ms

78661c815aa67889edf55e4bc19f92dd01fb8f3f.5c045e2e38ab272de817.js

78661c815aa67889edf55e4bc19f92dd01fb8f3f.5c045e2e38ab272de817.js

51 ms

main-53771034175c0fa9f943.js

main-53771034175c0fa9f943.js

54 ms

8543cd77ccacae148857b3095e6a6edb117d821e.66f2443b59f4cdfaaa46.js

8543cd77ccacae148857b3095e6a6edb117d821e.66f2443b59f4cdfaaa46.js

57 ms

a4293d2e1ba09d48595487625b875ea12619553f.5c95be2d1ab779f1c1bf.js

a4293d2e1ba09d48595487625b875ea12619553f.5c95be2d1ab779f1c1bf.js

57 ms

a0a4b383f8e2a7af934849d96dc8fa4f5bf9e9c2.9dced1a69b40a5e2596f.js

a0a4b383f8e2a7af934849d96dc8fa4f5bf9e9c2.9dced1a69b40a5e2596f.js

57 ms

db0b8e64064fc214aa818b1244242c5ffe5cfece.675977170bd201096d50.js

db0b8e64064fc214aa818b1244242c5ffe5cfece.675977170bd201096d50.js

57 ms

ad46b11f09ab2f28ea4bb42c62bc7f8a20cb726c.0307033d1f2b835e1111.js

ad46b11f09ab2f28ea4bb42c62bc7f8a20cb726c.0307033d1f2b835e1111.js

59 ms

819b9031de6a343e7055bf768f0ba1f96dba0dd2.ad220d4d0adf940b3950.js

819b9031de6a343e7055bf768f0ba1f96dba0dd2.ad220d4d0adf940b3950.js

59 ms

9d53d99eb5773eba0150bc1e12ae1d37d77f0995.8698d989b6eac2ea6036.js

9d53d99eb5773eba0150bc1e12ae1d37d77f0995.8698d989b6eac2ea6036.js

64 ms

8fde42969547960b3cf3f9a55a96c9b3fd380560.88c9c651287163db24da.js

8fde42969547960b3cf3f9a55a96c9b3fd380560.88c9c651287163db24da.js

61 ms

0a48171c93c04c6283b1b80f1672fd3c8eb426cb.606fd3453522568f11ae.js

0a48171c93c04c6283b1b80f1672fd3c8eb426cb.606fd3453522568f11ae.js

64 ms

4268a43e4bbf107836efaeea0800790c11938642.2b7a8fd343477773ea0a.js

4268a43e4bbf107836efaeea0800790c11938642.2b7a8fd343477773ea0a.js

64 ms

d20a598aca8dc5f0dac57254c59fcd9436af849b.2a9f7b3fe1f0d60d658e.js

d20a598aca8dc5f0dac57254c59fcd9436af849b.2a9f7b3fe1f0d60d658e.js

65 ms

fb2ba78d0af3116e47ea64dd7d3f07f9c0703b28.1921aa37dbb653fdb13e.js

fb2ba78d0af3116e47ea64dd7d3f07f9c0703b28.1921aa37dbb653fdb13e.js

64 ms

2a325b8a04c467cae4cc9e78e71d56d79c664bfa.89b5223f1511beb9e96b.js

2a325b8a04c467cae4cc9e78e71d56d79c664bfa.89b5223f1511beb9e96b.js

65 ms

b5deef23c7d8ef607d56d0077c937a2f99b5818b.32ca57ace11ae2c800e4.js

b5deef23c7d8ef607d56d0077c937a2f99b5818b.32ca57ace11ae2c800e4.js

66 ms

_app-d80d309f87da7ea29fb8.js

_app-d80d309f87da7ea29fb8.js

68 ms

66abe8ffcf7eaabd66cd14445db46e4a86ee700a.67a4fd55278a3f014ec7.js

66abe8ffcf7eaabd66cd14445db46e4a86ee700a.67a4fd55278a3f014ec7.js

68 ms

0c8975d1e75bd7ed73b85b140bbd856c0061ec33.489e6ec85cf3db665031.js

0c8975d1e75bd7ed73b85b140bbd856c0061ec33.489e6ec85cf3db665031.js

67 ms

fb269e6f8b07da382b580d2d7d0b75835414ceb3.85c75f481347e0f33476.js

fb269e6f8b07da382b580d2d7d0b75835414ceb3.85c75f481347e0f33476.js

87 ms

20f4d108508680e7784b8c03370dc088964f9f64.36ea820a4ecf1bc55fc7.js

20f4d108508680e7784b8c03370dc088964f9f64.36ea820a4ecf1bc55fc7.js

67 ms

4a3ecd6ab00130dc5fb8609bdd8469efe7ebf1fa.25a4673a85e3c23d1236.js

4a3ecd6ab00130dc5fb8609bdd8469efe7ebf1fa.25a4673a85e3c23d1236.js

77 ms

39995a91d39349d3e695f3c88d865a043c21cf24.d710002e2e73e3873f91.js

39995a91d39349d3e695f3c88d865a043c21cf24.d710002e2e73e3873f91.js

77 ms

edd5393bd2ccf4a9e513a88492fbb531773ca808.7d2819049b9c4e076e6c.js

edd5393bd2ccf4a9e513a88492fbb531773ca808.7d2819049b9c4e076e6c.js

76 ms

5e3e4dfc8d65377dda2e205d8fc652e290e659fb.2e9bba6674592d0b7363.js

5e3e4dfc8d65377dda2e205d8fc652e290e659fb.2e9bba6674592d0b7363.js

77 ms

edb45257637ca36ca76f840db02975c03f847c26.c3ffcff97a46c183b2c5.js

edb45257637ca36ca76f840db02975c03f847c26.c3ffcff97a46c183b2c5.js

77 ms

index-c7c2f783f493094036a6.js

index-c7c2f783f493094036a6.js

71 ms

gtm.js

gtm.js

72 ms

_buildManifest.js

_buildManifest.js

58 ms

_ssgManifest.js

_ssgManifest.js

58 ms

usd.static.e8b657d1161a08a32415d284a8e1dc89.svg

usd.static.e8b657d1161a08a32415d284a8e1dc89.svg

345 ms

Xe-App-iPhones__1_.png

Xe-App-iPhones__1_.png

394 ms

eur.static.7c6f881c3b6506b03bcbda3644485094.svg

eur.static.7c6f881c3b6506b03bcbda3644485094.svg

329 ms

app_store_en.static.8e10c93dd80dafcc4aefe463cb0d0206.svg

app_store_en.static.8e10c93dd80dafcc4aefe463cb0d0206.svg

321 ms

google_play_en.static.72ea44d7007622c2f7e41dae9df00236.svg

google_play_en.static.72ea44d7007622c2f7e41dae9df00236.svg

323 ms

gbp.static.da0ca3d1b6d9e74642276a0ea3cde603.svg

gbp.static.da0ca3d1b6d9e74642276a0ea3cde603.svg

316 ms

cad.static.0bfb6a6d0adf4f3b1c28c0c90248b18b.svg

cad.static.0bfb6a6d0adf4f3b1c28c0c90248b18b.svg

320 ms

aud.static.6e69da30d2a4593d811f765c491964af.svg

aud.static.6e69da30d2a4593d811f765c491964af.svg

325 ms

jpy.static.238642084e415a2c2304c9b3da2308d9.svg

jpy.static.238642084e415a2c2304c9b3da2308d9.svg

327 ms

inr.static.9f6afce19e2f7f491c4d1d4faea36747.svg

inr.static.9f6afce19e2f7f491c4d1d4faea36747.svg

374 ms

nzd.static.7a4b8c0de7fdfd2f038c970f38bb3c10.svg

nzd.static.7a4b8c0de7fdfd2f038c970f38bb3c10.svg

372 ms

chf.static.eb65ed7418d2ad8703a7c9c54467b785.svg

chf.static.eb65ed7418d2ad8703a7c9c54467b785.svg

375 ms

zar.static.f78bb14b642f545ed8016b99235b0c88.svg

zar.static.f78bb14b642f545ed8016b99235b0c88.svg

368 ms

rub.static.273cd67a9958739d7c9e2fa98fe1e4f0.svg

rub.static.273cd67a9958739d7c9e2fa98fe1e4f0.svg

370 ms

bgn.static.13c846b32c10f098953fed3ac5d3cdf4.svg

bgn.static.13c846b32c10f098953fed3ac5d3cdf4.svg

372 ms

5eec9076b7122a47bb63baa280245b3614395d2a.bca387f949c5bb3308ad.js

5eec9076b7122a47bb63baa280245b3614395d2a.bca387f949c5bb3308ad.js

87 ms

_error-afc68450382374c97025.js

_error-afc68450382374c97025.js

88 ms

Accessibility Review

xe.co accessibility score

91

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

Buttons do not have an accessible name

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

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

90

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

Links do not have descriptive text

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: