Tools & Wizards About Us
tokyo.andaz.hyatt.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tokyo.andaz.hyatt.jp

銀座、新橋近くの新たなランドマーク虎ノ門ヒルズ内の高級ホテル アンダーズ東京

Page Load Speed

1.4 sec in total

First Response

75 ms

Resources Loaded

945 ms

Page Rendered

344 ms

tokyo.andaz.hyatt.jp screenshot

About Website

Visit tokyo.andaz.hyatt.jp now to see the best up-to-date Tokyo Andaz Hyatt content for Japan and also check out these interesting facts you probably never knew about tokyo.andaz.hyatt.jp

銀座･新橋・虎ノ門エリアに初上陸、アンダーズ東京の公式サイト。新たなランドマーク虎ノ門ヒルズ内にオープンした『アンダーズ東京（Andaz Tokyo）』は、ラグジュアリーホテルとして知られるハイアットグループが手がけたライフスタイルホテルです。

Visit tokyo.andaz.hyatt.jp

Key Findings

We analyzed Tokyo.andaz.hyatt.jp page load time and found that the first response time was 75 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

tokyo.andaz.hyatt.jp performance score

0

Network Requests Diagram

tokyo.andaz.hyatt.jp

75 ms

home.html

24 ms

home.html

80 ms

A.compressed-main.css.pagespeed.cf.Z6at4cdJmm.css

15 ms

A.brand.css.pagespeed.cf.dyWwraNnYl.css

26 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Tokyo.andaz.hyatt.jp, 78% (46 requests) were made to Tokyo.andaz.hyatt.com and 5% (3 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (319 ms) relates to the external source Tags.tiqcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 837.6 kB (52%)

Content Size

1.6 MB

After Optimization

768.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyo.andaz.hyatt.jp main page is 1.6 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. Javascripts take 891.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 85.8 kB

  • Original 112.1 kB
  • After minification 102.3 kB
  • After compression 26.2 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 85.8 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 803 B

  • Original 462.1 kB
  • After minification 461.3 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 Andaz Hyatt images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 639.4 kB

  • Original 891.3 kB
  • After minification 890.6 kB
  • After compression 252.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 639.4 kB or 72% of the original size.

CSS Optimization

-79%

Potential reduce by 111.6 kB

  • Original 141.0 kB
  • After minification 139.1 kB
  • After compression 29.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.andaz.hyatt.jp needs all CSS files to be minified and compressed as it can save up to 111.6 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (63%)

Requests Now

56

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tokyo.andaz.hyatt.jp

tokyo.andaz.hyatt.jp

75 ms

home.html

home.html

24 ms

home.html

home.html

80 ms

A.compressed-main.css.pagespeed.cf.Z6at4cdJmm.css

A.compressed-main.css.pagespeed.cf.Z6at4cdJmm.css

15 ms

A.brand.css.pagespeed.cf.dyWwraNnYl.css

A.brand.css.pagespeed.cf.dyWwraNnYl.css

26 ms

A.ja.css.pagespeed.cf.l3Uo9DlpD6.css

A.ja.css.pagespeed.cf.l3Uo9DlpD6.css

14 ms

jquery-ui.js.pagespeed.jm.8E3XjkBZb4.js

jquery-ui.js.pagespeed.jm.8E3XjkBZb4.js

48 ms

A.jquery-ui.css.pagespeed.cf.w6N8bJjmRj.css

A.jquery-ui.css.pagespeed.cf.w6N8bJjmRj.css

23 ms

utag.sync.js

utag.sync.js

23 ms

compressed-core.js.pagespeed.jm.dHawd5OxYZ.js

compressed-core.js.pagespeed.jm.dHawd5OxYZ.js

26 ms

quickbook.js.pagespeed.jm.DWTdNabNz7.js

quickbook.js.pagespeed.jm.DWTdNabNz7.js

35 ms

A.quickbook.css+quickbook_calendar.css,Mcc._OxkaMTb5L.css.pagespeed.cf.F9bLQVMJTZ.css

A.quickbook.css+quickbook_calendar.css,Mcc._OxkaMTb5L.css.pagespeed.cf.F9bLQVMJTZ.css

39 ms

quickbook_calendar.js.pagespeed.jm.CXuv-DRnfD.js

quickbook_calendar.js.pagespeed.jm.CXuv-DRnfD.js

34 ms

css

css

73 ms

compressed.js.pagespeed.jm.SGyBM76yln.js

compressed.js.pagespeed.jm.SGyBM76yln.js

42 ms

AndazSlidePromo.js+main.js.pagespeed.jc.hXmG2w7_Db.js

AndazSlidePromo.js+main.js.pagespeed.jc.hXmG2w7_Db.js

56 ms

brandbar.css.pagespeed.ce.GXcZ3HDh1w.css

brandbar.css.pagespeed.ce.GXcZ3HDh1w.css

33 ms

skeleton.css

skeleton.css

15 ms

id

id

15 ms

target.js

target.js

67 ms

xicon_question_mark.gif.pagespeed.ic.nCoFKSwK3f.png

xicon_question_mark.gif.pagespeed.ic.nCoFKSwK3f.png

21 ms

gp_ja_signin_0.gif.pagespeed.ce.67yCe0qwx2.gif

gp_ja_signin_0.gif.pagespeed.ce.67yCe0qwx2.gif

100 ms

xgp_signup_not_a-Member_ja.gif.pagespeed.ic.FjC_NEX88N.jpg

xgp_signup_not_a-Member_ja.gif.pagespeed.ic.FjC_NEX88N.jpg

20 ms

icon_close_blue.gif.pagespeed.ce.AZnkG9wET0.gif

icon_close_blue.gif.pagespeed.ce.AZnkG9wET0.gif

24 ms

css

css

22 ms

1280x427xAndaz-Tokyo-Toranomon-Hills-P720-Elevator-Art.masthead-feature-panel-medium.jpg.pagespeed.ic.swThuYCmJ0.jpg

1280x427xAndaz-Tokyo-Toranomon-Hills-P720-Elevator-Art.masthead-feature-panel-medium.jpg.pagespeed.ic.swThuYCmJ0.jpg

17 ms

xinstagram-20x20.png.pagespeed.ic.asB2SZfkLf.png

xinstagram-20x20.png.pagespeed.ic.asB2SZfkLf.png

13 ms

xpinterest-20x20.png.pagespeed.ic.A6rOPKgG6d.png

xpinterest-20x20.png.pagespeed.ic.A6rOPKgG6d.png

92 ms

xgoogle-plus-20x20.png.pagespeed.ic.1vL-pLTIyB.png

xgoogle-plus-20x20.png.pagespeed.ic.1vL-pLTIyB.png

31 ms

570x190xcq5dam.thumbnail.570.190.png.pagespeed.ic.EospX_7j1q.jpg

570x190xcq5dam.thumbnail.570.190.png.pagespeed.ic.EospX_7j1q.jpg

92 ms

570x190xcq5dam.thumbnail.570.190.png.pagespeed.ic.usfx-BaIDT.jpg

570x190xcq5dam.thumbnail.570.190.png.pagespeed.ic.usfx-BaIDT.jpg

28 ms

xada-icon.png.pagespeed.ic.NKo11wpuK0.png

xada-icon.png.pagespeed.ic.NKo11wpuK0.png

63 ms

215x100xcq5dam.thumbnail.215.121.png.pagespeed.ic.pc0K2MJoL9.jpg

215x100xcq5dam.thumbnail.215.121.png.pagespeed.ic.pc0K2MJoL9.jpg

64 ms

215x100xcq5dam.thumbnail.215.121.png.pagespeed.ic.Me9CycQw1k.jpg

215x100xcq5dam.thumbnail.215.121.png.pagespeed.ic.Me9CycQw1k.jpg

63 ms

215x100xcq5dam.thumbnail.215.121.png.pagespeed.ic.j_Y_V7RDkK.jpg

215x100xcq5dam.thumbnail.215.121.png.pagespeed.ic.j_Y_V7RDkK.jpg

66 ms

215x100xcq5dam.thumbnail.215.121.png.pagespeed.ic.mylwVsV8aX.jpg

215x100xcq5dam.thumbnail.215.121.png.pagespeed.ic.mylwVsV8aX.jpg

62 ms

xfooter_JA.png.pagespeed.ic._DcMoX7vfh.png

xfooter_JA.png.pagespeed.ic._DcMoX7vfh.png

63 ms

utag.js

utag.js

319 ms

Andaz-Tokyo-Toranomon-Hills-P720-Elevator-Art.masthead-feature-panel-medium.jpg

Andaz-Tokyo-Toranomon-Hills-P720-Elevator-Art.masthead-feature-panel-medium.jpg

31 ms

xcontentBgImg_2.png.pagespeed.ic.uxr5Z4hOi9.png

xcontentBgImg_2.png.pagespeed.ic.uxr5Z4hOi9.png

10 ms

id

id

8 ms

ajax

ajax

23 ms

ajax

ajax

20 ms

xlogo_3.png.pagespeed.ic.v8Dn0J-E0Y.png

xlogo_3.png.pagespeed.ic.v8Dn0J-E0Y.png

8 ms

loading.gif.pagespeed.ce.3Wt7C_XDry.gif

loading.gif.pagespeed.ce.3Wt7C_XDry.gif

21 ms

xiconsprite.png.pagespeed.ic.OCKHSbfQvS.png

xiconsprite.png.pagespeed.ic.OCKHSbfQvS.png

8 ms

xlanguageIcon.png.pagespeed.ic.7q_lenxfQD.png

xlanguageIcon.png.pagespeed.ic.7q_lenxfQD.png

11 ms

xsocialBgbtm.png.pagespeed.ic.yTeQf7KsKs.png

xsocialBgbtm.png.pagespeed.ic.yTeQf7KsKs.png

8 ms

xsocialBg.png.pagespeed.ic.is0hJTnZJv.png

xsocialBg.png.pagespeed.ic.is0hJTnZJv.png

13 ms

xshareBgLeft.png.pagespeed.ic.KM7c6waUy9.png

xshareBgLeft.png.pagespeed.ic.KM7c6waUy9.png

17 ms

xshareBgRight.png.pagespeed.ic.rCE-USukft.png

xshareBgRight.png.pagespeed.ic.rCE-USukft.png

14 ms

xsocialsprite.png.pagespeed.ic.s2wmKddbHS.png

xsocialsprite.png.pagespeed.ic.s2wmKddbHS.png

17 ms

xgradt.png.pagespeed.ic.ebIZPGtC2M.png

xgradt.png.pagespeed.ic.ebIZPGtC2M.png

20 ms

brand-bar-sprite.png

brand-bar-sprite.png

23 ms

external_link_icon_grey.gif.pagespeed.ce._XuY4MSUFO.gif

external_link_icon_grey.gif.pagespeed.ce._XuY4MSUFO.gif

22 ms

xui-bg_highlight-soft_100_eeeeee_1x100.png.pagespeed.ic.XIVzfYzOrZ.png

xui-bg_highlight-soft_100_eeeeee_1x100.png.pagespeed.ic.XIVzfYzOrZ.png

32 ms

utag.currency.js

utag.currency.js

9 ms

login.js

login.js

83 ms

4

4

66 ms

SEO Factors

tokyo.andaz.hyatt.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • 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.andaz.hyatt.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tokyo.andaz.hyatt.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.andaz.hyatt.jp

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