Tools & Wizards About Us
terurou.hateblo.jp screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

terurou.hateblo.jp

terurouメモ

Page Load Speed

8.1 sec in total

First Response

485 ms

Resources Loaded

6.2 sec

Page Rendered

1.5 sec

terurou.hateblo.jp screenshot

About Website

Click here to check amazing Terurou Hateblo content for Japan. Otherwise, check out these important facts you probably never knew about terurou.hateblo.jp

terurouメモ

Visit terurou.hateblo.jp

Key Findings

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

Performance Metrics

terurou.hateblo.jp performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value4,190 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value27.4 s

0/100

10%

Network Requests Diagram

terurou.hateblo.jp

485 ms

blog.css

758 ms

01e3b744893ae666ca55e57ce15fd4bb12b24c3d

457 ms

hatena_afc_ydn-compiled.js

633 ms

widgets.js

6 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Terurou.hateblo.jp, 10% (13 requests) were made to Apis.google.com and 7% (9 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Blog.st-hatena.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (68%)

Content Size

1.8 MB

After Optimization

594.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Terurou.hateblo.jp main page is 1.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. 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 161.3 kB

  • Original 194.7 kB
  • After minification 167.7 kB
  • After compression 33.4 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 27.0 kB, which is 14% 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 161.3 kB or 83% of the original size.

Image Optimization

-22%

Potential reduce by 33.1 kB

  • Original 151.6 kB
  • After minification 118.5 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. Obviously, Terurou Hateblo needs image optimization as it can save up to 33.1 kB or 22% 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 958.0 kB

  • Original 1.4 MB
  • After minification 1.2 MB
  • After compression 425.8 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 958.0 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. Terurou.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 73 (57%)

Requests Now

128

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

terurou.hateblo.jp

terurou.hateblo.jp

485 ms

blog.css

blog.css

758 ms

01e3b744893ae666ca55e57ce15fd4bb12b24c3d

01e3b744893ae666ca55e57ce15fd4bb12b24c3d

457 ms

hatena_afc_ydn-compiled.js

hatena_afc_ydn-compiled.js

633 ms

widgets.js

widgets.js

6 ms

hatena_dfp2.js

hatena_dfp2.js

439 ms

HatenaStar.js

HatenaStar.js

1461 ms

widgets.js

widgets.js

54 ms

plusone.js

plusone.js

105 ms

bookmark_button.js

bookmark_button.js

663 ms

react-with-addons.min.js

react-with-addons.min.js

39 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

52 ms

jquery.flot.0.8.3.js

jquery.flot.0.8.3.js

52 ms

jquery.flot.time.0.8.3.js

jquery.flot.time.0.8.3.js

49 ms

hatenablog.js

hatenablog.js

1792 ms

texts-ja.js

texts-ja.js

622 ms

api.js

api.js

66 ms

profile.gif

profile.gif

558 ms

button-only.gif

button-only.gif

191 ms

analytics.js

analytics.js

39 ms

show_ads.js

show_ads.js

19 ms

zrt_lookup.html

zrt_lookup.html

30 ms

show_ads_impl.js

show_ads_impl.js

49 ms

ads

ads

246 ms

osd.js

osd.js

19 ms

ads

ads

195 ms

ads

ads

126 ms

search_g.png

search_g.png

155 ms

audience

audience

482 ms

jstag

jstag

72 ms

gpt.js

gpt.js

70 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

58 ms

pubads_impl_81.js

pubads_impl_81.js

26 ms

369 ms

369 ms

436 ms

434 ms

462 ms

465 ms

489 ms

container.html

container.html

8 ms

blogs

blogs

195 ms

recaptcha__en.js

recaptcha__en.js

161 ms

sdk.js

sdk.js

67 ms

tweet.04d20138f67ab41d6b4af6cc583926d9.js

tweet.04d20138f67ab41d6b4af6cc583926d9.js

60 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

60 ms

user.segment.json

user.segment.json

184 ms

hatena_bigmining.js

hatena_bigmining.js

119 ms

show.json

show.json

1172 ms

archive_module

archive_module

236 ms

notices.count.json

notices.count.json

883 ms

reset.css

reset.css

70 ms

entry-button.css

entry-button.css

71 ms

dfp.config.json

dfp.config.json

389 ms

syndication

syndication

176 ms

tweets.json

tweets.json

204 ms

bbtn-l_v3.png

bbtn-l_v3.png

49 ms

330 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

59 ms

xd_arbiter.php

xd_arbiter.php

70 ms

xd_arbiter.php

xd_arbiter.php

95 ms

globalheader.css

globalheader.css

153 ms

widgets.js

widgets.js

56 ms

api.js

api.js

66 ms

tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css

tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css

6 ms

tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css

tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css

10 ms

profile_normal.gif

profile_normal.gif

224 ms

CRXbTOCUsAUpDDI.png:large

CRXbTOCUsAUpDDI.png:large

462 ms

notices.count.json

notices.count.json

587 ms

init

init

245 ms

dropdown@2x.png

dropdown@2x.png

191 ms

ads

ads

427 ms

fastbutton

fastbutton

67 ms

fastbutton

fastbutton

116 ms

fastbutton

fastbutton

119 ms

fastbutton

fastbutton

200 ms

fastbutton

fastbutton

172 ms

fastbutton

fastbutton

102 ms

fastbutton

fastbutton

211 ms

jot.html

jot.html

17 ms

blogicon-regular.woff

blogicon-regular.woff

306 ms

info

info

275 ms

hatena-follow-button.png

hatena-follow-button.png

169 ms

rs=AGLTcCMjK4CJMIdNJ3yzirfRYfXhXxdyVw

rs=AGLTcCMjK4CJMIdNJ3yzirfRYfXhXxdyVw

67 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

53 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

57 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

91 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

18 ms

ajs.php

ajs.php

379 ms

ads

ads

184 ms

profile.gif

profile.gif

452 ms

profile.gif

profile.gif

377 ms

profile.gif

profile.gif

390 ms

ajs.php

ajs.php

345 ms

ads

ads

217 ms

adsbygoogle.js

adsbygoogle.js

6 ms

lg.php

lg.php

192 ms

ca-pub-5973519624968530.js

ca-pub-5973519624968530.js

22 ms

ads

ads

259 ms

ads

ads

257 ms

ads

ads

181 ms

lg.php

lg.php

180 ms

16612277218538372389

16612277218538372389

42 ms

abg.js

abg.js

26 ms

m_js_controller.js

m_js_controller.js

39 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

21 ms

s

s

35 ms

redir.html

redir.html

48 ms

x_button_blue2.png

x_button_blue2.png

34 ms

push

push

53 ms

alternatead-300x250-red-pc.html

alternatead-300x250-red-pc.html

189 ms

iframe.html

iframe.html

13 ms

pixel

pixel

14 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

3 ms

ad

ad

526 ms

45912_banner.png

45912_banner.png

668 ms

activeview

activeview

15 ms

activeview

activeview

39 ms

hatena-star-add-button.png

hatena-star-add-button.png

149 ms

comment.gif

comment.gif

360 ms

entries.json

entries.json

512 ms

dmp

dmp

343 ms

gtm.js

gtm.js

29 ms

tdim-0.11.2.js

tdim-0.11.2.js

29 ms

segment

segment

344 ms

share_button.php

share_button.php

107 ms

share_button.php

share_button.php

178 ms

share_button.php

share_button.php

178 ms

share_button.php

share_button.php

181 ms

share_button.php

share_button.php

166 ms

share_button.php

share_button.php

184 ms

share_button.php

share_button.php

174 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

79 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

129 ms

Accessibility Review

terurou.hateblo.jp accessibility score

90

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Best Practices

terurou.hateblo.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

terurou.hateblo.jp SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Terurou.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 Terurou.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

terurou.hateblo.jp

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