5 sec in total
365 ms
4.3 sec
341 ms
Welcome to foodist.de homepage info - get ready to check FOODIST best content for Germany right away, or after learning these important things about foodist.de
Foodist versendet hochwertige Lebensmittel im Abo. Das Angebot umfasst zahlreiche internationale Spezialitäten aus dem Feinkostbereich.
Visit foodist.deWe analyzed Foodist.de page load time and found that the first response time was 365 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
foodist.de performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value4.5 s
38/100
25%
Value8.7 s
16/100
10%
Value2,540 ms
4/100
30%
Value0.097
90/100
15%
Value15.1 s
7/100
10%
365 ms
1662 ms
204 ms
303 ms
64 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 43% of them (34 requests) were addressed to the original Foodist.de, 9% (7 requests) were made to Use.typekit.net and 8% (6 requests) were made to Cdn.foodist.de. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Foodist.de.
Page size can be reduced by 968.2 kB (49%)
2.0 MB
1.0 MB
In fact, the total size of Foodist.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. Javascripts take 769.2 kB which makes up the majority of the site volume.
Potential reduce by 29.7 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 29.7 kB or 72% of the original size.
Potential reduce by 15.8 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. FOODIST images are well optimized though.
Potential reduce by 490.8 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 490.8 kB or 64% of the original size.
Potential reduce by 431.9 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. Foodist.de needs all CSS files to be minified and compressed as it can save up to 431.9 kB or 83% of the original size.
Number of requests can be reduced by 46 (68%)
68
22
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FOODIST. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
foodist.de
365 ms
foodist.de
1662 ms
bootstrap.css
204 ms
flexslider.css
303 ms
css
64 ms
foodist.css
407 ms
trusted_shops.css
303 ms
paypal.css
298 ms
respond.min.js
303 ms
jquery-1.11.3.min.js
399 ms
webtrekk_v4.min.js
513 ms
customerTypeSwitch.js
397 ms
gtag_events.js
399 ms
bootstrap.min.js
444 ms
jquery-ui-1.10.3.custom.min.js
510 ms
jquery-migrate-1.2.1.min.js
36 ms
shopware-responsive.min.js
507 ms
krh7key.js
141 ms
jquery.trustedShops.js
506 ms
analytics.js
199 ms
201602_slider_startseite.jpg
770 ms
background.jpg
199 ms
dashed-line.png
198 ms
logo_shop-2x.png
248 ms
navi_foodistbox.png
248 ms
navi_healthybox_black.png
248 ms
navi_gourmetshop.png
247 ms
navi_geschenkideenpng.png
247 ms
icon_facebook.png
247 ms
icon_mail.png
401 ms
delipresselogo.png
397 ms
logopetra_kl.png
399 ms
freundin.png
399 ms
element_presse.png
395 ms
logo_companisto.png
397 ms
201602HB_slider.jpg
773 ms
201403_maerzbox_relaunch_4.jpg
878 ms
neue_produkte_kachel2.jpg
296 ms
201602_bundles_kacheln_startseite.jpg
771 ms
201601_kachel_stories.jpg
767 ms
gtm.js
185 ms
sprite-s8ad56c0822.png
649 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
181 ms
RJx13K4nQoQ
239 ms
trennlinie_strokes_365x6.png
520 ms
trennlinie_strokes_365x8.png
520 ms
Blokletters-Balpen.woff
578 ms
foodist.de
193 ms
p.gif
310 ms
collect
27 ms
collect
193 ms
conversion_async.js
162 ms
watch.js
581 ms
fbds.js
405 ms
j.php
155 ms
aquant.js
155 ms
spef.min.js
617 ms
tvib.js
258 ms
www-embed-player-vflQrT_sR.css
146 ms
www-embed-player.js
173 ms
base.js
294 ms
wt
605 ms
XB2A696B19AE67B4749AED540004CF027.js
1537 ms
OmaIed-3hka-3DR-Mg_REgpsXUQw0neILzMQAWv-1LSff5WcggMmeMJ6Mk6f5Mb.woff
109 ms
Pm-ClRfDbN43f_uMFwhduNdpSDJqX2e3KNqEIELYRIMffJrgggMmeMJ6Mk6f5M9.woff
262 ms
2TuPrSSz5cGDrpiPf_ja4Lz0bNpAH2bE_zV2KsBDLgjff4-gggMmeMJ6Mk6f5Mw.woff
346 ms
vsHljiTUx-oVan3kVJ-qIwRshRx4N5E_nnGzZwxe6i9ff4egggMmeMJ6Mk6f5MS.woff
319 ms
8AxGjPYiwG3b8AARs63tOlxObYMBk05TILenCpxn9bJff4pgggMmeMJ6Mk6f5M6.woff
324 ms
v.gif
27 ms
pixel;r=329797054;a=p-HKLJw_eTtX6ue;orderid=;revenue=;labels=_fp.event.Default;fpan=1;fpa=P0-1447412325-1456809542871;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456809542871;tzo=-180;ref=;url=https%3A%2F%2Ffoodist.de%2F;ogl=
151 ms
ga-audiences
150 ms
tvib.php
585 ms
74 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
37 ms
ad_status.js
72 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
31 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
60 ms
62 ms
advert.gif
90 ms
1
91 ms
foodist.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
foodist.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
foodist.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
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 Foodist.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 Foodist.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.
foodist.de
Open Graph description is not detected on the main page of FOODIST. 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: