www.rakuten-sec.co.jp speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:48 UTC. Grade A (93/100), with the screenshots, the timings and the fixes that matter.

https://www.rakuten-sec.co.jp/

20 October 2026 at 12:48 UTC · Free test · report pt_4407a794f92e
Grade
A
93/100
Performance97/100
Structure86/100

13 audit(s) passed, 3 need work

First byte (TTFB)233 msmeasured from this server
Fully loaded2.13 sfirst byte + slowest asset
Requests26document + assets
Page weight546.4 KBcompressed transfer
HTML document52.7 KBgzip
ProtocolHTTP/3server not sent
Third-party2.0 KBother hosts

Where the first byte went

  • DNS lookup 80 ms 34%
  • TCP connect 34 ms 15%
  • Server wait 118 ms 51%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 87% of 4,999 pages tested here233 ms against a median of 449 ms
Page weightlighter than 55% of 4,999 pages tested here546.4 KB against a median of 650.5 KB
Fully loadedslower than 62% of 4,999 pages tested here2.13 s against a median of 1.84 s
Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte arrived in 233 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 546.4 KB over 26 request(s). Images files are 90% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 1.77 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.019), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 400 ms, so taps and scrolling wait while scripts run.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of www.rakuten-sec.co.jp
Mobile 390 × 844 · 143.3 KB · page is 6000 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint1.77 sgood is under 2.5 s
Cumulative layout shift0.019under 0.1 is stable
Total blocking time400 mslong tasks during load
First contentful paint1.08 sfirst content on screen
Browser page weight3.31 MB210 request(s), scripts included
Failed requests17blocked or unreachable
Largest contentful paint1.77 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.019
Goodgood under 0.1, poor over 0.25
Total blocking time400 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests
493.7 KB 90%

Transfer size, compressed as sent. 26 request(s) in total, 546.4 KB across all of them.

Top issues

Render-blocking resources

high impact

8 render-blocking resource(s) in the document head (2 script(s), 6 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

Waterfall

Slowest requests

IMAGESwww.rakuten-sec.co.jp/web/images/banners/lp_standard/384x176…
1.89 s
IMAGESwww.rakuten-sec.co.jp/web/images/banners/lp_nisa_debut-p/02/…
1.80 s
IMAGESwww.rakuten-sec.co.jp/web/shared/images/nav-global/icon/mt4.png
1.80 s
IMAGESwww.rakuten-sec.co.jp/web/images/banners/lp_simpresent2026/2…
1.78 s
IMAGESwww.rakuten-sec.co.jp/web/shared/images/nav-global/icon/ms2.png
1.78 s
IMAGESwww.rakuten-sec.co.jp/web/shared/images/nav-global/icon/igro…
1.77 s
IMAGESwww.rakuten-sec.co.jp/web/images/banners/sp_merit-p/1176x368…
1.76 s
IMAGESwww.rakuten-sec.co.jp/web/images/banners/bond_jbond_products…
1.76 s
IMAGESwww.rakuten-sec.co.jp/web/shared/images/nav-global/icon/ms_m…
1.75 s
IMAGESwww.rakuten-sec.co.jp/web/shared/images/nav-global/banner-pi…
1.75 s

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.rakuten-sec.co.jp/web/images/banners/lp_standard/384x176.pngimages2001.89 s11.8 KB
https://www.rakuten-sec.co.jp/web/images/banners/lp_nisa_debut-p/02/1176x368.png?0324images2001.80 s78.0 KB
https://www.rakuten-sec.co.jp/web/shared/images/nav-global/icon/mt4.pngimages2001.80 s1.3 KB
https://www.rakuten-sec.co.jp/web/images/banners/lp_simpresent2026/220x100.pngimages2001.78 s38.8 KB
https://www.rakuten-sec.co.jp/web/shared/images/nav-global/icon/ms2.pngimages2001.78 s844 B
https://www.rakuten-sec.co.jp/web/shared/images/nav-global/icon/igrow.svgimages2001.77 s7.0 KB
https://www.rakuten-sec.co.jp/web/images/banners/sp_merit-p/1176x368.png?202607images2001.76 s54.0 KB
https://www.rakuten-sec.co.jp/web/images/banners/bond_jbond_products_20261019/2560x100.png?1016images2001.76 s47.8 KB
https://www.rakuten-sec.co.jp/web/shared/images/nav-global/icon/ms_mac.pngimages2001.75 s1.3 KB
https://www.rakuten-sec.co.jp/web/shared/images/nav-global/banner-pickup-tool.pngimages2001.75 s33.6 KB
https://www.rakuten-sec.co.jp/web/images/banners/cp_quiz_stockgift/220x100.pngimages2001.74 s8.6 KB
https://www.rakuten-sec.co.jp/web/images/banners/ext_bank_20261001/220x100.pngimages2001.73 s26.5 KB
https://www.rakuten-sec.co.jp/web/images/banners/cp_20260917-01/220x100.pngimages2001.72 s6.7 KB
https://www.rakuten-sec.co.jp/web/shared/img/top/s3-top-img-majority-01.png?0508images2001.72 s10.1 KB
https://www.rakuten-sec.co.jp/web/shared/images/nav-global/banner-pickup-market.pngimages2001.72 s46.0 KB
https://www.rakuten-sec.co.jp/web/shared/images/nav-global/icon/ispeed_op.pngimages2001.70 s593 B
https://www.rakuten-sec.co.jp/web/images/banners/seminar_list/384x176.pngimages2001.70 s14.7 KB
https://www.rakuten-sec.co.jp/web/images/banners/seminar_asset_college/384x176.pngimages2001.60 s92.8 KB
https://placehold.jp/176x75.png 3rd partyimages2001.52 s2.0 KB
https://www.rakuten-sec.co.jp/web/shared/images/nav-global/icon/ispeed.pngimages2001.46 s624 B
https://www.rakuten-sec.co.jp/web/shared/images/nav-global/icon/ms.pngimages2001.43 s1.5 KB
https://www.rakuten-sec.co.jp/web/shared/images/nav-global/icon/ms_fx.pngimages2001.43 s929 B
https://www.rakuten-sec.co.jp/web/images/banners/cp_20260901-01/220x100.pngimages2001.42 s5.2 KB
https://www.rakuten-sec.co.jp/web/shared/img/logo_pc.svgimages2001.29 s2.5 KB
https://www.rakuten-sec.co.jp/web/shared/images/nav-global/icon/ispeed_fx.pngimages2001.26 s524 B
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.