Access taku-blog.jp. Taku's Blog++

taku-blog.jp screenshot

54

Performance

Renders faster than
72% of other websites
63

Accessibility

Visual factors better than
that of 28% of websites
67

Best Practices

More advanced features
available than in
24% of websites
84

SEO

Google-friendlier than
53% of websites

First Response

895 ms

Resources Loaded

5 sec

Page Rendered

13.9 sec

taku-blog.jp screenshot

About Website

Click here to check amazing Taku Blog content for Japan. Otherwise, check out these important facts you probably never knew about taku-blog.jp

Visit taku-blog.jp

Key Findings

We analyzed Taku-blog.jp page load time and found that the first response time was 895 ms and then it took 18.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

taku-blog.jp

895 ms

jm_style.css

1184 ms

style.css

188 ms

cookie.js

360 ms

script.js

190 ms

Our browser made a total of 175 requests to load all elements on the main page. We found that 2% of them (4 requests) were addressed to the original Taku-blog.jp, 77% (134 requests) were made to Img-cdn.jg.jugem.jp and 6% (11 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Img-cdn.jg.jugem.jp.

Content Size

30.3 MB

After Optimization

28.2 MB

In fact, the total size of Taku-blog.jp main page is 30.3 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. 85% 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 30.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 124.3 kB

Original 149.1 kB
After minification 134.3 kB
After compression 24.8 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 124.3 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 2.0 MB

Original 30.1 MB
After minification 28.2 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. Taku Blog images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 32.9 kB

Original 54.2 kB
After minification 54.0 kB
After compression 21.3 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 32.9 kB or 61% of the original size.

CSS Optimization

-85%

Potential reduce by 10.2 kB

Original 12.1 kB
After minification 8.0 kB
After compression 1.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. Taku-blog.jp needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 85% of the original size.

Requests Now

171

After Optimization

154

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

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.

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Taku-blog.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 Taku-blog.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

taku-blog.jp

Open Graph description is not detected on the main page of Taku Blog. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: