4.3 sec in total
594 ms
3.5 sec
118 ms
Welcome to wiki.uni-due.de homepage info - get ready to check Wiki Uni Due best content for Germany right away, or after learning these important things about wiki.uni-due.de
Startseite
Visit wiki.uni-due.deWe analyzed Wiki.uni-due.de page load time and found that the first response time was 594 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
wiki.uni-due.de performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value2.8 s
82/100
25%
Value4.9 s
64/100
10%
Value240 ms
85/100
30%
Value0.026
100/100
15%
Value4.3 s
84/100
10%
594 ms
456 ms
528 ms
545 ms
549 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Wiki.uni-due.de, 95% (35 requests) were made to Uni-due.de. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Uni-due.de.
Page size can be reduced by 526.9 kB (60%)
885.2 kB
358.3 kB
In fact, the total size of Wiki.uni-due.de main page is 885.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. 25% of websites need less resources to load. Javascripts take 445.7 kB which makes up the majority of the site volume.
Potential reduce by 14.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 2.3 kB, which is 12% 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 14.5 kB or 78% of the original size.
Potential reduce by 34.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. Obviously, Wiki Uni Due needs image optimization as it can save up to 34.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 325.6 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 325.6 kB or 73% of the original size.
Potential reduce by 152.3 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. Wiki.uni-due.de needs all CSS files to be minified and compressed as it can save up to 152.3 kB or 89% of the original size.
Number of requests can be reduced by 18 (53%)
34
16
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wiki Uni Due. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
wiki.uni-due.de
594 ms
wiki.uni-due.de
456 ms
style_2013.css
528 ms
legacy.css
545 ms
uni-due.css
549 ms
cookies.js
555 ms
mobilemenu.js
554 ms
modernizr-1.7.min.js
557 ms
jquery-jqueryui.combined.js
1322 ms
jquery.colorbox.js
840 ms
effects.core.js
839 ms
effects.slide.js
841 ms
kalender.js
840 ms
form.js
841 ms
plugins_mobile.js
1133 ms
player.swf
1727 ms
video.combined.js
1357 ms
wolken_2015.jpg
1358 ms
ude-logo.png
571 ms
nav_icon.png
883 ms
touchlayer.png
884 ms
mainnav-icon.gif
1038 ms
en.gif
1084 ms
myude24.png
1176 ms
external.png
1177 ms
facebook24.png
1331 ms
twitter24.png
1383 ms
google24.png
1454 ms
list-icon.gif
1469 ms
zim_logo_jpg.jpg
1471 ms
webmail_blau.png
1622 ms
rss_16x16.gif
1656 ms
mailto.png
1682 ms
controls.png
932 ms
border.png
949 ms
loading_background.png
946 ms
loading.gif
1101 ms
wiki.uni-due.de accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[accesskey] values are not unique
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 IDs are not unique
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
wiki.uni-due.de 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
wiki.uni-due.de 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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wiki.uni-due.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wiki.uni-due.de 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.
wiki.uni-due.de
Open Graph description is not detected on the main page of Wiki Uni Due. 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: