6.4 sec in total
335 ms
5.6 sec
459 ms
Visit tm-no.hatenablog.jp now to see the best up-to-date Tm No Hatena Blog content for Japan and also check out these interesting facts you probably never knew about tm-no.hatenablog.jp
日記や豆知識など投稿しています。
Visit tm-no.hatenablog.jpWe analyzed Tm-no.hatenablog.jp page load time and found that the first response time was 335 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tm-no.hatenablog.jp performance score
335 ms
832 ms
319 ms
734 ms
257 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Tm-no.hatenablog.jp, 8% (10 requests) were made to Blog.st-hatena.com and 7% (9 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source S.hatena.ne.jp.
Page size can be reduced by 3.9 MB (77%)
5.1 MB
1.2 MB
In fact, the total size of Tm-no.hatenablog.jp main page is 5.1 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. 70% of websites need less resources to load. Javascripts take 4.7 MB which makes up the majority of the site volume.
Potential reduce by 62.1 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 62.1 kB or 78% of the original size.
Potential reduce by 21.1 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. Tm No Hatena Blog images are well optimized though.
Potential reduce by 3.8 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 3.8 MB or 80% of the original size.
Potential reduce by 83.8 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. Tm-no.hatenablog.jp needs all CSS files to be minified and compressed as it can save up to 83.8 kB or 83% of the original size.
Number of requests can be reduced by 79 (65%)
122
43
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tm No Hatena Blog. 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 6 to 1 for CSS and as a result speed up the page load time.
tm-no.hatenablog.jp
335 ms
blog.css
832 ms
1fab10f34c30dce163da8177ce362e2d24803940
319 ms
hatena_afc_ydn-compiled.js
734 ms
q
257 ms
hatena_dfp2.js
901 ms
HatenaStar.js
1535 ms
widgets.js
132 ms
plusone.js
77 ms
bookmark_button.js
770 ms
react-with-addons.min.js
45 ms
react-dom.min.js
48 ms
jquery-1.9.1.min.js
218 ms
jquery-ui.1.10.0.custom.min.js
217 ms
jquery.flot.0.8.3.js
217 ms
jquery.flot.time.0.8.3.js
217 ms
hatenablog.js
2024 ms
texts-ja.js
707 ms
api.js
57 ms
analytics.js
66 ms
20151106151333.png
1099 ms
button-only.gif
214 ms
profile.gif
542 ms
20151106152738.png
931 ms
profile.gif
503 ms
show_ads.js
25 ms
collect
15 ms
collect
58 ms
show_ads_impl.js
53 ms
ads
222 ms
osd.js
32 ms
search_w.png
148 ms
flash._V1391505555_.js
29 ms
audience
367 ms
jstag
39 ms
gpt.js
7 ms
pubads_impl_82.js
7 ms
container.html
11 ms
cb=gapi.loaded_0
58 ms
685 ms
681 ms
679 ms
dfp.config.json
169 ms
ads
358 ms
blogs
193 ms
recaptcha__en.js
103 ms
sdk.js
277 ms
user.segment.json
226 ms
hatena_bigmining.js
68 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
60 ms
show.json
1094 ms
archive_module
277 ms
recent_comments
386 ms
notices.count.json
948 ms
hatena-star-add-button.png
176 ms
comment.gif
366 ms
entries.json
2170 ms
reset.css
132 ms
entry-button.css
132 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
87 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
126 ms
globalheader.css
182 ms
hatenablog.js
1531 ms
texts-ja.js
235 ms
api.js
43 ms
bbtn-l_v3.png
32 ms
114 ms
ajs.php
386 ms
ads
188 ms
xd_arbiter.php
232 ms
xd_arbiter.php
444 ms
guest_icon.gif
486 ms
ajs.php
338 ms
jot.html
29 ms
adsbygoogle.js
7 ms
lg.php
179 ms
ca-pub-5973519624968530.js
25 ms
zrt_lookup.html
21 ms
ads
195 ms
ads
253 ms
lg.php
182 ms
adj
101 ms
adServerESI.aspx
63 ms
beacon
84 ms
skeleton.gif
120 ms
intel-vid4.png
91 ms
lidar.js
33 ms
sbhK2lTE.js
86 ms
pixel
61 ms
push
102 ms
pixel
93 ms
pixel
93 ms
adj
83 ms
adServerESI.aspx
81 ms
beacon
28 ms
cTrvNaRi.html
17 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
4 ms
m
121 ms
skeleton.gif
48 ms
intel-vid3.png
63 ms
pixel
59 ms
push
58 ms
pixel
30 ms
46 ms
35 ms
cse
314 ms
sd
11 ms
pixel
13 ms
notices.count.json
158 ms
dropdown@2x.png
151 ms
init
188 ms
fastbutton
55 ms
fastbutton
80 ms
fastbutton
86 ms
blogicon-regular.woff
293 ms
info
229 ms
hatena-follow-button.png
147 ms
rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw
5 ms
cb=gapi.loaded_0
12 ms
cb=gapi.loaded_1
31 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
41 ms
cb=gapi.loaded_0
20 ms
dmp
302 ms
gtm.js
23 ms
tdim-0.11.2.js
10 ms
segment
302 ms
share_button.php
92 ms
share_button.php
68 ms
share_button.php
62 ms
wy1X4hBW7e7.js
492 ms
LVx-xkvaJ0b.png
562 ms
pageviews
7 ms
tm-no.hatenablog.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tm-no.hatenablog.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 Tm-no.hatenablog.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.
tm-no.hatenablog.jp
Open Graph data is detected on the main page of Tm No Hatena Blog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: