3.4 sec in total
191 ms
2.9 sec
344 ms
Visit foodwatch.de now to see the best up-to-date Foodwatch content for Germany and also check out these interesting facts you probably never knew about foodwatch.de
foodwatch entlarvt die verbraucherfeindlichen Praktiken der Lebensmittelindustrie und kämpft für das Recht auf gute, gesunde und ehrliche Lebensmittel.
Visit foodwatch.deWe analyzed Foodwatch.de page load time and found that the first response time was 191 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
foodwatch.de performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value6.5 s
9/100
25%
Value5.5 s
54/100
10%
Value550 ms
53/100
30%
Value0.681
8/100
15%
Value5.9 s
66/100
10%
191 ms
446 ms
62 ms
160 ms
165 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Foodwatch.de, 92% (89 requests) were made to Foodwatch.org and 2% (2 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (971 ms) relates to the external source Foodwatch.org.
Page size can be reduced by 512.9 kB (26%)
2.0 MB
1.5 MB
In fact, the total size of Foodwatch.de main page is 2.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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 65.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. 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 65.5 kB or 80% of the original size.
Potential reduce by 52.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. Foodwatch images are well optimized though.
Potential reduce by 211.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 211.1 kB or 66% of the original size.
Potential reduce by 184.2 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. Foodwatch.de needs all CSS files to be minified and compressed as it can save up to 184.2 kB or 85% of the original size.
Number of requests can be reduced by 40 (43%)
93
53
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foodwatch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
foodwatch.de
191 ms
446 ms
psx2bzw.js
62 ms
stylesheet_112b77af6c.css
160 ms
jquery-ui-1.8.16.custom.css
165 ms
poll_additional.css
169 ms
tipafriend_plus.css
169 ms
jquery-1.7.x-1.8.x-1.2.x.js
343 ms
colorbox.css
172 ms
socialshareprivacy.css
237 ms
cloud-carousel.1.0.5.js
242 ms
jquery.tools.min.js
243 ms
ZeroClipboard.js
244 ms
doubletaptogo.js
256 ms
jquery.charCount.js
316 ms
json2.js
320 ms
slick.min.js
323 ms
artnology.js
323 ms
slider.js
384 ms
mobile-navigation.js
394 ms
theme-navigation.js
398 ms
jquery.colorbox-min.js
401 ms
layout_homepage_template.css
401 ms
localstorage.js
424 ms
localStorageChecker.js
423 ms
splashBox.js
475 ms
jquery.socialshareprivacy.js
474 ms
jquery.equalHeights.js
476 ms
d
165 ms
base.css
84 ms
basemod.css
90 ms
content.css
173 ms
buttons.css
85 ms
mobile-navigation.css
87 ms
slick.css
88 ms
slick-theme.css
163 ms
print.css
163 ms
bg_body_std.png
301 ms
hand.png
308 ms
sprites.png
316 ms
bg_topnav_search.png
301 ms
x.gif
303 ms
gb.gif
304 ms
bg_pipes.png
309 ms
fr.gif
309 ms
nl.gif
311 ms
logo_foodwatch.png
312 ms
csm_Gerstemeier_NEU_127806_150x150_57db391ba2.jpg
316 ms
glyphosat-foodwatch-widget_115x78.jpg
317 ms
becel-tansp94.png
373 ms
banner_bode_zitat_20141030.png
572 ms
Fokusbox1.jpg
488 ms
bg_focusbox.png
319 ms
sprites_ahrefs.png
321 ms
Mineraloel_in_Lebensmitteln530x230_Focusbox.jpg
735 ms
lmbk_kamp_bild_fokus_box_530x290_01.jpg
725 ms
Bode_Die-Freihandelsluege_TTIP_Fokusbox1_01.jpg
610 ms
E-Mail-Aktion_Tierhaltung_Fokusbox_mit-Pfeil_01.jpg
482 ms
wolfgang_fierek_200x200.jpg
565 ms
sybille_kambeck_155.jpg
569 ms
reinhard_schmalz_155.jpg
645 ms
stephan_schill_155.jpg
648 ms
aenne_hochmuth_155.jpg
732 ms
gabriele_hutt_155.jpg
696 ms
Schlegl_Tobias_200x200.jpg
728 ms
hans-werner_meyer_155.jpg
728 ms
joachim_koeper_155.jpg
781 ms
markus_hopfenspirger_155.jpg
810 ms
susanne_kistner_155.jpg
806 ms
nurhan_soykan_155.jpg
808 ms
e_mail_action-350x250_mit_copyright.png
971 ms
csm_eusa150-150part2_14_110e616cc4.jpg
811 ms
csm_europa-flagge-Fotolia_14141411_Alterfalter_150x150_df35cf1982.jpg
850 ms
65sYhlM3P+amO8hnQpQAAAA
6 ms
65sYhlM3P+amO8hnQpQAAAA
6 ms
ga.js
225 ms
localstorage-secure-helper.html
345 ms
counters.json
592 ms
csm_Aldi_sued_150x150_01_a91b0fadc0.jpg
598 ms
csm_vincent_klink_200x200_110b56f44d.jpg
598 ms
csm_dagmar_thiemann_155_e7db5e7fe5.jpg
595 ms
csm_stephan_schill_155_84ab28d574.jpg
653 ms
csm_anna_maszl_kantner_155_e0692ba2c6.jpg
664 ms
csm_susanne_kistner_155_4b9caeba7e.jpg
666 ms
csm_alexis__von_negri_155_67dc7358e1.jpg
667 ms
csm_talley_hoban_155_1af146820d.jpg
673 ms
csm_patricia__bauer_155_49d546a4d5.jpg
730 ms
csm_kinderernaehrung_220x90_a498719859.jpg
815 ms
csm_Tierhaltung-foodwatch_Fotolia_martina-berg_275544_220x90_1f28b68f1a.jpg
736 ms
p.gif
121 ms
__utm.gif
12 ms
RTEmagicC_a21c6fc06f.jpg.jpg
686 ms
Bode_Freihandelsluege_70px.jpg
683 ms
csm_TTIP-durchgestrichen_300x200_9dfb41950b.jpg
588 ms
loading_ddd_white_bg.gif
644 ms
gesichtZeigen.gif
569 ms
overlay.png
567 ms
foodwatch.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.
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
foodwatch.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
foodwatch.de 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 Foodwatch.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 Foodwatch.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.
foodwatch.de
Open Graph description is not detected on the main page of Foodwatch. 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: