7.6 sec in total
409 ms
5.4 sec
1.8 sec
Welcome to fooby.ch homepage info - get ready to check FOOBY best content for Switzerland right away, or after learning these important things about fooby.ch
FOOBY is all about the enjoyment of cooking. Coop’s culinary platform is full of great recipe ideas, lots of know-how, and exciting reports.
Visit fooby.chWe analyzed Fooby.ch page load time and found that the first response time was 409 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fooby.ch performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value14.0 s
0/100
25%
Value14.5 s
1/100
10%
Value14,080 ms
0/100
30%
Value0
100/100
15%
Value22.4 s
1/100
10%
409 ms
199 ms
188 ms
28 ms
484 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 44% of them (37 requests) were addressed to the original Fooby.ch, 23% (19 requests) were made to Recipecontent.fooby.ch and 5% (4 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Recipecontent.fooby.ch.
Page size can be reduced by 1.5 MB (42%)
3.5 MB
2.0 MB
In fact, the total size of Fooby.ch main page is 3.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. 60% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 314.2 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 43.1 kB, which is 12% 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 314.2 kB or 86% of the original size.
Potential reduce by 20.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. FOOBY images are well optimized though.
Potential reduce by 863.2 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 863.2 kB or 72% of the original size.
Potential reduce by 268.8 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. Fooby.ch needs all CSS files to be minified and compressed as it can save up to 268.8 kB or 85% of the original size.
Number of requests can be reduced by 27 (36%)
75
48
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FOOBY. 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 as a result speed up the page load time.
fooby.ch
409 ms
de.html
199 ms
CSRFT759.js
188 ms
swiper.min.css
28 ms
default.css
484 ms
modernizr-custom.js
291 ms
jquery.js
682 ms
utils.js
209 ms
granite.js
292 ms
jquery.js
290 ms
default.js
1425 ms
smartbanner.css
306 ms
smartbanner.js
678 ms
addthis_widget.js
45 ms
logo-header-desktop.png
298 ms
imageMobile.img.349.medium.jpg
296 ms
imageMobile.img.349.medium.jpg
462 ms
appstore.png
460 ms
googleplay.png
460 ms
imageTablet.img.500.medium.jpg
460 ms
utag.js
452 ms
sprite.png
215 ms
20170602-newsletter-register-new_low.jpg
278 ms
newsletter-success.jpg
468 ms
login.jpg
467 ms
open-sans-v13-latin-regular.woff
240 ms
open-sans-v13-latin-700.woff
240 ms
montserrat-v7-latin-700.woff
239 ms
amatica-sc-v1-latin-700.woff
240 ms
roboto-slab-v6-latin-regular.woff
240 ms
token.json
148 ms
hawaii_frequent_terms.sri
519 ms
userdata
511 ms
13112_179-150_358-300.jpg
1554 ms
webtrends.hm.js
557 ms
wtid.js
828 ms
fbevents.js
236 ms
activityi;src=6901483;type=pageview;cat=pagev0;u3=de-ch;u4=de;u5=FOOBY%3EFOOBY%20-%20de%3E%3E%3E%3E%3E%3E%3E%3E;u8=https%3A%2F%2Ffooby.ch%2Fde.html;ord=6186657128855.586
503 ms
utag.7.js
143 ms
utag.33.js
209 ms
_ate.track.config_resp
583 ms
300lo.json
496 ms
client.de.min.json
169 ms
13114_179-150_358-300.jpg
1454 ms
15048_179-150_358-300.jpg
1454 ms
15049_179-150_358-300.jpg
1454 ms
15050_179-150_358-300.jpg
1441 ms
15051_179-150_358-300.jpg
1442 ms
15052_131-150_262-300.jpg
1586 ms
15087_131-150_262-300.jpg
1584 ms
15107_131-150_262-300.jpg
1585 ms
15108_131-150_262-300.jpg
1584 ms
14632_131-150_262-300.jpg
1584 ms
14236_131-150_262-300.jpg
1584 ms
9640_131-150_262-300.jpg
1702 ms
12120_131-150_262-300.jpg
1782 ms
14551_179-150_358-300.jpg
1768 ms
14558_179-150_358-300.jpg
1782 ms
14561_179-150_358-300.jpg
1782 ms
14562_37-20_555-300.jpg
1782 ms
14563_37-20_555-300.jpg
1901 ms
image-3x2.img.1920.medium.jpg
1447 ms
image-179x127.img.358.medium.jpg
310 ms
image-179x127.img.358.medium.jpg
311 ms
image-179x127.img.358.medium.jpg
311 ms
imageDesktop.img.600.medium.jpg
422 ms
imageDesktop.img.600.medium.jpg
422 ms
imageDesktop.img.600.medium.jpg
684 ms
sh.d663e43787b663d5491cf753.html
359 ms
analytics.js
555 ms
cnt.js
1313 ms
_error
424 ms
utag.v.js
242 ms
1023301687776038
237 ms
de.html
348 ms
880 ms
layers.ccbc92d4047235e1c1a9.js
202 ms
ec.js
620 ms
86 ms
collect
78 ms
doit
137 ms
collect
192 ms
dcs.gif
328 ms
ga-audiences
213 ms
fooby.ch accessibility score
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
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.
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.
fooby.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fooby.ch 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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fooby.ch can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Fooby.ch 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.
fooby.ch
Open Graph data is detected on the main page of FOOBY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: