Tools & Wizards About Us
tokyo-marunouchi.jp screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

tokyo-marunouchi.jp

DMO TOKYO/Marunouchi | The perfect place for business events.

Page Load Speed

4.4 sec in total

First Response

352 ms

Resources Loaded

3.6 sec

Page Rendered

489 ms

tokyo-marunouchi.jp screenshot

About Website

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.jp

Key Findings

We analyzed Tokyo-marunouchi.jp page load time and found that the first response time was 352 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

tokyo-marunouchi.jp performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

74/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

tokyo-marunouchi.jp

352 ms

324 ms

common.css

289 ms

root.css

425 ms

js

62 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 67% of them (50 requests) were addressed to the original Tokyo-marunouchi.jp, 25% (19 requests) were made to Static.xx.fbcdn.net and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Tokyo-marunouchi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.2 kB (2%)

Content Size

7.1 MB

After Optimization

6.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyo-marunouchi.jp main page is 7.1 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. 75% 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.9 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 22.1 kB

  • Original 29.0 kB
  • After minification 26.7 kB
  • After compression 6.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 22.1 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 15.8 kB

  • Original 6.9 MB
  • After minification 6.9 MB

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.

JavaScript Optimization

-66%

Potential reduce by 72.0 kB

  • Original 108.4 kB
  • After minification 105.1 kB
  • After compression 36.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 72.0 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 53.3 kB

  • Original 63.7 kB
  • After minification 48.3 kB
  • After compression 10.4 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.

Requests Breakdown

Number of requests can be reduced by 32 (44%)

Requests Now

73

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 73 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 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tokyo-marunouchi.jp

tokyo-marunouchi.jp

352 ms

324 ms

common.css

common.css

289 ms

root.css

root.css

425 ms

js

js

62 ms

sdk.js

sdk.js

16 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

720 ms

common.js

common.js

482 ms

root.js

root.js

483 ms

jquery.inview.min.js

jquery.inview.min.js

483 ms

hd_logo_01.gif

hd_logo_01.gif

142 ms

gnav_btn_01.gif

gnav_btn_01.gif

186 ms

gnav_btn_01_sp.png

gnav_btn_01_sp.png

147 ms

gnav_btn_02.gif

gnav_btn_02.gif

151 ms

gnav_btn_02_sp.png

gnav_btn_02_sp.png

152 ms

gnav_btn_10.gif

gnav_btn_10.gif

284 ms

gnav_btn_10_sp.png

gnav_btn_10_sp.png

318 ms

gnav_btn_03.gif

gnav_btn_03.gif

318 ms

gnav_btn_03_sp.png

gnav_btn_03_sp.png

440 ms

gnav_btn_04.gif

gnav_btn_04.gif

339 ms

gnav_btn_04_sp.png

gnav_btn_04_sp.png

424 ms

gnav_btn_09.gif

gnav_btn_09.gif

432 ms

gnav_btn_09_sp.png

gnav_btn_09_sp.png

435 ms

gnav_btn_05.gif

gnav_btn_05.gif

441 ms

gnav_btn_05_sp.png

gnav_btn_05_sp.png

493 ms

gnav_btn_06.gif

gnav_btn_06.gif

616 ms

gnav_btn_06_sp.png

gnav_btn_06_sp.png

669 ms

gnav_btn_11.png

gnav_btn_11.png

669 ms

gnav_btn_12.png

gnav_btn_12.png

670 ms

gnav_btn_13.png

gnav_btn_13.png

671 ms

gnav_btn_07.png

gnav_btn_07.png

671 ms

gnav_btn_07_sp.png

gnav_btn_07_sp.png

706 ms

gnav_btn_08.png

gnav_btn_08.png

723 ms

gnav_btn_08_sp.png

gnav_btn_08_sp.png

723 ms

top_main_bg_01.png

top_main_bg_01.png

728 ms

top_main_vis_01.jpg

top_main_vis_01.jpg

1458 ms

top_main_vis_00.png

top_main_vis_00.png

805 ms

top_main_vis_02.jpg

top_main_vis_02.jpg

1557 ms

top_main_vis_03.jpg

top_main_vis_03.jpg

1445 ms

top_logo_01.png

top_logo_01.png

866 ms

top_logo_01_sp.png

top_logo_01_sp.png

872 ms

top_txt_scroll.png

top_txt_scroll.png

915 ms

top_img_01.png

top_img_01.png

1543 ms

top_btn_01.gif

top_btn_01.gif

972 ms

sdk.js

sdk.js

7 ms

top_img_02.png

top_img_02.png

1215 ms

top_img_03.png

top_img_03.png

1754 ms

top_img_04.png

top_img_04.png

1745 ms

top_img_05.png

top_img_05.png

1444 ms

top_img_06.png

top_img_06.png

1603 ms

gnav_btn_07_on.png

gnav_btn_07_on.png

1388 ms

gnav_btn_08_on.png

gnav_btn_08_on.png

1422 ms

page.php

page.php

232 ms

top_btn_01_on.gif

top_btn_01_on.gif

1424 ms

LO_ZbPzgR8d.css

LO_ZbPzgR8d.css

21 ms

RVjDLTes46u.css

RVjDLTes46u.css

23 ms

XB9agIerVXI.css

XB9agIerVXI.css

21 ms

_tdn2SGo1cv.js

_tdn2SGo1cv.js

27 ms

Mw5y7Z3v-mj.js

Mw5y7Z3v-mj.js

25 ms

pLoSlJD7y1F.js

pLoSlJD7y1F.js

55 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

26 ms

Glud--w-qOK.js

Glud--w-qOK.js

25 ms

_eawcKGGOQC.js

_eawcKGGOQC.js

26 ms

p55HfXW__mM.js

p55HfXW__mM.js

53 ms

ALTQi95mOyD.js

ALTQi95mOyD.js

51 ms

r5HcOUY3OX6.js

r5HcOUY3OX6.js

53 ms

DtR0X5vxkLl.js

DtR0X5vxkLl.js

64 ms

8IAOdJiZGNE.js

8IAOdJiZGNE.js

53 ms

Dpom1HQzAgH.js

Dpom1HQzAgH.js

64 ms

daRG11v-d-4.js

daRG11v-d-4.js

83 ms

HzxD9aAXSyD.js

HzxD9aAXSyD.js

63 ms

309040429_435747728540759_2326129196771561982_n.jpg

309040429_435747728540759_2326129196771561982_n.jpg

95 ms

309103125_435747725207426_7051825467293927118_n.jpg

309103125_435747725207426_7051825467293927118_n.jpg

85 ms

F3tBKTAgRNo.js

F3tBKTAgRNo.js

14 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

10 ms

Accessibility Review

tokyo-marunouchi.jp accessibility score

75

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

tokyo-marunouchi.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tokyo-marunouchi.jp SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: