13.8 sec in total
392 ms
10.5 sec
2.9 sec
Click here to check amazing Houlier Hatenadiary content for Japan. Otherwise, check out these important facts you probably never knew about houlier.hatenadiary.com
リンクは全部別ウィンドウで開きます。はい。
Visit houlier.hatenadiary.comWe analyzed Houlier.hatenadiary.com page load time and found that the first response time was 392 ms and then it took 13.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
houlier.hatenadiary.com performance score
392 ms
616 ms
343 ms
363 ms
655 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Houlier.hatenadiary.com, 23% (38 requests) were made to Cdn-ak.f.st-hatena.com and 7% (11 requests) were made to Blog.st-hatena.com. The less responsive or slowest element that took the longest time to load (9.4 sec) relates to the external source Cdn-ak.f.st-hatena.com.
Page size can be reduced by 2.8 MB (18%)
15.6 MB
12.7 MB
In fact, the total size of Houlier.hatenadiary.com main page is 15.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. 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 12.0 MB which makes up the majority of the site volume.
Potential reduce by 92.2 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 92.2 kB or 75% of the original size.
Potential reduce by 37.3 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. Houlier Hatenadiary images are well optimized though.
Potential reduce by 2.6 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.6 MB or 78% of the original size.
Potential reduce by 77.9 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. Houlier.hatenadiary.com needs all CSS files to be minified and compressed as it can save up to 77.9 kB or 84% of the original size.
Number of requests can be reduced by 79 (51%)
155
76
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Houlier Hatenadiary. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and as a result speed up the page load time.
houlier.hatenadiary.com
392 ms
blog.css
616 ms
4727ae8e9c35434c91a23fa35b467535c6bd4ed5
343 ms
hatena_afc_ydn-compiled.js
363 ms
hatena_dfp2.js
655 ms
HatenaStar.js
1204 ms
widgets.js
114 ms
plusone.js
147 ms
bookmark_button.js
754 ms
react-with-addons.min.js
103 ms
react-dom.min.js
109 ms
jquery-1.9.1.min.js
30 ms
jquery-ui.1.10.0.custom.min.js
64 ms
jquery.flot.0.8.3.js
32 ms
jquery.flot.time.0.8.3.js
32 ms
hatenablog.js
2016 ms
texts-ja.js
645 ms
api.js
105 ms
analytics.js
36 ms
20160309033653.jpg
1070 ms
profile.gif
488 ms
20160309033701.jpg
1066 ms
20160309033705.jpg
1067 ms
20160309033708.jpg
2013 ms
20160309033712.jpg
1998 ms
20160309033718.jpg
564 ms
20151129204705.jpg
1054 ms
20151129205145.jpg
1995 ms
20151129205154.jpg
1994 ms
20151129205205.jpg
1995 ms
20151129205213.jpg
1995 ms
20151129205319.jpg
2225 ms
20151129205550.jpg
1999 ms
20151106211558.jpg
2486 ms
20151106211606.jpg
2898 ms
20151106211757.jpg
2102 ms
20151105042558.jpg
2899 ms
20151105042628.jpg
4136 ms
20151105042647.jpg
2921 ms
20151105042701.jpg
3234 ms
20151105042719.jpg
3500 ms
20151105042733.jpg
4424 ms
20151105042744.jpg
3935 ms
20151105042802.jpg
3679 ms
20151105042812.jpg
4064 ms
20151105042824.jpg
5146 ms
20151105042834.jpg
4514 ms
20151105042844.jpg
5367 ms
20151105042859.jpg
9427 ms
20151104024124.jpg
7627 ms
20151104024252.jpg
4975 ms
20151104024401.jpg
5218 ms
20151104024539.jpg
7102 ms
20151104024546.jpg
6002 ms
20151104024554.jpg
6396 ms
20151104024604.jpg
6128 ms
profile.gif
444 ms
box2_bg.png
150 ms
tag.png
150 ms
TitilliumText22L003-webfont.woff
324 ms
collect
10 ms
collect
58 ms
collect
35 ms
comment.png
248 ms
show_ads.js
7 ms
show_ads_impl.js
45 ms
ads
297 ms
osd.js
91 ms
20151104024611.jpg
6162 ms
ads
149 ms
pager.png
245 ms
audience
312 ms
jstag
206 ms
gpt.js
205 ms
cb=gapi.loaded_0
132 ms
20151104024617.jpg
7087 ms
pubads_impl_82.js
31 ms
container.html
15 ms
dfp.config.json
190 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
195 ms
show.json
1003 ms
notices.count.json
1140 ms
comment.gif
344 ms
entries.json
413 ms
hatena-star-add-button.png
165 ms
ads
394 ms
blogs
429 ms
recaptcha__en.js
230 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
143 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
144 ms
expansion_embed.js
16 ms
ads
482 ms
bsredirect5.js
157 ms
surly.js
146 ms
ad
62 ms
gen_204
31 ms
globalheader.css
213 ms
api.js
29 ms
jot.html
1 ms
bst2tv3.html
376 ms
verifyc.js
252 ms
notices.count.json
389 ms
dropdown@2x.png
171 ms
init
218 ms
ajs.php
411 ms
ads
219 ms
clk
67 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
71 ms
lidar.js
4 ms
antenna2.js
94 ms
dvtp_src.js
263 ms
ca
102 ms
index.html
133 ms
firstevent
47 ms
blogicon-regular.woff
431 ms
info
327 ms
easeljs-0.8.1.min.js
139 ms
tweenjs-0.6.1.min.js
149 ms
movieclip-0.8.1.min.js
149 ms
preloadjs-0.6.1.min.js
154 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250.js
45 ms
dvtp_src_internal26.js
96 ms
4.gif
268 ms
ba.html
301 ms
sbhK2lTE.js
78 ms
push
331 ms
ca-pub-5973519624968530.js
213 ms
zrt_lookup.html
280 ms
ads
436 ms
lg.php
369 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250_atlas_.json
220 ms
cTrvNaRi.html
209 ms
t2tv7.html
232 ms
visit.js
119 ms
guest_icon_64.gif
464 ms
entries.json
267 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250_atlas_.png
38 ms
4311.js
103 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
29 ms
avs5639.js
100 ms
event.gif
71 ms
event.gif
2074 ms
pixel
21 ms
event.jpg
2058 ms
2530
68 ms
push
58 ms
6486ee8831ec61a50a12d1798da21d2e_1.html
155 ms
pixel
25 ms
st.v2.js
135 ms
entries.json
192 ms
4f65c37d23a53433a8172d800e75c3fb.jpg
115 ms
cvo.gif
23 ms
gr
27 ms
pixel_details.html
30 ms
box_19_top-right.png
27 ms
ci.png
28 ms
cap
5 ms
ca
12 ms
ca
12 ms
ca
8 ms
get
4 ms
get
4 ms
houlier.hatenadiary.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Houlier.hatenadiary.com 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 Houlier.hatenadiary.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.
houlier.hatenadiary.com
Open Graph data is detected on the main page of Houlier Hatenadiary. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: