4.7 sec in total
344 ms
4.2 sec
156 ms
Welcome to disy.net homepage info - get ready to check Disy best content for Germany right away, or after learning these important things about disy.net
Disy ist führender Anbieter von Lösungen zur Datenanalyse und zum Berichtswesen für Fachbehörden. Unsere Lösungen vereinen Data Analytics, Reporting und GIS
Visit disy.netWe analyzed Disy.net page load time and found that the first response time was 344 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
disy.net performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value10.5 s
0/100
25%
Value9.1 s
13/100
10%
Value3,130 ms
2/100
30%
Value0.036
100/100
15%
Value10.1 s
26/100
10%
344 ms
930 ms
112 ms
319 ms
216 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 91% of them (48 requests) were addressed to the original Disy.net, 8% (4 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Disy.net.
Page size can be reduced by 690.0 kB (29%)
2.4 MB
1.7 MB
In fact, the total size of Disy.net main page is 2.4 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. 35% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 33.0 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 33.0 kB or 80% of the original size.
Potential reduce by 103.7 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. Disy images are well optimized though.
Potential reduce by 481.5 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 481.5 kB or 75% of the original size.
Potential reduce by 71.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. Disy.net needs all CSS files to be minified and compressed as it can save up to 71.8 kB or 84% of the original size.
Number of requests can be reduced by 22 (44%)
50
28
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Disy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
disy.net
344 ms
home.html
930 ms
jquery.fancybox-1.3.4.css
112 ms
stylesheet_926bc429d8.css
319 ms
richmenu.css
216 ms
mainstyles.css
433 ms
rte.css
218 ms
jquery-1.8.3.js
979 ms
jquery-ui-1.9.2.custom.min.js
795 ms
javascript_53e87dcd5e.js
321 ms
jquery.144.min.js
647 ms
t4y_scrollable.css
423 ms
fade-plugin.js
427 ms
jquery.fancybox-1.3.4_patch.js
633 ms
bib.js
533 ms
ga.js
20 ms
side-button-jobs.png
116 ms
side-button_newsletter.png
113 ms
side-button_techblog.png
109 ms
disy-logo.jpg
113 ms
disy-logo-left.jpg
113 ms
globalMenuBg.png
115 ms
searchbox.png
529 ms
menu_trenner.png
222 ms
menu_background_disy198.png
221 ms
grafikreferenzen.jpg
324 ms
disy_Homepage_ueber_uns_01.jpg
546 ms
disy_Homepage_cadenza02.jpg
836 ms
disy_Homepage_preludio_02.jpg
1082 ms
disy_Homepage_cadenza_mobile_01.jpg
1195 ms
disy_Homepage_dienstleistungen_02.jpg
854 ms
bottom-left.png
635 ms
bottom-center.png
657 ms
bottom-right.png
742 ms
contentBox3-290.png
768 ms
csm_Services_Thumb_441373369f.jpg
851 ms
csm_Thumb_Disy_Akademie_2016_2_2174c06698.jpg
877 ms
csm_2015_Ausgabe6_Doag_73f7a03486.png
945 ms
csm_Thumb_Disy_Services_Broschuere_d3dfdf1d55.gif
956 ms
Disy-News.jpg
962 ms
startseite_karriere_neu.jpg
987 ms
tech-blog_small.png
1054 ms
RTEmagicC_facebook.png.png
1062 ms
RTEmagicC_xing.png.png
1067 ms
googleplus.png
1096 ms
twitter.png
1162 ms
RTEmagicC_youtube3.png.png
1168 ms
inpage_linkid.js
15 ms
navigator.png
1147 ms
__utm.gif
13 ms
__utm.gif
6 ms
collect
66 ms
print.css
113 ms
disy.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
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
disy.net 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
disy.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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Disy.net can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Disy.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.
disy.net
Open Graph description is not detected on the main page of Disy. 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: