9 sec in total
892 ms
7.6 sec
510 ms
Visit otokuru.com now to see the best up-to-date Otokuru content for Japan and also check out these interesting facts you probably never knew about otokuru.com
ぴったりの車がサクッと見つかる。簡単&無料 中古車お探しサービス『お得る』
Visit otokuru.comWe analyzed Otokuru.com page load time and found that the first response time was 892 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
otokuru.com performance score
892 ms
336 ms
312 ms
523 ms
874 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 65% of them (66 requests) were addressed to the original Otokuru.com, 4% (4 requests) were made to Googleads.g.doubleclick.net and 4% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Otokuru.com.
Page size can be reduced by 437.8 kB (26%)
1.7 MB
1.3 MB
In fact, the total size of Otokuru.com main page is 1.7 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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 42.8 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 42.8 kB or 80% of the original size.
Potential reduce by 163.2 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, Otokuru needs image optimization as it can save up to 163.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 217.0 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 217.0 kB or 61% of the original size.
Potential reduce by 14.7 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. Otokuru.com needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 81% of the original size.
Number of requests can be reduced by 39 (41%)
95
56
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otokuru. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
otokuru.com
892 ms
base.css
336 ms
alert.css
312 ms
common.css
523 ms
jquery.min.js
874 ms
jquery1.8.1_min.js
860 ms
form_sale.js
817 ms
jquery.customSelect.min.js
680 ms
realtime_length_count.js
661 ms
DD_belatedPNG.js
894 ms
jquery.alerts.js
970 ms
common.js
1090 ms
conversion.js
18 ms
s_retargeting.js
1028 ms
r.js
66 ms
80jjl0zd2f.js
15 ms
otokuru_logo01.png
176 ms
mainvisual01.jpg
736 ms
mainvisual02.jpg
1033 ms
form_h01.png
531 ms
nini_ic01.png
361 ms
btn_get01.png
843 ms
nayami_h01.png
889 ms
nayami_check01.png
704 ms
nayami_check02.png
876 ms
nayami_check03.png
1105 ms
nayami_check04.png
1134 ms
nayami_check05.png
1135 ms
nayami_h02.png
1459 ms
nayami_img01.png
1873 ms
nayami_img02.png
2097 ms
nayami_img03.png
1790 ms
nayami_h03.png
1574 ms
btn_get02.png
1849 ms
voice_h01.png
2011 ms
voice_silhouette01.png
1872 ms
voice_silhouette02.png
2085 ms
voice_silhouette03.png
2176 ms
voice_silhouette04.png
2167 ms
voice_silhouette05.png
2219 ms
voice_h02.png
2497 ms
step_h01.png
2544 ms
step_box01.png
2659 ms
step_box02.png
2663 ms
arrow_ic02.png
2525 ms
step_box03.png
2758 ms
step_box04.png
3032 ms
gulliver_logo01.png
2983 ms
gyousya_box01.png
2884 ms
gyousya_box02.png
2978 ms
plus_ic01.png
3040 ms
gtm.js
68 ms
analytics.js
15 ms
gyousya_box03.png
3105 ms
tag.js
227 ms
47 ms
collect
24 ms
35 ms
gyousya_h01.png
3158 ms
72 ms
83 ms
84 ms
pix.js
495 ms
img
1030 ms
fbds.js
66 ms
itm.js
424 ms
17 ms
94 ms
tag
8 ms
19 ms
21 ms
maker_and_cars
5350 ms
form_bg01.png
2808 ms
audience
366 ms
cube_ic01.png
2746 ms
bg_input_01.png
2831 ms
pixel
16 ms
fl_01.png
2648 ms
nayami_bg02.png
2756 ms
bg_h_01.png
2832 ms
gtm.js
15 ms
nayami_bg01.jpg
3043 ms
beacon.html
10 ms
tdim-1.1.0.min.js
10 ms
set
298 ms
segment
299 ms
voice_bg03.png
3152 ms
voice_bg01.png
2725 ms
step_bg01.png
2813 ms
pageviews
1314 ms
arrow_bg01.png
2657 ms
gyousya_bg01.png
2585 ms
gyousya_bg02.png
2517 ms
gyousya_bg03.png
2619 ms
arrow_ic01.png
2603 ms
ic_select_01.png
2637 ms
b
1055 ms
ya.js
341 ms
22 ms
pb.js
1027 ms
320 ms
otokuru.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otokuru.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 Otokuru.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.
otokuru.com
Open Graph description is not detected on the main page of Otokuru. 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: