Access rakuten-sec.co.jp. 楽天証券 | ネット証券（株・FX・投資信託･確定拠出年金･NISA）

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,850 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.207

60/100

15%

TTI (Time to Interactive)

Value30.7 s

0/100

10%

www.rakuten-sec.co.jp

226 ms

s3-style_top.css

25 ms

sure-icon.css

35 ms

s3-style-groval-nav.css

33 ms

mfx-sbox.css

36 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 92% of them (102 requests) were addressed to the original Rakuten-sec.co.jp, 2% (2 requests) were made to Jp.rakuten-static.com and 2% (2 requests) were made to C.marsflag.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Rakuten-sec.co.jp.

Content Size

2.3 MB

After Optimization

1.4 MB

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

HTML Optimization

-89%

Potential reduce by 263.0 kB

Original 297.0 kB
After minification 226.4 kB
After compression 34.0 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 70.6 kB, which is 24% 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 263.0 kB or 89% of the original size.

Image Optimization

-19%

Potential reduce by 276.6 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, Rakuten Sec needs image optimization as it can save up to 276.6 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 201.9 kB

Original 307.8 kB
After minification 292.0 kB
After compression 105.9 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 201.9 kB or 66% of the original size.

CSS Optimization

-71%

Potential reduce by 146.3 kB

Original 205.6 kB
After minification 181.4 kB
After compression 59.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. Rakuten-sec.co.jp needs all CSS files to be minified and compressed as it can save up to 146.3 kB or 71% of the original size.

Requests Now

107

After Optimization

The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rakuten Sec. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 7 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

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

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

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

Report Summary

Performance

Accessibility

Best Practices

SEO

楽天証券 | ネット証券（株・FX・投資信託･確定拠出年金･NISA）

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

www.rakuten-sec.co.jp

s3-style_top.css

sure-icon.css

s3-style-groval-nav.css

mfx-sbox.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

www.rakuten-sec.co.jp

s3-style_top.css

sure-icon.css

s3-style-groval-nav.css

mfx-sbox.css

ai-chat.min.css

s3-head-foot.css

polyfill.min.js

jquery-3.3.1.min.js

jquery.cookie.js

getjsonp.js

s3-script_top.js

swiper.min.js

swiper_core.js

common.header.js

select-pc-sp.js

galfsram.js

global.js

s3-megamenu.js

ecl_new.js

cmmn.js

prm_selector_02.js

vista.js

ai_chat_renewal.js

Draggable.js

keybord.js

explicit-defer.js

logo_pc.svg

banner-pickup-beginner.png

create_fintech.js

384x176.png

banner-pickup-tool.png

ms2.png

ms.png

ms_mac.png

ms_fx.png

mt4.png

ispeed.png

ispeed_fx.png

ispeed_op.png

banner-pickup-market.png

banner-pickup-learn.png

font-awesome.css