1.6 sec in total
15 ms
1.1 sec
506 ms
Welcome to omniaustindowntown.com homepage info - get ready to check Omni Austin Downtown best content right away, or after learning these important things about omniaustindowntown.com
Book your stay at Omni Austin Hotel Downtown for an unforgettable Austin, TX city getaway. Visit the State Capitol, 6th Street nightlife, or Zilker Park.
Visit omniaustindowntown.comWe analyzed Omniaustindowntown.com page load time and found that the first response time was 15 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.
omniaustindowntown.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value10.0 s
0/100
25%
Value28.7 s
0/100
10%
Value26,230 ms
0/100
30%
Value0.088
92/100
15%
Value106.6 s
0/100
10%
15 ms
53 ms
38 ms
140 ms
52 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Omniaustindowntown.com, 75% (47 requests) were made to Omnihotels.com and 10% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (384 ms) relates to the external source Omnihotels.com.
Page size can be reduced by 287.0 kB (4%)
8.0 MB
7.7 MB
In fact, the total size of Omniaustindowntown.com main page is 8.0 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. Only a small number of websites need less resources to load. Images take 7.4 MB which makes up the majority of the site volume.
Potential reduce by 108.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 29.4 kB, which is 21% 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 108.9 kB or 79% of the original size.
Potential reduce by 175.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. Omni Austin Downtown images are well optimized though.
Potential reduce by 2.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 708 B
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. Omniaustindowntown.com needs all CSS files to be minified and compressed as it can save up to 708 B or 14% of the original size.
Number of requests can be reduced by 23 (45%)
51
28
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Omni Austin Downtown. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
omniaustindowntown.com
15 ms
AustinDowntown.aspx
53 ms
austin-downtown
38 ms
austin-downtown
140 ms
100411844-100413964.js
52 ms
OtAutoBlock.js
102 ms
otSDKStub.js
170 ms
bundle
42 ms
css2
63 ms
gsx0mqu.css
48 ms
bundle
52 ms
horizontal-accordion.css
43 ms
themes.css
56 ms
horizontal-accordion-loop.js
44 ms
destinctively-omni-slider.css
51 ms
distinctively-omni-slider.js
52 ms
photo-gallery-simple.css
55 ms
photo-gallery-simple.js
56 ms
resort-faqs.css
64 ms
jquery.min.js
62 ms
js
162 ms
d036fc462f.js
71 ms
p.css
26 ms
account_icon--solid.svg
19 ms
arrow-forward--white.svg
90 ms
austctr-omni-austin-hotel-downtown-couple.jpg
92 ms
hero-slider-cta-arrow-white.svg
88 ms
ausctr_7_2880x1870.jpg
96 ms
austin-downtown-547404980-2880x1870.jpg
384 ms
omni-holiday-connecting-rooms-2880.jpg
91 ms
account_icon--solid.svg
86 ms
icon-info-connecting-rooms.svg
88 ms
x-connecting.svg
89 ms
omni-bright-lights-big-savings-1170x660.jpg
90 ms
omni-magical-memories-1170x660.jpg
92 ms
ausctr-omni-austin-downtown-parlor-suite-living-room.jpg
93 ms
car-couple-shutterstock_482490445.jpg
92 ms
ausctr-se-bourbon-bbq-music-1170x660.jpg
98 ms
ausctr-dining-food.jpg
94 ms
ausctr-fitness-rendering.jpg
172 ms
ausctr-omni_austin_hotel_downtown-2023-exterior_night_1170x660.jpg
174 ms
ausctr-omni-austin-hotel-downtown-capital-a-restaurant-1.jpg
96 ms
ausctr-omni_austin_hotel_downtown-2023-pool_overview_1170x660.jpg
97 ms
ausctr-omni_austin_hotel_downtown-2023-pool_bar_1170x660.jpg
381 ms
ausctr-omni-austin-hotel-downtown-presidents-house-coffee-shop.jpg
173 ms
ausctr-omni-austin-hotel-downtown-boardroom-foyer.jpg
382 ms
omni-orchid-black.png
380 ms
plp-calendar-icon.svg
295 ms
S6u9w4BMUTPHh7USeww.woff
384 ms
S6uyw4BMUTPHvxo.woff
383 ms
d
278 ms
d
280 ms
d
381 ms
d
379 ms
d
379 ms
omni-bright-lights-big-savings-1170x660.jpg
278 ms
omni-magical-memories-1170x660.jpg
278 ms
ausctr-omni-austin-downtown-parlor-suite-living-room.jpg
276 ms
car-couple-shutterstock_482490445.jpg
276 ms
tertiary-cta-arrow-r1.svg
276 ms
calendar.svg
276 ms
tertiary-cta-arrow.svg
106 ms
S6u_w4BMUTPHjxsI9w2PHw.woff
32 ms
omniaustindowntown.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
ARIA IDs are not unique
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.
omniaustindowntown.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
omniaustindowntown.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
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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omniaustindowntown.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 Omniaustindowntown.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.
omniaustindowntown.com
Open Graph description is not detected on the main page of Omni Austin Downtown. 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: