9.7 sec in total
536 ms
8.8 sec
416 ms
Visit hanakazoku.net now to see the best up-to-date Hanakazoku content and also check out these interesting facts you probably never knew about hanakazoku.net
開店祝い・記念日にお祝いスタンド花。日本全国どこへでもお花の当日配送いたします。お花の事なら花家族。
Visit hanakazoku.netWe analyzed Hanakazoku.net page load time and found that the first response time was 536 ms and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hanakazoku.net performance score
536 ms
2809 ms
351 ms
974 ms
374 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 78% of them (109 requests) were addressed to the original Hanakazoku.net, 6% (9 requests) were made to Plugins.mixi.jp and 3% (4 requests) were made to Img.mixi.net. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Hanakazoku.net.
Page size can be reduced by 659.9 kB (26%)
2.5 MB
1.9 MB
In fact, the total size of Hanakazoku.net main page is 2.5 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. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 85.9 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 85.9 kB or 86% of the original size.
Potential reduce by 29.2 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. Hanakazoku images are well optimized though.
Potential reduce by 469.2 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 469.2 kB or 69% of the original size.
Potential reduce by 75.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. Hanakazoku.net needs all CSS files to be minified and compressed as it can save up to 75.7 kB or 83% of the original size.
Number of requests can be reduced by 45 (33%)
137
92
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hanakazoku. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
hanakazoku.net
536 ms
www.hanakazoku.net
2809 ms
import.css
351 ms
jquery.js
974 ms
rollover.js
374 ms
jquery-1.4.2.min.js
1056 ms
jquery.flexslider.js
382 ms
css.js
542 ms
navi.js
559 ms
win_op.js
581 ms
site.js
714 ms
scroll_product_bloc.js
739 ms
scroll_product_bloc.css
740 ms
bookmark_button.js
366 ms
reset.css
427 ms
base.css
539 ms
contents.css
580 ms
table.css
579 ms
bloc.css
616 ms
bloc_alpha.css
717 ms
popup.css
766 ms
button-only.gif
226 ms
bg_header.gif
229 ms
logo.gif
225 ms
entry_bt.gif
226 ms
log_bt.gif
228 ms
cart_bt.gif
230 ms
search_btn_on.jpg
230 ms
banner01.jpg
536 ms
title_reco_side.jpg
368 ms
10091010_507379a1e7838.jpg
371 ms
10022259_506af333d17b6.jpg
403 ms
02231430_56cbee67ea7e4.jpg
403 ms
convenience01.jpg
404 ms
convenience02.jpg
546 ms
convenience03.jpg
578 ms
title_method_side.jpg
601 ms
method_tel.jpg
578 ms
btn_first.jpg
586 ms
maintop_04.jpg
1676 ms
maintop_03.jpg
1366 ms
maintop_05.jpg
2594 ms
title_delivery.jpg
949 ms
delivery01.jpg
778 ms
delivery02.jpg
795 ms
delivery03.jpg
972 ms
delivery04.jpg
984 ms
top_banner01.jpg
1441 ms
edition09.jpg
1348 ms
edition32.jpg
1302 ms
edition11.jpg
1492 ms
companies01.jpg
1722 ms
companies02.jpg
1713 ms
10022242_506aef2b2095f.jpg
1651 ms
btn_detail_s.jpg
1705 ms
10022120_506adc13a9d7e.jpg
1837 ms
08181925_55d3080d30092.jpg
1878 ms
10022256_506af291231f7.jpg
1900 ms
plugins.js
306 ms
widgets.js
155 ms
like.php
184 ms
594 ms
ga.js
44 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
123 ms
10021349_506a72542fcaa.jpg
1675 ms
03251329_53310621a36a9.jpg
1693 ms
10021142_506a5481ac83c.jpg
1802 ms
10021514_506a8652b33d0.jpg
1829 ms
11261638_5475838abf2c4.jpg
1849 ms
__utm.gif
16 ms
11041753_5458940b4a4ab.jpg
1838 ms
qeKvIRsJabD.js
487 ms
LVx-xkvaJ0b.png
552 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
45 ms
12261207_50da69fd70a3f.jpg
1741 ms
10022155_506ae44ce0c86.jpg
1845 ms
10022308_506af55c592e3.jpg
1828 ms
10022303_506af436580ff.jpg
1849 ms
03171058_55078a3c5fe9f.jpg
1878 ms
jot
90 ms
10022121_506adc6068e39.jpg
1764 ms
10022333_506afb41aa4a2.jpg
1858 ms
02102039_54d9eddbe171f.jpg
1828 ms
10022302_506af3ee6fb58.jpg
1880 ms
10022159_506ae5247e39b.jpg
1884 ms
05191504_555ad25a7105e.jpg
1890 ms
reset.css
181 ms
entry-button.css
181 ms
12261208_50da6a491e901.jpg
1811 ms
11050947_545973a8048e7.jpg
1785 ms
bbtn-l_v3.png
4 ms
02102032_54d9ec3a08d1f.jpg
1684 ms
10021428_506a7b775f696.jpg
1713 ms
02102031_54d9ebfc7d566.jpg
1695 ms
10021138_506a53be2e73e.jpg
1450 ms
10022115_506adaca8c7dd.jpg
1455 ms
11272133_50b4b303821b9.jpg
1409 ms
10022339_506afc8f1fb73.jpg
1371 ms
02102039_54d9edf4c2e21.jpg
1376 ms
01261416_56a7013f3f276.jpg
1222 ms
10021620_506a95d9bb1d4.jpg
1252 ms
10022304_506af47b84460.jpg
1242 ms
02132033_54dde0ee1dbe5.jpg
1276 ms
top_banner02.jpg
1565 ms
01211027_56a03407093b7.jpg
1221 ms
01211128_56a0423828fbf.jpg
1188 ms
01211056_56a03addb234c.jpg
1204 ms
pay.jpg
1230 ms
logo_footer.gif
1271 ms
navi_01.jpg
1250 ms
navi_02.jpg
1228 ms
navi_03.jpg
1223 ms
navi_04.jpg
1248 ms
navi_05.jpg
1288 ms
navi_06.jpg
1277 ms
navi_07.jpg
1268 ms
topic_news.jpg
1226 ms
title_category_side.jpg
1197 ms
ico_arrow_06.gif
1219 ms
title_convenience_side.jpg
1186 ms
ico_arrow_07.gif
1250 ms
title_main.jpg
1226 ms
favorite.pl
356 ms
bg_control_nav.png
196 ms
arrow_left.png
179 ms
arrow_right.png
185 ms
mixi_check_entry.css
14 ms
errorreport.production.js
293 ms
json.js
295 ms
underscore-string-1.3.3-2.0.0-compress.js
302 ms
namespace-brook-compress.js
308 ms
prototype-effects-1.6.1-1.8.3-compress.js
455 ms
mixi.js
312 ms
favorite.production.js
584 ms
jquery-1.7.1.min-noconflict-compress.js
738 ms
analytics.js
4 ms
comment001.gif
9 ms
favorite_button004.png
7 ms
comment_content_top001.gif
6 ms
hanakazoku.net SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hanakazoku.net 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 Hanakazoku.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.
hanakazoku.net
Open Graph description is not detected on the main page of Hanakazoku. 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: