2.7 sec in total
458 ms
1.7 sec
567 ms
Visit elfri.be now to see the best up-to-date Elfri content for Belgium and also check out these interesting facts you probably never knew about elfri.be
Advocaat Elfri De Neve. Stationsstraat 29. B 9700 Oudenaarde
Visit elfri.beWe analyzed Elfri.be page load time and found that the first response time was 458 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
elfri.be performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value7.0 s
6/100
25%
Value11.1 s
6/100
10%
Value340 ms
75/100
30%
Value0.159
73/100
15%
Value11.0 s
21/100
10%
458 ms
332 ms
422 ms
9 ms
348 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 67% of them (28 requests) were addressed to the original Elfri.be, 12% (5 requests) were made to Platform.twitter.com and 10% (4 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (818 ms) belongs to the original domain Elfri.be.
Page size can be reduced by 765.0 kB (65%)
1.2 MB
420.8 kB
In fact, the total size of Elfri.be main page is 1.2 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. 40% of websites need less resources to load. Javascripts take 732.1 kB which makes up the majority of the site volume.
Potential reduce by 205.3 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 205.3 kB or 79% of the original size.
Potential reduce by 12.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. Elfri images are well optimized though.
Potential reduce by 498.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 498.2 kB or 68% of the original size.
Potential reduce by 49.0 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. Elfri.be needs all CSS files to be minified and compressed as it can save up to 49.0 kB or 80% of the original size.
Number of requests can be reduced by 24 (59%)
41
17
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elfri. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
elfri.be
458 ms
css_e044d2b6c120e9a99655264f40eebace.css
332 ms
js_550bae7f206cd2648069470db29e56f1.js
422 ms
addthis_widget.js
9 ms
serve.php
348 ms
serve.php
256 ms
iPad-icon.png
57 ms
kantoorlogo.jpg
288 ms
page-bg.png
203 ms
primary-menu-bg.png
203 ms
blue-bullet.png
203 ms
menu-leaf.png
204 ms
primary-menu-active-bg.png
205 ms
menu-collapsed.png
206 ms
preface-wrapper-bg.jpg
580 ms
main-wrapper-bg.png
335 ms
title-blue-line.png
336 ms
sidebar-delimiter.png
337 ms
arrow-bullet.gif
337 ms
text-area-bg.png
337 ms
facebook-64.png
579 ms
myspace-64.png
580 ms
youtube-64.png
581 ms
feed-icon-48x48.png
503 ms
feed.png
502 ms
x-click-butcc-donate.gif
91 ms
layers.3643cb2e25fb91c29386.js
35 ms
widgets.js
33 ms
aSmall.gif
583 ms
aBig.gif
584 ms
CEDIRES170.jpg
818 ms
nl.js
61 ms
postscript-bg.png
600 ms
footer-sidebar-bg.png
601 ms
ga.js
48 ms
300lo.json
58 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
51 ms
sh.7c7179124ea24ac6ba46caac.html
38 ms
__utm.gif
34 ms
follow_button.6a78875565a912489e9aef879c881358.nl.html
13 ms
tweet_button.6a78875565a912489e9aef879c881358.nl.html
21 ms
jot.html
2 ms
elfri.be 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
Form elements do not have associated labels
elfri.be 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
elfri.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
N/A
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elfri.be can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Dutch. Our system also found out that Elfri.be 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.
elfri.be
Open Graph description is not detected on the main page of Elfri. 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: