9.2 sec in total
558 ms
7.9 sec
693 ms
Welcome to yaoichi801.jp homepage info - get ready to check Yaoichi 801 best content right away, or after learning these important things about yaoichi801.jp
九州産の野菜・果物のことならヤオイチ~稲田青果店~全国配送致します!
Visit yaoichi801.jpWe analyzed Yaoichi801.jp page load time and found that the first response time was 558 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
yaoichi801.jp performance score
558 ms
1004 ms
1018 ms
1036 ms
542 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 72% of them (66 requests) were addressed to the original Yaoichi801.jp, 20% (18 requests) were made to Web.xaas.jp and 2% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Ssl.xaas.jp.
Page size can be reduced by 399.2 kB (28%)
1.4 MB
1.0 MB
In fact, the total size of Yaoichi801.jp main page is 1.4 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. 35% of websites need less resources to load. Images take 930.3 kB which makes up the majority of the site volume.
Potential reduce by 58.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 58.5 kB or 79% of the original size.
Potential reduce by 21.8 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. Yaoichi 801 images are well optimized though.
Potential reduce by 175.7 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 175.7 kB or 74% of the original size.
Potential reduce by 143.2 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. Yaoichi801.jp needs all CSS files to be minified and compressed as it can save up to 143.2 kB or 82% of the original size.
Number of requests can be reduced by 29 (32%)
90
61
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yaoichi 801. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
yaoichi801.jp
558 ms
www.yaoichi801.jp
1004 ms
A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.1FlClNpo4U.css
1018 ms
jquery.js.pagespeed.jm.xea4kgmxDf.js
1036 ms
ajax.js.pagespeed.jm.WTNt_xGIWK.js
542 ms
jcarousellite.js.pagespeed.jm.yo9DZGAYlG.js
535 ms
jscrollpane.js.pagespeed.jm.2wYEC_BNG3.js
722 ms
treeview.js.pagespeed.jm.Ccxdh7coVu.js
542 ms
common.js.pagespeed.jm.C_WZ9FZvi3.js
931 ms
prettyphoto.js,q20150527.pagespeed.jm.0Xhh9MVqND.js
899 ms
theme.css
569 ms
searchGoodsView.js.pagespeed.jm.zc052OUAiF.js
545 ms
sessionStorageCache.js.pagespeed.jm.sO8NkBNyTZ.js
733 ms
categoryViewSs.js.pagespeed.jm.UQ156MjblN.js
728 ms
calendarView.js.pagespeed.jm.ov3yFrZUnI.js
903 ms
header.jpg
2613 ms
logo.gif
199 ms
xspace.gif.pagespeed.ic.lRMfmktUso.png
185 ms
main_img.jpg
2565 ms
resize.jpg
711 ms
Qrcode
557 ms
bnr_img001.jpg
1853 ms
bnr_img002.jpg
1196 ms
bnr_img003.jpg
1128 ms
db_02.gif
752 ms
gf_02.gif
889 ms
ftr_credit.png
1334 ms
convenience.jpg
1231 ms
ftr_bank.png
1503 ms
rkFooter_timezoneSagawa7.png
1592 ms
bg_gnv.jpg
1406 ms
icn_home.gif
1513 ms
bg_search.jpg
1753 ms
icn_search.gif
1697 ms
btn_search.gif
1698 ms
title_bar01.gif
1773 ms
all.js
276 ms
rook.tracking.min.js
182 ms
index
2032 ms
campaigninfoshow
2048 ms
calendarheaderinfo
2285 ms
index
2154 ms
loading_icon.gif
403 ms
space.gif
181 ms
index
2491 ms
index
2500 ms
index
2448 ms
index
2494 ms
m.php
180 ms
129 ms
t.php
217 ms
nv_login.gif
428 ms
nv_cart.gif
623 ms
bana_01.jpg
729 ms
bana_02.jpg
1309 ms
bana_03.jpg
973 ms
bg_border01.gif
620 ms
calendarplug
979 ms
icn_arrow04.gif
361 ms
icn_arrow05.gif
419 ms
btn_new_pc001.gif
416 ms
IMG_0912.jpg
616 ms
IMG_0742.jpg
711 ms
IMG_0653.jpg
809 ms
IMG_1677.jpg
938 ms
141.jpg
960 ms
shironegi1.jpg
916 ms
btn_ranking_01_pc001.png
1010 ms
IMG_0734.jpg
1194 ms
IMG_0721.jpg
1060 ms
btn_ranking_02_pc001.png
1097 ms
btn_ranking_03_pc001.png
1095 ms
IMG_0999.jpg
1270 ms
1307106327898.jpg
1382 ms
IMG_0683.jpg
1453 ms
127.jpg
1465 ms
112.jpg
1314 ms
1307939603888.jpg
1554 ms
IMG_0853.jpg
1612 ms
151.jpg
1696 ms
IMG_0854.jpg
1769 ms
IMG_0679.jpg
1812 ms
IMG_0900.jpg
1829 ms
1307937335134.jpg
1737 ms
IMG_0825.jpg
1961 ms
0010.jpg
2124 ms
icn_arrow06.gif
1923 ms
xd_arbiter.php
212 ms
xd_arbiter.php
416 ms
like.php
167 ms
wy1X4hBW7e7.js
548 ms
LVx-xkvaJ0b.png
608 ms
yaoichi801.jp SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yaoichi801.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Yaoichi801.jp 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.
yaoichi801.jp
Open Graph description is not detected on the main page of Yaoichi 801. 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: