Tools & Wizards About Us
reraku.jp screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

reraku.jp

リラクゼーションサロン | マッサージ・整体ファンにも大人気のRe.Ra.Ku グループ(リラクグループ)

Page Load Speed

16.9 sec in total

First Response

1.3 sec

Resources Loaded

14.9 sec

Page Rendered

684 ms

reraku.jp screenshot

About Website

Click here to check amazing Re Ra Ku content for Japan. Otherwise, check out these important facts you probably never knew about reraku.jp

全国に約300店舗のリラクゼーションサロンを展開。肩甲骨と骨盤に着目したボディケアでお客様の疲労を撃退し、マッサージ好きなあなたの健康で快適な生活をサポートします。

Visit reraku.jp

Key Findings

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

reraku.jp performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value44.8 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,380 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.578

12/100

15%

TTI (Time to Interactive)

Value29.2 s

0/100

10%

Network Requests Diagram

reraku.jp

1301 ms

styles.css

360 ms

top.css

361 ms

js.js

366 ms

widgets.js

89 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 79% of them (71 requests) were addressed to the original Reraku.jp, 3% (3 requests) were made to Platform.twitter.com and 3% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (11.6 sec) belongs to the original domain Reraku.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 532.8 kB (5%)

Content Size

11.7 MB

After Optimization

11.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Reraku.jp main page is 11.7 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. 40% of websites need less resources to load. Images take 11.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 25.9 kB

  • Original 33.4 kB
  • After minification 29.7 kB
  • After compression 7.5 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. This page needs HTML code to be minified as it can gain 3.7 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.9 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 99.9 kB

  • Original 11.1 MB
  • After minification 11.0 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. Re Ra Ku images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 192.0 kB

  • Original 312.3 kB
  • After minification 308.0 kB
  • After compression 120.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 192.0 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 215.0 kB

  • Original 259.9 kB
  • After minification 253.7 kB
  • After compression 44.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. Reraku.jp needs all CSS files to be minified and compressed as it can save up to 215.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (31%)

Requests Now

86

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

reraku.jp

reraku.jp

1301 ms

styles.css

styles.css

360 ms

top.css

top.css

361 ms

js.js

js.js

366 ms

widgets.js

widgets.js

89 ms

common.css

common.css

347 ms

head_navi.css

head_navi.css

344 ms

header.css

header.css

359 ms

footer.css

footer.css

359 ms

image_navigation.css

image_navigation.css

364 ms

jquery.js

jquery.js

913 ms

jquery.imageNavigation.js

jquery.imageNavigation.js

338 ms

jquery.smooth.js

jquery.smooth.js

345 ms

Rollover.js

Rollover.js

366 ms

analytics.js

analytics.js

49 ms

gtm.js

gtm.js

49 ms

logo.png

logo.png

339 ms

utility_yururila.png

utility_yururila.png

360 ms

utility_news.jpg

utility_news.jpg

364 ms

utility_column.jpg

utility_column.jpg

365 ms

utility_blog.jpg

utility_blog.jpg

458 ms

search.png

search.png

458 ms

menu_bg.png

menu_bg.png

705 ms

menu1.png

menu1.png

719 ms

menu2.png

menu2.png

722 ms

menu3.png

menu3.png

728 ms

menu4.png

menu4.png

722 ms

menu5.png

menu5.png

737 ms

mail.png

mail.png

1084 ms

line.png

line.png

1076 ms

5437575a5b665.png

5437575a5b665.png

1973 ms

52aa46c1ddedc.png

52aa46c1ddedc.png

2178 ms

52aa46e54a962.png

52aa46e54a962.png

1932 ms

5437576fa7e56.jpg

5437576fa7e56.jpg

1272 ms

52aa466521c1b.jpg

52aa466521c1b.jpg

1434 ms

52aa46929645b.jpg

52aa46929645b.jpg

1464 ms

543757627db40.jpg

543757627db40.jpg

2001 ms

52aa465043a0b.jpg

52aa465043a0b.jpg

1935 ms

52aa46845e642.jpg

52aa46845e642.jpg

2009 ms

52675d2b49586.png

52675d2b49586.png

2433 ms

5510d0db76659.png

5510d0db76659.png

2650 ms

5363653cf186a.jpg

5363653cf186a.jpg

2698 ms

button_list.jpg

button_list.jpg

2380 ms

56cd91a5af349.png

56cd91a5af349.png

2919 ms

533e85d835985.png

533e85d835985.png

2720 ms

553715c0f2c0e.jpg

553715c0f2c0e.jpg

3887 ms

button_studiolist.jpg

button_studiolist.jpg

2788 ms

slide_new.png

slide_new.png

3007 ms

studio_0000000073_02.jpg

studio_0000000073_02.jpg

4220 ms

studio_0000000115_02.jpg

studio_0000000115_02.jpg

6010 ms

studio_0000000195_02.jpg

studio_0000000195_02.jpg

5831 ms

studio_0000000169_02.jpg

studio_0000000169_02.jpg

6656 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

137 ms

like.php

like.php

149 ms

tkp0rD7kG-8

tkp0rD7kG-8

112 ms

collect

collect

27 ms

collect

collect

63 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

81 ms

www-embed-player.js

www-embed-player.js

109 ms

base.js

base.js

175 ms

tweet_button.6a78875565a912489e9aef879c881358.en.html

tweet_button.6a78875565a912489e9aef879c881358.en.html

44 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

96 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

95 ms

studio_0000000175_02.jpg

studio_0000000175_02.jpg

5192 ms

studio_0000000136_02.jpg

studio_0000000136_02.jpg

7803 ms

studio_0000000019_02.jpg

studio_0000000019_02.jpg

5149 ms

studio_0000000192_01.jpg

studio_0000000192_01.jpg

8003 ms

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

35 ms

ad_status.js

ad_status.js

70 ms

jot

jot

112 ms

studio_0000000068_01.jpg

studio_0000000068_01.jpg

7591 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

85 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

97 ms

studio_0000000057_02.jpg

studio_0000000057_02.jpg

6741 ms

studio_0000000123_02.jpg

studio_0000000123_02.jpg

7470 ms

studio_0000000170_01.jpg

studio_0000000170_01.jpg

8108 ms

studio_0000000078_02.jpg

studio_0000000078_02.jpg

9000 ms

studio_0000000145_02.jpg

studio_0000000145_02.jpg

11586 ms

studio_0000000153_02.jpg

studio_0000000153_02.jpg

8647 ms

523273ce5f4f7.jpg

523273ce5f4f7.jpg

7819 ms

523272d81bb28.jpg

523272d81bb28.jpg

7972 ms

52328e55e8bf0.jpg

52328e55e8bf0.jpg

7985 ms

5649e3813fb00.jpg

5649e3813fb00.jpg

7910 ms

pagetop.png

pagetop.png

7978 ms

icon_newopen.png

icon_newopen.png

7963 ms

icon_campaign.png

icon_campaign.png

7643 ms

icon_info.png

icon_info.png

7793 ms

icon_media.png

icon_media.png

7777 ms

foot_logo.png

foot_logo.png

7807 ms

footer_bar_1.png

footer_bar_1.png

7900 ms

Accessibility Review

reraku.jp accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

reraku.jp best practices score

83

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

High

Browser errors were logged to the console

SEO Factors

reraku.jp SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Reraku.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 Reraku.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

reraku.jp

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