10.5 sec in total
941 ms
9.2 sec
336 ms
Visit kasite.com now to see the best up-to-date Kasite content for Japan and also check out these interesting facts you probably never knew about kasite.com
厳選された家電・家具を新品、中古で全国にお届けレンタル。圧倒的な品揃えとレンタル後のアフターサービスが人気です。家電レンタル、家具レンタルは業界44年、年間受注実績210,000件(2025年)の「かして!どっとこむ」にお任せください。
Visit kasite.comWe analyzed Kasite.com page load time and found that the first response time was 941 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kasite.com performance score
name
value
score
weighting
Value8.2 s
0/100
10%
Value18.3 s
0/100
25%
Value16.5 s
0/100
10%
Value5,440 ms
0/100
30%
Value0.287
42/100
15%
Value32.4 s
0/100
10%
941 ms
359 ms
367 ms
735 ms
690 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 80% of them (112 requests) were addressed to the original Kasite.com, 12% (17 requests) were made to Static.xx.fbcdn.net and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Kasite.com.
Page size can be reduced by 119.7 kB (21%)
564.2 kB
444.4 kB
In fact, the total size of Kasite.com main page is 564.2 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. 35% of websites need less resources to load. Images take 397.6 kB which makes up the majority of the site volume.
Potential reduce by 26.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. This page needs HTML code to be minified as it can gain 4.4 kB, which is 12% 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 26.6 kB or 75% of the original size.
Potential reduce by 11.4 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. Kasite images are well optimized though.
Potential reduce by 54.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 54.6 kB or 55% of the original size.
Potential reduce by 27.1 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. Kasite.com needs all CSS files to be minified and compressed as it can save up to 27.1 kB or 87% of the original size.
Number of requests can be reduced by 44 (32%)
136
92
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kasite. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
kasite.com
941 ms
import.css
359 ms
import.css
367 ms
script.js
735 ms
style.css
690 ms
style.css
382 ms
conversion.js
18 ms
clickjs.php
1337 ms
bl_track.js
391 ms
header_bg.gif
205 ms
logo.gif
363 ms
header_btn1.gif
388 ms
header_btn2.gif
386 ms
header_btn3.gif
392 ms
header_btn4.gif
408 ms
header_btn_gohome.gif
548 ms
beginner_btn.jpg
900 ms
bt_header_cust.png
897 ms
navi.gif
951 ms
main.jpg
1809 ms
bnr_30th.jpg
1527 ms
arrow1.gif
885 ms
delivs_box_bg.gif
1243 ms
delivs_box_bottom.gif
1269 ms
delivs_box_title.gif
1487 ms
delivs_box_arrow.gif
1293 ms
point_bg.gif
1636 ms
point_bg_upper.gif
1652 ms
point_bg_bottom.gif
1673 ms
point_title.gif
1869 ms
point_lead.gif
2068 ms
point_img1.gif
2002 ms
point_img2.gif
1988 ms
point_img3.gif
2009 ms
point_img4.gif
2175 ms
point_img5.gif
2267 ms
point_img6.gif
2356 ms
point_img7.gif
2399 ms
point_b_img1.gif
2777 ms
point_b_img2.gif
2774 ms
point_b_img3.gif
2881 ms
category_bg.gif
2616 ms
category_bottom.gif
2726 ms
category_title.gif
2733 ms
ga.js
26 ms
category_border.gif
2943 ms
33 ms
__utm.gif
24 ms
35 ms
43 ms
category_box_bg.gif
2885 ms
likebox.php
313 ms
category_img1.gif
2734 ms
category_btn1.gif
2751 ms
category_img2.gif
2783 ms
category_btn2.gif
2879 ms
category_img3.gif
2960 ms
jTuqQ-OPDr6.css
283 ms
n370yiaI2G6.css
350 ms
dbNRhrdsQao.css
418 ms
1-xIpmMldel.css
548 ms
_rx8naC75Dy.js
555 ms
x5F9OMjKyLw.js
618 ms
ICDbTSzjQEg.js
484 ms
TTCre3391I0.js
485 ms
njO1TPvGzoR.js
526 ms
b_6HNn_J2BZ.js
568 ms
7cm7D75Y0Sf.js
639 ms
rFmE1g6Dkoz.js
790 ms
category_btn3.gif
2910 ms
bl_track.cgi
335 ms
category_img4.gif
2586 ms
category_btn4.gif
2606 ms
category_img5.gif
2644 ms
category_btn5.gif
2700 ms
category_img6.gif
2474 ms
category_btn6.gif
2528 ms
category_img7.gif
2528 ms
184650_108026389276306_59985_n.jpg
280 ms
wL6VQj7Ab77.png
97 ms
s7jcwEQH7Sx.png
97 ms
QDwYpIaRyfG.png
98 ms
category_btn7.gif
2390 ms
category_img8.gif
2407 ms
category_btn8.gif
2367 ms
I6-MnjEovm5.js
70 ms
vlXaquuXMrr.js
135 ms
category_img9.gif
2454 ms
category_btn9.gif
2490 ms
category_img10.gif
2386 ms
category_btn10.gif
2393 ms
category_img11.gif
2330 ms
category_btn11.gif
2385 ms
category_img12.gif
2469 ms
category_btn12.gif
2478 ms
category_img13.gif
2386 ms
category_btn13.gif
2359 ms
category_img14.gif
2352 ms
category_btn14.gif
2372 ms
category_img15.gif
2242 ms
category_btn15.gif
2186 ms
category_img17.gif
2166 ms
category_btn17.gif
2203 ms
howto_title.gif
2283 ms
side_campaign_title.gif
2242 ms
bnr201007.gif
2242 ms
card1.jpg
2636 ms
tokuten_title.gif
2211 ms
tokuten_bnr1.gif
2219 ms
tokuten_bnr2.gif
2287 ms
bnr_hikaku.gif
2252 ms
bnr_media.gif
2240 ms
bnr_blog.gif
2217 ms
bnr_link.gif
2436 ms
side_ranking_bg.gif
2319 ms
side_ranking_bottom.gif
2324 ms
side_ranking_title.gif
2325 ms
side_ranking_box_bg.gif
2334 ms
side_ranking_1.jpg
2276 ms
side_ranking_2.jpg
2405 ms
side_ranking_3.jpg
2325 ms
side_ranking_4.jpg
2320 ms
side_ranking_5.jpg
2325 ms
side_inqbox_title11.jpg
2547 ms
side_inqbox_txt31.jpg
2649 ms
side_inqbox_txt12_5.jpg
2569 ms
side_inqbox_txt13.jpg
2479 ms
side_inqbox_txt14.jpg
2484 ms
side_inqbox_txt19.jpg
2689 ms
side_inqbox_txt15.jpg
2703 ms
side_mobile_title2.gif
2585 ms
side_mobile_img2.gif
2551 ms
qrcode2.gif
2542 ms
gotop.gif
2472 ms
bottomlink_bg.gif
2645 ms
bottomlink_upper.gif
2597 ms
bottomlink_bottom.gif
2613 ms
bottomlink_title_bg.gif
2595 ms
footer_bg.gif
2583 ms
__utm.gif
10 ms
kasite.com 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
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
Form elements do not have associated labels
Links do not have a discernible name
kasite.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
kasite.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 doesn't use legible font sizes
Tap targets are not sized appropriately
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kasite.com 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 Kasite.com 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.
kasite.com
Open Graph description is not detected on the main page of Kasite. 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: