3.6 sec in total
303 ms
3 sec
235 ms
Click here to check amazing EDIS content. Otherwise, check out these important facts you probably never knew about edis.net
EDIS Hosting offers international High-End website hosting in 40+ countries. Personal support & service, modern infrastructure. click for more!
Visit edis.netWe analyzed Edis.net page load time and found that the first response time was 303 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
edis.net performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value7.1 s
6/100
25%
Value4.2 s
77/100
10%
Value630 ms
48/100
30%
Value0.001
100/100
15%
Value9.0 s
34/100
10%
303 ms
102 ms
202 ms
205 ms
207 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Edis.net, 7% (8 requests) were made to Apis.google.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (892 ms) relates to the external source Edis.at.
Page size can be reduced by 573.3 kB (48%)
1.2 MB
612.6 kB
In fact, the total size of Edis.net 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. 55% of websites need less resources to load. Images take 591.8 kB which makes up the majority of the site volume.
Potential reduce by 60.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 14.8 kB, which is 21% 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 60.5 kB or 84% of the original size.
Potential reduce by 139.1 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. Obviously, EDIS needs image optimization as it can save up to 139.1 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 314.8 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 314.8 kB or 70% of the original size.
Potential reduce by 58.8 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. Edis.net needs all CSS files to be minified and compressed as it can save up to 58.8 kB or 84% of the original size.
Number of requests can be reduced by 49 (43%)
114
65
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EDIS. 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.
home
303 ms
jquery.fancybox.css
102 ms
global.css
202 ms
typography.css
205 ms
blocks.css
207 ms
jquery-1.4.2.min.js
305 ms
jquery-ui-1.8.14.custom.min.js
211 ms
jquery.pngFix.pack.js
211 ms
ccm.base.css
300 ms
jquery.js
500 ms
ccm.base.js
324 ms
jquery.cycle.all.js
324 ms
jquery.fancybox.pack.js
323 ms
jquery.jplayer.min.js
400 ms
jquery.validate.min.js
405 ms
jquery.metadata.js
404 ms
env.js
406 ms
scripts.js
409 ms
jquery.form.js
522 ms
plusone.js
53 ms
bg_headerNav.png
163 ms
logo.png
164 ms
header_print.png
224 ms
topNav_divider.png
163 ms
bg_linkList_item.png
164 ms
icon_googlePlus.png
162 ms
flappe_domain.png
718 ms
icon_flag_de.png
250 ms
icon_flag_aut.png
251 ms
icon_flag_us.png
249 ms
icon_flag_gb.png
249 ms
icon_flag_hk.png
333 ms
icon_flag_south_africa.png
336 ms
icon_flag_nl.png
338 ms
icon_flag_ch.png
337 ms
afterlogic_icon.png
334 ms
f1df76f3ddaf6ea2179cdfe62d14ce31.png
431 ms
ac46f7447441372ae88eb67b07dae0ed.png
826 ms
8192e7444b3eb58f1d65707a600faecd.png
865 ms
ec0984c056d27a3590b971038ea243d1.png
437 ms
ipv6.png
434 ms
no-backup.png
534 ms
tuntap_y.png
536 ms
vpn_y.png
538 ms
4e6d50a2a996fc4da6c1e584549932fb.png
640 ms
intel_xeon.png
640 ms
1tb_hdd.png
642 ms
16gb_ram.png
736 ms
hw_raid.png
738 ms
cb=gapi.loaded_0
16 ms
icon_facebook.png
710 ms
icon_twitter.png
781 ms
icon_flag_en.png
808 ms
button_search.png
810 ms
bg_mainNav.png
814 ms
icons_mainNav_domain.png
883 ms
icons_mainNav_hosting.png
892 ms
atrk.js
106 ms
analytics.js
66 ms
cb=gapi.loaded_1
42 ms
fastbutton
90 ms
icons_mainNav_server.png
793 ms
icons_mainNav_hdstreaming.png
796 ms
icons_mainNav_textMessage.png
798 ms
bg_mainNav_green_leftEdge.png
810 ms
bg_mainNav_green_center.png
866 ms
collect
20 ms
like.php
180 ms
postmessageRelay
84 ms
atrk.gif
101 ms
icons_mainNav_shop.png
816 ms
cb=gapi.loaded_0
33 ms
cb=gapi.loaded_1
31 ms
bg_mainNav_green_rightEdge.png
810 ms
bg_sideNav.png
812 ms
listImage_productOverview.png
815 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
64 ms
icon_sideNav_hotline.png
822 ms
test.png
295 ms
3193398744-postmessagerelay.js
38 ms
rpc:shindig_random.js
42 ms
cb=gapi.loaded_0
8 ms
icon_sideNav_newsletter.png
796 ms
icon_sideNav_webmail.png
804 ms
icon_sideNav_adminLogin.png
827 ms
arrow_slider_prev.png
825 ms
arrow_slider_next.png
826 ms
TY3MhkXpWJ-.js
301 ms
LVx-xkvaJ0b.png
334 ms
bg_teaserArea.png
746 ms
bg_fullWidthBlock_top.png
795 ms
bg_fullWidthBlock_center.png
803 ms
bg_sideColBlock_gradient.png
731 ms
bg_input_submit.png
728 ms
button_rightEdge.png
729 ms
bg_fullWidthBlock_bottom.png
637 ms
bg_priceTag_small.png
691 ms
button_leftEdge_green.png
699 ms
button_center_green.png
657 ms
button_rightEdge_green.png
634 ms
bg_sideColBlock_top.png
631 ms
bg_sideColBlock_center.png
637 ms
button_leftEdge.png
626 ms
button_center.png
622 ms
bg_sideColBlock_bottom.png
631 ms
bg_metaNav.png
629 ms
bg_metaNav_footer_item.png
628 ms
arrow_sitemap.png
622 ms
button_leftEdge_big_green.png
626 ms
button_center_big_green.png
622 ms
button_rightEdge_big_green.png
631 ms
bg_priceTag_big.png
629 ms
icon_sliderPager.png
628 ms
selectCustom_bg.png
622 ms
selectCustom_MoreButton.png
626 ms
print.css
101 ms
edis.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
Buttons do not have an accessible name
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
edis.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
edis.net SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edis.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 Edis.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.
edis.net
Open Graph description is not detected on the main page of EDIS. 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: