Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

rakuten.jp

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

Page Load Speed

11.4 sec in total

First Response

534 ms

Resources Loaded

10.8 sec

Page Rendered

52 ms

rakuten.jp screenshot

About Website

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

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

Visit rakuten.jp

Key Findings

We analyzed Rakuten.jp page load time and found that the first response time was 534 ms and then it took 10.8 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.jp performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value20.1 s

0/100

10%

TBT (Total Blocking Time)

Value2,590 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.178

68/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

Network Requests Diagram

rakuten.jp

534 ms

www.rakuten.co.jp

10229 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Rakuten.jp, 50% (1 request) were made to Rakuten.co.jp. The less responsive or slowest element that took the longest time to load (10.2 sec) relates to the external source Rakuten.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (14%)

Content Size

15.4 MB

After Optimization

13.3 MB

In fact, the total size of Rakuten.jp main page is 15.4 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 14.4 MB which makes up the majority of the site volume.

HTML Optimization

-5%

Potential reduce by 4 B

  • Original 81 B
  • After minification 80 B
  • After compression 77 B

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. This web page is already compressed.

Image Optimization

-9%

Potential reduce by 1.4 MB

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

JavaScript Optimization

-69%

Potential reduce by 617.3 kB

  • Original 898.9 kB
  • After minification 871.2 kB
  • After compression 281.6 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 617.3 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 142.1 kB

  • Original 173.6 kB
  • After minification 172.0 kB
  • After compression 31.4 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.jp needs all CSS files to be minified and compressed as it can save up to 142.1 kB or 82% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

rakuten.jp accessibility score

67

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

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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rakuten.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Rakuten.jp main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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