14.8 sec in total
567 ms
13.8 sec
460 ms
Welcome to hyoudo.jp homepage info - get ready to check Hyoudo best content right away, or after learning these important things about hyoudo.jp
接待や会議、慶事やお祝いなどの仕出し弁当・高級弁当は逸品弁当におまかせください。特別なおもてなしのために、厳選した品質の宅配弁当を販売しております。他では味わえない一味違ったお弁当を出したい時にもご利用ください。首都圏へは送料無料で宅配いたします。
Visit hyoudo.jpWe analyzed Hyoudo.jp page load time and found that the first response time was 567 ms and then it took 14.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
hyoudo.jp performance score
567 ms
6569 ms
434 ms
1309 ms
627 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hyoudo.jp, 37% (56 requests) were made to Ippin-bento.com and 23% (35 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6.6 sec) relates to the external source Ippin-bento.com.
Page size can be reduced by 576.6 kB (26%)
2.2 MB
1.6 MB
In fact, the total size of Hyoudo.jp main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 31.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 31.5 kB or 73% of the original size.
Potential reduce by 32.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. Hyoudo images are well optimized though.
Potential reduce by 407.6 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 407.6 kB or 65% of the original size.
Potential reduce by 104.7 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. Hyoudo.jp needs all CSS files to be minified and compressed as it can save up to 104.7 kB or 84% of the original size.
Number of requests can be reduced by 82 (58%)
142
60
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hyoudo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
hyoudo.jp
567 ms
6569 ms
reset.css
434 ms
common.css
1309 ms
galleriffic-2.css
627 ms
responsiveslides.css
450 ms
jquery.min.js
9 ms
jquery.js
1410 ms
yuga.js
861 ms
jquery.lightbox-0.5.js
1069 ms
responsiveslides.js
707 ms
responsiveslides.min.js
815 ms
smp.js
897 ms
order_form.js
542 ms
ice.js
713 ms
s_retargeting.js
551 ms
404.php
2401 ms
convert.js
578 ms
gtm.js
39 ms
tag.js
38 ms
header_bg1.png
270 ms
logo.png
268 ms
header_tel1.png
398 ms
header_order.png
292 ms
logo_hyoudo.png
285 ms
hyoudo_main_01.jpg
1037 ms
hyoudo_main_02.jpg
1143 ms
hyoudo_main_03.jpg
905 ms
hyoudo_main_04.jpg
1094 ms
24.jpg
1630 ms
05.jpg
1772 ms
23.jpg
1440 ms
29.jpg
1781 ms
30.jpg
1630 ms
choice_btn_order.png
1651 ms
choice_btn_fax.png
1812 ms
choice_btn_tel1.png
1867 ms
side_catalog2.png
1904 ms
side_catalog_cate.png
3191 ms
cse.js
77 ms
nav_1.png
1980 ms
nav_2.png
2102 ms
nav_3.png
2103 ms
nav_4.png
2104 ms
nav_5.png
2262 ms
brand.gif
2246 ms
menu.gif
2256 ms
area.gif
2291 ms
order.gif
2309 ms
title_h2.png
2427 ms
ranking_icon_no1.png
2430 ms
ranking_icon_no2.png
2472 ms
ranking_icon_no3.png
2516 ms
ranking_icon_no4.png
2536 ms
ranking_icon_no5.png
2626 ms
netbox_choice_bg1.png
2637 ms
all.js
34 ms
tag
17 ms
cse.js
95 ms
ga.js
44 ms
fbds.js
35 ms
munchkin.js
42 ms
rtp.js
334 ms
236 ms
252 ms
xd_arbiter.php
19 ms
xd_arbiter.php
37 ms
munchkin.js
13 ms
visitWebPage
156 ms
visitWebPage
16 ms
f_mid_bg.png
2730 ms
foot_arrow.png
2733 ms
foot_arrow.png
2719 ms
jquery-ui-insightera-custom-1.8.css
11 ms
trw
152 ms
insightera-bar-2.1.js
4 ms
ga-integration-2.0.1.js
7 ms
pv_beacon.gif
346 ms
ice.conf.js
992 ms
d02f83cd-0ff4-42b4-b2ae-49e93cc7a222.js
9 ms
WRf4.js
2 ms
pta.js
306 ms
analytics.js
55 ms
mixpanel-2-latest.min.js
52 ms
jquery.min.js
34 ms
ya.js
362 ms
linkid.js
31 ms
24 ms
20 ms
jquery-custom-ui.min.js
37 ms
collect
7 ms
collect
102 ms
collect
15 ms
collect
91 ms
insightera-bar-1.3.css
7 ms
font-awesome-custom.css
7 ms
rcmd
150 ms
ga-audiences
47 ms
ga-audiences
38 ms
like_box.php
360 ms
54077e96.js
642 ms
cta-bar-sprite.png
9 ms
fontawesome-webfont.woff
111 ms
pb.js
704 ms
533 ms
UKF7BfrH59e.css
40 ms
Mlo1cafniKV.css
43 ms
drXqyuWvz8i.css
41 ms
RKGhp9sp483.css
51 ms
ncOYyFQkKRB.css
59 ms
jNip3BsFFRm.css
48 ms
PkxQAaxhm0E.css
69 ms
Os9VKVlRF51.css
81 ms
q68gy-v_YMF.js
89 ms
ehA1CqzHyzE.js
104 ms
0wM5s1Khldu.js
104 ms
1bNoFZUdlYZ.js
115 ms
njO1TPvGzoR.js
117 ms
1QuX41zDRrx.js
117 ms
Oagsvfb4VWi.js
123 ms
LTv6ZK-5zxz.js
131 ms
1FCa-btixu2.js
119 ms
IjqSyiwKeaX.js
120 ms
rBxSIHk4zIe.js
129 ms
n6VgtouijQL.js
118 ms
7BE0CZr3HTs.js
126 ms
pQrUxxo5oQp.js
126 ms
_UYztdBNTjs.js
128 ms
-7JBD_ybv4q.js
170 ms
Kt4tkgSRvHH.js
169 ms
H3EKDTObx05.js
169 ms
10403328_939765399370670_1992041427265899814_n.jpg
180 ms
safe_image.php
183 ms
b8XhdWI9eAN.js
49 ms
1044382_700636806616865_1895994736_n.png
38 ms
12742426_1316034371743769_8295769420458207687_n.jpg
38 ms
12514157_613468525474300_1371851413_n.jpg
41 ms
12745671_1316028361744370_6261510209793018789_n.jpg
41 ms
safe_image.php
45 ms
wL6VQj7Ab77.png
37 ms
s7jcwEQH7Sx.png
36 ms
QDwYpIaRyfG.png
36 ms
l5aPruN9xMM.png
35 ms
K_65vAc89SX.png
35 ms
K00K-UgnsKu.png
40 ms
404.php
2292 ms
404.php
2478 ms
pn
373 ms
eR-qA8bp1RM.js
7 ms
I6-MnjEovm5.js
3 ms
print.css
204 ms
22 ms
hyoudo.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hyoudo.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Hyoudo.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.
hyoudo.jp
Open Graph description is not detected on the main page of Hyoudo. 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: