5.5 sec in total
1.5 sec
3.7 sec
254 ms
Click here to check amazing Ca Fo Re content for Japan. Otherwise, check out these important facts you probably never knew about cafore.jp
クルマを貸したい人と、借りたい人をマッチング。みんなのカーシェアリング、CaFoRe(カフォレ)。 格安レンタカー・激安レンタカーよりも、地球にもやさしい個人間カーシェアリング。全国の珍しいクルマからお手軽なクルマまで、みんなでカーシェアリング!
Visit cafore.jpWe analyzed Cafore.jp page load time and found that the first response time was 1.5 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
cafore.jp performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value2.5 s
90/100
25%
Value4.4 s
74/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.5 s
98/100
10%
1539 ms
392 ms
398 ms
413 ms
414 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 84% of them (61 requests) were addressed to the original Cafore.jp, 16% (12 requests) were made to Image.cafore.jp. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Cafore.jp.
Page size can be reduced by 154.7 kB (38%)
408.8 kB
254.1 kB
In fact, the total size of Cafore.jp main page is 408.8 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. 30% of websites need less resources to load. Images take 252.3 kB which makes up the majority of the site volume.
Potential reduce by 57.5 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 57.5 kB or 82% of the original size.
Potential reduce by 27.5 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. Obviously, Ca Fo Re needs image optimization as it can save up to 27.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 13.1 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 13.1 kB or 75% of the original size.
Potential reduce by 56.5 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. Cafore.jp needs all CSS files to be minified and compressed as it can save up to 56.5 kB or 82% of the original size.
Number of requests can be reduced by 19 (26%)
72
53
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ca Fo Re. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for CSS and as a result speed up the page load time.
cafore.jp
1539 ms
style.css
392 ms
swfobject.js
398 ms
AC_RunActiveContent.js
413 ms
alphafilter.js
414 ms
base.css
197 ms
common.css
206 ms
navigation.css
228 ms
contents.css
474 ms
link.css
391 ms
title.css
406 ms
table.css
402 ms
comment.css
428 ms
0eb276af2129886.jpg
524 ms
4db72c3bee3ec07.jpg
556 ms
4e09ecbd53fe73a.jpg
586 ms
5b953debb3e6013.jpg
595 ms
e1a67cebb90e379.jpg
596 ms
edb6941eff67f6f.jpg
597 ms
23dd523b30c9e17.jpg
695 ms
a611a930a342b2e.jpg
747 ms
ce0e8a275e57862.jpg
790 ms
8381a5d16e38033.jpg
803 ms
4754f395899ed53.jpg
806 ms
13213.jpg
807 ms
background_contents.jpg
207 ms
background.jpg
196 ms
logo_cafore.gif
208 ms
nav_borrower_back.gif
208 ms
btn_borrower_search.gif
199 ms
btn_borrower_req.gif
203 ms
nav_lender_back.gif
391 ms
btn_lender_entry.gif
397 ms
btn_lender_req.gif
404 ms
nav_head_back.gif
411 ms
icn_entry.gif
414 ms
icn_login.gif
412 ms
btn_head_business.gif
584 ms
box_entry_back.png
594 ms
home_input_back.png
605 ms
btn_login.png
615 ms
btn_entry.png
616 ms
banner_nippon.gif
617 ms
no-image_car3.jpg
779 ms
no-image_user3.jpg
791 ms
status_appo_req2.gif
806 ms
badge_voice.png
821 ms
icn_signal-a.png
823 ms
icn_signal-b.png
845 ms
back_about.jpg
1150 ms
btn_about2.png
971 ms
btn_about1.png
990 ms
btn_about3.png
1011 ms
btn_about4.png
1009 ms
btn_about5.png
1012 ms
back_search_category.gif
1169 ms
btn_cate_01.gif
1190 ms
btn_cate_02.gif
1214 ms
btn_cate_03.gif
1214 ms
btn_cate_04.gif
1217 ms
back_pickup.jpg
1348 ms
news_panel.png
1196 ms
home_back_map.jpg
1217 ms
news_brw_back.jpg
1243 ms
news_ldr_back.jpg
1241 ms
mark_arrow1.gif
1242 ms
back_value.jpg
1360 ms
status_lender.gif
1198 ms
status_borrower.gif
1220 ms
back_news.jpg
1450 ms
status_info.gif
1238 ms
status_media.gif
1240 ms
back_foot.gif
1348 ms
cafore.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.
cafore.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
cafore.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cafore.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cafore.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.
cafore.jp
Open Graph description is not detected on the main page of Ca Fo Re. 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: