4.7 sec in total
358 ms
4.1 sec
206 ms
Welcome to gd.hatenablog.jp homepage info - get ready to check Gd Hatenablog best content for Japan right away, or after learning these important things about gd.hatenablog.jp
20131207
Visit gd.hatenablog.jpWe analyzed Gd.hatenablog.jp page load time and found that the first response time was 358 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
gd.hatenablog.jp performance score
358 ms
797 ms
518 ms
51 ms
350 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Gd.hatenablog.jp, 11% (8 requests) were made to Blog.st-hatena.com and 8% (6 requests) were made to Fls-fe.amazon-adsystem.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Blog.st-hatena.com.
Page size can be reduced by 2.2 MB (78%)
2.8 MB
612.8 kB
In fact, the total size of Gd.hatenablog.jp main page is 2.8 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. 55% of websites need less resources to load. Javascripts take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 28.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. This page needs HTML code to be minified as it can gain 4.8 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 28.2 kB or 76% of the original size.
Potential reduce by 1.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. Gd Hatenablog images are well optimized though.
Potential reduce by 2.0 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.0 MB or 81% 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. Gd.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 44 (63%)
70
26
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gd Hatenablog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
gd.hatenablog.jp
358 ms
blog.css
797 ms
2511aad00dfeda6b84a000e86985c6fd84e1726e
518 ms
q
51 ms
line-button.js
350 ms
ads.js
264 ms
HatenaStar.js
1250 ms
widgets.js
62 ms
plusone.js
169 ms
bookmark_button.js
756 ms
react-with-addons.min.js
62 ms
react-dom.min.js
70 ms
jquery-1.9.1.min.js
54 ms
jquery-ui.1.10.0.custom.min.js
60 ms
jquery.flot.0.8.3.js
52 ms
jquery.flot.time.0.8.3.js
52 ms
hatenablog.js
2132 ms
texts-ja.js
814 ms
api.js
112 ms
counter.js
513 ms
q
407 ms
ir
87 ms
button-only.gif
185 ms
profile.gif
363 ms
json
185 ms
ir
157 ms
ir
167 ms
ir
170 ms
analytics.js
27 ms
cm
178 ms
cm
196 ms
search_w.png
158 ms
ads-common.js
338 ms
43_asooc_728x90.jpg
16 ms
89 ms
51NpLPrsIQL._SL100_.jpg
11 ms
buy-from-tan.gif
7 ms
93 ms
cm
133 ms
cm
127 ms
json
115 ms
cb=gapi.loaded_0
53 ms
x-site_ume_2015_examinee_728x90.gif
20 ms
86 ms
645 ms
51YVQjkxgmL._SL80_.jpg
16 ms
94 ms
1039 ms
240 ms
reset.css
11 ms
entry-button.css
9 ms
bbtn-l_v3.png
5 ms
101
182 ms
blogs
163 ms
recaptcha__en.js
26 ms
globalheader.css
150 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
40 ms
show.json
932 ms
archive_module
186 ms
notices.count.json
677 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
13 ms
notices.count.json
687 ms
init
346 ms
dropdown@2x.png
302 ms
jot
83 ms
fastbutton
71 ms
blogicon-regular.woff
297 ms
info
198 ms
hatena-follow-button.png
150 ms
cb=gapi.loaded_0
10 ms
cb=gapi.loaded_1
13 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
49 ms
hatena-star-add-button.png
157 ms
comment.gif
305 ms
entries.json
358 ms
gd.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 Gd.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 Gd.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.
gd.hatenablog.jp
Open Graph data is detected on the main page of Gd Hatenablog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: