11.4 sec in total
501 ms
10.8 sec
106 ms
Click here to check amazing DIGI content. Otherwise, check out these important facts you probably never knew about digi.eu
Globale site van Digi Group. Vind product/oplossing informatie, service informatie, support informatie, bedrijfsinformatie en info over tewerkstelling.
Visit digi.euWe analyzed Digi.eu page load time and found that the first response time was 501 ms and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
digi.eu performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value3.2 s
73/100
25%
Value10.4 s
8/100
10%
Value710 ms
41/100
30%
Value1.506
0/100
15%
Value13.6 s
11/100
10%
501 ms
708 ms
650 ms
609 ms
813 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Digi.eu, 5% (6 requests) were made to Google.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Digisystem.com.
Page size can be reduced by 190.2 kB (7%)
2.7 MB
2.5 MB
In fact, the total size of Digi.eu main page is 2.7 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. 45% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 46.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 46.9 kB or 84% of the original size.
Potential reduce by 102.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. DIGI images are well optimized though.
Potential reduce by 32.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 32.1 kB or 31% of the original size.
Potential reduce by 9.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. Digi.eu needs all CSS files to be minified and compressed as it can save up to 9.1 kB or 83% of the original size.
Number of requests can be reduced by 28 (26%)
107
79
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DIGI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
501 ms
style.css
708 ms
top.css
650 ms
nl.css
609 ms
modal.css
813 ms
jquery-1.10.2.min.js
1250 ms
libs.js
716 ms
jquery.flatheights.js
927 ms
imageloaded.js
724 ms
main.image.slide.js
1116 ms
languageCheck.js
1044 ms
modal.window.js
912 ms
pageTopSW.js
887 ms
analytics.js
26 ms
load.gif
559 ms
header_logo.png
402 ms
ico_header_1.png
592 ms
nav_shadow.png
539 ms
btn_gnav_1.png
707 ms
gnav_sub_bg.png
760 ms
main_message_1.png
521 ms
main_img_1.jpg
1295 ms
main_message_2.png
874 ms
main_img_2.jpg
3385 ms
main_message_3.png
672 ms
main_img_3.jpg
2019 ms
main_message_4.png
1098 ms
main_img_4.jpg
2471 ms
main_message_5.png
1299 ms
main_img_5.jpg
2819 ms
main_message_6.png
1662 ms
main_img_6.jpg
3037 ms
btn_next.png
1987 ms
btn_back.png
2430 ms
nav_btn_current_off.png
2214 ms
tit_1.png
2540 ms
ttl_bussiness_1.png
3014 ms
btn_bussiness_1.jpg
3036 ms
ttl_bussiness_2.png
3135 ms
btn_bussiness_2.jpg
3150 ms
ttl_bussiness_3.png
3598 ms
btn_bussiness_3.jpg
3855 ms
ttl_bussiness_4.png
3344 ms
cse.js
23 ms
btn_bussiness_4.jpg
3283 ms
linkid.js
10 ms
cse.js
80 ms
collect
11 ms
collect
58 ms
ttl_bussiness_5.png
3399 ms
btn_bussiness_5.jpg
3675 ms
tit_5.png
3554 ms
jsapi
39 ms
default+nl.css
5 ms
minimalist.css
20 ms
default+nl.I.js
23 ms
minimalist.css
29 ms
txt_tab_1_on.png
3580 ms
txt_tab_2.png
3543 ms
linerless_WT02.png
3551 ms
jquery.easing.1.3.js
3532 ms
jquery.transit.min.js
3598 ms
jquery-ui-1.10.3.custom.min.js
4486 ms
jquery.cookie.js
3656 ms
borderInline.js
3711 ms
tab_nav.js
3598 ms
global_nav.js
3708 ms
languageChoice.js
3676 ms
mouseover.js
3677 ms
selfproduce_WT02.png
3490 ms
labelmanegemet_WT02.png
3574 ms
packaging_WT02.png
3612 ms
pricemang_WT02.png
3420 ms
productimp_WT02.png
2881 ms
aw5600_WT03.png
3225 ms
sm5500alpha_WT03.png
3205 ms
dps5600_WT03.jpg
2909 ms
lllabel_WT03.jpg
2814 ms
esl_global_WT03.png
3369 ms
aw4600cp_WT03.png
2501 ms
tit_2.png
2587 ms
img_topics_5.png
2998 ms
ico_ar_white_l.png
2626 ms
img_topics_1.png
2932 ms
img_topics_2.png
2892 ms
tit_3.png
2743 ms
bnr_mailmagazine_green.png
2829 ms
tit_6.png
3010 ms
img_order_b.jpg
3068 ms
img_cali_b.jpg
2645 ms
ico_ar_green_l.png
2878 ms
img_group_1.png
3138 ms
purl.js
1664 ms
sha512.js
1643 ms
async-ads.js
46 ms
small-logo.png
40 ms
ico_ar_white.png
388 ms
ico_ar_white_2.png
479 ms
bg_arrow_7.png
478 ms
bg_header_1.png
377 ms
img_load_off.gif
498 ms
nav_btn_current_on.png
509 ms
ico_header_2.png
727 ms
gnav_1.png
930 ms
bg_contentmenu_1.png
874 ms
bg_keytopics_2.png
878 ms
bg_keytopics_3.png
876 ms
ico_gototp_1.png
915 ms
bg_footer_1.png
1058 ms
ico_footernav_1.png
1219 ms
ico_footerserch_1.png
1406 ms
digi.eu accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
digi.eu 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
digi.eu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digi.eu can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Digi.eu 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.
digi.eu
Open Graph description is not detected on the main page of DIGI. 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: