Tools & Wizards About Us
cu-rire.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cu-rire.jp

haruシャンプーの口コミと効果・ヘアケアはシンプルがいい！

Page Load Speed

6.3 sec in total

First Response

1.1 sec

Resources Loaded

4.8 sec

Page Rendered

307 ms

cu-rire.jp screenshot

About Website

Visit cu-rire.jp now to see the best up-to-date Cu Rire content for Japan and also check out these interesting facts you probably never knew about cu-rire.jp

haruシャンプーは忙しい女性を中心に口コミで効果や魅力が大変評価されています。美髪ケアは土台になる頭皮からきちんとアプローチすることが大切。 haruシャンプーはナチュラルに疲れた髪をケアする厳選素材が話題に。このサイトで頭皮や髪の悩みを持つ方に必見のharuシャンプー口コミや効果について解説します。

Visit cu-rire.jp

Key Findings

We analyzed Cu-rire.jp page load time and found that the first response time was 1.1 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

cu-rire.jp performance score

0

Network Requests Diagram

cu-rire.jp

1134 ms

style.css

244 ms

preset.css

317 ms

margin.css

355 ms

rire.css

321 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 90% of them (91 requests) were addressed to the original Cu-rire.jp, 3% (3 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Code.analysis.shinobi.jp. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Cu-rire.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 722.1 kB (36%)

Content Size

2.0 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 26.7 kB

  • Original 33.8 kB
  • After minification 32.1 kB
  • After compression 7.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 26.7 kB or 79% of the original size.

Image Optimization

-23%

Potential reduce by 356.5 kB

  • Original 1.5 MB
  • After minification 1.2 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. Obviously, Cu Rire needs image optimization as it can save up to 356.5 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-84%

Potential reduce by 239.8 kB

  • Original 285.7 kB
  • After minification 161.0 kB
  • After compression 46.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 239.8 kB or 84% of the original size.

CSS Optimization

-84%

Potential reduce by 99.2 kB

  • Original 118.1 kB
  • After minification 98.1 kB
  • After compression 18.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. Cu-rire.jp needs all CSS files to be minified and compressed as it can save up to 99.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (17%)

Requests Now

100

After Optimization

83

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cu-rire.jp

cu-rire.jp

1134 ms

style.css

style.css

244 ms

preset.css

preset.css

317 ms

margin.css

margin.css

355 ms

rire.css

rire.css

321 ms

jquery.js

jquery.js

724 ms

jquery.easing.js

jquery.easing.js

336 ms

jquery.smoothScroll.js

jquery.smoothScroll.js

425 ms

main.js

main.js

481 ms

main01.jpg

main01.jpg

936 ms

main02.jpg

main02.jpg

551 ms

main03.jpg

main03.jpg

664 ms

main04.jpg

main04.jpg

673 ms

main05.jpg

main05.jpg

402 ms

top_head_logo.png

top_head_logo.png

192 ms

head_twitter.png

head_twitter.png

352 ms

head_facebook.png

head_facebook.png

509 ms

head_instagram.png

head_instagram.png

567 ms

head_wear.png

head_wear.png

670 ms

head_reserve.png

head_reserve.png

720 ms

head_tel.png

head_tel.png

746 ms

head_logo_sp.png

head_logo_sp.png

819 ms

salon_gnavi_sp_btn_off.png

salon_gnavi_sp_btn_off.png

828 ms

salon_foot_access_tb.png

salon_foot_access_tb.png

832 ms

salon_foot_tel_tb.png

salon_foot_tel_tb.png

890 ms

salon_foot_reserve_tb.png

salon_foot_reserve_tb.png

913 ms

salon_gnavi_home.png

salon_gnavi_home.png

986 ms

salon_gnavi_menu.png

salon_gnavi_menu.png

996 ms

salon_gnavi_haircatalog.png

salon_gnavi_haircatalog.png

1003 ms

salon_gnavi_staff.png

salon_gnavi_staff.png

1069 ms

salon_gnavi_blog.png

salon_gnavi_blog.png

1088 ms

salon_gnavi_voice.png

salon_gnavi_voice.png

1123 ms

salon_gnavi_saloninfo.png

salon_gnavi_saloninfo.png

1152 ms

salon_gnavi_movie.png

salon_gnavi_movie.png

1165 ms

salon_gnavi_product.png

salon_gnavi_product.png

1174 ms

salon_gnavi_recruit.png

salon_gnavi_recruit.png

1249 ms

salon_gnavi_sp_home.png

salon_gnavi_sp_home.png

1254 ms

salon_gnavi_sp_menu.png

salon_gnavi_sp_menu.png

1303 ms

salon_gnavi_sp_haircatalog.png

salon_gnavi_sp_haircatalog.png

1310 ms

salon_gnavi_sp_staff.png

salon_gnavi_sp_staff.png

1324 ms

salon_gnavi_sp_blog.png

salon_gnavi_sp_blog.png

1335 ms

salon_gnavi_sp_voice.png

salon_gnavi_sp_voice.png

1420 ms

salon_gnavi_sp_saloninfo.png

salon_gnavi_sp_saloninfo.png

1423 ms

salon_gnavi_sp_movie.png

salon_gnavi_sp_movie.png

1483 ms

sdk.js

sdk.js

14 ms

salon_gnavi_sp_product.png

salon_gnavi_sp_product.png

1449 ms

widgets.js

widgets.js

83 ms

NewScript

NewScript

601 ms

103 ms

xd_arbiter.php

xd_arbiter.php

45 ms

xd_arbiter.php

xd_arbiter.php

67 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

115 ms

salon_gnavi_sp_recruit.png

salon_gnavi_sp_recruit.png

1297 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

47 ms

salon_gnavi_tb_home.png

salon_gnavi_tb_home.png

1148 ms

jot

jot

92 ms

salon_gnavi_tb_menu.png

salon_gnavi_tb_menu.png

1191 ms

salon_gnavi_tb_haircatalog.png

salon_gnavi_tb_haircatalog.png

1084 ms

salon_gnavi_tb_staff.png

salon_gnavi_tb_staff.png

1076 ms

salon_gnavi_tb_blog.png

salon_gnavi_tb_blog.png

1099 ms

NewReceive

NewReceive

412 ms

salon_gnavi_tb_voice.png

salon_gnavi_tb_voice.png

985 ms

salon_gnavi_tb_saloninfo.png

salon_gnavi_tb_saloninfo.png

992 ms

salon_gnavi_tb_movie.png

salon_gnavi_tb_movie.png

1090 ms

salon_gnavi_tb_product.png

salon_gnavi_tb_product.png

1040 ms

salon_gnavi_tb_recruit.png

salon_gnavi_tb_recruit.png

1036 ms

top_head_twitter_sp.png

top_head_twitter_sp.png

996 ms

top_head_facebook_sp.png

top_head_facebook_sp.png

1006 ms

top_head_instagram_sp.png

top_head_instagram_sp.png

1024 ms

top_head_wear_sp.png

top_head_wear_sp.png

1047 ms

top_head_reserve.png

top_head_reserve.png

1023 ms

top_title_news.png

top_title_news.png

1013 ms

top_title_news_sp.png

top_title_news_sp.png

1002 ms

image37-338x450.jpeg

image37-338x450.jpeg

1073 ms

image40-360x450.jpeg

image40-360x450.jpeg

1085 ms

image35-425x450.jpeg

image35-425x450.jpeg

1236 ms

image25-450x388.jpg

image25-450x388.jpg

1056 ms

image23-450x450.jpg

image23-450x450.jpg

1030 ms

image32-338x450.jpeg

image32-338x450.jpeg

1160 ms

image29-363x450.jpeg

image29-363x450.jpeg

1228 ms

image31-450x338.jpeg

image31-450x338.jpeg

1129 ms

top_rightcol_reserve.png

top_rightcol_reserve.png

1068 ms

top_title_sns.png

top_title_sns.png

1067 ms

top_rightcol_twitter_off.png

top_rightcol_twitter_off.png

1194 ms

top_rightcol_instagram_off.png

top_rightcol_instagram_off.png

1177 ms

top_rightcol_facebook_off.png

top_rightcol_facebook_off.png

1157 ms

top_rightcol_wear_off.png

top_rightcol_wear_off.png

1160 ms

top_title_contents.png

top_title_contents.png

1069 ms

top_salon_contentsimg_menu.jpg

top_salon_contentsimg_menu.jpg

1151 ms

top_salon_contentsimg_hair.jpg

top_salon_contentsimg_hair.jpg

1185 ms

top_salon_contentsimg_staff.jpg

top_salon_contentsimg_staff.jpg

1197 ms

top_salon_contentsimg_voice.jpg

top_salon_contentsimg_voice.jpg

1179 ms

top_salon_contentsimg_movie.jpg

top_salon_contentsimg_movie.jpg

1184 ms

top_salon_contentsimg_coupon.jpg

top_salon_contentsimg_coupon.jpg

1094 ms

linebutton_82x20.png

linebutton_82x20.png

1147 ms

salon_foot_pagetop_sp.png

salon_foot_pagetop_sp.png

1190 ms

salon_foot_logo.png

salon_foot_logo.png

1191 ms

salon_foot_pagetop.png

salon_foot_pagetop.png

1201 ms

salon_foot_reserve_sp.png

salon_foot_reserve_sp.png

1189 ms

salon_foot_tel_sp.png

salon_foot_tel_sp.png

1107 ms

salon_foot_access_sp.png

salon_foot_access_sp.png

1142 ms

SEO Factors

cu-rire.jp SEO score

0

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 Cu-rire.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 Cu-rire.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

cu-rire.jp

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