Tools & Wizards About Us
ecoto.rakuten.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ecoto.rakuten.co.jp

CSR | 楽天株式会社

Page Load Speed

9.7 sec in total

First Response

561 ms

Resources Loaded

8.5 sec

Page Rendered

673 ms

ecoto.rakuten.co.jp screenshot

About Website

Visit ecoto.rakuten.co.jp now to see the best up-to-date Ecoto Rakuten content for Japan and also check out these interesting facts you probably never knew about ecoto.rakuten.co.jp

楽天株式会社のCSRトップページです。楽天とつながる皆様とともに、日本を元気に、世界を元気にしていきたい。豊かな生活と社会に貢献する楽天CSRの取り組みについて掲載しています。

Visit ecoto.rakuten.co.jp

Key Findings

We analyzed Ecoto.rakuten.co.jp page load time and found that the first response time was 561 ms and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

ecoto.rakuten.co.jp performance score

0

Network Requests Diagram

ecoto.rakuten.co.jp

561 ms

502 ms

common.css

329 ms

layout.css

352 ms

common.css

353 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ecoto.rakuten.co.jp, 89% (65 requests) were made to Corp.rakuten.co.jp and 4% (3 requests) were made to Jp.rakuten-static.com. The less responsive or slowest element that took the longest time to load (4.8 sec) relates to the external source Corp.rakuten.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 354.5 kB (23%)

Content Size

1.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ecoto.rakuten.co.jp main page is 1.6 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. 25% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 26.4 kB

  • Original 34.6 kB
  • After minification 30.0 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 4.5 kB, which is 13% 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 26.4 kB or 76% of the original size.

Image Optimization

-8%

Potential reduce by 91.7 kB

  • Original 1.2 MB
  • After minification 1.1 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. Ecoto Rakuten images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 198.8 kB

  • Original 301.2 kB
  • After minification 291.8 kB
  • After compression 102.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 198.8 kB or 66% of the original size.

CSS Optimization

-80%

Potential reduce by 37.6 kB

  • Original 46.9 kB
  • After minification 34.2 kB
  • After compression 9.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. Ecoto.rakuten.co.jp needs all CSS files to be minified and compressed as it can save up to 37.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (23%)

Requests Now

71

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ecoto.rakuten.co.jp

ecoto.rakuten.co.jp

561 ms

502 ms

common.css

common.css

329 ms

layout.css

layout.css

352 ms

common.css

common.css

353 ms

style.css

style.css

749 ms

style.css

style.css

741 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

1371 ms

header.js

header.js

674 ms

arrayLine.js

arrayLine.js

674 ms

suggest_ext.js

suggest_ext.js

703 ms

s_code-csr_n.js

s_code-csr_n.js

352 ms

img_logo.gif

img_logo.gif

380 ms

bg_search.gif

bg_search.gif

335 ms

btn_en.gif

btn_en.gif

333 ms

text_h1.gif

text_h1.gif

354 ms

main1.jpg

main1.jpg

1829 ms

main2.jpg

main2.jpg

1296 ms

main3.jpg

main3.jpg

1477 ms

main4.jpg

main4.jpg

1318 ms

main5.jpg

main5.jpg

1529 ms

main6.jpg

main6.jpg

1559 ms

bg_line.gif

bg_line.gif

1621 ms

ttl_info.gif

ttl_info.gif

1695 ms

icn_list_green.gif

icn_list_green.gif

1820 ms

icon_hot.gif

icon_hot.gif

1869 ms

btn_info.gif

btn_info.gif

1929 ms

ttl_activities.gif

ttl_activities.gif

1960 ms

bg_panel.gif

bg_panel.gif

2014 ms

panel1.jpg

panel1.jpg

2125 ms

panel2.jpg

panel2.jpg

2164 ms

panel3.jpg

panel3.jpg

2219 ms

panel4.jpg

panel4.jpg

2305 ms

panel5.jpg

panel5.jpg

2589 ms

panel6.jpg

panel6.jpg

2963 ms

panel7.jpg

panel7.jpg

3048 ms

panel8.jpg

panel8.jpg

3058 ms

panel9.jpg

panel9.jpg

3183 ms

panel10.jpg

panel10.jpg

3089 ms

panel11.jpg

panel11.jpg

3509 ms

panel12.jpg

panel12.jpg

3823 ms

panel13.jpg

panel13.jpg

3744 ms

panel14.jpg

panel14.jpg

3807 ms

img_crach.gif

img_crach.gif

3437 ms

ttl_bokin.gif

ttl_bokin.gif

3482 ms

bg_dot.gif

bg_dot.gif

3736 ms

btn_bokin.gif

btn_bokin.gif

3851 ms

icn_facebook.gif

icn_facebook.gif

3826 ms

bg_sitenav.gif

bg_sitenav.gif

399 ms

like.php

like.php

163 ms

jqueryg.min.js

jqueryg.min.js

4755 ms

fy8tT2klpgR.js

fy8tT2klpgR.js

301 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

337 ms

jsonp.min.js

jsonp.min.js

3794 ms

yahoo-min.js

yahoo-min.js

3833 ms

dom-min.js

dom-min.js

3839 ms

initJSONPSuggest.js

initJSONPSuggest.js

2906 ms

view.js

view.js

2891 ms

ttl_highlight.gif

ttl_highlight.gif

3047 ms

btn_topmes.jpg

btn_topmes.jpg

3429 ms

icn_list2_green.gif

icn_list2_green.gif

2946 ms

icn_dot.gif

icn_dot.gif

2903 ms

icn_download.gif

icn_download.gif

2868 ms

ttl_groupcsr.gif

ttl_groupcsr.gif

3002 ms

icn_arrow_green.gif

icn_arrow_green.gif

3027 ms

20160301_100x75.gif

20160301_100x75.gif

3032 ms

weco_100x75_.gif

weco_100x75_.gif

3026 ms

tohokub2b-100x75.jpg

tohokub2b-100x75.jpg

3838 ms

bosai-100x75-20130529.gif

bosai-100x75-20130529.gif

3186 ms

el-sistema-100x75-20131016.gif

el-sistema-100x75-20131016.gif

3089 ms

donationdelivery-100x75.jpg

donationdelivery-100x75.jpg

3451 ms

s31041275553870

s31041275553870

11 ms

print-preview.css

print-preview.css

192 ms

SEO Factors

ecoto.rakuten.co.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 Ecoto.rakuten.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 Ecoto.rakuten.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

ecoto.rakuten.co.jp

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