3.6 sec in total
314 ms
3.1 sec
152 ms
Visit immundefekt.com now to see the best up-to-date Immundefekt content and also check out these interesting facts you probably never knew about immundefekt.com
Visit immundefekt.comWe analyzed Immundefekt.com page load time and found that the first response time was 314 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 60% of websites can load faster.
immundefekt.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value6.9 s
6/100
25%
Value6.8 s
34/100
10%
Value460 ms
61/100
30%
Value0.116
85/100
15%
Value7.5 s
48/100
10%
314 ms
320 ms
95 ms
189 ms
2035 ms
Our browser made a total of 17 requests to load all elements on the main page. We found that 88% of them (15 requests) were addressed to the original Immundefekt.com, 12% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Immundefekt.com.
Page size can be reduced by 25.2 kB (11%)
235.7 kB
210.5 kB
In fact, the total size of Immundefekt.com main page is 235.7 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. 20% of websites need less resources to load. Images take 189.7 kB which makes up the majority of the site volume.
Potential reduce by 5.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 5.0 kB or 65% of the original size.
Potential reduce by 3.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. Immundefekt images are well optimized though.
Potential reduce by 12.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 12.1 kB or 38% of the original size.
Potential reduce by 5.0 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. Immundefekt.com needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 76% of the original size.
We found no issues to fix!
14
14
The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Immundefekt. According to our analytics all requests are already optimized.
immundefekt.com
314 ms
www.immundefekt.com
320 ms
x_kiovig.css
95 ms
SuggestFramework.css
189 ms
SuggestFramework.js
2035 ms
hg_immundefekt.jpg
2042 ms
spc.gif
1943 ms
n_top.gif
98 ms
hg_nav_kiovig.gif
1749 ms
n_navleft_orange.gif
2281 ms
Patienteninfo-Immunglobuline-2012.jpg
469 ms
Patienteninfo-MMN-2012.jpg
657 ms
Patienteninfo-Primaerer-Immundefekt.jpg
751 ms
Baxalta-logo-72px.jpg
845 ms
n_link_orange.gif
95 ms
ga.js
6 ms
__utm.gif
13 ms
immundefekt.com 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
Image elements do not have [alt] attributes
Links do not have a discernible 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.
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
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.
immundefekt.com 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
Page has valid source maps
immundefekt.com 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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Immundefekt.com 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 Immundefekt.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
immundefekt.com
Open Graph description is not detected on the main page of Immundefekt. 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: