3.9 sec in total
237 ms
3.5 sec
178 ms
Welcome to afex.com homepage info - get ready to check Afex best content for Canada right away, or after learning these important things about afex.com
Simplify the way you connect with the global marketplace. Our world-class trading platform and integrated payment solutions can be customized to your unique business requirements.
Visit afex.comWe analyzed Afex.com page load time and found that the first response time was 237 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
afex.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value3.6 s
62/100
25%
Value6.8 s
35/100
10%
Value2,230 ms
6/100
30%
Value0.019
100/100
15%
Value16.6 s
5/100
10%
237 ms
515 ms
582 ms
452 ms
601 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 88% of them (64 requests) were addressed to the original Afex.com, 3% (2 requests) were made to Googleads.g.doubleclick.net and 3% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (901 ms) belongs to the original domain Afex.com.
Page size can be reduced by 1.2 MB (60%)
2.0 MB
805.7 kB
In fact, the total size of Afex.com main page is 2.0 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. 45% of websites need less resources to load. Javascripts take 960.7 kB which makes up the majority of the site volume.
Potential reduce by 223.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 223.6 kB or 93% of the original size.
Potential reduce by 68.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. Obviously, Afex needs image optimization as it can save up to 68.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 753.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 753.2 kB or 78% of the original size.
Potential reduce by 141.8 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. Afex.com needs all CSS files to be minified and compressed as it can save up to 141.8 kB or 86% of the original size.
Number of requests can be reduced by 23 (38%)
60
37
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Afex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
afex.com
237 ms
www.afex.com
515 ms
582 ms
jquery-ui.css
452 ms
jquery-1.10.2-min.js
601 ms
jqueryui-1.10.3.js
901 ms
normalise.css
307 ms
stylesheet.css
231 ms
style.css
380 ms
layout_style.css
529 ms
slider.css
439 ms
cookiemonster.js
454 ms
settings.css
515 ms
jquery.themepunch.plugins.min.js
673 ms
jquery.themepunch.revolution.js
825 ms
waypoints.min.js
589 ms
waypoints-sticky.js
619 ms
jquery.mmenu.css
664 ms
jquery.mmenu.js
673 ms
sign_up.js
675 ms
conversion.js
38 ms
news_brief.css
738 ms
news_brief.js
746 ms
frs-app-95763.js
385 ms
60 ms
dc.js
105 ms
gtm.js
353 ms
menu-icon-large.png
88 ms
afex-direct-button.png
123 ms
global.png
122 ms
logo.png
123 ms
king_1.png
122 ms
rook_1.png
122 ms
knight_1.png
325 ms
bulb_1.png
329 ms
wrench_1.png
327 ms
phone_1.png
328 ms
afex_1.png
328 ms
transparent.png
328 ms
ufonts.com_berthold_akzidenz_grotesk_be_regular_1_-webfont.woff
330 ms
AFEX_Currency_Risk_outlook_2015.jpg
405 ms
rm.jpg
340 ms
playbutton.png
339 ms
ad_background.jpg
339 ms
ad_planes_ur.png
414 ms
ad_planes_ul.png
340 ms
ad_planes_lr.png
411 ms
ad_planes_ll.png
412 ms
risk_management.jpg
564 ms
currency_chart.png
409 ms
social-media2.png
478 ms
social-media4.png
483 ms
social-media3.png
482 ms
social-media5.png
484 ms
dot.png
463 ms
__utm.gif
215 ms
179 ms
ui-bg_flat_75_ffffff_40x100.png
127 ms
video.js
321 ms
video-js.min.css
332 ms
loader.gif
254 ms
timer.png
254 ms
large_left.png
254 ms
large_right.png
311 ms
ui-icons_222222_256x240.png
20 ms
23 ms
ufonts.com_berthold_akzidenz_grotesk_be_regular_1_-webfont.woff
318 ms
ufonts.com_berthold_akzidenz_grotesk_be_regular_1_-webfont.woff
90 ms
ufonts.com_berthold_akzidenz_grotesk_be_regular_1_-webfont.woff
90 ms
ufonts.com_berthold_akzidenz_grotesk_be_regular_1_-webfont.woff
92 ms
ufonts.com_berthold_akzidenz_grotesk_be_regular_1_-webfont.woff
98 ms
ufonts.com_berthold_akzidenz_grotesk_be_regular_1_-webfont.woff
135 ms
ufonts.com_berthold_akzidenz_grotesk_be_regular_1_-webfont.ttf
76 ms
afex.com accessibility score
afex.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
afex.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Afex.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 Afex.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
afex.com
Open Graph description is not detected on the main page of Afex. 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: