Tools & Wizards About Us

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

rakuten.net

【楽天市場】Shopping is Entertainment! ： インターネット最大級の通信販売、通販オンラインショッピングコミュニティ

Page Load Speed

14 sec in total

First Response

522 ms

Resources Loaded

12.7 sec

Page Rendered

825 ms

About Website

Welcome to rakuten.net homepage info - get ready to check Rakuten best content for Japan right away, or after learning these important things about rakuten.net

楽天市場はインターネット通販が楽しめる総合ショッピングモール。楽天ポイントがどんどん貯まる！使える！毎日お得なクーポンも。食品から家電、ファッション、ベビー用品、コスメまで、充実の品揃え。

Visit rakuten.net

Key Findings

We analyzed Rakuten.net page load time and found that the first response time was 522 ms and then it took 13.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

rakuten.net performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value17.8 s

0/100

10%

TBT (Total Blocking Time)

Value4,740 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value24.5 s

0/100

10%

Network Requests Diagram

rakuten.net

522 ms

www.rakuten.co.jp

239 ms

scout.min.js

376 ms

css

65 ms

ichiba_top-1.2.4.min.css

235 ms

Our browser made a total of 545 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Rakuten.net, 48% (264 requests) were made to R.r10s.jp and 23% (128 requests) were made to Tshop.r10s.jp. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Tshop.r10s.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (15%)

Content Size

7.6 MB

After Optimization

6.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rakuten.net main page is 7.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. Only a small number of websites need less resources to load. Images take 5.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 443.1 kB

  • Original 523.3 kB
  • After minification 508.6 kB
  • After compression 80.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 443.1 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 280.3 kB

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

JavaScript Optimization

-25%

Potential reduce by 320.9 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 979.1 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 320.9 kB or 25% of the original size.

CSS Optimization

-46%

Potential reduce by 63.1 kB

  • Original 136.6 kB
  • After minification 131.8 kB
  • After compression 73.5 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. Rakuten.net needs all CSS files to be minified and compressed as it can save up to 63.1 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 156 (29%)

Requests Now

535

After Optimization

379

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 535 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 64 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

rakuten.net accessibility score

57

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-*] attributes do not match their roles

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

Buttons do not have an accessible name

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

rakuten.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

rakuten.net SEO score

86

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

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 Rakuten.net 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 Rakuten.net 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

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