Access rakuten-bank.co.jp. 楽天銀行（旧イーバンク銀行）- ネット銀行

rakuten-bank.co.jp screenshot

9

Performance

Renders faster than
23% of other websites
73

Accessibility

Visual factors better than
that of 38% of websites
75

Best Practices

More advanced features
available than in
35% of websites
90

SEO

Google-friendlier than
68% of websites

First Response

337 ms

Resources Loaded

8 sec

Page Rendered

1 sec

rakuten-bank.co.jp screenshot

About Website

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

楽天銀行（旧イーバンク銀行）は1,600万口座を超える日本最大級のインターネット銀行です。インターネットバンキングで各種お取引毎に「楽天ポイント」を貯められます。

Visit rakuten-bank.co.jp

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value22.7 s

0/100

10%

TBT (Total Blocking Time)

Value3,270 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.318

36/100

15%

TTI (Time to Interactive)

Value37.5 s

0/100

10%

rakuten-bank.co.jp

337 ms

www.rakuten-bank.co.jp

207 ms

www.rakuten-bank.co.jp

385 ms

accessibility.css

25 ms

swiper-bundle.min.css

79 ms

Our browser made a total of 219 requests to load all elements on the main page. We found that 77% of them (168 requests) were addressed to the original Rakuten-bank.co.jp, 2% (4 requests) were made to Googletagmanager.com and 2% (4 requests) were made to Jp.rakuten-static.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Rakuten-bank.co.jp.

Content Size

567.4 kB

After Optimization

172.0 kB

In fact, the total size of Rakuten-bank.co.jp main page is 567.4 kB. 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. HTML takes 404.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 341.0 kB

Original 404.7 kB
After minification 364.9 kB
After compression 63.6 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 341.0 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 2.6 kB

Original 40.4 kB
After minification 37.8 kB

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 Bank images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 46.4 kB

Original 115.6 kB
After minification 115.6 kB
After compression 69.2 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 46.4 kB or 40% of the original size.

CSS Optimization

-79%

Potential reduce by 5.3 kB

Original 6.7 kB
After minification 6.7 kB
After compression 1.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-bank.co.jp needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 79% of the original size.

Requests Now

209

After Optimization

132

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

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

High

[role] values are not valid

High

ARIA IDs are not unique

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

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

rakuten-bank.co.jp

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