8 sec in total
534 ms
6.7 sec
844 ms
Visit tokyo-marunouchi.jp now to see the best up-to-date TOKYO Marunouchi content for Japan and also check out these interesting facts you probably never knew about tokyo-marunouchi.jp
The Marunouchi area is the setting for MICE and business events in Tokyo, the capital of Japan. Inquire about high-class venues and services suitable for international conferences, academic meetings, ...
Visit tokyo-marunouchi.jpWe analyzed Tokyo-marunouchi.jp page load time and found that the first response time was 534 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
tokyo-marunouchi.jp performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value3.9 s
53/100
25%
Value10.8 s
6/100
10%
Value2,160 ms
6/100
30%
Value0
100/100
15%
Value7.2 s
51/100
10%
534 ms
824 ms
698 ms
518 ms
29 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 49% of them (50 requests) were addressed to the original Tokyo-marunouchi.jp, 38% (39 requests) were made to Static.xx.fbcdn.net and 4% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Tokyo-marunouchi.jp.
Page size can be reduced by 165.1 kB (3%)
6.5 MB
6.3 MB
In fact, the total size of Tokyo-marunouchi.jp main page is 6.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.3 MB which makes up the majority of the site volume.
Potential reduce by 23.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. 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 23.9 kB or 77% of the original size.
Potential reduce by 15.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. TOKYO Marunouchi images are well optimized though.
Potential reduce by 72.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 72.0 kB or 56% of the original size.
Potential reduce by 53.3 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. Tokyo-marunouchi.jp needs all CSS files to be minified and compressed as it can save up to 53.3 kB or 84% of the original size.
Number of requests can be reduced by 53 (54%)
98
45
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TOKYO Marunouchi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
tokyo-marunouchi.jp
534 ms
824 ms
common.css
698 ms
root.css
518 ms
sdk.js
29 ms
jquery-1.11.1.min.js
1055 ms
common.js
510 ms
root.js
522 ms
jquery.inview.min.js
516 ms
analytics.js
238 ms
hd_logo_01.gif
404 ms
gnav_btn_01.gif
373 ms
gnav_btn_01_sp.png
557 ms
gnav_btn_02.gif
374 ms
gnav_btn_02_sp.png
393 ms
gnav_btn_10.gif
557 ms
gnav_btn_10_sp.png
558 ms
gnav_btn_03.gif
557 ms
gnav_btn_03_sp.png
755 ms
gnav_btn_04.gif
667 ms
gnav_btn_04_sp.png
694 ms
gnav_btn_09.gif
697 ms
gnav_btn_09_sp.png
693 ms
gnav_btn_05.gif
725 ms
gnav_btn_05_sp.png
1075 ms
gnav_btn_06.gif
1080 ms
gnav_btn_06_sp.png
1149 ms
gnav_btn_11.png
1076 ms
gnav_btn_12.png
1073 ms
gnav_btn_13.png
1074 ms
gnav_btn_07.png
1140 ms
gnav_btn_07_sp.png
1141 ms
gnav_btn_08.png
1141 ms
gnav_btn_08_sp.png
1143 ms
top_main_bg_01.png
1145 ms
top_main_vis_01.jpg
2198 ms
top_main_vis_00.png
1291 ms
top_main_vis_02.jpg
2907 ms
top_main_vis_03.jpg
3602 ms
top_logo_01.png
1522 ms
top_logo_01_sp.png
1518 ms
top_txt_scroll.png
1510 ms
top_img_01.png
3141 ms
top_btn_01.gif
1564 ms
top_img_02.png
1815 ms
sdk.js
62 ms
collect
95 ms
83 ms
collect
60 ms
top_img_03.png
3169 ms
top_img_04.png
2830 ms
top_img_05.png
2405 ms
top_img_06.png
2709 ms
gnav_btn_07_on.png
2488 ms
gnav_btn_08_on.png
2646 ms
top_btn_01_on.gif
2656 ms
page.php
100 ms
VkoVFOmZg4e.css
43 ms
KCBgpVwfLM_.css
60 ms
nYa8oQZnpdr.js
76 ms
iiDbYMCPtB3.js
74 ms
WOLN5pzG8JN.js
74 ms
q6VzhXzzuec.js
73 ms
irCgPB7CJbM.js
73 ms
I-9YqvQlahI.js
69 ms
SixM03AXEw8.js
248 ms
YJojGYumZIr.js
251 ms
1lYRIUv3fB9.js
256 ms
309040429_435747728540759_2326129196771561982_n.jpg
281 ms
309103125_435747725207426_7051825467293927118_n.jpg
477 ms
UXtr_j2Fwe-.png
89 ms
uf1h26SmGil.js
44 ms
1092 ms
127 ms
xgVgalBG80z.png
26 ms
css;base64,
7 ms
YU1prgYt23u.css
82 ms
VuJkCablhEU.js
7 ms
css;%20charset=utf-8,.l_c3pyo2v0u%7Bmargin-bottom:6px%7D.a_c3pyo4on2%7Bmargin-right:8px%7D.r_c3pyo2ey1%20.h_c3pyo4oy5%7B-webkit-box-align:center;display:-webkit-box%7D.y_c3pyo2ta3%7Bmargin-bottom:-6px%7D.u_c3pyo2ta4%7Bpadding-bottom:6px%7D._5v3q%20.l_c3pyo2v0u%7Bmargin-bottom:11px%7D._5v3q%20.l_c3pyo2v0u.i_c3pynyi2f%7Bmargin-bottom:-1px%7D._5v3q%20.l_c3pyo2v0u.i_c3pynyi2f%20.o_c3pynyi2g%7Bpadding-bottom:3px%7D._5v3q%20._5pa-%20.l_c3pyo2v0u%7Bmargin-bottom:7px%7D.r_c3pyo2ey1%7Bborder-bottom:1px%20solid%20%2523e9e9e9;color:%25237f7f7f;display:block;font-size:13px;margin:-18px%200%2014px;padding:13px%200%2013px%7D._5v3q%20._90od%20.r_c3pyo2ey1%7Bborder-bottom:none;padding-bottom:0;padding-top:12px%7D._5v3q%20._90oc%20._1s31%20.r_c3pyo2ey1,._5v3q%20._90oc%20._1s31%20.r_c3pyo2ey1%20a%7Bcolor:%2523606770%7D._5v3q%20._90oc%20._1s31%20.r_c3pyo2ey1%20.profileLink%7Bfont-weight:500%7D._5v3q%20.r_c3pyo2ey1%7Bborder-bottom-color:%2523e5e5e5;color:%252390949c;line-height:15px;margin:-12px%200%2012px;padding:10px%2023px%2010px%200%7D._5v3q%20.r_c3pyo2ey1.x_c3pynzq_4,._1s31.x_c3pynzq_4%20.r_c3pyo2ey1%7Bcolor:%2523616770%7D._5v3q%20.r_c3pyo2ey1.v_c3pynzq_6,._1s31.v_c3pynzq_6%20.r_c3pyo2ey1%7Bfont-size:13px%7D._3ccb%20.r_c3pyo2ey1%7Bfont-size:12px;padding-bottom:9px;padding-top:11px%7D._6q1a%20.i_c3pyo4rdp.r_c3pyo2ey1%7B-webkit-box-align:center;display:-webkit-box%7D._6q1a%20.i_c3pyo4rdp%20.w_c3pyo4re7%7Bfont-size:14px;line-height:16px%7D._6q1a%20.i_c3pyo4rdp%20.w_c3pyo4re7%20.profileLink%7Bfont-weight:bold%7D._6q1a%20.i_c3pyo4rdp%20.e_c3pyo4re8%7B-webkit-box-align:center;background-color:%252342b72a;border-radius:50%25;-webkit-box-shadow:0%202px%204px%200%20rgba(0,%200,%200,%20.1);display:-webkit-inline-box;height:24px;-webkit-box-pack:center;margin-right:8px;width:24px%7D%2523bootloader_TvoAAb3%7Bheight:42px;%7D.bootloader_TvoAAb3%7Bdisplay:block!important;%7D
6 ms
vMwEbhXEBhM.css
70 ms
00PN0lDxo3L.css
77 ms
DCzlKMwEItk.css
73 ms
JJlvtKKOBzX.js
6 ms
urinFwKapiT.js
7 ms
RvYJCw_ESBi.css
82 ms
6NWFpg-EZsH.js
26 ms
Nq8nSHiYqQL.js
25 ms
ihjLACFC70L.js
26 ms
kllmdWKFTV2.js
27 ms
eQFRPNFkGO0.js
27 ms
nP8xyDpQQVA.js
27 ms
oO86OpA-1FB.js
28 ms
HVDm-VZQNzO.js
29 ms
bH0dE9LKoe-.js
65 ms
WQRTrUPFYqs.js
66 ms
4LqA1KsPuLZ.js
65 ms
2B-0v05oM19.js
68 ms
lASDM10I6Wp.js
71 ms
PSu_oQteh80.js
72 ms
hBYHra2Vbh5.js
73 ms
Z2V_OZxOld1.js
76 ms
aJf13HRCfaQ.js
76 ms
tokyo-marunouchi.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
tokyo-marunouchi.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
tokyo-marunouchi.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyo-marunouchi.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Tokyo-marunouchi.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.
tokyo-marunouchi.jp
Open Graph data is detected on the main page of TOKYO Marunouchi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: