10.6 sec in total
1.1 sec
8.6 sec
924 ms
Visit rentio.jp now to see the best up-to-date Rentio content for Japan and also check out these interesting facts you probably never knew about rentio.jp
どんな製品も買わずに試せる、家電お試しサービス「レンティオ」 各メーカーの新製品も続々登場!月間10万人が利用中!数日間のお試し体験からサブスク型の月額制利用まで。3,156種類の品揃えを送料無料でお届け。試して気に入れば返さずにそのまま購入も可能。身分証・アプリも不要で注文から返却までカンタン。公式クーポン・割引も要チェック。
Visit rentio.jpWe analyzed Rentio.jp page load time and found that the first response time was 1.1 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
rentio.jp performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value19.5 s
0/100
25%
Value13.4 s
2/100
10%
Value2,380 ms
5/100
30%
Value0.004
100/100
15%
Value27.7 s
0/100
10%
1102 ms
511 ms
48 ms
47 ms
50 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rentio.jp, 12% (18 requests) were made to Static.xx.fbcdn.net and 10% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6.7 sec) relates to the external source Cdn.rentio.jp.
Page size can be reduced by 485.0 kB (23%)
2.1 MB
1.6 MB
In fact, the total size of Rentio.jp main page is 2.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 58.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 58.2 kB or 78% of the original size.
Potential reduce by 39.7 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. Rentio images are well optimized though.
Potential reduce by 238.5 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 238.5 kB or 48% of the original size.
Potential reduce by 148.6 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. Rentio.jp needs all CSS files to be minified and compressed as it can save up to 148.6 kB or 84% of the original size.
Number of requests can be reduced by 76 (53%)
143
67
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rentio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.rentio.jp
1102 ms
cross-border-cart.css
511 ms
jquery.min.js
48 ms
bootstrap.min.css
47 ms
slick.min.css
50 ms
font-awesome.min.css
26 ms
style.css
40 ms
css
25 ms
jquery.min.js
5 ms
bootstrap.min.js
7 ms
slick.min.js
8 ms
moment.min.js
8 ms
function.js
710 ms
platform.js
41 ms
castanet.js
500 ms
cart.js
372 ms
product_stock.js
374 ms
gtm.js
157 ms
tag.js
154 ms
li.php
630 ms
li.php
496 ms
button-only@2x.png
939 ms
94390478_th.jpg
607 ms
rentio_logo.png
123 ms
main201511.jpg
6661 ms
step1_sq.jpg
665 ms
step2_sq.jpg
1056 ms
step4_sq.jpg
1608 ms
step3_sq.jpg
1678 ms
ribon2.png
793 ms
maintenance.jpg
1545 ms
creditcard_03.gif
1545 ms
89331080_th.png
121 ms
89404707_th.png
658 ms
93273024_th.jpg
116 ms
94687016_th.jpg
119 ms
89138006_th.jpg
118 ms
89501481_th.png
119 ms
90991727_th.jpg
657 ms
91743818_th.jpg
121 ms
89176210_th.jpg
697 ms
89248435_th.jpg
153 ms
fontawesome-webfont.woff
33 ms
tag
13 ms
analytics.js
77 ms
conversion_async.js
78 ms
widgets.js
74 ms
sdk.js
483 ms
brick.js
75 ms
s_retargeting.js
841 ms
conversion.js
846 ms
fbevents.js
567 ms
widget_v2.132.js
68 ms
collect
20 ms
collect
402 ms
381 ms
UA-62229088-1.js
381 ms
__$$__stringtable_lang_ja.js
260 ms
castanet.gif
158 ms
ajax-loader.gif
466 ms
tracker.js
204 ms
bookmark_button.js
366 ms
ya.js
389 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
95 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
93 ms
209 ms
ga-audiences
205 ms
209 ms
xd_arbiter.php
271 ms
xd_arbiter.php
822 ms
syndication
156 ms
614443501707620355
299 ms
170 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
31 ms
like.php
98 ms
page.php
625 ms
rU2ubZ6l1Q5.js
842 ms
LVx-xkvaJ0b.png
777 ms
522 ms
brick.heatmap.js
512 ms
sync.php
1089 ms
pb.js
804 ms
595 ms
conversion.js
794 ms
203c.png
460 ms
263a.png
451 ms
1f495.png
452 ms
1f374.png
451 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
346 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
122 ms
aL63HcygAAVYuCCsAAA==
3 ms
PoLKMrE3dQt.css
323 ms
MW9gLaVqJGn.css
318 ms
MKiDk2JIhZf.css
324 ms
_rx8naC75Dy.js
449 ms
3o1espZ6Mhb.js
387 ms
nfTYZZc0iSn.js
522 ms
SFuJyO56WQT.js
388 ms
pJPDNGWM_rf.js
521 ms
reset.css
82 ms
entry-button.css
82 ms
q8lEufma_normal.png
159 ms
ia3v5mu6_normal.jpg
185 ms
Eyd9hFuc_normal.jpeg
227 ms
p2J7KUNy_normal.jpg
419 ms
icon4880828281165598590636827_24_normal.jpg
268 ms
fyRExw61_normal.jpg
273 ms
_XWN6H1U_normal.jpeg
290 ms
zzop-O-e_normal.jpg
290 ms
PWymnOdo_normal.jpg
291 ms
oMQ9LoyP_normal.jpg
295 ms
y7HxCIM2_normal.jpg
306 ms
CbBXJrHUEAQfsjz.jpg:large
311 ms
bbtn-l_v3.png
13 ms
brick.lib.js
190 ms
brick.heatmap_base.js
353 ms
905 ms
jot.html
2 ms
11008462_1614257585527313_2836139729067316652_n.png
372 ms
safe_image.php
303 ms
safe_image.php
433 ms
safe_image.php
569 ms
safe_image.php
567 ms
safe_image.php
596 ms
10985914_1614257725527299_8623554317873375125_n.png
431 ms
12642794_179344125754917_2919884175584267164_n.jpg
500 ms
12039263_962181757201653_5169059625389669261_n.jpg
563 ms
562884_345529455524960_1521584068_n.jpg
568 ms
10156050_690643484330657_4013801805710470987_n.jpg
565 ms
12494882_912860012124424_7036144585089942899_n.jpg
565 ms
1379841_10150004552801901_469209496895221757_n.jpg
564 ms
10269393_1410050909279394_4326117765112366144_n.jpg
568 ms
216361_141833685888719_5530557_n.jpg
631 ms
12631373_740496199415018_4571893088601648976_n.jpg
632 ms
10420122_818967881511772_8589873413863028007_n.jpg
633 ms
10983576_819533001472353_632709521365077618_n.jpg
634 ms
12741908_1099929100017470_835493245304463267_n.jpg
635 ms
12795269_1826284864265320_497808554525262050_n.jpg
635 ms
wL6VQj7Ab77.png
95 ms
s7jcwEQH7Sx.png
94 ms
LT9rONw9UJp.png
94 ms
lRyN50VcaFW.js
72 ms
sync.php
189 ms
collect
3 ms
collect
12 ms
R9a_DtVRZgv.js
69 ms
cUDgRFxaoIk.js
70 ms
0JBr1QHp8Gi.js
71 ms
kDOzhTr2W91.js
70 ms
rentio.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
rentio.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
rentio.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rentio.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 Rentio.jp main page’s claimed encoding is euc-jp. 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.
rentio.jp
Open Graph data is detected on the main page of Rentio. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: