Tools & Wizards About Us
rittor-music.co.jp screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

rittor-music.co.jp

リットーミュージック

Page Load Speed

12.9 sec in total

First Response

353 ms

Resources Loaded

11.6 sec

Page Rendered

879 ms

rittor-music.co.jp screenshot

About Website

Visit rittor-music.co.jp now to see the best up-to-date Rittor Music content for Japan and also check out these interesting facts you probably never knew about rittor-music.co.jp

音楽専門出版社リットーミュージックの公式サイト。楽器や音楽に関する専門雑誌、書籍、楽譜・スコア、教本、教則DVDなどを中心に紹介。初心者からプロまで、音楽ライフをサポートします。

Visit rittor-music.co.jp

Key Findings

We analyzed Rittor-music.co.jp page load time and found that the first response time was 353 ms and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

rittor-music.co.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value20.1 s

0/100

10%

TBT (Total Blocking Time)

Value990 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

rittor-music.co.jp

353 ms

www.rittor-music.co.jp

1209 ms

main.min.css

2133 ms

main.min.js

514 ms

dependency.min.js

1192 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 86% of them (59 requests) were addressed to the original Rittor-music.co.jp, 9% (6 requests) were made to Log1.mobylog.jp and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Rittor-music.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 815.0 kB (59%)

Content Size

1.4 MB

After Optimization

566.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rittor-music.co.jp main page is 1.4 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. 45% of websites need less resources to load. Javascripts take 717.0 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 106.4 kB

  • Original 118.5 kB
  • After minification 117.4 kB
  • After compression 12.2 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 106.4 kB or 90% of the original size.

Image Optimization

-2%

Potential reduce by 6.9 kB

  • Original 296.1 kB
  • After minification 289.2 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. Rittor Music images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 484.6 kB

  • Original 717.0 kB
  • After minification 651.5 kB
  • After compression 232.4 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 484.6 kB or 68% of the original size.

CSS Optimization

-87%

Potential reduce by 217.1 kB

  • Original 249.3 kB
  • After minification 249.3 kB
  • After compression 32.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. Rittor-music.co.jp needs all CSS files to be minified and compressed as it can save up to 217.1 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (73%)

Requests Now

67

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rittor-music.co.jp

rittor-music.co.jp

353 ms

www.rittor-music.co.jp

www.rittor-music.co.jp

1209 ms

main.min.css

main.min.css

2133 ms

main.min.js

main.min.js

514 ms

dependency.min.js

dependency.min.js

1192 ms

main-nomodule.min.js

main-nomodule.min.js

708 ms

gtm.js

gtm.js

184 ms

text.svg

text.svg

347 ms

icon.svg

icon.svg

964 ms

main-nomodule-2e863ffa.js

main-nomodule-2e863ffa.js

2466 ms

js

js

57 ms

bi.js

bi.js

854 ms

fbevents.js

fbevents.js

16 ms

500738.js

500738.js

885 ms

_tag_mobylog.js

_tag_mobylog.js

174 ms

xd_plugin.js

xd_plugin.js

346 ms

msb.php

msb.php

498 ms

xd_jquery_selectors.js

xd_jquery_selectors.js

497 ms

dot.php

dot.php

205 ms

SmoothScrollable-2e3d93c8.js

SmoothScrollable-2e3d93c8.js

496 ms

Togglable-4c283ac2.js

Togglable-4c283ac2.js

534 ms

RotationBannerCarousel-d8317028.js

RotationBannerCarousel-d8317028.js

589 ms

SuggestionSearch-fc6510b0.js

SuggestionSearch-fc6510b0.js

638 ms

LogoBannerList-10804979.js

LogoBannerList-10804979.js

619 ms

MagazineList-37a7312b.js

MagazineList-37a7312b.js

667 ms

ProductList-5cf3276f.js

ProductList-5cf3276f.js

903 ms

NewsList-8f58e238.js

NewsList-8f58e238.js

1032 ms

WeeklyRecommendWidget-75ee6a19.js

WeeklyRecommendWidget-75ee6a19.js

1094 ms

dom-6b32e839.js

dom-6b32e839.js

790 ms

banner-ace7dda4.js

banner-ace7dda4.js

686 ms

ArrowButton-a568f93a.js

ArrowButton-a568f93a.js

1006 ms

validation-d08b633e.js

validation-d08b633e.js

929 ms

dayjs.min-53d0aae1.js

dayjs.min-53d0aae1.js

1105 ms

propTypes-fec6664a.js

propTypes-fec6664a.js

1177 ms

logger-c1300db4.js

logger-c1300db4.js

1203 ms

useDispatch-d4367490.js

useDispatch-d4367490.js

1335 ms

useSelector-902fa5f5.js

useSelector-902fa5f5.js

1439 ms

Fetchable-18bb02b5.js

Fetchable-18bb02b5.js

1635 ms

es.array.find-4a9df50a.js

es.array.find-4a9df50a.js

1688 ms

conversion-f5f905b0.js

conversion-f5f905b0.js

1712 ms

Transition-c58f402a.js

Transition-c58f402a.js

1880 ms

GenericTextNavi-dd3de3f7.js

GenericTextNavi-dd3de3f7.js

1937 ms

useKeyPressEvent-b6308f2f.js

useKeyPressEvent-b6308f2f.js

1997 ms

product-e944cb9b.js

product-e944cb9b.js

2138 ms

magazine-eef6ff50.js

magazine-eef6ff50.js

2030 ms

useMagazineListResource-b8f00ae4.js

useMagazineListResource-b8f00ae4.js

2153 ms

FetchableProductList-35d86e6a.js

FetchableProductList-35d86e6a.js

2267 ms

es.array.slice-93089e6d.js

es.array.slice-93089e6d.js

2391 ms

GenericList-70319056.js

GenericList-70319056.js

2521 ms

CategoryListNavi-6dd9df62.js

CategoryListNavi-6dd9df62.js

2551 ms

ProductListItemPlaceholder-75e05d09.js

ProductListItemPlaceholder-75e05d09.js

2713 ms

news-648598f0.js

news-648598f0.js

2478 ms

NewsList-ed6b4c8c.js

NewsList-ed6b4c8c.js

2478 ms

recommend-e6528dee.js

recommend-e6528dee.js

2629 ms

AssistTextNavi-0eaf0043.js

AssistTextNavi-0eaf0043.js

2653 ms

mergeMultipleErrors-dd0a8e34.js

mergeMultipleErrors-dd0a8e34.js

2773 ms

posts.json

posts.json

1548 ms

04b9c648dcb6efd454feb8c355e91aa8.jpeg

04b9c648dcb6efd454feb8c355e91aa8.jpeg

2497 ms

1f3eb2868d0bb0a28b44f3e9afebd53d.jpg

1f3eb2868d0bb0a28b44f3e9afebd53d.jpg

2474 ms

posts.json

posts.json

758 ms

posts.json

posts.json

1266 ms

posts.json

posts.json

956 ms

posts.json

posts.json

667 ms

logo_guitar_grey_1.png

logo_guitar_grey_1.png

643 ms

logo_bass_grey_1.png

logo_bass_grey_1.png

967 ms

logo_drums_grey_1.png

logo_drums_grey_1.png

1074 ms

logo_snrec_grey.png

logo_snrec_grey.png

1158 ms

logo_agm_grey.png

logo_agm_grey.png

1320 ms

logo_ukulele_grey_1.png

logo_ukulele_grey_1.png

1460 ms

Accessibility Review

rittor-music.co.jp accessibility score

97

Accessibility Issues

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.

Best Practices

rittor-music.co.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

rittor-music.co.jp SEO score

99

Search Engine Optimization Advices

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 Rittor-music.co.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 Rittor-music.co.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

rittor-music.co.jp

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