6.6 sec in total
980 ms
5.4 sec
226 ms
Click here to check amazing Ifaf content. Otherwise, check out these important facts you probably never knew about ifaf.info
Visit ifaf.infoWe analyzed Ifaf.info page load time and found that the first response time was 980 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ifaf.info performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value4.4 s
40/100
25%
Value5.6 s
52/100
10%
Value710 ms
42/100
30%
Value0.006
100/100
15%
Value8.3 s
40/100
10%
980 ms
303 ms
215 ms
196 ms
226 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 33% of them (34 requests) were addressed to the original Ifaf.info, 30% (31 requests) were made to Bradforderie.com and 8% (8 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Bradforderie.com.
Page size can be reduced by 888.2 kB (32%)
2.8 MB
1.9 MB
In fact, the total size of Ifaf.info 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. 65% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 61.5 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 61.5 kB or 84% of the original size.
Potential reduce by 109.5 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. Ifaf images are well optimized though.
Potential reduce by 418.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 418.1 kB or 73% of the original size.
Potential reduce by 299.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. Ifaf.info needs all CSS files to be minified and compressed as it can save up to 299.1 kB or 85% of the original size.
Number of requests can be reduced by 51 (53%)
97
46
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ifaf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.ifaf.info
980 ms
wp-emoji-release.min.js
303 ms
style.css
215 ms
front.css
196 ms
styles.css
226 ms
style.css
217 ms
color-picker.min.css
317 ms
preset1.css
323 ms
css
23 ms
css
35 ms
flexslider.css
339 ms
quick-style.php
756 ms
socialcount.css
398 ms
jquery.js
630 ms
jquery-migrate.min.js
444 ms
buttons.js
6 ms
bootstrap.min.css
454 ms
font-awesome.min.css
235 ms
animate.min.css
375 ms
main.css
421 ms
woocommerce.css
442 ms
core.min.js
360 ms
widget.min.js
389 ms
tabs.min.js
401 ms
jquery.posttabs.js
476 ms
jquery.form.min.js
476 ms
scripts.js
476 ms
bootstrap.min.js
509 ms
jquery.flexslider-min.js
515 ms
jquery.fitvids.js
541 ms
main.js
541 ms
socialcount.min.js
558 ms
wp-embed.min.js
580 ms
How-Far-Would-You-Go-1.jpg
1772 ms
IFAF_Logo_2.png
327 ms
Screenshot-2015-10-18-09.27.46.png
427 ms
IFAF-IOC.jpg
328 ms
ffec15-001-1200x473.jpg
2273 ms
IFAF-WEC-2015-ALL-STAR-TEAM.jpg
1986 ms
INTERNATIONAL-FEDERATION-OF-AMERICAN-FOOTBALL-2015-CONGRESS.jpg
1066 ms
1546-388x230-296x164.jpg
823 ms
bild8353-296x164.jpg
845 ms
swc_competition-296x164.jpg
1294 ms
271191_10150226816218133_133079_n-1-296x164.jpg
1091 ms
bild0498-296x164.jpg
1302 ms
AUT_vs_GER_Kratky_015-1024.jpg
2538 ms
USA_CAN_Kratky_003-296x164.jpg
1778 ms
1546-388x230-388x222.jpg
1542 ms
bild8353.jpg
2010 ms
INTERNATIONAL-FEDERATION-OF-AMERICAN-FOOTBALL-2015-CONGRESS-296x164.jpg
2002 ms
Screenshot-2015-10-18-10.20.10-64x64.png
2026 ms
ffec15-001-1200x473-64x64.jpg
2228 ms
How-Far-Would-You-Go-1-64x64.jpg
2245 ms
271191_10150226816218133_133079_n-1-64x64.jpg
2241 ms
Screenshot-2015-10-18-10.45.36-64x64.png
2269 ms
IFAF-WEC-2015-ALL-STAR-TEAM-64x64.jpg
2468 ms
bild0498-64x64.jpg
2472 ms
USA_CAN_Kratky_003-64x64.jpg
2484 ms
Screenshot-2015-10-18-11.19.09-64x64.png
2512 ms
1281-388x230-64x64.jpg
2522 ms
swc_competition-64x64.jpg
2698 ms
Screenshot-2015-10-18-10.20.10-280x155.png
2707 ms
Screenshot-2015-10-18-10.45.36-280x155.png
2954 ms
Screenshot-2015-10-18-11.19.09-280x155.png
3222 ms
271191_10150226816218133_133079_n-1-280x155.jpg
2765 ms
bild0498-280x155.jpg
2775 ms
USA_CAN_Kratky_003-280x155.jpg
2930 ms
all.js
10 ms
7XUFZ5tgS-tD6QamInJTcU3KvHLhcNjEHFQzwNtdMQY.ttf
8 ms
anMUvcNT0H1YN4FII8wprzsSLeNQG2cy_mKit6iEdYs.ttf
34 ms
fontawesome-webfont.woff
295 ms
255 ms
xd_arbiter.php
33 ms
xd_arbiter.php
247 ms
getAllAppDefault.esi
93 ms
getSegment.php
10 ms
checkOAuth.esi
6 ms
t.dhj
9 ms
t.dhj
15 ms
like_box.php
161 ms
cm
8 ms
x35248
114 ms
s-3271.xgi
6 ms
hbpix
59 ms
xrefid.xgi
9 ms
9 ms
15 ms
pixel
23 ms
pixel
25 ms
2981
34 ms
kyEKgjk51ZE.css
45 ms
xgj7bXhJNEH.css
39 ms
q68gy-v_YMF.js
45 ms
FJmpeSpHpjS.js
42 ms
0wM5s1Khldu.js
35 ms
1bNoFZUdlYZ.js
35 ms
I6-MnjEovm5.js
3 ms
pQrUxxo5oQp.js
6 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
21 ms
buttons.ab966a004186897711de4a5ed256c924.css
14 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
3 ms
st.1188278743c14064d5e8ae56c8ada29c.js
5 ms
ifaf.info accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
ifaf.info 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
Browser errors were logged to the console
ifaf.info SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifaf.info 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 Ifaf.info 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.
ifaf.info
Open Graph description is not detected on the main page of Ifaf. 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: