7.2 sec in total
387 ms
6 sec
823 ms
Click here to check amazing FOOBY content. Otherwise, check out these important facts you probably never knew about fooby.net
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.netWe analyzed Fooby.net page load time and found that the first response time was 387 ms and then it took 6.8 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.net performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value15.2 s
0/100
25%
Value9.5 s
11/100
10%
Value2,550 ms
4/100
30%
Value0
100/100
15%
Value14.3 s
9/100
10%
387 ms
98 ms
902 ms
115 ms
117 ms
Our browser made a total of 26 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Fooby.net, 50% (13 requests) were made to Fooby.ch and 19% (5 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Fooby.ch.
Page size can be reduced by 429.6 kB (70%)
611.8 kB
182.1 kB
In fact, the total size of Fooby.net main page is 611.8 kB. 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. HTML takes 310.5 kB which makes up the majority of the site volume.
Potential reduce by 275.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. This page needs HTML code to be minified as it can gain 54.7 kB, which is 18% 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 275.5 kB or 89% of the original size.
Potential reduce by 116.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 116.8 kB or 62% of the original size.
Potential reduce by 37.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. Fooby.net needs all CSS files to be minified and compressed as it can save up to 37.3 kB or 33% of the original size.
Number of requests can be reduced by 11 (61%)
18
7
The browser has sent 18 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 12 to 1 for JavaScripts and as a result speed up the page load time.
fooby.net
387 ms
en.html
98 ms
en.html
902 ms
utag.sync.js
115 ms
js
117 ms
critical-67bfbde4a1.css
687 ms
modernizr-custom.js
645 ms
analytics.js
154 ms
vendors-sync-7ccc00bd2d7083dc1035.js
976 ms
templates-0c76f28b25f6060b95a9.js
234 ms
main-4b227af6912fdd0cb9fe.js
1033 ms
js
153 ms
logo-header-desktop.svg
673 ms
utag.js
598 ms
app-5bb7211ca4.css
268 ms
collect
521 ms
open-sans-v13-latin-regular-ce65961588.woff
457 ms
open-sans-v13-latin-700-72862e7cf1.woff
456 ms
amatica-sc-v1-latin-700-9912f6c100.woff
454 ms
roboto-slab-v6-latin-regular-fc6efd0243.woff
488 ms
montserrat-v7-latin-700-916a3d6c6a.woff
486 ms
collect
920 ms
utag.244.js
302 ms
utag.33.js
309 ms
ga-audiences
186 ms
utag.v.js
60 ms
fooby.net 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.net 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.net 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fooby.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fooby.net 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.net
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: