1.7 sec in total
121 ms
1.4 sec
154 ms
Visit hyattplaceaustin.com now to see the best up-to-date Hyatt Place Austin content and also check out these interesting facts you probably never knew about hyattplaceaustin.com
With over 400 global locations, Hyatt Place hotels offer everything you need for a work/life balance—spacious rooms, 24/7 fitness centers and free breakfast with your stay at most locations.
Visit hyattplaceaustin.comWe analyzed Hyattplaceaustin.com page load time and found that the first response time was 121 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
hyattplaceaustin.com performance score
121 ms
23 ms
50 ms
38 ms
37 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hyattplaceaustin.com, 15% (18 requests) were made to Tags.tiqcdn.com and 7% (8 requests) were made to Hyatt.com. The less responsive or slowest element that took the longest time to load (330 ms) relates to the external source Tags.tiqcdn.com.
Page size can be reduced by 1.4 MB (60%)
2.3 MB
920.0 kB
In fact, the total size of Hyattplaceaustin.com main page is 2.3 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. 65% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 54.3 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 54.3 kB or 77% of the original size.
Potential reduce by 19.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. Hyatt Place Austin images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 70% of the original size.
Potential reduce by 250.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. Hyattplaceaustin.com needs all CSS files to be minified and compressed as it can save up to 250.8 kB or 81% of the original size.
Number of requests can be reduced by 92 (84%)
109
17
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hyatt Place Austin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
hyattplace.html
121 ms
utag.sync.js
23 ms
A.global_corporate.css+global_shared.css+hyattBuilt.css,Mcc.TET0PmJj5C.css.pagespeed.cf.B0z1aPxndv.css
50 ms
A.hyatt_global.css.pagespeed.cf.vUYkpkPlr9.css
38 ms
A.brand.css.pagespeed.cf.kd08u3h_zx.css
37 ms
modernizr-1.7.min.js.pagespeed.jm.nmJjtiVLOf.js
36 ms
json2.js.pagespeed.jm.ujKTlw4TsD.js
55 ms
en.css
161 ms
mapcontrol.ashx
80 ms
jquery-ui.js.pagespeed.jm.8E3XjkBZb4.js
48 ms
quickbook.js.pagespeed.jm.DWTdNabNz7.js
46 ms
A.jquery-ui.css.pagespeed.cf.w6N8bJjmRj.css
47 ms
A.quickbook.css+quickbook_search.css+quickbook_calendar.css,Mcc.UO2wviV6u1.css.pagespeed.cf.0tZl1oUT7E.css
81 ms
quickbook_search.js+quickbook_calendar.js.pagespeed.jc.CpZcu7Rz7G.js
58 ms
A.mediaelementplayer.css.pagespeed.cf.kVzXemlRNy.css
58 ms
A.jquery.jplayer.css.pagespeed.cf.paZnKFSjr-.css
51 ms
css
122 ms
sha1.js+aes.js.pagespeed.jc.Kg_g0H69aT.js
60 ms
login.js.pagespeed.jm.juSB3mAOjf.js
59 ms
jquery.hashchange.js+V7ClientSideClustering.js+jquery.nivo.slider.hyatt.js+jquery.bgiframe.js+jquery.hoverIntent.js.pagespeed.jc.OTMobNyGJ7.js
71 ms
hyattOverlay.js.pagespeed.jm.zNDDl0lpSs.js
70 ms
jquery.jplayer.min.js.pagespeed.jm.iievTw5GIV.js
75 ms
jScrollPane.js+jquery.mousewheel.js.pagespeed.jc.ysh2MGYTTe.js
74 ms
hyatt.js.pagespeed.jm.ckDUZaFDg1.js
74 ms
TweenLite.js.pagespeed.jm.CPbPK5rmA_.js
75 ms
CSSPlugin.js.pagespeed.jm.1PYCgqLuVg.js
76 ms
EasePack.min.js.pagespeed.jm.pjiOJ0Ogt5.js
73 ms
global.js.pagespeed.jm.TNf3uDq6ID.js
115 ms
main.js.pagespeed.jm.BRMEodoEaI.js
115 ms
id
35 ms
target.js
63 ms
brandbar.css.pagespeed.ce.GXcZ3HDh1w.css
13 ms
skeleton.css
12 ms
utag.js
318 ms
veapicore.js
65 ms
xhyattLogoGray.png.pagespeed.ic.ZPIDQw1qi1.png
56 ms
down_arrow_grey.gif.pagespeed.ce.M1FIkq9yPR.gif
55 ms
css
24 ms
xicon_question_mark.gif.pagespeed.ic.nCoFKSwK3f.png
8 ms
xsignin_0.gif.pagespeed.ic.EGtSx-NU9H.png
9 ms
xgp_signup_not_a-Member_en.gif.pagespeed.ic.-guXznhVPS.png
13 ms
icon_close_blue.gif.pagespeed.ce.AZnkG9wET0.gif
9 ms
xHP150580_Hyatt-Place-JD-Power-Award-Creative_956x550.jpg.pagespeed.ic.WM2hQ208ml.jpg
32 ms
xbrandLogo.png.pagespeed.ic.fP7rBozmdk.png
9 ms
xada-icon.png.pagespeed.ic.NKo11wpuK0.png
104 ms
xfooter_EN.png.pagespeed.ic.a0MOwNr8zP.png
105 ms
xicon_facebook.png.pagespeed.ic.sMW4JAALMr.jpg
106 ms
xicon_twitter.png.pagespeed.ic.A56zPPtbmu.png
100 ms
xicon_youtube.png.pagespeed.ic.MdZZEZfym1.jpg
106 ms
xui-bg_highlight-soft_100_eeeeee_1x100.png.pagespeed.ic.XIVzfYzOrZ.png
28 ms
xui-icons_222222_256x240.png.pagespeed.ic.r5medQJvsG.png
8 ms
loading.gif.pagespeed.ce.3Wt7C_XDry.gif
28 ms
HyattPlace_BRG_v2.jpg
64 ms
HyattPlace_SkilletMasthead.jpeg
77 ms
HyattPlace_WifiMasthead.jpg.jpeg
9 ms
iframe.jsp
107 ms
utag.currency.js
8 ms
ajax
69 ms
ajax
37 ms
utag.88220.js
7 ms
utag.88241.js
8 ms
utag.88227.js
30 ms
utag.86172.js
27 ms
utag.86005.js
29 ms
utag.88167.js
29 ms
utag.86179.js
28 ms
utag.86180.js
28 ms
utag.86465.js
29 ms
utag.88073.js
30 ms
utag.88048.js
30 ms
utag.86118.js
28 ms
utag.88120.js
29 ms
utag.88187.js
29 ms
90078857-753a-48d3-9a79-857b623313bf.js
24 ms
s45483914492651
42 ms
jquery-1.7.2.js.pagespeed.jm.Q81GAaiYtU.js
97 ms
sha1.js+aes.js.pagespeed.jc.bReV0h7-ul.js
107 ms
5369.js
34 ms
4
29 ms
conversion_async.js
29 ms
channel.js
26 ms
i.gif
139 ms
875ncf34667.js
30 ms
hhotels.html
36 ms
g.js
32 ms
activityi;src=4837240;type=media0;cat=brand0;u11=en;u17=BrandPlace%3ALandindPage;ord=5961366943083.703
62 ms
111 ms
ps
72 ms
7
145 ms
xcurr_lang_bg.gif.pagespeed.ic.Jj8K8WO9Dd.png
93 ms
xlanguageIcon.png.pagespeed.ic.7q_lenxfQD.png
76 ms
tp
76 ms
i.gif
78 ms
xcarousel_rotator_active.png.pagespeed.ic.oJ-jClQIQW.png
69 ms
xcarousel_rotator_inactive.png.pagespeed.ic.x8TYwb5-S0.png
105 ms
brand-bar-sprite.png
109 ms
external_link_icon_grey.gif.pagespeed.ce._XuY4MSUFO.gif
76 ms
id
60 ms
dayUpdate.jsp;jsessionid=17A1324595C48ADFD3647D85E7ECEB18.atg05-ord-atg2
100 ms
01539474c9b3009a1c72160d453800048004e04000720
93 ms
1bHRUMxmJHoup12DnI9XmQ.woff
66 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
35 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
48 ms
wkfQbvfT_02e2IWO3yYueQ.woff
67 ms
pixel
64 ms
ibs:dpid=22069&dpuuid=206723832735
29 ms
Pug
46 ms
60 ms
pixel
41 ms
76 ms
tap.php
29 ms
32 ms
cmap
46 ms
utag.js
330 ms
src=4886625;type=sales;cat=otb6yqt5;qty=1;cost=0;u1=%7C%7Cen%7C;u6=[ffl];u8=en;u16=[pc];ord=[OrderID]
80 ms
beacon
106 ms
pixel
44 ms
sd
38 ms
sync
51 ms
AdX
70 ms
hyattplaceaustin.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hyattplaceaustin.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Hyattplaceaustin.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.
hyattplaceaustin.com
Open Graph description is not detected on the main page of Hyatt Place Austin. 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: