Access recochoku.jp. 音楽ダウンロード・ランキング・歌詞・音楽配信サイト | レコチョク

recochoku.jp screenshot

3

Performance

Renders faster than
20% of other websites
78

Accessibility

Visual factors better than
that of 46% of websites
75

Best Practices

More advanced features
available than in
36% of websites
98

SEO

Google-friendlier than
92% of websites

First Response

2.2 sec

Resources Loaded

9.9 sec

Page Rendered

539 ms

recochoku.jp screenshot

About Website

Welcome to recochoku.jp homepage info - get ready to check Recochoku best content for Japan right away, or after learning these important things about recochoku.jp

レコチョクは、音楽ダウンロード・ランキング・歌詞を楽しめる音楽配信サイト・音楽アプリです。邦楽/J-POP・洋楽・ドラマ主題歌・アニソンなど最新曲・流行曲・ヒット曲を配信中！（iPhone/Android対応の音楽アプリ）1曲から購入可能で、無料で人気曲の歌詞や音楽試聴も可能です。

Visit recochoku.jp

Key Findings

We analyzed Recochoku.jp page load time and found that the first response time was 2.2 sec and then it took 10.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.

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

3/100

10%

LCP (Largest Contentful Paint)

Value21.8 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value8,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.534

14/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

recochoku.jp

2194 ms

import.css

302 ms

jquery1.7.1.min.js

744 ms

rollover.js

328 ms

jquery.easing.1.3.js

326 ms

Our browser made a total of 231 requests to load all elements on the main page. We found that 7% of them (17 requests) were addressed to the original Recochoku.jp, 81% (186 requests) were made to Img.lap.recochoku.jp and 2% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Recochoku.jp.

Content Size

7.0 MB

After Optimization

6.1 MB

In fact, the total size of Recochoku.jp main page is 7.0 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. 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. Images take 6.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 132.2 kB

Original 160.1 kB
After minification 158.8 kB
After compression 27.9 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 132.2 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 450.0 kB

Original 6.4 MB
After minification 5.9 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. Recochoku images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 190.1 kB

Original 296.6 kB
After minification 258.0 kB
After compression 106.5 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 190.1 kB or 64% of the original size.

CSS Optimization

-88%

Potential reduce by 141.8 kB

Original 161.1 kB
After minification 131.5 kB
After compression 19.3 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. Recochoku.jp needs all CSS files to be minified and compressed as it can save up to 141.8 kB or 88% of the original size.

Requests Now

229

After Optimization

170

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

Accessibility Issues

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

Buttons do not have an accessible name

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 keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

Search Engine Optimization Advices

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

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Recochoku.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 Recochoku.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

recochoku.jp

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