Tools & Wizards About Us
fcexchange.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

fcexchange.com

Cross Border Payments & Currency Risk Management | Corpay

Page Load Speed

2 sec in total

First Response

49 ms

Resources Loaded

898 ms

Page Rendered

1 sec

fcexchange.com screenshot

About Website

Visit fcexchange.com now to see the best up-to-date Fcexchange content for United Kingdom and also check out these interesting facts you probably never knew about fcexchange.com

Solutions that help your business spend less and do more. Corpay helps you track, manage, and pay expenses.

Visit fcexchange.com

Key Findings

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

Performance Metrics

fcexchange.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value10,320 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value37.6 s

0/100

10%

Network Requests Diagram

fcexchange.com

49 ms

www.globalreachgroup.com

62 ms

en-GB

266 ms

ed4b6f7280755c33.css

48 ms

7ce24792dd4b7e74.css

73 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fcexchange.com, 84% (68 requests) were made to Corpay.com and 10% (8 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (394 ms) relates to the external source Corpay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 424.6 kB (15%)

Content Size

2.8 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fcexchange.com main page is 2.8 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. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 278.9 kB

  • Original 331.3 kB
  • After minification 331.0 kB
  • After compression 52.4 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 278.9 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 145.5 kB

  • Original 2.3 MB
  • After minification 2.2 MB

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. Fcexchange images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 214 B

  • Original 156.2 kB
  • After minification 156.2 kB
  • After compression 156.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 4.1 kB
  • After minification 4.1 kB
  • After compression 4.1 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. Fcexchange.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

76

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fcexchange. 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 from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fcexchange.com

fcexchange.com

49 ms

www.globalreachgroup.com

www.globalreachgroup.com

62 ms

en-GB

en-GB

266 ms

ed4b6f7280755c33.css

ed4b6f7280755c33.css

48 ms

7ce24792dd4b7e74.css

7ce24792dd4b7e74.css

73 ms

64a987b1775e6608.css

64a987b1775e6608.css

58 ms

6d12a6a5dfa4b8f1.css

6d12a6a5dfa4b8f1.css

57 ms

359d957e7286d365.css

359d957e7286d365.css

59 ms

b537699e48ccbce1.css

b537699e48ccbce1.css

61 ms

a83db493ab746be5.css

a83db493ab746be5.css

63 ms

bf2127ca726d8e47.css

bf2127ca726d8e47.css

61 ms

47f2d431300b1bda.css

47f2d431300b1bda.css

73 ms

123df91f877e601a.css

123df91f877e601a.css

71 ms

8b862162635eb367.css

8b862162635eb367.css

75 ms

3d4e90ba4dd778a1.css

3d4e90ba4dd778a1.css

82 ms

55d791d0d60ae423.css

55d791d0d60ae423.css

76 ms

7f4a3959157fd7f7.css

7f4a3959157fd7f7.css

98 ms

901378a6353a3e28.css

901378a6353a3e28.css

119 ms

8d4abb359d01a0d7.css

8d4abb359d01a0d7.css

90 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

100 ms

otSDKStub.js

otSDKStub.js

60 ms

5282-9829818ae3d1e8b7.js

5282-9829818ae3d1e8b7.js

93 ms

1211.ebd4f74ec421204d.js

1211.ebd4f74ec421204d.js

141 ms

7128.1aafc5a9cc3d8f65.js

7128.1aafc5a9cc3d8f65.js

142 ms

4804.00d3a9a76a10628c.js

4804.00d3a9a76a10628c.js

150 ms

2322.e176ff75a35355e6.js

2322.e176ff75a35355e6.js

145 ms

1608-5048f3551174fb7f.js

1608-5048f3551174fb7f.js

143 ms

5906.f85fc2a2d9aad35f.js

5906.f85fc2a2d9aad35f.js

143 ms

3481.0b36c494cf651370.js

3481.0b36c494cf651370.js

143 ms

7967.0dc2802b7c344d09.js

7967.0dc2802b7c344d09.js

144 ms

5095.80554a99a59b8ca2.js

5095.80554a99a59b8ca2.js

144 ms

9610.4a0889e9bb8e55e8.js

9610.4a0889e9bb8e55e8.js

146 ms

7984.efbc55ceda71a6f5.js

7984.efbc55ceda71a6f5.js

147 ms

6747.a920135ce9e68117.js

6747.a920135ce9e68117.js

147 ms

7778.29822baa66692e11.js

7778.29822baa66692e11.js

155 ms

1078.6e224c278e06e14e.js

1078.6e224c278e06e14e.js

147 ms

7316.a238e9432b1a449e.js

7316.a238e9432b1a449e.js

156 ms

7569.c17238eee52e8b8a.js

7569.c17238eee52e8b8a.js

162 ms

webpack-ba91cac8a2fad628.js

webpack-ba91cac8a2fad628.js

161 ms

framework-4ed89e9640adfb9e.js

framework-4ed89e9640adfb9e.js

145 ms

main-6767437de3f73091.js

main-6767437de3f73091.js

238 ms

_app-f5aed4d36d91e3d1.js

_app-f5aed4d36d91e3d1.js

112 ms

7074-349c9e5039b11925.js

7074-349c9e5039b11925.js

110 ms

index-3195e679d329d12d.js

index-3195e679d329d12d.js

153 ms

_buildManifest.js

_buildManifest.js

154 ms

_ssgManifest.js

_ssgManifest.js

152 ms

_Incapsula_Resource

_Incapsula_Resource

122 ms

image

image

175 ms

image

image

270 ms

image

image

269 ms

image

image

248 ms

image

image

215 ms

image

image

260 ms

image

image

301 ms

image

image

265 ms

image

image

242 ms

81259a04-ee55-401d-93a5-39af1207f517.json

81259a04-ee55-401d-93a5-39af1207f517.json

40 ms

check-ul.svg

check-ul.svg

50 ms

background_image.jpg

background_image.jpg

71 ms

image

image

202 ms

GT-America-Standard-Medium.1bc4959f.woff

GT-America-Standard-Medium.1bc4959f.woff

202 ms

image

image

294 ms

image

image

248 ms

image

image

246 ms

image

image

300 ms

image

image

313 ms

image

image

321 ms

image

image

292 ms

image

image

292 ms

image

image

317 ms

image

image

394 ms

image

image

353 ms

location

location

74 ms

_Incapsula_Resource

_Incapsula_Resource

234 ms

otBannerSdk.js

otBannerSdk.js

89 ms

GT-America-Standard-Regular.ade95456.woff

GT-America-Standard-Regular.ade95456.woff

137 ms

en.json

en.json

33 ms

otFlat.json

otFlat.json

17 ms

otPcCenter.json

otPcCenter.json

19 ms

otCommonStyles.css

otCommonStyles.css

24 ms

Corpay_Final-Logo_No-TM_Two-Tone_Black_(002).png

Corpay_Final-Logo_No-TM_Two-Tone_Black_(002).png

20 ms

Accessibility Review

fcexchange.com accessibility score

91

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.

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

Image elements do not have [alt] attributes

Best Practices

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

Page has valid source maps

SEO Factors

fcexchange.com SEO score

79

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

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

fcexchange.com

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