5.4 sec in total
197 ms
4.8 sec
402 ms
Visit itaste.com now to see the best up-to-date ITaste content for Switzerland and also check out these interesting facts you probably never knew about itaste.com
iTaste, the food critics' taste network
Visit itaste.comWe analyzed Itaste.com page load time and found that the first response time was 197 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
itaste.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value6.8 s
7/100
25%
Value7.6 s
25/100
10%
Value510 ms
57/100
30%
Value0.003
100/100
15%
Value7.9 s
43/100
10%
197 ms
429 ms
372 ms
207 ms
180 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 51% of them (48 requests) were addressed to the original Itaste.com, 7% (7 requests) were made to Css.itaste.com and 6% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Itaste.com.
Page size can be reduced by 1.0 MB (39%)
2.6 MB
1.6 MB
In fact, the total size of Itaste.com main page is 2.6 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 65.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. 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 65.5 kB or 77% of the original size.
Potential reduce by 27.5 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. ITaste images are well optimized though.
Potential reduce by 927.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 927.8 kB or 72% of the original size.
Potential reduce by 58 B
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. Itaste.com needs all CSS files to be minified and compressed as it can save up to 58 B or 26% of the original size.
Number of requests can be reduced by 58 (64%)
91
33
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ITaste. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
itaste.com
197 ms
www.itaste.com
429 ms
372 ms
207 ms
iTasteLoader.js
180 ms
207 ms
css
25 ms
adv_searchResto.js
170 ms
gpt.js
8 ms
pubads_impl_81.js
8 ms
container.html
24 ms
jquery.min.js
43 ms
jquery-ui.min.js
62 ms
jquery.nyroModal.min.js
291 ms
jquery-ui-i18n.js
336 ms
jquery.ajaxmanager.js
173 ms
jquery.json.min.js
172 ms
jquery.autocomplete.js
254 ms
jquery.cookie.min.js
173 ms
jquery.blockUI.js
420 ms
jquery.form.js
421 ms
jquery.tooltip.pack.js
340 ms
jquery-asyncUpload-0.1.js
424 ms
jquery.jgrowl_min.js
456 ms
jquery.validate.min.js
584 ms
jquery.scrollTo-min.js
506 ms
jquery.cluetip.js
670 ms
easySlider.packed.js
587 ms
ajaxupload.js
588 ms
superfish.js
621 ms
ui.selectmenu.js
755 ms
jquery.tipsy.js
752 ms
jquery.uploadify-3.1.min.js
919 ms
maps
92 ms
iTasteLoaderCONCAT.js
1170 ms
iTasteLoader2.js
786 ms
iTasteLoaderReady.js
833 ms
plusone.js
101 ms
cb=gapi.loaded_0
24 ms
geocoder.js
337 ms
markermanager_packed.js
170 ms
google.tooltip.js
170 ms
share_facebook_en.png
170 ms
connextionBox_point.png
171 ms
une_article_wiin_me_3.jpg
506 ms
pic_subscribe.png
672 ms
une_art_2_wiine_me.jpg
355 ms
une_cc_amateur_vfaop.jpg
507 ms
une_premiers_certifs_ecocook.jpg
765 ms
une_ammolite.jpg
765 ms
une_article_wiine_me1.jpg
764 ms
RE_8282_4e48d84cd65eb_250x200.jpg
679 ms
RE_117820_53b12e8c53602_250x200.jpg
680 ms
RE_322758_i1342259291725_250x200.jpg
765 ms
RE_127378_55c9f33f5902f_250x200.jpg
849 ms
RE_147078_55c9fca29a9de_250x200.jpg
848 ms
RE_151043_55acfe1e355ac_250x200.jpg
929 ms
RE_298846_i1376306851301_250x200.jpg
927 ms
RE_127391_55c9f78db9aba_250x200.jpg
926 ms
unknown_02.gif
930 ms
ME_161_4db14bff2f004_medium.png
1183 ms
logo-itaste.png
170 ms
picto-search.png
170 ms
bkg_accueil.png
171 ms
picto-home.png
172 ms
ads
267 ms
m_js_controller.js
32 ms
abg.js
55 ms
bkg_accueil.png
716 ms
osd.js
31 ms
ads
251 ms
s
23 ms
nessie_icon_tiamat_white.png
81 ms
googlelogo_color_112x36dp.png
59 ms
x_button_blue2.png
32 ms
imgad
33 ms
ga.js
41 ms
home
667 ms
all.js
271 ms
ads
32 ms
__utm.gif
22 ms
common.js
18 ms
util.js
34 ms
geocoder.js
32 ms
53 ms
xd_arbiter.php
223 ms
xd_arbiter.php
441 ms
blank.gif
211 ms
activeview
12 ms
ui
30 ms
xd_arbiter.php
137 ms
login_button.php
59 ms
BYwTqiJVYSC.js
551 ms
teE39sffXW8.png
644 ms
iqVGY7gYXlg.gif
683 ms
itaste.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
itaste.com 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
itaste.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Itaste.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Itaste.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.
itaste.com
Open Graph description is not detected on the main page of ITaste. 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: