7.3 sec in total
324 ms
6.6 sec
285 ms
Click here to check amazing Whatisforex content for Egypt. Otherwise, check out these important facts you probably never knew about whatisforex.co
Visit whatisforex.coWe analyzed Whatisforex.co page load time and found that the first response time was 324 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
whatisforex.co performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value4.3 s
41/100
25%
Value2.9 s
94/100
10%
Value1,820 ms
9/100
30%
Value0
100/100
15%
Value9.9 s
27/100
10%
324 ms
2030 ms
466 ms
164 ms
205 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 34% of them (51 requests) were addressed to the original Whatisforex.co, 10% (15 requests) were made to Static.xx.fbcdn.net and 9% (13 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source I1.wp.com.
Page size can be reduced by 1.6 MB (67%)
2.4 MB
801.7 kB
In fact, the total size of Whatisforex.co main page is 2.4 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 78.7 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 78.7 kB or 83% of the original size.
Potential reduce by 2.8 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. Whatisforex images are well optimized though.
Potential reduce by 958.3 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 958.3 kB or 73% of the original size.
Potential reduce by 554.6 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. Whatisforex.co needs all CSS files to be minified and compressed as it can save up to 554.6 kB or 84% of the original size.
Number of requests can be reduced by 82 (61%)
135
53
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatisforex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
whatisforex.co
324 ms
www.whatisforex.co
2030 ms
466 ms
styles.css
164 ms
fontsforwebstyle.css
205 ms
jquery-ui-1.8.14.custom.css
203 ms
colorpicker.css
201 ms
settings.css
181 ms
wordpress-svg-icon-plugin-style.min.css
311 ms
css
75 ms
css
87 ms
css
99 ms
css
104 ms
css
106 ms
css
106 ms
td-bootstrap.css
372 ms
style.css
500 ms
jetpack.css
370 ms
jquery.js
583 ms
jquery-migrate.min.js
528 ms
jquery.fcarousel.min.js
527 ms
core.min.js
528 ms
widget.min.js
581 ms
mouse.min.js
678 ms
draggable.min.js
659 ms
slider.min.js
661 ms
colorpicker.js
670 ms
sortable.min.js
707 ms
jquery.fontPlugin.js
796 ms
pluginscripts.js
785 ms
jquery.themepunch.tools.min.js
851 ms
jquery.themepunch.revolution.min.js
873 ms
photon.js
787 ms
jquery.form.min.js
809 ms
scripts.js
912 ms
add-to-cart.min.js
952 ms
jquery.blockUI.min.js
953 ms
woocommerce.min.js
957 ms
jquery.cookie.min.js
1806 ms
cart-fragments.min.js
1804 ms
devicepx-jetpack.js
38 ms
gprofiles.js
183 ms
wpgroho.js
1739 ms
td_external.js
2067 ms
e-201611.js
37 ms
site.js
2051 ms
wp-embed.min.js
1690 ms
js_composer_front.js
1908 ms
waypoints.min.js
1888 ms
postmessage.js
1861 ms
jquery.jetpack-resize.js
1870 ms
jquery.inview.js
1922 ms
queuehandler.js
1845 ms
comment-reply.min.js
1852 ms
wp-emoji-release.min.js
1746 ms
atrk.js
154 ms
analytics.js
158 ms
image.creative.crt_.image_3770_0_0.png
1461 ms
11749360_1449711875354853_540422403_n.jpg
1277 ms
11747217_1444174689241905_56560813_n.gif
1461 ms
5465122218_39392b52db_b.jpg
1123 ms
11.jpg
1572 ms
11651279_1425044461154928_1966276958_n.jpg
1460 ms
11666986_1428441820815192_1600056196_n.jpg
1460 ms
trading_in_metatrader4_en.jpg
1126 ms
11738654_1443493149310059_2020619692_n.gif
1196 ms
9s1I5EzD.jpeg
1321 ms
LYNXNPEB7O0H7_L.jpg
1458 ms
LYNXNPEB7N0PZ_L.jpg
1459 ms
11737020_1442431252749582_1398906130_n.jpg
1671 ms
5053368585_1397e3a5a4_b.jpg
1788 ms
11717234_1439247799734594_711379464_n.jpg
1874 ms
5890431924_e41f158e2d_b.jpg
2192 ms
Exchange-rates-1024x749.jpg
2071 ms
11733401_1439871816338859_1564413486_n.jpg
1895 ms
image.creative.crt_.image_3771_0_0.png
2067 ms
logo-300x100.gif
1452 ms
elements.png
1456 ms
11753822_1444793749179999_1789444739_n-1.jpg
1304 ms
eur_usd_800x533_L_1411988069.jpg
1495 ms
LYNXNPEB7Q0LZ_L.jpg
1038 ms
pips-logo-thumb.png
1167 ms
4148265552_7b438be4ab_b.jpg
1560 ms
about-us-banner.jpg
1559 ms
5709944739_578bc434a7_b.jpg
2324 ms
4670941507_362d27af89_b.jpg
2322 ms
11717106_1440701759589198_785438156_n.jpg
2030 ms
11667193_1430048100654564_1437062380_n.jpg
1752 ms
wtwJ9UuQFa_G0mIQrZmRFaCWcynf_cDxXwCLxiixG1c.ttf
173 ms
F51BEgHuR0tYHxF0bD4vwnYhjbSpvc47ee6xR_80Hnw.ttf
193 ms
dOHPuLxZLrMk445slyoc7PesZW2xOQ-xsNqO47m55DA.ttf
217 ms
JdU2LguLZettxbfEVhxaCQLUuEpTyoUstqEm5AMlJo4.ttf
221 ms
IU2I5IZfkiURW7PugFx42ALUuEpTyoUstqEm5AMlJo4.ttf
217 ms
VdagwMxBFZkgd4HennBoVgLUuEpTyoUstqEm5AMlJo4.ttf
220 ms
atrk.gif
54 ms
collect
17 ms
Zd2E9abXLFGSr9G3YK2MsMpp4g5tvqSBklP-nsXxvLc.ttf
11 ms
b9QBgL0iMZfDSpmcXcE8nHuF9xLuFSdm0i1_s5LqWg0.ttf
22 ms
b9QBgL0iMZfDSpmcXcE8nNrV8IdH2TGAFS-9nMQUrUA.ttf
22 ms
oj6PesrTK2iLtsHDyYi4ROvvDin1pK8aKteLpeZ5c0A.ttf
23 ms
NWdMogIO7U6AtEM4dDdf_SZ2oysoEQEeKwjgmXLRnTc.ttf
46 ms
j-TYDdXcC_eQzhhp386SjSZ2oysoEQEeKwjgmXLRnTc.ttf
34 ms
pqisLQoeO9YTDCNnlQ9bfyZ2oysoEQEeKwjgmXLRnTc.ttf
34 ms
style1-32.png
1019 ms
top-shadow.png
875 ms
sdk.js
425 ms
28 ms
xd_arbiter.php
447 ms
master.html
113 ms
www.whatisforex.co
1296 ms
hovercard.css
63 ms
services.css
96 ms
g.gif
46 ms
page.php
421 ms
jquery.js
13 ms
postmessage.js
2 ms
jed.js
5 ms
underscore.min.js
8 ms
jquery.wpcom-proxy-request.js
2 ms
21 ms
4 ms
likes-rest.js
3 ms
batch
81 ms
2 ms
noticons.css
10 ms
style.css
8 ms
4n08FrZmW0I.css
290 ms
X6vRG7qpshl.css
359 ms
q68gy-v_YMF.js
561 ms
YvxwM8R7ol8.js
628 ms
ihptErjAmMX.js
583 ms
1BQnIVjTFoC.js
640 ms
6PDLJFN-l6_.js
640 ms
cUsKAwzqrQw.js
639 ms
Noticons.svg
5 ms
BaABdRAi2AAAA
1 ms
11109017_487440361415312_3234529853270874983_n.jpg
419 ms
11350709_487442144748467_2267481763247433861_n.jpg
563 ms
10354686_10150004552801856_220367501106153455_n.jpg
622 ms
12112347_549591888528383_5854038389446913931_n.jpg
643 ms
12744418_192430871124654_8288016284062840090_n.jpg
682 ms
10329132_204621363239139_1752902788612762325_n.jpg
645 ms
1384038_562135627168714_1152564797_n.jpg
623 ms
577434_619359794745887_600259744_n.jpg
680 ms
12140813_913863985366562_2875251187812504842_n.jpg
763 ms
wL6VQj7Ab77.png
81 ms
s7jcwEQH7Sx.png
81 ms
6GqoI2ZyIrf.png
83 ms
R9a_DtVRZgv.js
70 ms
cUDgRFxaoIk.js
72 ms
0JBr1QHp8Gi.js
71 ms
kDOzhTr2W91.js
105 ms
whatisforex.co accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
whatisforex.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
whatisforex.co SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatisforex.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 Whatisforex.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.
whatisforex.co
Open Graph description is not detected on the main page of Whatisforex. 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: