1.5 sec in total
304 ms
1.1 sec
114 ms
Click here to check amazing EAF content. Otherwise, check out these important facts you probably never knew about eaf.net
Welcome to the new EAF site, the former site of and present repository for Evangelical Anabaptist Fellowship which disbanded in late 2001.
Visit eaf.netWe analyzed Eaf.net page load time and found that the first response time was 304 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
eaf.net performance score
name
value
score
weighting
Value1.5 s
95/100
10%
Value2.5 s
90/100
25%
Value1.9 s
100/100
10%
Value10 ms
100/100
30%
Value0.056
98/100
15%
Value2.0 s
99/100
10%
304 ms
671 ms
28 ms
87 ms
147 ms
Our browser made a total of 8 requests to load all elements on the main page. We found that 75% of them (6 requests) were addressed to the original Eaf.net, 25% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (671 ms) belongs to the original domain Eaf.net.
Page size can be reduced by 2.9 kB (13%)
22.1 kB
19.2 kB
In fact, the total size of Eaf.net main page is 22.1 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. Only 5% of websites need less resources to load. Javascripts take 17.2 kB which makes up the majority of the site volume.
Potential reduce by 2.9 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 2.9 kB or 59% of the original size.
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.
We found no issues to fix!
6
6
The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EAF. According to our analytics all requests are already optimized.
eaf.net
304 ms
www.eaf.net
671 ms
ga.js
28 ms
eaf_bg.gif
87 ms
eaf-logo.gif
147 ms
a-call.gif
147 ms
2dpoint.gif
146 ms
__utm.gif
11 ms
eaf.net accessibility score
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eaf.net 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
eaf.net 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
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 Eaf.net 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 Eaf.net 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.
eaf.net
Open Graph description is not detected on the main page of EAF. 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: