Tools & Wizards About Us
tokyo-office-web.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tokyo-office-web.com

Page Load Speed

8.5 sec in total

First Response

1.6 sec

Resources Loaded

6.4 sec

Page Rendered

411 ms

tokyo-office-web.com screenshot

About Website

Visit tokyo-office-web.com now to see the best up-to-date Tokyo Office Web content and also check out these interesting facts you probably never knew about tokyo-office-web.com

Visit tokyo-office-web.com

Key Findings

We analyzed Tokyo-office-web.com page load time and found that the first response time was 1.6 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

tokyo-office-web.com performance score

0

Network Requests Diagram

1643 ms

common_tenant_en.css

310 ms

asobi_en.css

335 ms

jquery.js

668 ms

jquery.bxSlider.min.js

363 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 22% of them (19 requests) were addressed to the original Tokyo-office-web.com, 66% (57 requests) were made to Tokyo-tenant-web.com and 3% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Tokyo-tenant-web.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 470.2 kB (53%)

Content Size

886.8 kB

After Optimization

416.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyo-office-web.com main page is 886.8 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. 65% of websites need less resources to load. Javascripts take 305.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 49.7 kB

  • Original 59.6 kB
  • After minification 50.2 kB
  • After compression 9.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 9.4 kB, which is 16% 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 49.7 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 20.7 kB

  • Original 267.6 kB
  • After minification 246.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 Office Web images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 189.3 kB

  • Original 305.8 kB
  • After minification 305.4 kB
  • After compression 116.4 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 189.3 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 210.5 kB

  • Original 253.9 kB
  • After minification 251.8 kB
  • After compression 43.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-office-web.com needs all CSS files to be minified and compressed as it can save up to 210.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (34%)

Requests Now

82

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokyo Office Web. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

1643 ms

common_tenant_en.css

common_tenant_en.css

310 ms

asobi_en.css

asobi_en.css

335 ms

jquery.js

jquery.js

668 ms

jquery.bxSlider.min.js

jquery.bxSlider.min.js

363 ms

jquery.prettyPopin.js

jquery.prettyPopin.js

377 ms

11253-1s.jpg

11253-1s.jpg

906 ms

header_button2.gif

header_button2.gif

371 ms

header_button3_en.gif

header_button3_en.gif

372 ms

header_button4_en.gif

header_button4_en.gif

373 ms

title_english2.jpg

title_english2.jpg

539 ms

com_info32.gif

com_info32.gif

375 ms

menu_button1.jpg

menu_button1.jpg

384 ms

menu_button2_en.jpg

menu_button2_en.jpg

689 ms

menu_button3_en.jpg

menu_button3_en.jpg

692 ms

menu_button4_en.jpg

menu_button4_en.jpg

678 ms

menu_button5_en.jpg

menu_button5_en.jpg

693 ms

menu_button6_en.jpg

menu_button6_en.jpg

740 ms

map_en.jpg

map_en.jpg

1114 ms

a_search_button1.gif

a_search_button1.gif

1007 ms

a_search_button2.gif

a_search_button2.gif

1062 ms

a_search_button3.gif

a_search_button3.gif

1068 ms

a_search_button4.gif

a_search_button4.gif

1082 ms

a_search_button5.gif

a_search_button5.gif

1095 ms

cond_search_button1_en.jpg

cond_search_button1_en.jpg

1320 ms

cond_search_button2_en.jpg

cond_search_button2_en.jpg

1383 ms

cond_search_submit_en.jpg

cond_search_submit_en.jpg

1417 ms

button_reset_eng.jpg

button_reset_eng.jpg

1447 ms

syousai_button2_en.gif

syousai_button2_en.gif

1446 ms

hr.gif

hr.gif

1447 ms

syousai_button_en.gif

syousai_button_en.gif

1662 ms

twitter_logo.gif

twitter_logo.gif

1709 ms

back1_en.gif

back1_en.gif

1721 ms

footer_hr.gif

footer_hr.gif

1777 ms

footer_partition.gif

footer_partition.gif

1777 ms

map_shibuya_d0.gif

map_shibuya_d0.gif

1946 ms

map_shinjuku_d0.gif

map_shinjuku_d0.gif

2150 ms

map_chuo_d0.gif

map_chuo_d0.gif

2203 ms

map_chiyoda_d0.gif

map_chiyoda_d0.gif

2284 ms

map_minato_d0.gif

map_minato_d0.gif

2281 ms

11159-1s.jpg

11159-1s.jpg

896 ms

9285-1s.jpg

9285-1s.jpg

897 ms

8992-1s.jpg

8992-1s.jpg

919 ms

615-1s.jpg

615-1s.jpg

920 ms

11254-1s.jpg

11254-1s.jpg

948 ms

11251-1s.jpg

11251-1s.jpg

1224 ms

229-1s.jpg

229-1s.jpg

1231 ms

9137-1s.jpg

9137-1s.jpg

1246 ms

11246-1s.jpg

11246-1s.jpg

1274 ms

11235-1s.jpg

11235-1s.jpg

1271 ms

11164-1s.jpg

11164-1s.jpg

1280 ms

11194-1s.jpg

11194-1s.jpg

1556 ms

11166-1s.jpg

11166-1s.jpg

1607 ms

11140-1s.jpg

11140-1s.jpg

1601 ms

11127-1s.jpg

11127-1s.jpg

1616 ms

10930-1s.jpg

10930-1s.jpg

1626 ms

8692-1s.jpg

8692-1s.jpg

1627 ms

10651-1s.jpg

10651-1s.jpg

1888 ms

ga.js

ga.js

18 ms

menu_button2_o_en.jpg

menu_button2_o_en.jpg

2121 ms

menu_button3_o_en.jpg

menu_button3_o_en.jpg

2269 ms

menu_button4_o_en.jpg

menu_button4_o_en.jpg

2449 ms

__utm.gif

__utm.gif

18 ms

FN3__VAbWWY

FN3__VAbWWY

66 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

19 ms

www-embed-player.js

www-embed-player.js

44 ms

base.js

base.js

72 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

49 ms

ad_status.js

ad_status.js

53 ms

menu_button5_o_en.jpg

menu_button5_o_en.jpg

2158 ms

menu_button6_o_en.jpg

menu_button6_o_en.jpg

2193 ms

pankuzu_bg.jpg

pankuzu_bg.jpg

2253 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

81 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

82 ms

a_search_bg_en.gif

a_search_bg_en.gif

2250 ms

a_search_button1_o.gif

a_search_button1_o.gif

2265 ms

a_search_button2_o.gif

a_search_button2_o.gif

2265 ms

a_search_button3_o.gif

a_search_button3_o.gif

2237 ms

a_search_button4_o.gif

a_search_button4_o.gif

2235 ms

a_search_button5_o.gif

a_search_button5_o.gif

2242 ms

d_frame_bg_en.jpg

d_frame_bg_en.jpg

2430 ms

d_frame_bg2.gif

d_frame_bg2.gif

2236 ms

frame_bg2.jpg

frame_bg2.jpg

2503 ms

mini_frame_bg2.jpg

mini_frame_bg2.jpg

2194 ms

mini_hr.gif

mini_hr.gif

2232 ms

li.gif

li.gif

2208 ms

SEO Factors

tokyo-office-web.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyo-office-web.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Tokyo-office-web.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.

Social Sharing Optimization

tokyo-office-web.com

Open Graph description is not detected on the main page of Tokyo Office Web. 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: