Tools & Wizards About Us
mdrs1.hateblo.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mdrs1.hateblo.jp

シバイチのトレーディング千夜一夜

Page Load Speed

6.6 sec in total

First Response

522 ms

Resources Loaded

5.4 sec

Page Rendered

628 ms

mdrs1.hateblo.jp screenshot

About Website

Welcome to mdrs1.hateblo.jp homepage info - get ready to check Mdrs 1 Hateblo best content for Japan right away, or after learning these important things about mdrs1.hateblo.jp

投資の考え方と具体的な技術について書き綴っています。リスク管理と短期～中期の株式トレーディングについてが話題の中心ですが、その他の投資にも応用できますよ。

Visit mdrs1.hateblo.jp

Key Findings

We analyzed Mdrs1.hateblo.jp page load time and found that the first response time was 522 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

mdrs1.hateblo.jp performance score

0

Network Requests Diagram

mdrs1.hateblo.jp

522 ms

blog.css

650 ms

c36977e501177d16370ba733918bfa69712e1cc8

345 ms

hatena_afc_ydn-compiled.js

353 ms

hatena_dfp2.js

612 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Mdrs1.hateblo.jp, 11% (14 requests) were made to Apis.google.com and 7% (9 requests) were made to Cdn.api.b.hatena.ne.jp. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Cdn-ak.f.st-hatena.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (41%)

Content Size

3.6 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mdrs1.hateblo.jp main page is 3.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. 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. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 119.8 kB

  • Original 145.7 kB
  • After minification 132.3 kB
  • After compression 25.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 119.8 kB or 82% of the original size.

Image Optimization

-17%

Potential reduce by 332.7 kB

  • Original 2.0 MB
  • After minification 1.6 MB

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. Obviously, Mdrs 1 Hateblo needs image optimization as it can save up to 332.7 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 948.4 kB

  • Original 1.4 MB
  • After minification 1.2 MB
  • After compression 434.0 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 948.4 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 82.3 kB

  • Original 98.6 kB
  • After minification 80.2 kB
  • After compression 16.3 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. Mdrs1.hateblo.jp needs all CSS files to be minified and compressed as it can save up to 82.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (52%)

Requests Now

124

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mdrs 1 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 52 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

mdrs1.hateblo.jp

mdrs1.hateblo.jp

522 ms

blog.css

blog.css

650 ms

c36977e501177d16370ba733918bfa69712e1cc8

c36977e501177d16370ba733918bfa69712e1cc8

345 ms

hatena_afc_ydn-compiled.js

hatena_afc_ydn-compiled.js

353 ms

hatena_dfp2.js

hatena_dfp2.js

612 ms

HatenaStar.js

HatenaStar.js

1269 ms

widgets.js

widgets.js

126 ms

plusone.js

plusone.js

86 ms

bookmark_button.js

bookmark_button.js

671 ms

react-with-addons.min.js

react-with-addons.min.js

49 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

49 ms

jquery-ui.1.10.0.custom.min.js

jquery-ui.1.10.0.custom.min.js

49 ms

jquery.flot.0.8.3.js

jquery.flot.0.8.3.js

47 ms

jquery.flot.time.0.8.3.js

jquery.flot.time.0.8.3.js

47 ms

hatenablog.js

hatenablog.js

1979 ms

texts-ja.js

texts-ja.js

667 ms

api.js

api.js

72 ms

20160229063406.jpg

20160229063406.jpg

58 ms

tic.png

tic.png

986 ms

profile.gif

profile.gif

279 ms

button-only.gif

button-only.gif

280 ms

theme8.png

theme8.png

191 ms

20160229055152.jpg

20160229055152.jpg

815 ms

20041024012644.jpg

20041024012644.jpg

1211 ms

20160224063812.jpg

20160224063812.jpg

1642 ms

20100504180600.jpg

20100504180600.jpg

1041 ms

20160222063015.jpg

20160222063015.jpg

1278 ms

20160219060229.jpg

20160219060229.jpg

1405 ms

profile.gif

profile.gif

202 ms

banner.png

banner.png

985 ms

analytics.js

analytics.js

28 ms

20130306233715.png

20130306233715.png

3852 ms

show_ads.js

show_ads.js

