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 an excellent result, as only a small number 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.
{{url}}
{{time}} 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.
{{og_description}}
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: