Tools & Wizards About Us
fx.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fx.com

LSEG Data & Analytics | Financial Technology & Data | LSEG

Page Load Speed

5 sec in total

First Response

2.1 sec

Resources Loaded

2.7 sec

Page Rendered

223 ms

fx.com screenshot

About Website

Click here to check amazing Fx content for United Arab Emirates. Otherwise, check out these important facts you probably never knew about fx.com

LSEG Data & Analytics: Partnering with 40,000+ customers and 400,000+ users worldwide to empower financial insights through data and technology.

Visit fx.com

Key Findings

We analyzed Fx.com page load time and found that the first response time was 2.1 sec and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

fx.com performance score

0

Network Requests Diagram

www.fxall.com

2068 ms

jquery-1.4.3.min.js

50 ms

BasePageCss.css

34 ms

SiteOverlay.js

36 ms

BasepageHeader.js

31 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fx.com, 5% (3 requests) were made to T2.trackalyzer.com and 3% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Fxall.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 935.8 kB (75%)

Content Size

1.2 MB

After Optimization

305.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Fx.com main page is 1.2 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. 50% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 68.5 kB

  • Original 100.1 kB
  • After minification 92.9 kB
  • After compression 31.6 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 68.5 kB or 68% of the original size.

JavaScript Optimization

-76%

Potential reduce by 820.7 kB

  • Original 1.1 MB
  • After minification 914.2 kB
  • After compression 265.1 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 820.7 kB or 76% of the original size.

CSS Optimization

-84%

Potential reduce by 46.7 kB

  • Original 55.6 kB
  • After minification 41.3 kB
  • After compression 8.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. Fx.com needs all CSS files to be minified and compressed as it can save up to 46.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (75%)

Requests Now

51

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.fxall.com

www.fxall.com

2068 ms

jquery-1.4.3.min.js

jquery-1.4.3.min.js

50 ms

BasePageCss.css

BasePageCss.css

34 ms

SiteOverlay.js

SiteOverlay.js

36 ms

BasepageHeader.js

BasepageHeader.js

31 ms

flashEmbed.js

flashEmbed.js

33 ms

base2014.css

base2014.css

34 ms

components.css

components.css

65 ms

scripts.js

scripts.js

62 ms

WebResource.axd

WebResource.axd

63 ms

General.js

General.js

69 ms

WebResource.axd

WebResource.axd

62 ms

WebResource.axd

WebResource.axd

70 ms

ScriptResource.axd

ScriptResource.axd

77 ms

ScriptResource.axd

ScriptResource.axd

71 ms

ScriptResource.axd

ScriptResource.axd

72 ms

ScriptResource.axd

ScriptResource.axd

73 ms

ScriptResource.axd

ScriptResource.axd

73 ms

ScriptResource.axd

ScriptResource.axd

74 ms

ScriptResource.axd

ScriptResource.axd

97 ms

ScriptResource.axd

ScriptResource.axd

97 ms

ScriptResource.axd

ScriptResource.axd

99 ms

addthis_widget.js

addthis_widget.js

10 ms

CustomTrackingScript.js

CustomTrackingScript.js

165 ms

BasepageBody_PageEnd.js

BasepageBody_PageEnd.js

164 ms

trackalyze.js

trackalyze.js

265 ms

ga.js

ga.js

118 ms

fxallbodybg.jpg

fxallbodybg.jpg

151 ms

FXall_UpperMessageText.gif

FXall_UpperMessageText.gif

151 ms

trcompany-transparent.png

trcompany-transparent.png

152 ms

topRatesTicker

topRatesTicker

112 ms

iconLock.gif

iconLock.gif

56 ms

thomson-reuters-logo.png

thomson-reuters-logo.png

55 ms

fxall-logo.png

fxall-logo.png

58 ms

dropdownarrow1.gif

dropdownarrow1.gif

57 ms

demotopsmallBg.gif

demotopsmallBg.gif

58 ms

demoBtns.gif

demoBtns.gif

56 ms

demobotsmallBg.gif

demobotsmallBg.gif

59 ms

grayBtn.gif

grayBtn.gif

60 ms

drkgrayBg.gif

drkgrayBg.gif

61 ms

drkgrayRt1.gif

drkgrayRt1.gif

62 ms

drkgraybtnBg.gif

drkgraybtnBg.gif

62 ms

drkbluBg.gif

drkbluBg.gif

62 ms

h4Bg.gif

h4Bg.gif

70 ms

__utm.gif

__utm.gif

28 ms

rateticker-toprates.css

rateticker-toprates.css

22 ms

jquery.min.js

jquery.min.js

23 ms

rateticker.js

rateticker.js

22 ms

knowledge-regular-webfont.woff

knowledge-regular-webfont.woff

103 ms

knowledge-light-webfont.woff

knowledge-light-webfont.woff

31 ms

fxrateListBg.gif

fxrateListBg.gif

15 ms

fxrateHeader.gif

fxrateHeader.gif

15 ms

delta.gif

delta.gif

14 ms

boost

boost

17 ms

300lo.json

300lo.json

13 ms

trackalyze.asp

trackalyze.asp

80 ms

sh.07f0d9bf220d07a763adad1e.html

sh.07f0d9bf220d07a763adad1e.html

27 ms

dot.gif

dot.gif

77 ms

pd.js

pd.js

15 ms

SEO Factors

fx.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fx.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fx.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

fx.com

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