9.3 sec in total
2.2 sec
6.8 sec
276 ms
Click here to check amazing IPPNW content for Germany. Otherwise, check out these important facts you probably never knew about ippnw.de
IPPNW Deutsche Sektion | Für eine Welt ohne atomare Bedrohung. Für eine Welt in Frieden. Für eine Medizin in sozialer Verantwortung.
Visit ippnw.deWe analyzed Ippnw.de page load time and found that the first response time was 2.2 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize Ippnw.de rating and web reputation
ippnw.de performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value4.4 s
39/100
25%
Value6.0 s
46/100
10%
Value220 ms
87/100
30%
Value0
100/100
15%
Value9.2 s
32/100
10%
2201 ms
506 ms
588 ms
600 ms
589 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 68% of them (62 requests) were addressed to the original Ippnw.de, 20% (18 requests) were made to Pbs.twimg.com and 5% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Ippnw.de.
Page size can be reduced by 408.6 kB (40%)
1.0 MB
604.8 kB
In fact, the total size of Ippnw.de main page is 1.0 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. 45% of websites need less resources to load. Images take 485.4 kB which makes up the majority of the site volume.
Potential reduce by 40.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 40.0 kB or 79% of the original size.
Potential reduce by 34.9 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. IPPNW images are well optimized though.
Potential reduce by 238.3 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 238.3 kB or 66% of the original size.
Potential reduce by 95.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. Ippnw.de needs all CSS files to be minified and compressed as it can save up to 95.3 kB or 81% of the original size.
Number of requests can be reduced by 53 (60%)
89
36
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IPPNW. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
ippnw.de
2201 ms
stylesheet_585d542afd.css
506 ms
Celayout.css
588 ms
Menu.css
600 ms
N4mcelist.css
589 ms
N4mtagcloud.css
570 ms
Twitterbox.css
595 ms
N4mbanner.css
600 ms
Flickr.css
694 ms
shariff.complete.css
722 ms
0_position.css
691 ms
0_navigation.css
699 ms
0_inhalt.css
736 ms
0_rand.css
697 ms
0_footer.css
822 ms
csc.css
791 ms
rte.css
834 ms
n4m_ce.css
798 ms
mailform.css
817 ms
jquery.fancybox.css
840 ms
jquery-1.8.3.min.js
1102 ms
hoverIntent.js
902 ms
superfish.min.js
935 ms
widgets.js
21 ms
jquery.fancybox.pack.js
928 ms
jquery.socialshareprivacy.js
931 ms
zoom.js
959 ms
menuStory.js
1073 ms
jquery.tagcanvas.min.js
1070 ms
javascript_a79086632c.js
1063 ms
jsfunc.validateform.js
1056 ms
shariff.complete.js
1329 ms
logo_ippnw.gif
160 ms
clear.gif
113 ms
print_logo.gif
245 ms
icon-zoom-in.png
183 ms
icon-zoom-out.png
143 ms
icon-print.png
243 ms
icon-mail.png
245 ms
icon-sitemap.png
259 ms
aff58de88c.jpg
426 ms
f10df277d5.jpg
411 ms
b792f5e257.jpg
553 ms
3ee65dbda3.jpg
570 ms
icon_facebook_border_28x28.gif
371 ms
icon_flickr_border_28x28.gif
377 ms
icon_twitter_border_28x28.gif
562 ms
icon_youtube_border_28x28.gif
561 ms
7dda888523.png
604 ms
27fc4a8623.jpg
607 ms
d635cd06b7.jpg
651 ms
6445a6814b.jpg
772 ms
143080e5be.jpg
754 ms
af269c41eb.jpg
752 ms
IPPNW_report_T30F5_133.jpg
841 ms
SZ_Anzeige_160311.jpg
892 ms
icon_home_gray_20x20.gif
732 ms
icon_arrow_white_trans_18x18.png
832 ms
icon_arrow_green_trans_18x18.png
831 ms
button_search.png
868 ms
icon_arrow_white_trans_18x18.png
859 ms
piwik.js
930 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
5 ms
syndication
82 ms
575975140787417088
161 ms
proxy.jpg
15 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
5 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
7 ms
Ippnw_100_normal.jpg
111 ms
DT8yF3tn_normal.jpeg
58 ms
andrewkanter-sm_normal.jpg
58 ms
f7614831cbd4d45ee3426b71f7f62e33_normal.jpeg
111 ms
acG33xcO_normal.jpeg
123 ms
icanlogo_orange150_normal.gif
150 ms
4b5dc0bf52ddee4fe7fcfee4cb816dea_normal.jpeg
92 ms
U5LzzrTU_normal.png
93 ms
gj35zOsn_normal.jpeg
94 ms
0eudnDyT_normal.png
96 ms
angelika_normal.jpg
140 ms
CdhOAQLXEAA-yC3.jpg:small
99 ms
Cc-LEf6W8AAbWia.jpg:small
100 ms
CdCpT4AUUAA57nZ.jpg:small
107 ms
Cc8zaNfWoAAWW9F.jpg:small
144 ms
CcTcUVXW0AA1ii2.jpg:small
107 ms
CcTcUUmW4AAaU3r.jpg:small
108 ms
CcTbWoJWIAALjVt.jpg:small
109 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
49 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
80 ms
proxy.jpg
5 ms
jot.html
2 ms
0_print.css
808 ms
ippnw.de accessibility score
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
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
Form elements do not have associated labels
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.
ippnw.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
ippnw.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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ippnw.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 Ippnw.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.
ippnw.de
Open Graph description is not detected on the main page of IPPNW. 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: