1.1 sec in total
57 ms
886 ms
204 ms
Visit austin.intercontinental.com now to see the best up-to-date Austin Intercontinental content for United States and also check out these interesting facts you probably never knew about austin.intercontinental.com
View Austin hotels available for your next trip. IHG offers great rates on 43 in Austin with flexible cancellation fees. Whether you're traveling for business or to relax, browse our Austin hotels and...
Visit austin.intercontinental.comWe analyzed Austin.intercontinental.com page load time and found that the first response time was 57 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
austin.intercontinental.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value20.0 s
0/100
25%
Value10.1 s
9/100
10%
Value7,940 ms
0/100
30%
Value0.199
62/100
15%
Value26.4 s
0/100
10%
57 ms
43 ms
41 ms
33 ms
36 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 44% of them (34 requests) were addressed to the original Austin.intercontinental.com, 30% (23 requests) were made to Assets.letgroup.com and 9% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (331 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 233.8 kB (11%)
2.1 MB
1.9 MB
In fact, the total size of Austin.intercontinental.com main page is 2.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. 70% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 22.0 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.0 kB or 77% of the original size.
Potential reduce by 81.1 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. Austin Intercontinental images are well optimized though.
Potential reduce by 110.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 110.0 kB or 69% of the original size.
Potential reduce by 20.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. Austin.intercontinental.com needs all CSS files to be minified and compressed as it can save up to 20.8 kB or 83% of the original size.
Number of requests can be reduced by 23 (30%)
76
53
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Austin Intercontinental. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
austin.intercontinental.com
57 ms
jx.stylesheet.css
43 ms
colorbox.css
41 ms
jquery.min.js
33 ms
jquery.jixedbar.min-u20151218v2.js
36 ms
jquery.colorbox-min.js
75 ms
bookmarks-u20151218.js
43 ms
googletranslate-let.js
158 ms
austin.intercontinental.css
11 ms
jquery.cycle.all.min.js
51 ms
theme.css
49 ms
calendar.js
52 ms
calendar-en.js
49 ms
calendar-setup.js
74 ms
date_functions.js
71 ms
jx.bar.css
17 ms
plusone.js
180 ms
logo.jpg
38 ms
ga.js
37 ms
home-22.png
27 ms
bookmark-22.png
24 ms
calendar-22.png
22 ms
maps-22a.png
148 ms
tripadvisor-22.png
24 ms
rateus-22.png
152 ms
weather-22.png
27 ms
facebook-22.png
25 ms
twitter-22.png
27 ms
broadway-austin-banner.png
28 ms
jqg_13741628250.jpg
151 ms
jqg_13741628251.jpg
149 ms
jqg_1374162825.jpg
151 ms
jqg_13741628253.jpg
148 ms
jqg_13741628252.jpg
148 ms
jqg_13669326880.jpg
151 ms
jqg_1366932688.jpg
151 ms
jqg_13669324582.jpg
152 ms
jqg_1390936227.jpg
175 ms
jqg_13909362270.jpg
152 ms
jqg_13909362271.jpg
175 ms
jqg_13909362272.jpg
172 ms
jqg_13909362273.jpg
175 ms
jqg_13909362274.jpg
176 ms
jqg_13909362275.jpg
196 ms
jqg_13669324590.jpg
197 ms
jqg_13669324592.jpg
228 ms
jqg_1366932458.jpg
227 ms
jqg_13669324596.jpg
228 ms
jqg_13669324599.jpg
230 ms
bknd_nav.jpg
227 ms
decorativeline.jpg
226 ms
cmsimg_1260379294.jpg
227 ms
cmsimg_1260379953.jpg
231 ms
cmsimg_1260379954.jpg
235 ms
bknd_gallery.png
234 ms
ico-twitter.gif
233 ms
logo-aaa.jpg
233 ms
bknd_footer.gif
233 ms
ihg-rewards-club.png
257 ms
__utm.gif
66 ms
controls.png
132 ms
hide.gif
36 ms
border.png
89 ms
loading_background.png
89 ms
loading.gif
89 ms
like.php
159 ms
cb=gapi.loaded_0
33 ms
cb=gapi.loaded_1
75 ms
fastbutton
109 ms
postmessageRelay
53 ms
cb=gapi.loaded_0
29 ms
cb=gapi.loaded_1
28 ms
vpc6VNjRPXV.js
294 ms
LVx-xkvaJ0b.png
331 ms
api.js
44 ms
core:rpc:shindig.random:shindig.sha1.js
82 ms
2536007149-postmessagerelay.js
59 ms
austin.intercontinental.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s are not contained by their required parent element
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
austin.intercontinental.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
austin.intercontinental.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Austin.intercontinental.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Austin.intercontinental.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
austin.intercontinental.com
Open Graph description is not detected on the main page of Austin Intercontinental. 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: