1.7 sec in total
172 ms
1.4 sec
149 ms
Click here to check amazing Udisfood content. Otherwise, check out these important facts you probably never knew about udisfood.com
Visit udisfood.comWe analyzed Udisfood.com page load time and found that the first response time was 172 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
udisfood.com performance score
172 ms
113 ms
95 ms
40 ms
45 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Udisfood.com, 48% (33 requests) were made to Static.parastorage.com and 23% (16 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (391 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.3 MB (71%)
3.2 MB
937.5 kB
In fact, the total size of Udisfood.com main page is 3.2 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. 65% of websites need less resources to load. Javascripts take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 95.8 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 95.8 kB or 86% of the original size.
Potential reduce by 33.9 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. Obviously, Udisfood needs image optimization as it can save up to 33.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.1 MB
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 2.1 MB or 77% of the original size.
Potential reduce by 44.1 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. Udisfood.com needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.
Number of requests can be reduced by 39 (64%)
61
22
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Udisfood. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
udisfood.com
172 ms
www.etaisfood.com
113 ms
bt
95 ms
require.min.js
40 ms
main-r.min.js
45 ms
viewer.css
57 ms
dynamicmodel
8 ms
d4a627_f4bee166d59999d383f699fccb42e4df_137.json.z
256 ms
d4a627_8a7117ff5c2b5309464fe33d35e05f95_139.json.z
260 ms
ugc-viewer
211 ms
bt
211 ms
skins.min.js
83 ms
components.min.js
81 ms
utils.min.js
35 ms
core.min.js
35 ms
react-with-addons.min.js
82 ms
lodash.min.js
79 ms
TweenMax.min.js
203 ms
layout.min.js
203 ms
tpa.min.js
203 ms
fonts.min.js
202 ms
animations.min.js
202 ms
swfobject.min.js
202 ms
mousetrap.min.js
240 ms
tweenEngine.min.js
238 ms
DrawSVGPlugin.min.js
240 ms
react-dom.min.js
238 ms
ScrollToPlugin.min.js
236 ms
widgets.min.js
236 ms
experiment.js
238 ms
render.min.js
238 ms
wixappsCore.min.js
243 ms
wixappsClassics.min.js
246 ms
wixappsBuilder.min.js
241 ms
zepto.min.js
240 ms
color.min.js
240 ms
react-dom-server.min.js
128 ms
bt
91 ms
bt
232 ms
latin.css
225 ms
dc.js
230 ms
d4a627_acd7da5581604cbf981dced3c664d7e7.png
144 ms
css
82 ms
d4a627_fcedda27413e10faed315b66340ad688.html
79 ms
d4a627_ae9cd18b2fa84c46bbb74a5d66a57951.jpg
289 ms
d4a627_ec91c8ac0ce7426cbfc5a2e84d1c5ffd.jpg
68 ms
d4a627_bfa4849202cf4df39c26dc4d0a8cd1a4.jpg
93 ms
d4a627_894edffd4301417790fb70185ff09fbd.jpg
95 ms
d4a627_cd5ae4b4ccac4b708c5e8010fa26db5f.png
97 ms
d4a627_616e7a971d314d5287a271c9a4e9490e.png
240 ms
d4a627_67bb2b13e6f34a518b52cf2a92056859.png
201 ms
d4a627_edd107cbb3eb48628f8587c35def138b.png
204 ms
d4a627_b5139a67f2cc47dda0ca996cf9349672.jpg
391 ms
7c9158607e5e8f1a97f44394700bad4f.png
200 ms
b1dba49d4e5dad0d56b4abfcd0cb2dcd.png
200 ms
2da03695edbb21f98322b66fd54c5f21.png
202 ms
dd261446d24872b7b7cb84ff55b8d911.jpg
201 ms
bt
64 ms
bt
65 ms
bt
63 ms
form.js
225 ms
__utm.gif
17 ms
03805817-4611-4dbc-8c65-0f73031c3973.woff
10 ms
opensans-bold-webfont.woff
35 ms
opensans-regular-webfont.woff
35 ms
gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf
23 ms
gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf
33 ms
ga-audiences
137 ms
ugc-viewer
43 ms
udisfood.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Udisfood.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Udisfood.com 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.
udisfood.com
Open Graph description is not detected on the main page of Udisfood. 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: