2.2 sec in total
374 ms
1.1 sec
752 ms
Visit digilife.be now to see the best up-to-date D I G L F E content for Belgium and also check out these interesting facts you probably never knew about digilife.be
digilife web sites
Visit digilife.beWe analyzed Digilife.be page load time and found that the first response time was 374 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
digilife.be performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.038
100/100
15%
Value0
0/100
10%
374 ms
130 ms
344 ms
288 ms
375 ms
Our browser made a total of 17 requests to load all elements on the main page. We found that 94% of them (16 requests) were addressed to the original Digilife.be, 6% (1 request) were made to Rheologie-rheology.be. The less responsive or slowest element that took the longest time to load (571 ms) belongs to the original domain Digilife.be.
Page size can be reduced by 3.0 kB (6%)
50.2 kB
47.2 kB
In fact, the total size of Digilife.be main page is 50.2 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. Images take 49.4 kB which makes up the majority of the site volume.
Potential reduce by 386 B
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 386 B or 47% of the original size.
Potential reduce by 2.6 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. D I G L F E images are well optimized though.
We found no issues to fix!
15
15
The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of D I G L F E. According to our analytics all requests are already optimized.
digilife.be
374 ms
language.htm
130 ms
welcome.htm
344 ms
banner.pl
288 ms
applogo_50.jpg
375 ms
schoolnet_logo.gif
571 ms
Image3.jpg
157 ms
dutch.gif
204 ms
english.gif
218 ms
Anton%20Paar%20Double%20Arrow.png
325 ms
digilife_foto.jpg
470 ms
digilife_text.gif
196 ms
image3.jpg
320 ms
notepad.gif
239 ms
about.gif
227 ms
language.gif
240 ms
ap2.gif
431 ms
digilife.be 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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
digilife.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
digilife.be SEO score
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digilife.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Digilife.be main page’s claimed encoding is . 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.
digilife.be
Open Graph description is not detected on the main page of D I G L F E. 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: