8 sec in total
520 ms
4.3 sec
3.2 sec
Welcome to mosuke5.hateblo.jp homepage info - get ready to check Mosuke 5 Hateblo best content for Japan right away, or after learning these important things about mosuke5.hateblo.jp
mosuke5の技術ブログ。ソフトウェア開発から、クラウド上でのインフラ運用など幅広く。
Visit mosuke5.hateblo.jpWe analyzed Mosuke5.hateblo.jp page load time and found that the first response time was 520 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mosuke5.hateblo.jp performance score
520 ms
763 ms
349 ms
359 ms
508 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Mosuke5.hateblo.jp, 8% (12 requests) were made to Apis.google.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 (2 sec) relates to the external source Blog.st-hatena.com.
Page size can be reduced by 2.7 MB (69%)
3.9 MB
1.2 MB
In fact, the total size of Mosuke5.hateblo.jp main page is 3.9 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. 75% 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. Javascripts take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 154.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 154.1 kB or 76% of the original size.
Potential reduce by 43.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. Mosuke 5 Hateblo images are well optimized though.
Potential reduce by 2.3 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.3 MB or 78% of the original size.
Potential reduce by 153.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. Mosuke5.hateblo.jp needs all CSS files to be minified and compressed as it can save up to 153.9 kB or 84% of the original size.
Number of requests can be reduced by 77 (55%)
140
63
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mosuke 5 Hateblo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
mosuke5.hateblo.jp
520 ms
blog.css
763 ms
5c7f18263ebe52be4635b879673105d7e2b6927c
349 ms
hatena_afc_ydn-compiled.js
359 ms
hatena_dfp2.js
508 ms
HatenaStar.js
1086 ms
widgets.js
63 ms
plusone.js
148 ms
bookmark_button.js
636 ms
react-with-addons.min.js
60 ms
react-dom.min.js
63 ms
jquery-1.9.1.min.js
58 ms
jquery-ui.1.10.0.custom.min.js
55 ms
jquery.flot.0.8.3.js
53 ms
jquery.flot.time.0.8.3.js
54 ms
hatenablog.js
1951 ms
texts-ja.js
634 ms
api.js
69 ms
css
25 ms
analytics.js
15 ms
20160319233634.jpg
93 ms
51T4L8K2yLL._SL160_.jpg
91 ms
profile.gif
407 ms
button-only.gif
147 ms
20160207182051.png
1079 ms
20160125214934.png
380 ms
20160125215405.png
347 ms
20160125215618.png
1165 ms
20160125220823.png
313 ms
20151227172616.png
422 ms
profile.gif
376 ms
embed
311 ms
embed
1513 ms
embed
568 ms
mrl8jkM18OlOQN8JLgasD9Hq-FFgoDNV3GTKpHwuvtI.woff
8 ms
show_ads.js
36 ms
show_ads_impl.js
48 ms
ads
281 ms
osd.js
24 ms
embed.css
151 ms
cdn-ak.favicon.st-hatena.com
204 ms
entry.count.image
320 ms
321 ms
embed
1626 ms
embed
1546 ms
embed
1683 ms
ads
241 ms
http%3A%2F%2Fitpro.nikkeibp.co.jp%2Farticle%2FCOLUMN%2F20071126%2F287920%2Flevel1.jpg
233 ms
cdn-ak.favicon.st-hatena.com
226 ms
entry.count.image
182 ms
179 ms
00184.gif
10 ms
ansible_local-provisioner-in-vagrant
338 ms
135844
201 ms
ads
118 ms
00000.gif
5 ms
search.png
162 ms
audience
420 ms
jstag
90 ms
gpt.js
88 ms
http%3A%2F%2Fcdn-ak.f.st-hatena.com%2Fimages%2Ffotolife%2Fm%2Fmosuke5%2F20150718%2F20150718230605.png
551 ms
entry.count.image
159 ms
135844
160 ms
blog-icon-noimage.png
147 ms
embed-logo.gif
147 ms
cb=gapi.loaded_0
49 ms
pubads_impl_82.js
23 ms
embed.css
294 ms
entry.count.image
291 ms
ansible_local-provisioner-in-vagrant
292 ms
embed-logo.gif
292 ms
http%3A%2F%2Fcdn-ak.f.st-hatena.com%2Fimages%2Ffotolife%2Fs%2Fshin1x1%2F20160120%2F20160120181043.png
1117 ms
298 ms
296 ms
300 ms
295 ms
299 ms
298 ms
411 ms
container.html
6 ms
blogs
175 ms
recaptcha__en.js
66 ms
sdk.js
175 ms
user.segment.json
200 ms
hatena_bigmining.js
58 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
37 ms
show.json
915 ms
archive_module
218 ms
notices.count.json
883 ms
reset.css
24 ms
entry-button.css
24 ms
00433.gif
22 ms
dfp.config.json
438 ms
bbtn-l_v3.png
29 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
45 ms
cdn-ak.favicon.st-hatena.com
390 ms
entry.count.image
154 ms
4873115892
163 ms
globalheader.css
149 ms
api.js
31 ms
272 ms
xd_arbiter.php
270 ms
xd_arbiter.php
376 ms
00209.gif
20 ms
notices.count.json
704 ms
init
208 ms
dropdown@2x.png
189 ms
00072.gif
13 ms
jot.html
3 ms
cdn-ak.favicon.st-hatena.com
241 ms
entry.count.image
173 ms
ref=pd_lpo_sbs_dp_ss_1
207 ms
fastbutton
64 ms
fastbutton
126 ms
fastbutton
151 ms
fastbutton
165 ms
fastbutton
179 ms
fastbutton
163 ms
fastbutton
175 ms
blogicon-regular.woff
325 ms
favicon.ico
88 ms
entry.count.image
175 ms
atp_scraper
175 ms
hatena-follow-button.png
175 ms
https%3A%2F%2Favatars1.githubusercontent.com%2Fu%2F733334%3Fv%3D3%26s%3D400
976 ms
info
245 ms
ads
372 ms
rs=AGLTcCMmxxv5a__MjyaVcD74l1XyH_kiOQ
69 ms
entry.count.image
180 ms
cdn-ak.favicon.st-hatena.com
208 ms
ref=sr_1_cc_3
261 ms
cb=gapi.loaded_0
39 ms
cb=gapi.loaded_1
39 ms
xZQOmYg4x3YaWkTJi1kErvesZW2xOQ-xsNqO47m55DA.woff
63 ms
00000.gif
5 ms
00000.gif
5 ms
expansion_embed.js
14 ms
ads
256 ms
adj
117 ms
adServerESI.aspx
220 ms
beacon
85 ms
skeleton.gif
99 ms
intel-vid3.png
45 ms
lidar.js
21 ms
sbhK2lTE.js
20 ms
pixel
35 ms
push
71 ms
cTrvNaRi.html
9 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
5 ms
pixel
40 ms
pixel
62 ms
66 ms
pixel
47 ms
ads
213 ms
sd
6 ms
00000.gif
6 ms
mosuke5.hateblo.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mosuke5.hateblo.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 Mosuke5.hateblo.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.
mosuke5.hateblo.jp
Open Graph data is detected on the main page of Mosuke 5 Hateblo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: