4.8 sec in total
965 ms
3.6 sec
260 ms
Visit efaf.info now to see the best up-to-date EFAF content and also check out these interesting facts you probably never knew about efaf.info
Homepage of the EFAF
Visit efaf.infoWe analyzed Efaf.info page load time and found that the first response time was 965 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
efaf.info performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value1.4 s
100/100
25%
Value1.9 s
100/100
10%
Value10 ms
100/100
30%
Value0.023
100/100
15%
Value2.1 s
99/100
10%
965 ms
209 ms
223 ms
2912 ms
239 ms
Our browser made a total of 29 requests to load all elements on the main page. We found that 55% of them (16 requests) were addressed to the original Efaf.info, 38% (11 requests) were made to Eurobowl.efaf.info and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Eurobowl.efaf.info.
Page size can be reduced by 58.5 kB (6%)
916.3 kB
857.9 kB
In fact, the total size of Efaf.info main page is 916.3 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. 25% of websites need less resources to load. Images take 866.1 kB which makes up the majority of the site volume.
Potential reduce by 15.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. This page needs HTML code to be minified as it can gain 3.9 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 15.5 kB or 80% of the original size.
Potential reduce by 32.0 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. EFAF images are well optimized though.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 10.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. Efaf.info needs all CSS files to be minified and compressed as it can save up to 10.9 kB or 80% of the original size.
Number of requests can be reduced by 6 (21%)
28
22
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EFAF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
efaf.info
965 ms
main.css
209 ms
scheme.css
223 ms
bild0657.jpg
2912 ms
bild0654.jpg
239 ms
bild0655.jpg
256 ms
bild0650.jpg
370 ms
bild0642.jpg
371 ms
bild0619.jpg
274 ms
bild0548.jpg
350 ms
bild0549.jpg
459 ms
arrow-up.jpg
217 ms
bild0401.jpg
253 ms
bild102.gif
308 ms
bg-side.jpg
111 ms
carbon.jpg
117 ms
bg21.jpg
396 ms
nav.gif
216 ms
seperator.gif
191 ms
aside.gif
216 ms
section.gif
247 ms
printer.jpg
285 ms
bg-aside.jpg
296 ms
arrow.gif
289 ms
ul-style01.gif
321 ms
bild1007.gif
164 ms
ga.js
8 ms
__utm.gif
13 ms
print.css
101 ms
efaf.info accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
efaf.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
efaf.info SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Efaf.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 Efaf.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.
efaf.info
Open Graph description is not detected on the main page of EFAF. 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: