8 sec in total
664 ms
6.9 sec
423 ms
Visit oasisnavi.com now to see the best up-to-date Oasisnavi content for Japan and also check out these interesting facts you probably never knew about oasisnavi.com
有料老人ホーム・介護施設の資料請求・見学予約が会員登録不要で全て無料利用!全国約35,000件(2019年10月29日更新)。老人ホーム検索サイトはオアシスナビ!施設料金はもちろん、スタッフ情報や料理など日常の生活状況まで比較可能です!
Visit oasisnavi.comWe analyzed Oasisnavi.com page load time and found that the first response time was 664 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Oasisnavi.com rating and web reputation
oasisnavi.com performance score
664 ms
1663 ms
363 ms
375 ms
556 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 90% of them (129 requests) were addressed to the original Oasisnavi.com, 2% (3 requests) were made to Google-analytics.com and 2% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Oasisnavi.com.
Page size can be reduced by 415.9 kB (56%)
745.3 kB
329.4 kB
In fact, the total size of Oasisnavi.com main page is 745.3 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. Javascripts take 303.9 kB which makes up the majority of the site volume.
Potential reduce by 140.9 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 97.0 kB, which is 63% 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 140.9 kB or 92% of the original size.
Potential reduce by 14.9 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. Oasisnavi images are well optimized though.
Potential reduce by 206.3 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 206.3 kB or 68% of the original size.
Potential reduce by 53.9 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. Oasisnavi.com needs all CSS files to be minified and compressed as it can save up to 53.9 kB or 85% of the original size.
Number of requests can be reduced by 24 (18%)
136
112
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oasisnavi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
oasisnavi.com
664 ms
www.oasisnavi.com
1663 ms
layout3.css
363 ms
general.css
375 ms
top-2.0.css
556 ms
style_a.css
389 ms
jquery.min.js
1002 ms
jquery.page-scroller.js
542 ms
smartRollover.js
563 ms
heightLine.js
581 ms
jquery.carouFredSel-6.1.0.js
905 ms
common.js
743 ms
top.js
751 ms
conversion.js
18 ms
footer.css
584 ms
entry.js
445 ms
osnv.js
323 ms
s_retargeting.js
567 ms
ga.js
28 ms
inpage_linkid.js
10 ms
__utm.gif
13 ms
collect
59 ms
ga-audiences
36 ms
logo_categ0.jpg
199 ms
g_navi01_out.gif
200 ms
g_navi02_out.gif
183 ms
g_navi03_out.gif
193 ms
g_navi04_out.gif
207 ms
g_navi05_out.gif
189 ms
g_navi06_out.gif
363 ms
g_navi08_out.gif
376 ms
g_navi09_out.gif
384 ms
icon15.gif
395 ms
map_title09.gif
398 ms
map_title10.gif
413 ms
map_title11.gif
543 ms
map_title12.gif
563 ms
map_title13.gif
578 ms
map_title14.gif
591 ms
map_title15.gif
596 ms
map_title16.gif
618 ms
map_title17.gif
723 ms
map_title18.gif
750 ms
map_title19.gif
770 ms
map_title20.gif
788 ms
map_title21.gif
794 ms
map_title22.gif
825 ms
map_title23.gif
903 ms
map_title24.gif
937 ms
map_title01.gif
963 ms
map_title02.gif
983 ms
map_title03.gif
991 ms
map_title04.gif
1032 ms
map_title05.gif
1084 ms
map_title06.gif
1123 ms
map_title07.gif
1152 ms
map_title08.gif
1179 ms
map_title25.gif
1188 ms
gtm.js
84 ms
80 ms
map_title26.gif
1234 ms
113 ms
54 ms
16 ms
map_title27.gif
1128 ms
map_title28.gif
1157 ms
map_title29.gif
1187 ms
map_title30.gif
1196 ms
map_title31.gif
1244 ms
map_title32.gif
1087 ms
icon15.gif
1128 ms
mikawa_720x160.gif
1523 ms
icon21.gif
1186 ms
goodhome.jpg
1195 ms
icon07.gif
1219 ms
jiehu.png
1310 ms
icon08.gif
1129 ms
2small4.jpg
1201 ms
img01.gif
1201 ms
2small31.jpg
1218 ms
1small4.jpg
1261 ms
icon20.gif
1252 ms
30829.jpg
1428 ms
imgtext01.gif
1224 ms
icon10.gif
1271 ms
f40S.png
1272 ms
icon11.gif
1271 ms
icon12.gif
1268 ms
f60S.png
1238 ms
f30S.png
1298 ms
f50S.png
1269 ms
icon16.gif
1292 ms
ring.gif
1335 ms
room.jpg
1272 ms
room2.jpg
1249 ms
room3.jpg
1287 ms
icon14.gif
1284 ms
doctor.jpg
1283 ms
old_computer%20.jpg
1297 ms
smarty_tel.gif
1299 ms
top_qr.gif
1257 ms
bookmark.gif
1283 ms
magazine.png
1290 ms
service.png
1272 ms
top_tel.gif
1273 ms
mail.gif
1316 ms
computer.png
1265 ms
comment_bottom.gif
1239 ms
img03.gif
1262 ms
icon17.gif
1246 ms
img04.gif
1212 ms
line02.gif
1185 ms
f_img01.jpg
1172 ms
f_img02.jpg
1195 ms
img_head_icon01.gif
1190 ms
img_head_icon01.png
1199 ms
img_head_icon02.png
1177 ms
g_navi01_over.gif
1184 ms
g_navi02_over.gif
1164 ms
g_navi03_over.gif
1136 ms
g_navi04_over.gif
1165 ms
g_navi05_over.gif
1186 ms
g_navi06_over.gif
1094 ms
g_navi08_over.gif
1180 ms
g_navi09_over.gif
1179 ms
search_bg.gif
1130 ms
icon02.gif
1158 ms
btn01.gif
1160 ms
map_tab_bg.gif
1126 ms
map.gif
1181 ms
map_area_bg04.gif
1184 ms
map_area_bg05.gif
1134 ms
map_area_bg06.gif
1141 ms
detail_box_bg.gif
1156 ms
h2_bg02.gif
1147 ms
icon04.gif
1179 ms
icon02.gif
1189 ms
line02.gif
1139 ms
icon09.gif
1133 ms
s_box_bg.png
1144 ms
comment_bg.gif
1173 ms
comment_input_bg.gif
1177 ms
old_box_bg.gif
1194 ms
oasisnavi.com SEO score
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oasisnavi.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 Oasisnavi.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.
oasisnavi.com
Open Graph description is not detected on the main page of Oasisnavi. 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: