10.3 sec in total
575 ms
9.4 sec
367 ms
Click here to check amazing Coredo content. Otherwise, check out these important facts you probably never knew about coredo.jp
三井不動産がプロデュースするコレド室町/コレド日本橋の公式ウェブサイト。
Visit coredo.jpWe analyzed Coredo.jp page load time and found that the first response time was 575 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
coredo.jp performance score
575 ms
715 ms
340 ms
342 ms
35 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Coredo.jp, 81% (62 requests) were made to 31urban.jp and 4% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source 31urban.jp.
Page size can be reduced by 528.2 kB (37%)
1.4 MB
916.0 kB
In fact, the total size of Coredo.jp main page is 1.4 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. 25% of websites need less resources to load. Images take 913.3 kB which makes up the majority of the site volume.
Potential reduce by 19.7 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 19.7 kB or 73% of the original size.
Potential reduce by 192.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. Obviously, Coredo needs image optimization as it can save up to 192.4 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 276.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 276.3 kB or 61% of the original size.
Potential reduce by 39.8 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. Coredo.jp needs all CSS files to be minified and compressed as it can save up to 39.8 kB or 83% of the original size.
Number of requests can be reduced by 28 (39%)
72
44
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Coredo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
coredo.jp
575 ms
715 ms
import.css
340 ms
sp_coredo.css
342 ms
jsapi
35 ms
satelliteLib-187b2f720167e28d79dcc3c179602794bb06f9ce.js
89 ms
rollover.js
390 ms
smooth.pack.js
395 ms
jquery-1.4.2.min.js
1465 ms
feature.js
2085 ms
s_retargeting.js
528 ms
conversion.js
15 ms
base.css
336 ms
layouts.css
913 ms
common.css
808 ms
contents.css
904 ms
jquery.min.js
62 ms
ga.js
81 ms
logo_mspu.png
478 ms
logo_mitsuifudosan.gif
335 ms
icon_sqsbl.png
487 ms
menu_blda.png
489 ms
menu_coredo.png
776 ms
menu_bldb.png
881 ms
menu_ginza.png
892 ms
menu_akasaka.png
879 ms
menu_oi.png
993 ms
menu_si.png
1159 ms
title.png
2281 ms
coredo_map_141001.gif
1987 ms
icon_arrowr.png
1277 ms
institutionbn_0013.png
1356 ms
institutionbn_0015.png
1413 ms
institutionbn_0009.png
1512 ms
pagelinks_omotenashinihonbashi.jpg
1959 ms
pagelinks_tohotheater.jpg
2418 ms
pagelinks_shinise.jpg
2670 ms
pagelinks_cruise.jpg
3003 ms
pagelinks_mebuki2015.jpg
2699 ms
pagelinks_shopsnakadori2015.jpg
2792 ms
pagelinks_shopsedosakuradori.jpg
3903 ms
pagelinks_shopschuodori.jpg
3564 ms
card.png
3851 ms
logo_coredo_uni.gif
3066 ms
leftarea_hbox_btn_coredo.gif
3191 ms
leftarea_hbox_map_coredo_uni.gif
3438 ms
member_login1410_title.png
3543 ms
member_login_btn.png
3633 ms
icon_tribl.png
3770 ms
member_pointpresent.jpg
4229 ms
member_signup.png
3954 ms
member_signup1410_title.png
4383 ms
__utm.gif
14 ms
__utm.gif
4 ms
collect
52 ms
ga-audiences
16 ms
member_signup_cards_20151021.png
3797 ms
member_signup_btn.png
3781 ms
member_btn_entrys.png
4025 ms
icon_wcarrow.png
3850 ms
sidebar_search_title.png
4047 ms
sidebar_search_restaurant_img.png
3791 ms
icon_bcarrow.png
3695 ms
sidebar_search_restaurant_title.png
3830 ms
icon_arrowbl.png
3894 ms
sidebar_search_shop_img.png
3971 ms
30 ms
s-code-contents-373638d43ce2e3b6c0627874f4c75b1ef9d8ceaa.js
51 ms
sidebar_search_shop_title.png
4077 ms
16 ms
15-092_link.jpg
3907 ms
s722298572584
11 ms
tohotheater.jpg
4130 ms
nihonbashitokyojp.jpg
4066 ms
nihonbashihall.jpg
4235 ms
n-aji.jpg
4204 ms
leftarea_hbox_btn_coredo_o.gif
336 ms
coredo.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Coredo.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 Coredo.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.
coredo.jp
Open Graph description is not detected on the main page of Coredo. 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: