17.2 sec in total
5.5 sec
11.2 sec
437 ms
Click here to check amazing FXcomparison content for United States. Otherwise, check out these important facts you probably never knew about fxcomparison.com
FXComparison - Stay up to date with forex vote and fxcompared and last brokers news with fxcomparison.com
Visit fxcomparison.comWe analyzed Fxcomparison.com page load time and found that the first response time was 5.5 sec and then it took 11.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fxcomparison.com performance score
5520 ms
279 ms
365 ms
189 ms
286 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 71% of them (63 requests) were addressed to the original Fxcomparison.com, 13% (12 requests) were made to Ad.fxcomparison.com and 4% (4 requests) were made to Jadcapital.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Fxcomparison.com.
Page size can be reduced by 294.3 kB (49%)
600.0 kB
305.7 kB
In fact, the total size of Fxcomparison.com main page is 600.0 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. 35% of websites need less resources to load. Images take 345.3 kB which makes up the majority of the site volume.
Potential reduce by 112.3 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 112.3 kB or 91% of the original size.
Potential reduce by 89.6 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, FXcomparison needs image optimization as it can save up to 89.6 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 66.2 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 66.2 kB or 67% of the original size.
Potential reduce by 26.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. Fxcomparison.com needs all CSS files to be minified and compressed as it can save up to 26.1 kB or 82% of the original size.
Number of requests can be reduced by 54 (62%)
87
33
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FXcomparison. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
www.fxcomparison.com
5520 ms
style.css
279 ms
jquery-1.3.2.min.js
365 ms
jcookie.js
189 ms
jcarousellite.js
286 ms
superfish.js
194 ms
global.js
280 ms
loopedslider.js
280 ms
scrolltopcontrol.js
286 ms
language-selector430c.css
382 ms
flags_usa.png
93 ms
flags_arabia.png
93 ms
flags_italy.png
94 ms
flags_spain.png
95 ms
flags_germany.png
95 ms
flags_japan.png
184 ms
flags_polish.png
184 ms
flags_id.png
187 ms
flags_russia.png
188 ms
flags_france.png
187 ms
flags_ro.png
275 ms
flags_turkey.png
275 ms
flags_china.png
280 ms
flags_greek.png
280 ms
vn.png
281 ms
flags_finland.png
365 ms
ee.gif
365 ms
bg.png
371 ms
hu.png
373 ms
flags_portuguese.png
374 ms
icon-search.gif
455 ms
timthumb.php
570 ms
ajs.php
2251 ms
nav-arrow-down.png
455 ms
small-twitter.gif
456 ms
small-facebook.png
455 ms
small-forum.png
534 ms
small-email.png
547 ms
fxcomparison.gif
548 ms
timthumb.php
818 ms
timthumb.php
805 ms
timthumb.php
808 ms
timthumb.php
253 ms
timthumb.php
273 ms
timthumb.php
463 ms
timthumb.php
310 ms
timthumb.php
432 ms
timthumb.php
308 ms
timthumb.php
215 ms
timthumb.php
233 ms
timthumb.php
122 ms
728x90.gif
261 ms
lg.php
124 ms
menu.gif
95 ms
dot.gif
94 ms
slidernav.png
100 ms
hatch.gif
97 ms
arrow_carousel.png
99 ms
ajs.php
219 ms
jad.gif
97 ms
B6229493.114073180;sz=100x33;ord=[timestamp]
32 ms
gltfx.png
223 ms
277 ms
hymarkets.gif
159 ms
100x33.jpg
250 ms
fxcminf.js
24 ms
netotrade.jpg
165 ms
lg.php
661 ms
468x60.gif
101 ms
rss.png
98 ms
bg-title.jpg
93 ms
ajs.php
132 ms
1920100X33.gif
196 ms
icon-bullet.gif
100 ms
lg.php
135 ms
ajs.php
238 ms
300x250.gif
87 ms
lg.php
131 ms
3-24option-Logo-EN-100x33.jpg
15 ms
lidar.js
26 ms
sbhK2lTE.js
7 ms
ajs.php
130 ms
cTrvNaRi.html
4 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
22 ms
120x600.gif
91 ms
lg.php
123 ms
ajs.php
136 ms
go-up.png
93 ms
lg.php
123 ms
fxcomparison.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fxcomparison.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 Fxcomparison.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.
fxcomparison.com
Open Graph description is not detected on the main page of FXcomparison. 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: