3.7 sec in total
329 ms
2.7 sec
663 ms
Click here to check amazing IITR content for Germany. Otherwise, check out these important facts you probably never knew about iitr.de
Als externer Datenschutzbeauftragter unterstützen wir Unternehmen mit kosteneffizienten Datenschutz-Lösungen sowie mit Rechtsberatung im Datenschutzrecht.
Visit iitr.deWe analyzed Iitr.de page load time and found that the first response time was 329 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
iitr.de performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value5.9 s
14/100
25%
Value4.1 s
79/100
10%
Value0 ms
100/100
30%
Value0.089
92/100
15%
Value2.9 s
96/100
10%
329 ms
708 ms
31 ms
301 ms
417 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 94% of them (67 requests) were addressed to the original Iitr.de, 3% (2 requests) were made to Consent.cookiebot.com and 3% (2 requests) were made to Consentcdn.cookiebot.com. The less responsive or slowest element that took the longest time to load (925 ms) belongs to the original domain Iitr.de.
Page size can be reduced by 230.7 kB (51%)
453.5 kB
222.8 kB
In fact, the total size of Iitr.de main page is 453.5 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. 55% of websites need less resources to load. Javascripts take 222.8 kB which makes up the majority of the site volume.
Potential reduce by 131.6 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 131.6 kB or 79% of the original size.
Potential reduce by 96.0 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 96.0 kB or 43% of the original size.
Potential reduce by 3.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. Iitr.de has all CSS files already compressed.
Number of requests can be reduced by 45 (73%)
62
17
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IITR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
iitr.de
329 ms
www.iitr.de
708 ms
uc.js
31 ms
jquery-3.5.1.min.js
301 ms
bootstrap.min.css
417 ms
fontawesome.all.css
404 ms
template.css
409 ms
tracking.js
356 ms
awesomplete.css
357 ms
calendar.min.css
400 ms
template.min.css
408 ms
content.css
414 ms
jcemediabox.min.css
592 ms
gstyle.css
593 ms
visforms.tooltip.min.css
595 ms
visforms.default.min.css
596 ms
visforms.min.css
599 ms
jquery.min.js
598 ms
jquery-noconflict.min.js
634 ms
core.min.js
635 ms
finder-es5.min.js
636 ms
bootstrap-es5.min.js
706 ms
awesomplete.min.js
636 ms
finder.min.js
637 ms
collapse.min.js
699 ms
menu-es5.min.js
706 ms
popover.min.js
706 ms
date-helper.min.js
710 ms
calendar.min.js
710 ms
alert.min.js
797 ms
button.min.js
805 ms
carousel.min.js
807 ms
dropdown.min.js
808 ms
modal.min.js
808 ms
offcanvas.min.js
807 ms
scrollspy.min.js
902 ms
tab.min.js
906 ms
toast.min.js
903 ms
configuration.js
46 ms
cc.js
100 ms
jcemediabox.min.js
925 ms
results.js
560 ms
dropdown.js
557 ms
bc-v4.min.html
9 ms
popuphighslide-with-html.js
662 ms
jquery.validate.min.js
620 ms
visforms.js
613 ms
bootstrap.min.js
618 ms
template.js
606 ms
iitr-logo.svg
703 ms
datenschutzberatung.webp
698 ms
iitr-datenschutz-kit.svg
525 ms
iitr-externer-dsb.svg
528 ms
iitr-elearning.svg
531 ms
be-solution.gif
533 ms
enmacc-logo-referenz.gif
599 ms
roboto-regular-webfont.woff
600 ms
fa-solid-900.woff
694 ms
fa-regular-400.woff
679 ms
roboto-bold-webfont.woff
604 ms
roboto-medium-webfont.woff
605 ms
fa-brands-400.woff
778 ms
visIcon.woff
628 ms
idnow-logo-referenz.gif
622 ms
NavVis-logo-referenz.gif
651 ms
chatbot-load.gif
910 ms
loading.gif
743 ms
datenschutzberatung-fuer-unternehmen.webp
744 ms
bestellung-externer-datenschutzbeauftragter.webp
656 ms
contactbox-bg.webp
818 ms
jquery.min.js
102 ms
iitr.de 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
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
Image elements do not have [alt] attributes
iitr.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
iitr.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iitr.de 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 Iitr.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.
iitr.de
Open Graph data is detected on the main page of IITR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: