Tools & Wizards About Us
wchicago-lakeshore.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

wchicago-lakeshore.com

Hotel in Chicago, Illinois | W Chicago - Lakeshore

Page Load Speed

6.6 sec in total

First Response

190 ms

Resources Loaded

5.1 sec

Page Rendered

1.3 sec

wchicago-lakeshore.com screenshot

About Website

Visit wchicago-lakeshore.com now to see the best up-to-date W Chicago Lakeshore content for United States and also check out these interesting facts you probably never knew about wchicago-lakeshore.com

Book your stay at our pet-friendly hotel in downtown Chicago, Illinois. Enjoy an indoor pool and a fab waterfront location on Lake Shore Drive.

Visit wchicago-lakeshore.com

Key Findings

We analyzed Wchicago-lakeshore.com page load time and found that the first response time was 190 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

wchicago-lakeshore.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value35.7 s

0/100

10%

TBT (Total Blocking Time)

Value18,700 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.245

51/100

15%

TTI (Time to Interactive)

Value53.7 s

0/100

10%

Network Requests Diagram

wchicago-lakeshore.com

190 ms

www.wchicago-lakeshore.com

171 ms

normalize.css

60 ms

lps.css

101 ms

whotels.css

146 ms

Our browser made a total of 160 requests to load all elements on the main page. We found that 26% of them (42 requests) were addressed to the original Wchicago-lakeshore.com, 23% (36 requests) were made to Maps.googleapis.com and 13% (20 requests) were made to Assets.wchicago-lakeshore.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Assets.wchicago-lakeshore.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (8%)

Content Size

21.6 MB

After Optimization

19.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wchicago-lakeshore.com main page is 21.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. 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 19.4 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 338.3 kB

  • Original 388.6 kB
  • After minification 342.4 kB
  • After compression 50.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. This page needs HTML code to be minified as it can gain 46.2 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 338.3 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 137.4 kB

  • Original 19.4 MB
  • After minification 19.2 MB

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. W Chicago Lakeshore images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 1.1 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 536.7 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 1.1 MB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 187.7 kB

  • Original 218.8 kB
  • After minification 204.1 kB
  • After compression 31.1 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. Wchicago-lakeshore.com needs all CSS files to be minified and compressed as it can save up to 187.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (55%)

Requests Now

147

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wchicago-lakeshore.com

wchicago-lakeshore.com

190 ms

www.wchicago-lakeshore.com

www.wchicago-lakeshore.com

171 ms

normalize.css

normalize.css

60 ms

lps.css

lps.css

101 ms

whotels.css

whotels.css

146 ms

modernizr-2.6.2-respond-1.1.0.min.js

modernizr-2.6.2-respond-1.1.0.min.js

30 ms

picturefill.js

picturefill.js

29 ms

BrightcoveExperiences.js

BrightcoveExperiences.js

30 ms

home.min.js

home.min.js

436 ms

js

js

96 ms

addthis_widget.js

addthis_widget.js

45 ms

infobubble.js

infobubble.js

15 ms

s_code.js

s_code.js

419 ms

s_code_library.js

s_code_library.js

5 ms

s_code_webcanada.js

s_code_webcanada.js

29 ms

normalize.css

normalize.css

19 ms

tag.js

tag.js

261 ms

who2005cl.152048_tb-4.jpg

who2005cl.152048_tb-4.jpg

2335 ms

lines_lg_white.png

lines_lg_white.png

127 ms

logo-whotels-header.png

logo-whotels-header.png

126 ms

1600x900_View.jpg

1600x900_View.jpg

339 ms

1600x900_WonderfulKing.jpg

1600x900_WonderfulKing.jpg

1810 ms

1600x900_CurrentSeating.jpg

1600x900_CurrentSeating.jpg

341 ms

1600x900_LivingRoom.jpg

1600x900_LivingRoom.jpg

585 ms

1600x900_Altitude.jpg

1600x900_Altitude.jpg

584 ms

WSansNew-Bold.woff

WSansNew-Bold.woff

28 ms

WSansNew-Book.woff

WSansNew-Book.woff

29 ms

WSansNew-Light.woff

WSansNew-Light.woff

62 ms

lps.ttf

lps.ttf

15 ms

tag

tag

16 ms

9df31eb8428f2f2e8d242309efbd49e0cdb3c6d5.js

9df31eb8428f2f2e8d242309efbd49e0cdb3c6d5.js

54 ms

sf-icon-divider.png

sf-icon-divider.png

54 ms

tag.js

tag.js

112 ms

social.ttf

social.ttf

28 ms

abb5af81099611c078c8d31d574d570cf624f04a.js

abb5af81099611c078c8d31d574d570cf624f04a.js

77 ms

Starwood.woff

Starwood.woff

327 ms

who2005re.153518_tb-4.jpg

who2005re.153518_tb-4.jpg

1473 ms

who2005mf.161896_tb-4.jpg

who2005mf.161896_tb-4.jpg

1474 ms

who2005re.161900_tb.jpg

who2005re.161900_tb.jpg

312 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

187 ms

bat.js

bat.js

167 ms

sdk.js

sdk.js

1147 ms

analytics.js

analytics.js

1102 ms

localtime

localtime

1943 ms

weather

weather

1938 ms

Cubs.jpg

Cubs.jpg

2240 ms

common.js

common.js

1128 ms

map.js

map.js

1206 ms

util.js

util.js

1307 ms

marker.js

marker.js

1252 ms

overlay.js

overlay.js

1233 ms

geometry.js

geometry.js

1168 ms

directions.js

directions.js

1216 ms

300lo.json

300lo.json

234 ms

1600x900_WonderfulDouble.jpg

1600x900_WonderfulDouble.jpg

415 ms

1600x900_SpectacularKing.jpg

1600x900_SpectacularKing.jpg

412 ms

1600x900_MarvelousSuiteLivingRoom.jpg

1600x900_MarvelousSuiteLivingRoom.jpg

597 ms

1600x900_WOWSuite.jpg

1600x900_WOWSuite.jpg

2041 ms

1600x900_ExtremeWOWSuite.jpg

1600x900_ExtremeWOWSuite.jpg

720 ms

infowindow-close.png

infowindow-close.png

306 ms

2048x1536_Misc.jpg

2048x1536_Misc.jpg

1304 ms

2048x1536_PLAY.jpg

2048x1536_PLAY.jpg

1151 ms

2048x1536_3019_Wheels.jpg

2048x1536_3019_Wheels.jpg

1148 ms

Cubs.jpg

Cubs.jpg

896 ms

2048x1536_Misc.jpg

2048x1536_Misc.jpg

722 ms

2048x1536_PLAY.jpg

2048x1536_PLAY.jpg

901 ms

2048x1536_3019_Wheels.jpg

2048x1536_3019_Wheels.jpg

1071 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

231 ms

conversion_async.js

conversion_async.js

440 ms

ytc.js

ytc.js

410 ms

collect

collect

172 ms

1600x900_WonderfulDouble.jpg

1600x900_WonderfulDouble.jpg

759 ms

1600x900_SpectacularKing.jpg

1600x900_SpectacularKing.jpg

380 ms

1600x900_MarvelousSuiteLivingRoom.jpg

1600x900_MarvelousSuiteLivingRoom.jpg

583 ms

1600x900_WOWSuite.jpg

1600x900_WOWSuite.jpg

581 ms

1600x900_ExtremeWOWSuite.jpg

1600x900_ExtremeWOWSuite.jpg

1529 ms

Cubs.jpg

Cubs.jpg

962 ms

2048x1536_Misc.jpg

2048x1536_Misc.jpg

1515 ms

2048x1536_PLAY.jpg

2048x1536_PLAY.jpg

1109 ms

2048x1536_3019_Wheels.jpg

2048x1536_3019_Wheels.jpg

1154 ms

562 ms

xd_arbiter.php

xd_arbiter.php

193 ms

xd_arbiter.php

xd_arbiter.php

348 ms

onion.js

onion.js

185 ms

openhand_8_8.cur

openhand_8_8.cur

254 ms

s76466264112386

s76466264112386

135 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

213 ms

stats.js

stats.js

137 ms

controls.js

controls.js

197 ms

like.php

like.php

483 ms

100

100

179 ms

infowindow.js

infowindow.js

146 ms

css

css

511 ms

101

101

142 ms

102

102

262 ms

355 ms

map-marker.png

map-marker.png

174 ms

marker-1.png

marker-1.png

172 ms

marker-2.png

marker-2.png

167 ms

marker-3.png

marker-3.png

164 ms

marker-4.png

marker-4.png

345 ms

marker-5.png

marker-5.png

344 ms

marker-6.png

marker-6.png

347 ms

marker-7.png

marker-7.png

347 ms

marker-8.png

marker-8.png

409 ms

marker-9.png

marker-9.png

410 ms

marker-10.png

marker-10.png

411 ms

marker-11.png

marker-11.png

410 ms

marker-12.png

marker-12.png

403 ms

marker-13.png

marker-13.png

409 ms

marker-14.png

marker-14.png

521 ms

marker-15.png

marker-15.png

516 ms

marker-16.png

marker-16.png

520 ms

marker-17.png

marker-17.png

519 ms

marker-18.png

marker-18.png

518 ms

transparent.png

transparent.png

327 ms

google4.png

google4.png

281 ms

mapcnt6.png

mapcnt6.png

279 ms

sv5.png

sv5.png

281 ms

vt

vt

163 ms

vt

vt

178 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

308 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

297 ms

vt

vt

211 ms

vt

vt

212 ms

vt

vt

207 ms

vt

vt

207 ms

vt

vt

209 ms

vt

vt

206 ms

vt

vt

234 ms

vt

vt

233 ms

vt

vt

233 ms

vt

vt

232 ms

vt

vt

234 ms

vt

vt

233 ms

vt

vt

273 ms

vt

vt

271 ms

vt

vt

271 ms

vt

vt

270 ms

vt

vt

270 ms

vt

vt

270 ms

vt

vt

293 ms

vt

vt

295 ms

tmapctrl.png

tmapctrl.png

203 ms

cb_scout5.png

cb_scout5.png

230 ms

tmapctrl4.png

tmapctrl4.png

228 ms

247 ms

214 ms

215 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

130 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

209 ms

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

210 ms

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

210 ms

127 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

64 ms

nr-885.min.js

nr-885.min.js

43 ms

who2005gr.153520_tb-4.2.jpg

who2005gr.153520_tb-4.2.jpg

518 ms

who2005re.161900_tb.2.jpg

who2005re.161900_tb.2.jpg

441 ms

who2005wn.161902_tb-4.5.jpg

who2005wn.161902_tb-4.5.jpg

572 ms

448c072440

448c072440

68 ms

Accessibility Review

wchicago-lakeshore.com accessibility score

74

Accessibility Issues

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

High

button, link, and menuitem elements do not have accessible names.

High

[aria-*] attributes do not have valid values

High

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Best Practices

wchicago-lakeshore.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

wchicago-lakeshore.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wchicago-lakeshore.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 Wchicago-lakeshore.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.

Social Sharing Optimization

wchicago-lakeshore.com

Open Graph description is not detected on the main page of W Chicago Lakeshore. 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: