Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 42

    SEO

    Google-friendlier than
    18% of websites

Page Load Speed

2.9 sec in total

First Response

763 ms

Resources Loaded

1.9 sec

Page Rendered

294 ms

oto-kanade.net screenshot

About Website

Visit oto-kanade.net now to see the best up-to-date Oto Kanade content and also check out these interesting facts you probably never knew about oto-kanade.net

箏三味線弾きのウェブサイト。演奏会・ライブの情報など

Visit oto-kanade.net

Key Findings

We analyzed Oto-kanade.net page load time and found that the first response time was 763 ms and then it took 2.2 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

oto-kanade.net performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.225

55/100

15%

TTI (Time to Interactive)

Value0.8 s

100/100

10%

Network Requests Diagram

oto-kanade.net

763 ms

style.css

366 ms

kaze_468.jpg

754 ms

miko468_68.jpg

951 ms

oryza24-468.jpg

777 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 69% of them (9 requests) were addressed to the original Oto-kanade.net, 31% (4 requests) were made to Thumbnail.image.rakuten.co.jp. The less responsive or slowest element that took the longest time to load (953 ms) belongs to the original domain Oto-kanade.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.5 kB (7%)

Content Size

332.8 kB

After Optimization

309.3 kB

In fact, the total size of Oto-kanade.net main page is 332.8 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. 15% of websites need less resources to load. Images take 314.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 9.0 kB

  • Original 12.4 kB
  • After minification 12.0 kB
  • After compression 3.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 9.0 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 10.2 kB

  • Original 314.7 kB
  • After minification 304.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. Oto Kanade images are well optimized though.

CSS Optimization

-74%

Potential reduce by 4.2 kB

  • Original 5.7 kB
  • After minification 4.8 kB
  • After compression 1.5 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. Oto-kanade.net needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 74% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oto Kanade. According to our analytics all requests are already optimized.

Accessibility Review

oto-kanade.net accessibility score

65

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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

oto-kanade.net best practices score

75

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

oto-kanade.net SEO score

42

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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oto-kanade.net 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 Oto-kanade.net main page’s claimed encoding is shift_jis. 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

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