17 ms

collect

collect

12 ms

collect

collect

60 ms

collect

collect

9 ms

collect

collect

105 ms

zrt_lookup.html

zrt_lookup.html

37 ms

show_ads_impl.js

show_ads_impl.js

53 ms

ads

ads

245 ms

osd.js

osd.js

32 ms

ads

ads

209 ms

ads

ads

104 ms

search_w.png

search_w.png

197 ms

audience

audience

327 ms

jstag

jstag

126 ms

gpt.js

gpt.js

125 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

86 ms

pubads_impl_81.js

pubads_impl_81.js

27 ms

222 ms

208 ms

202 ms

205 ms

202 ms

377 ms

392 ms

container.html

container.html

8 ms

dfp.config.json

dfp.config.json

152 ms

reset.css

reset.css

10 ms

entry-button.css

entry-button.css

10 ms

bbtn-l_v3.png

bbtn-l_v3.png

6 ms

ads

ads

305 ms

blogs

blogs

224 ms

recaptcha__en.js

recaptcha__en.js

40 ms

sdk.js

sdk.js

194 ms

hatena_bigmining.js

hatena_bigmining.js

31 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

55 ms

log

log

317 ms

show.json

show.json

845 ms

archive_module

archive_module

204 ms

notices.count.json

notices.count.json

855 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

104 ms

globalheader.css

globalheader.css

174 ms

api.js

api.js

25 ms

39 ms

xd_arbiter.php

xd_arbiter.php

251 ms

xd_arbiter.php

xd_arbiter.php

310 ms

ajs.php

ajs.php

461 ms

ads

ads

220 ms

log

log

201 ms

notices.count.json

notices.count.json

544 ms

init

init

215 ms

dropdown@2x.png

dropdown@2x.png

160 ms

ajs.php

ajs.php

375 ms

ads

ads

206 ms

jot.html

jot.html

27 ms

fastbutton

fastbutton

82 ms

fastbutton

fastbutton

93 ms

fastbutton

fastbutton

131 ms

fastbutton

fastbutton

159 ms

fastbutton

fastbutton

133 ms

fastbutton

fastbutton

156 ms

fastbutton

fastbutton

139 ms

blogicon-regular.woff

blogicon-regular.woff

315 ms

ads

ads

235 ms

hatena-follow-button.png

hatena-follow-button.png

170 ms

info

info

205 ms

adsbygoogle.js

adsbygoogle.js

12 ms

lg.php

lg.php

176 ms

ca-pub-5973519624968530.js

ca-pub-5973519624968530.js

21 ms

ads

ads

200 ms

rs=AGLTcCPNzfuyiR2SRdOysTpopVYTZZwedQ

rs=AGLTcCPNzfuyiR2SRdOysTpopVYTZZwedQ

20 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

44 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

44 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

79 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

46 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

46 ms

ads

ads

177 ms

lg.php

lg.php

168 ms

alternatead-300x250-red.html

alternatead-300x250-red.html

7 ms

ad

ad

363 ms

alternatead-300x250-red-pc.html

alternatead-300x250-red-pc.html

5 ms

ad

ad

384 ms

45851_banner.png

45851_banner.png

509 ms

45914_banner.png

45914_banner.png

669 ms

hatena-star-add-button.png

hatena-star-add-button.png

172 ms

comment.gif

comment.gif

353 ms

entries.json

entries.json

476 ms

dmp

dmp

294 ms

gtm.js

gtm.js

52 ms

tdim-0.11.2.js

tdim-0.11.2.js

6 ms

share_button.php

share_button.php

54 ms

share_button.php

share_button.php

64 ms

segment

segment

299 ms

share_button.php

share_button.php

69 ms

share_button.php

share_button.php

80 ms

share_button.php

share_button.php

79 ms

share_button.php

share_button.php

90 ms

share_button.php

share_button.php

85 ms

-1cfYrhulAt.js

-1cfYrhulAt.js

299 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

345 ms

pageviews

pageviews

7 ms

SEO Factors

mdrs1.hateblo.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mdrs1.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 Mdrs1.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.

Social Sharing Optimization

mdrs1.hateblo.jp

Open Graph data is detected on the main page of Mdrs 1 Hateblo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: