27.5 sec in total
1.2 sec
24 sec
2.3 sec
Welcome to foody.es homepage info - get ready to check Foody best content for Spain right away, or after learning these important things about foody.es
Tienda especializada en alimentos Saludables sin gluten, sin frutos secos, sin huevos, sin levadura, sin lácteos, sin soja, sin trigo... Envíos 24h.
Visit foody.esWe analyzed Foody.es page load time and found that the first response time was 1.2 sec and then it took 26.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
foody.es performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value3.8 s
55/100
25%
Value5.2 s
61/100
10%
Value390 ms
69/100
30%
Value0.004
100/100
15%
Value9.5 s
30/100
10%
1216 ms
4802 ms
326 ms
470 ms
465 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 97% of them (128 requests) were addressed to the original Foody.es, 2% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (7.3 sec) belongs to the original domain Foody.es.
Page size can be reduced by 924.9 kB (37%)
2.5 MB
1.6 MB
In fact, the total size of Foody.es main page is 2.5 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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 266.1 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. This page needs HTML code to be minified as it can gain 103.3 kB, which is 36% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 266.1 kB or 93% of the original size.
Potential reduce by 50.4 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. Foody images are well optimized though.
Potential reduce by 378.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 378.0 kB or 68% of the original size.
Potential reduce by 230.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. Foody.es needs all CSS files to be minified and compressed as it can save up to 230.3 kB or 82% of the original size.
Number of requests can be reduced by 55 (42%)
130
75
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foody. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
foody.es
1216 ms
www.foody.es
4802 ms
modal.css
326 ms
k2.css
470 ms
font-awesome.css
465 ms
normalize.css
452 ms
layout.css
613 ms
joomla.css
759 ms
system.css
758 ms
template.css
916 ms
menu.css
1623 ms
gk.stuff.css
1067 ms
vm.css
1197 ms
style9.css
1193 ms
override.css
1336 ms
screen.css
1341 ms
vm-ltr-common.css
1474 ms
vm-ltr-site.css
1615 ms
vm-ltr-reviews.css
1598 ms
style.css
1625 ms
jquery.fancybox-1.3.4.css
1730 ms
styles.css
2015 ms
dmt_social.css
1914 ms
theme3.css
1911 ms
jquery.min.js
2374 ms
jquery-noconflict.js
2051 ms
jquery-migrate.min.js
2074 ms
bootstrap.min.js
2345 ms
mootools-core.js
2851 ms
core.js
2315 ms
mootools-more.js
4210 ms
modal.js
2633 ms
gk.scripts.js
2631 ms
gk.menu.js
4908 ms
powertools-1.2.0.js
2780 ms
slider.js
2955 ms
vmprices.js
5446 ms
jquery-ui.min.js
252 ms
jquery.fancybox-1.3.4.pack.js
2836 ms
jcarousel.js
5219 ms
jquery.mousewheel.js
2845 ms
jquery.touchwipe.1.1.1.js
2977 ms
flexible_update_cart.js
4883 ms
jquery.ui.autocomplete.html.js
3957 ms
jquery.noconflict.js
3997 ms
vmsite.js
5709 ms
ga.js
195 ms
logo.jpg
2331 ms
facebook_32.png
473 ms
twitter_32.png
951 ms
google_talk_32.png
473 ms
banner01.jpg
3600 ms
banner_wilmersburger_700x271.jpg
718 ms
banner_tienda.jpg
2092 ms
banner06.jpg
2360 ms
banner03.jpg
2421 ms
prev.png
1675 ms
next.png
7257 ms
play.png
2969 ms
pause.png
2971 ms
banner01_new.jpg
3253 ms
banner02_new.jpg
3278 ms
banner03_new.jpg
7040 ms
b.jpg
3394 ms
ft.jpg
3600 ms
frt.jpg
3766 ms
g.jpg
3755 ms
h.jpg
3904 ms
la.jpg
3926 ms
le.jpg
4090 ms
lg.jpg
4074 ms
p.jpg
4199 ms
s.jpg
4213 ms
t.jpg
4351 ms
ve.jpg
4343 ms
z.jpg
4466 ms
b6ed79d7264651eee645f89e7020a7bb.jpg
4475 ms
nophoto.jpg
4816 ms
37fd68f0e07ab57841089545407b9e4c.jpg
6281 ms
1e00e6b2a9ad593f1f120da3da628bb9.jpg
4704 ms
bd5abeaaa61c43f125920fe735b6d4fc.jpg
4830 ms
8501b86cf594d4754009229d7d836168.png
5031 ms
0c278527a52c1be843ea9b455b5eb1db.png
5159 ms
__utm.gif
70 ms
__utm.gif
247 ms
b951cbdb631c7d30eef45f3eac850180.png
4781 ms
9f451a5eefc4efed0c92f02311aa142c.png
4977 ms
2a1db60341b5f399cdf3a03d6c7b2b0a.jpg
4595 ms
ac57d38811cf4751526736238b231649.png
4710 ms
4aacc8085c91353b50f2f26fcdfac4ad.png
4250 ms
861bbc9d34ab81a99e93885aced3ed8a.png
3818 ms
9dff191287f8ac919d6db032c39512f1.jpg
3627 ms
74d88b7b67bb7042f50be282eab16313.png
3962 ms
41d056b219948f1c85e6e3fd33677da8.png
3966 ms
22565a4cf0e6be9397bdb3cd94146530.jpg
3350 ms
1.gif
3579 ms
3.gif
3365 ms
4.gif
3341 ms
5.gif
4015 ms
6.gif
3280 ms
7.gif
3265 ms
8.gif
3479 ms
9.gif
3480 ms
10.gif
3405 ms
11.gif
3539 ms
12.gif
3416 ms
13.gif
3414 ms
14.gif
3390 ms
15.gif
3488 ms
18.gif
3325 ms
19.gif
3380 ms
20.gif
3261 ms
21.gif
3364 ms
22.gif
3229 ms
23.gif
3134 ms
bn_tienda.jpg
3719 ms
bn_dieta.jpg
3047 ms
bn_blog.jpg
3101 ms
bn_facebook.jpg
3058 ms
bn_twitter.jpg
2869 ms
bn_google.jpg
2973 ms
bn_garantia.jpg
3039 ms
icon2.png
2655 ms
loader.gif
2673 ms
loading.gif
2805 ms
arrow_down.png
2393 ms
przez.png
2554 ms
button.png
4222 ms
small.desktop.css
111 ms
tablet.css
235 ms
small.tablet.css
232 ms
mobile.css
553 ms
foody.es 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
foody.es 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
Page has valid source maps
foody.es SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foody.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Foody.es 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.
foody.es
Open Graph description is not detected on the main page of Foody. 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: