Tools & Wizards About Us
osoraku.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

osoraku.com

ヨシタケシンスケ公式web

Page Load Speed

3 sec in total

First Response

604 ms

Resources Loaded

2.3 sec

Page Rendered

102 ms

osoraku.com screenshot

About Website

Click here to check amazing Osoraku content for Japan. Otherwise, check out these important facts you probably never knew about osoraku.com

絵本『りんごかもしれない』などで知られる絵本作家・イラストレーター、ヨシタケシンスケの公式サイトです。

Visit osoraku.com

Key Findings

We analyzed Osoraku.com page load time and found that the first response time was 604 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

osoraku.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

osoraku.com

604 ms

prototype.js

1113 ms

scriptaculous.js

349 ms

lightbox.js

734 ms

lightbox.css

383 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that all of those requests were addressed to Osoraku.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Osoraku.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 189.4 kB (81%)

Content Size

234.3 kB

After Optimization

44.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Osoraku.com main page is 234.3 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. Only 10% of websites need less resources to load. Javascripts take 228.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 3.4 kB

  • Original 4.7 kB
  • After minification 4.3 kB
  • After compression 1.3 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 3.4 kB or 72% of the original size.

JavaScript Optimization

-81%

Potential reduce by 185.0 kB

  • Original 228.0 kB
  • After minification 166.2 kB
  • After compression 43.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 185.0 kB or 81% of the original size.

CSS Optimization

-66%

Potential reduce by 1.1 kB

  • Original 1.6 kB
  • After minification 1.4 kB
  • After compression 559 B

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. Osoraku.com needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (25%)

Requests Now

16

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

osoraku.com

osoraku.com

604 ms

prototype.js

prototype.js

1113 ms

scriptaculous.js

scriptaculous.js

349 ms

lightbox.js

lightbox.js

734 ms

lightbox.css

lightbox.css

383 ms

effects.js

effects.js

187 ms

builder.js

builder.js

192 ms

title.gif

title.gif

188 ms

news01.gif

news01.gif

193 ms

profile01.gif

profile01.gif

186 ms

kaburimono01.gif

kaburimono01.gif

176 ms

sakuhinsyu01.gif

sakuhinsyu01.gif

339 ms

ehon01.gif

ehon01.gif

349 ms

mail01.gif

mail01.gif

368 ms

copy.gif

copy.gif

372 ms

loading.gif

loading.gif

380 ms

closelabel.gif

closelabel.gif

381 ms

Accessibility Review

osoraku.com accessibility score

55

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

Best Practices

osoraku.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

osoraku.com SEO score

58

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Osoraku.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Osoraku.com main page’s claimed encoding is . 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

osoraku.com

Open Graph description is not detected on the main page of Osoraku. 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: