Tools & Wizards About Us
hidekikaji.net screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hidekikaji.net

Kaji Hideki

Page Load Speed

2 sec in total

First Response

213 ms

Resources Loaded

1.1 sec

Page Rendered

734 ms

hidekikaji.net screenshot

About Website

Welcome to hidekikaji.net homepage info - get ready to check Hideki Kaji best content for Japan right away, or after learning these important things about hidekikaji.net

Kaji Hideki Official Website

Visit hidekikaji.net

Key Findings

We analyzed Hidekikaji.net page load time and found that the first response time was 213 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

hidekikaji.net performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.35

31/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

hidekikaji.net

213 ms

pre_tumblelog.js

116 ms

css

130 ms

css

147 ms

css

160 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hidekikaji.net, 40% (32 requests) were made to Static.tumblr.com and 14% (11 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (392 ms) relates to the external source Platform.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.8 kB (42%)

Content Size

458.2 kB

After Optimization

264.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hidekikaji.net main page is 458.2 kB. 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. HTML takes 215.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 175.4 kB

  • Original 215.1 kB
  • After minification 205.5 kB
  • After compression 39.7 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 175.4 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 3.0 kB

  • Original 109.6 kB
  • After minification 106.6 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. Hideki Kaji images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 6.8 kB

  • Original 100.7 kB
  • After minification 100.7 kB
  • After compression 93.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-26%

Potential reduce by 8.6 kB

  • Original 32.8 kB
  • After minification 32.0 kB
  • After compression 24.2 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. Hidekikaji.net needs all CSS files to be minified and compressed as it can save up to 8.6 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (75%)

Requests Now

67

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hideki Kaji. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hidekikaji.net

hidekikaji.net

213 ms

pre_tumblelog.js

pre_tumblelog.js

116 ms

css

css

130 ms

css

css

147 ms

css

css

160 ms

lib-normalize.css

lib-normalize.css

113 ms

lib-elements.css

lib-elements.css

115 ms

lib-animate.css

lib-animate.css

113 ms

font-awesome.min.css

font-awesome.min.css

136 ms

slick-nav.css

slick-nav.css

113 ms

slick_tumblr.css

slick_tumblr.css

112 ms

colorbox_tumblr.css

colorbox_tumblr.css

122 ms

tooltipster.css

tooltipster.css

125 ms

style_tumblr.css

style_tumblr.css

126 ms

style-posts.css

style-posts.css

127 ms

style-posts-typography.css

style-posts-typography.css

126 ms

customizer-colors.css

customizer-colors.css

128 ms

customizer-fonts.css

customizer-fonts.css

130 ms

style-responsive.css

style-responsive.css

132 ms

moment.min.js

moment.min.js

136 ms

widgets.js

widgets.js

392 ms

pinit.js

pinit.js

124 ms

bilmur.min.js

bilmur.min.js

128 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

119 ms

stylesheet.css

stylesheet.css

119 ms

wp-jquery.js

wp-jquery.js

131 ms

wp-jquery-migrate.min.js

wp-jquery-migrate.min.js

131 ms

lib-modernizr.js

lib-modernizr.js

134 ms

lib-placeholder.js

lib-placeholder.js

134 ms

jquery.fitvids.js

jquery.fitvids.js

130 ms

slick-nav.js

slick-nav.js

136 ms

sticky-kit.js

sticky-kit.js

134 ms

slick.min.js

slick.min.js

136 ms

colorbox.min.js

colorbox.min.js

136 ms

tooltipster.js

tooltipster.js

135 ms

imagesloaded.js

imagesloaded.js

135 ms

instafeed.min.js

instafeed.min.js

136 ms

jflickrfeed.min.js

jflickrfeed.min.js

137 ms

prettysocial.js

prettysocial.js

136 ms

photoset-grid.js

photoset-grid.js

138 ms

functions_tumblr.js

functions_tumblr.js

137 ms

index.build.js

index.build.js

131 ms

tumblr_static_56jeuqexhfwo80cwc8ogw8ksk.png

tumblr_static_56jeuqexhfwo80cwc8ogw8ksk.png

255 ms

9d9f0c46ba30de3edc390dafd5b18191994dd8e6.jpg

9d9f0c46ba30de3edc390dafd5b18191994dd8e6.jpg

379 ms

like_iframe.html

like_iframe.html

234 ms

impixu

impixu

366 ms

g.gif

g.gif

251 ms

recent

recent

314 ms

posts

posts

154 ms

posts

posts

153 ms

posts

posts

167 ms

a0e13ccde92583dfbb84433133ff4bc068fe4f57.jpg

a0e13ccde92583dfbb84433133ff4bc068fe4f57.jpg

141 ms

788474077edd87862522ece08ddbee70c8814166.jpg

788474077edd87862522ece08ddbee70c8814166.jpg

142 ms

106a5714747c84d8a5c04c15519552e7fcf4e29d.jpg

106a5714747c84d8a5c04c15519552e7fcf4e29d.jpg

148 ms

712e05df16751e77dcb96e7d33af674aa99e7b13.jpg

712e05df16751e77dcb96e7d33af674aa99e7b13.jpg

141 ms

09b22337f105232075aee9888a550002b0ad130e.jpg

09b22337f105232075aee9888a550002b0ad130e.jpg

141 ms

c7957b84c96bed968065a1bb95f94e29248dc717.jpg

c7957b84c96bed968065a1bb95f94e29248dc717.jpg

176 ms

eddde0d8cedd444b660d2018d74a3fa88f4e7fc9.jpg

eddde0d8cedd444b660d2018d74a3fa88f4e7fc9.jpg

176 ms

impixu

impixu

182 ms

tumblr_static_c3dbjtm5srccw8cgs4kgggwww.jpg

tumblr_static_c3dbjtm5srccw8cgs4kgggwww.jpg

177 ms

analytics.html

analytics.html

36 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

181 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

204 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

225 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

111 ms

u-440qyriQwlOrhSvowK_l5-fCZJ.ttf

u-440qyriQwlOrhSvowK_l5-fCZJ.ttf

236 ms

u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf

u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf

237 ms

ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZqFCTx8cP.ttf

ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZqFCTx8cP.ttf

283 ms

ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZT1eTx8cP.ttf

ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZT1eTx8cP.ttf

237 ms

login_check.html

login_check.html

36 ms

pinit_main.js

pinit_main.js

91 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

129 ms

g.gif

g.gif

98 ms

consent

consent

142 ms

overlay.png

overlay.png

215 ms

cs.js

cs.js

37 ms

header.build.js

header.build.js

10 ms

exceptions.js

exceptions.js

11 ms

index.build.js

index.build.js

14 ms

cdn.json

cdn.json

73 ms

g.gif

g.gif

26 ms

Accessibility Review

hidekikaji.net accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Links do not have a discernible name

Best Practices

hidekikaji.net 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

SEO Factors

hidekikaji.net SEO score

86

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hidekikaji.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Hidekikaji.net 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

hidekikaji.net

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