13.5 sec in total
447 ms
12.5 sec
612 ms
Visit yoyogi-uchi-navi.jp now to see the best up-to-date Yoyogi Uchi Navi content and also check out these interesting facts you probably never knew about yoyogi-uchi-navi.jp
東京・神奈川・埼玉・千葉・大阪の賃貸マンション・アパート情報・お部屋探しは東京No.1賃貸仲介会社「うちナビ」にお任せください。うちナビは日本一顧客満足度の高いお部屋探しをお約束します!
Visit yoyogi-uchi-navi.jpWe analyzed Yoyogi-uchi-navi.jp page load time and found that the first response time was 447 ms and then it took 13.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yoyogi-uchi-navi.jp performance score
447 ms
1215 ms
332 ms
338 ms
336 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yoyogi-uchi-navi.jp, 85% (128 requests) were made to Uchi-navi.jp and 7% (11 requests) were made to Img-asp.jp. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Uchi-navi.jp.
Page size can be reduced by 331.9 kB (10%)
3.3 MB
2.9 MB
In fact, the total size of Yoyogi-uchi-navi.jp main page is 3.3 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. 55% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 104.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. This page needs HTML code to be minified as it can gain 39.0 kB, which is 33% 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 104.5 kB or 88% of the original size.
Potential reduce by 120.6 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. Yoyogi Uchi Navi images are well optimized though.
Potential reduce by 88.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 88.5 kB or 58% of the original size.
Potential reduce by 18.2 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. Yoyogi-uchi-navi.jp needs all CSS files to be minified and compressed as it can save up to 18.2 kB or 83% of the original size.
Number of requests can be reduced by 52 (35%)
147
95
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yoyogi Uchi Navi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
yoyogi-uchi-navi.jp
447 ms
www.uchi-navi.jp
1215 ms
common.css
332 ms
aside.css
338 ms
jquery.bxslider.css
336 ms
top.css
345 ms
jquery-1.8.2.js
923 ms
yugaAutoLine.js
376 ms
jquery.cookie.js
700 ms
common.js
709 ms
jquery.easing.1.3.js
686 ms
change-img.js
707 ms
jquery.bxSlider.js
749 ms
jquery.lazyload.js
1016 ms
jquery.bxslider.min.js
1027 ms
top_index.js
1019 ms
jquery.page-scroller-306.js
1040 ms
jquerypngfix.js
1120 ms
mainslider.js
1299 ms
header.css
1355 ms
footer.css
1397 ms
dc.js
129 ms
21991_1_171_134_3.jpg
414 ms
bg_service.jpg
171 ms
bg_head_history.jpg
178 ms
bg_header_favorite.jpg
335 ms
logo.jpg
347 ms
tel.jpg
360 ms
bt_nav_home.jpg
382 ms
bt_nav_search.jpg
500 ms
bt_nav_acd01.jpg
509 ms
bt_nav_acd02.jpg
655 ms
bt_nav_acd03.jpg
696 ms
bt_nav_staff.jpg
701 ms
bt_nav_customer.jpg
692 ms
bt_nav_shop.jpg
808 ms
bt_nav_contact.jpg
818 ms
bt_umeda.png
996 ms
bt_ikebukuro.png
1013 ms
bt_shinjuku.png
1027 ms
bt_shibuya.png
1045 ms
bt_gotanda.png
1149 ms
bt_tokyo.png
1167 ms
bt_roppongi.png
1320 ms
bt_shinagawa.png
1354 ms
bt_ebisu.png
1380 ms
bt_kanda.png
1385 ms
bt_s_line.jpg
1478 ms
bt_s_area.jpg
1528 ms
bt_s_map.jpg
1661 ms
bg_slide_machi.png
2578 ms
bg_slide2.png
2819 ms
bg_slide_staff.png
3042 ms
bg_slide_voice.png
2675 ms
bg_slide4.png
2554 ms
bg_slide5.png
3365 ms
gray.png
2877 ms
9543_1_171_134_3.jpg
415 ms
11023_1_171_134_3.jpg
427 ms
9648_1_171_134_3.jpg
434 ms
14400_1_171_134_3.jpg
450 ms
9675_1_171_134_3.jpg
453 ms
27265_1_171_134_3.jpg
565 ms
52905_1_126_98_3.jpg
598 ms
12903_1_126_98_3.jpg
602 ms
12902_1_126_98_3.jpg
614 ms
46949_1_126_98_3.jpg
639 ms
bt_linesearch.jpg
3322 ms
tag.js
100 ms
bt_areasearch.jpg
3342 ms
__utm.gif
12 ms
tag
11 ms
bt_mapsearch.jpg
3313 ms
mini_machi.jpg
3429 ms
ttl_top_staff.jpg
3088 ms
bt_stafflist.jpg
3375 ms
ttl_top_customer.jpg
3353 ms
bt_customerlist.jpg
3361 ms
ttl_rent_info.jpg
3263 ms
ttl_rent_topic.jpg
3436 ms
ttl_top_about.jpg
3292 ms
pht_office01.jpg
3726 ms
pht_office02.jpg
3742 ms
bt_side_org02.jpg
3703 ms
bt_side_org03.jpg
3436 ms
bt_side_org04.jpg
3649 ms
bt_side_org07.jpg
3503 ms
bt_side_org08.jpg
3696 ms
bt_side_org09.jpg
3946 ms
ttl_side_info.jpg
3733 ms
page_top.png
3649 ms
bg_nav.jpg
3638 ms
clearfix.gif
3523 ms
bg_slide1.png
4491 ms
icn_arw2.jpg
3726 ms
img_fkds.png
3737 ms
icn_arw.jpg
3687 ms
bg_customer.jpg
3846 ms
icn_arw4.jpg
3689 ms
img_tab_on.jpg
2862 ms
img_tab.jpg
2853 ms
img_border.jpg
2831 ms
bg_footer.jpg
2878 ms
bg_footermenu.jpg
2845 ms
bg_footer_arw.jpg
2695 ms
bt_nav_home_on.jpg
2419 ms
bt_nav_search_on.jpg
2527 ms
bt_nav_acd01_on.jpg
2675 ms
bt_nav_acd02_on.jpg
2632 ms
bt_nav_acd03_on.jpg
2623 ms
bt_nav_staff_on.jpg
2485 ms
bt_nav_customer_on.jpg
2485 ms
bt_nav_shop_on.jpg
2499 ms
bt_nav_contact_on.jpg
2654 ms
bt_umeda_on.png
2650 ms
bt_ikebukuro_on.png
2500 ms
bt_shinjuku_on.png
2514 ms
bt_shibuya_on.png
2262 ms
bt_gotanda_on.png
2172 ms
bt_tokyo_on.png
2354 ms
bt_roppongi_on.png
2332 ms
bt_shinagawa_on.png
2298 ms
bt_ebisu_on.png
2266 ms
bt_kanda_on.png
2138 ms
bt_s_line_on.jpg
2136 ms
bt_s_area_on.jpg
2300 ms
bt_s_map_on.jpg
2322 ms
bt_linesearch_on.jpg
2641 ms
bt_areasearch_on.jpg
2537 ms
bt_mapsearch_on.jpg
2464 ms
mini_machi_on.jpg
2473 ms
bt_stafflist_on.jpg
2265 ms
bt_customerlist_on.jpg
2131 ms
bt_side_org02_on.jpg
2712 ms
bt_side_org03_on.jpg
2531 ms
bt_side_org04_on.jpg
2542 ms
bt_side_org07_on.jpg
2515 ms
bt_side_org08_on.jpg
2364 ms
bt_side_org09_on.jpg
2385 ms
gray_prev.png
2555 ms
gray_next.png
2532 ms
bt_prev.gif
2539 ms
bt_next.gif
2531 ms
loading.gif
2426 ms
ya.js
343 ms
conversion_async.js
48 ms
37 ms
31 ms
pb.js
541 ms
327 ms
yoyogi-uchi-navi.jp SEO score
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yoyogi-uchi-navi.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 Yoyogi-uchi-navi.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.
yoyogi-uchi-navi.jp
Open Graph data is detected on the main page of Yoyogi Uchi Navi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: