4.4 sec in total
188 ms
3.3 sec
936 ms
Click here to check amazing Westin Indianapolis content for United States. Otherwise, check out these important facts you probably never knew about westinindianapolis.com
Book Directly at The Westin Indianapolis & Get Exclusive Rates. Plan Your Next Vacation or Business Trip at Our Hotel.
Visit westinindianapolis.comWe analyzed Westinindianapolis.com page load time and found that the first response time was 188 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
westinindianapolis.com performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value8.2 s
2/100
25%
Value21.4 s
0/100
10%
Value25,700 ms
0/100
30%
Value0.53
14/100
15%
Value53.1 s
0/100
10%
188 ms
152 ms
18 ms
19 ms
14 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 18% of them (31 requests) were addressed to the original Westinindianapolis.com, 22% (37 requests) were made to Maps.googleapis.com and 11% (18 requests) were made to Assets.westinindianapolis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source C075bc729c06f1660ab0-26036f841beec34b6ee6033739fb1571.r9.cf1.rackcdn.com.
Page size can be reduced by 1.6 MB (14%)
11.2 MB
9.6 MB
In fact, the total size of Westinindianapolis.com main page is 11.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 9.0 MB which makes up the majority of the site volume.
Potential reduce by 315.4 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 44.5 kB, which is 12% 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 315.4 kB or 85% of the original size.
Potential reduce by 24.6 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. Westin Indianapolis images are well optimized though.
Potential reduce by 1.1 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.1 MB or 67% of the original size.
Potential reduce by 180.0 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. Westinindianapolis.com needs all CSS files to be minified and compressed as it can save up to 180.0 kB or 86% of the original size.
Number of requests can be reduced by 73 (48%)
152
79
The browser has sent 152 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Westin Indianapolis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
westinindianapolis.com
188 ms
www.westinindianapolis.com
152 ms
normalize.css
18 ms
lps.css
19 ms
westin.css
14 ms
modernizr-2.6.2-respond-1.1.0.min.js
16 ms
picturefill.js
18 ms
BrightcoveExperiences.js
37 ms
home.min.js
28 ms
js
326 ms
addthis_widget.js
245 ms
infobubble.js
28 ms
s_code.js
338 ms
s_code_library.js
27 ms
s_code_webcanada.js
26 ms
normalize.css
39 ms
tag.js
191 ms
wes1033ex-123308-Exterior-1.2.jpg
1735 ms
tag.js
217 ms
jquery.mousewheel.min.js
59 ms
logo-westin-header.png
35 ms
trust_mark.png
35 ms
sf-icon-divider.png
37 ms
wes1033ex-123308-Exterior.jpg
1213 ms
wes1033gr-153605-King-Plaza-Suite-Bedroom.jpg
1070 ms
wes1033gr-153591-Chairmans-Suite-Living-Area.jpg
1425 ms
wes1033ex63185.jpg
1537 ms
wes1033po123317.jpg
1118 ms
wes1033re.123318_tb-1.jpg
1262 ms
wes1033cl.123316_tb-1.jpg
1797 ms
wes1033re.123319_tb-1.jpg
1796 ms
wes1033br.123310_tb-1.jpg
1900 ms
GalaxieCopernicus-Medium.woff
93 ms
GalaxieCopernicus-Book.woff
21 ms
lps.ttf
6 ms
social.ttf
19 ms
Starwood.woff
1182 ms
tag
584 ms
sdk.js
683 ms
analytics.js
667 ms
localtime
1215 ms
weather
809 ms
westin-hotels-better-tomorrows-lifestyle.jpg
1198 ms
common.js
664 ms
map.js
701 ms
util.js
769 ms
marker.js
696 ms
overlay.js
725 ms
geometry.js
663 ms
directions.js
664 ms
infowindow-close.png
136 ms
wes1033gr-153594-Spacious-Double-Bed-Guest-Room.jpg
736 ms
wes1033gr-153606-Spacious-King-Guest-Room.jpg
732 ms
wes1033cl-153611-Club-Lounge.jpg
1130 ms
wes1033gr-153595-Executive-Suite-Living-Area.jpg
856 ms
wes1033gr-153605-King-Plaza-Suite-Bedroom.jpg
857 ms
Westin-Birthday.jpg
926 ms
westin-hotels-better-tomorrows-lifestyle.jpg
1120 ms
Westin-Birthday.jpg
1067 ms
9df31eb8428f2f2e8d242309efbd49e0cdb3c6d5.js
172 ms
wes1033gr-153594-Spacious-Double-Bed-Guest-Room.jpg
629 ms
wes1033gr-153606-Spacious-King-Guest-Room.jpg
705 ms
wes1033cl-153611-Club-Lounge.jpg
774 ms
wes1033gr-153595-Executive-Suite-Living-Area.jpg
799 ms
wes1033gr-153605-King-Plaza-Suite-Bedroom.jpg
773 ms
westin-hotels-better-tomorrows-lifestyle.jpg
1102 ms
Westin-Birthday.jpg
1103 ms
300lo.json
177 ms
collect
109 ms
sh.8e5f85691f9aaa082472a194.html
87 ms
489 ms
xd_arbiter.php
113 ms
xd_arbiter.php
139 ms
abb5af81099611c078c8d31d574d570cf624f04a.js
64 ms
onion.js
95 ms
openhand_8_8.cur
184 ms
ViewportInfoService.GetViewportInfo
155 ms
stats.js
61 ms
controls.js
56 ms
ViewportInfoService.GetViewportInfo
213 ms
infowindow.js
116 ms
css
322 ms
bat.js
281 ms
s74621068276464
98 ms
transparent.png
128 ms
map-marker.png
84 ms
marker-1.png
83 ms
marker-2.png
83 ms
marker-3.png
83 ms
marker-4.png
84 ms
marker-5.png
83 ms
marker-6.png
84 ms
marker-7.png
100 ms
marker-8.png
83 ms
google4.png
194 ms
mapcnt6.png
194 ms
sv5.png
212 ms
like.php
283 ms
tmapctrl.png
170 ms
cb_scout5.png
172 ms
tmapctrl4.png
168 ms
vt
143 ms
vt
138 ms
vt
132 ms
vt
135 ms
vt
133 ms
vt
133 ms
vt
137 ms
vt
137 ms
vt
203 ms
vt
138 ms
vt
149 ms
vt
141 ms
vt
142 ms
vt
149 ms
vt
154 ms
vt
202 ms
vt
202 ms
vt
201 ms
vt
201 ms
vt
199 ms
vt
219 ms
vt
225 ms
qeKvIRsJabD.js
166 ms
LVx-xkvaJ0b.png
140 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
176 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
249 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
311 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
343 ms
FM_Pages_Westin
89 ms
conversion_async.js
357 ms
ta.bfp;dc_seg=19666690;ord=7189848166890.442
116 ms
tre
188 ms
activity;src=4161152;type=invmedia;cat=wn2r01pn;ord=7081495241727.68;prd=
349 ms
ytc.js
278 ms
tag
69 ms
AuthenticationService.Authenticate
193 ms
tre
318 ms
lb
277 ms
uat_homepage_westin
270 ms
beacon
269 ms
153 ms
ps
149 ms
tre
165 ms
tre
165 ms
pixel
83 ms
83 ms
Pug
72 ms
lb
44 ms
69 ms
64 ms
xuid
26 ms
demconf.jpg
25 ms
55 ms
54 ms
sd
23 ms
40 ms
cmap
25 ms
sync
91 ms
39 ms
45 ms
43 ms
39 ms
pixel
17 ms
tap.php
77 ms
nr-885.min.js
46 ms
wes1033gr.153605_tb-1.2.jpg
395 ms
wes1033wn.123307_tb-1.4.jpg
574 ms
448c072440
64 ms
westinindianapolis.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
button, link, and menuitem elements do not have accessible names.
ARIA IDs are not unique
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
Buttons do not have an accessible name
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
westinindianapolis.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
westinindianapolis.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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Westinindianapolis.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 Westinindianapolis.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.
westinindianapolis.com
Open Graph description is not detected on the main page of Westin Indianapolis. 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: