4.9 sec in total
210 ms
3.4 sec
1.2 sec
Welcome to wseattle.com homepage info - get ready to check W Seattle best content for United States right away, or after learning these important things about wseattle.com
Book your stay at W Seattle, a trendy hotel offering contemporary accommodations, luxury amenities and lively experiences in a vibrant downtown setting.
Visit wseattle.comWe analyzed Wseattle.com page load time and found that the first response time was 210 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
wseattle.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value16.5 s
0/100
25%
Value23.1 s
0/100
10%
Value14,470 ms
0/100
30%
Value0.249
50/100
15%
Value51.1 s
0/100
10%
210 ms
241 ms
39 ms
109 ms
48 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 18% of them (29 requests) were addressed to the original Wseattle.com, 31% (48 requests) were made to Maps.googleapis.com and 11% (18 requests) were made to Assets.wseattle.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Assets.wseattle.com.
Page size can be reduced by 1.6 MB (11%)
14.7 MB
13.1 MB
In fact, the total size of Wseattle.com main page is 14.7 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 12.5 MB which makes up the majority of the site volume.
Potential reduce by 338.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.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 338.3 kB or 87% of the original size.
Potential reduce by 42.5 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. W Seattle 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 67% of the original size.
Potential reduce by 187.7 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. Wseattle.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.
Number of requests can be reduced by 55 (39%)
141
86
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of W Seattle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
wseattle.com
210 ms
www.wseattle.com
241 ms
normalize.css
39 ms
lps.css
109 ms
whotels.css
48 ms
modernizr-2.6.2-respond-1.1.0.min.js
96 ms
picturefill.js
52 ms
BrightcoveExperiences.js
11 ms
home.min.js
75 ms
js
85 ms
addthis_widget.js
28 ms
infobubble.js
74 ms
s_code.js
96 ms
s_code_library.js
39 ms
s_code_webcanada.js
45 ms
normalize.css
66 ms
tag.js
172 ms
who1154cl.118730_tb-2.2.jpg
1857 ms
lines_lg_white.png
103 ms
logo-whotels-header.png
101 ms
trust_mark.png
102 ms
W_Seattle_Exterior.jpg
1790 ms
W_Seattle_TRACE_Sushi.jpg
1846 ms
W_Seattle_Fabulous_Corner_King_Room.jpg
1850 ms
W_Seattle_Living_Room.jpg
2032 ms
W_Seattle_EWOW_Suite.jpg
1788 ms
WSansNew-Bold.woff
64 ms
WSansNew-Book.woff
64 ms
WSansNew-Light.woff
63 ms
lps.ttf
1138 ms
tag
15 ms
sf-icon-divider.png
89 ms
tag.js
77 ms
9df31eb8428f2f2e8d242309efbd49e0cdb3c6d5.js
54 ms
social.ttf
55 ms
Starwood.woff
992 ms
abb5af81099611c078c8d31d574d570cf624f04a.js
108 ms
who1154re.118737_tb-2.jpg
1246 ms
jquery.mousewheel.min.js
27 ms
who1154re-118739-TRACE---Sushi-Bar.jpg
1331 ms
who1154re-118734-TRACE-Bar.jpg
1424 ms
who1154mf.118729_tb-2.jpg
1479 ms
sdk.js
878 ms
analytics.js
859 ms
localtime
1675 ms
weather
1278 ms
WSeattle-SpectacularRm.jpg
1971 ms
common.js
712 ms
map.js
1004 ms
util.js
1007 ms
marker.js
1004 ms
overlay.js
985 ms
geometry.js
965 ms
directions.js
966 ms
W_Seattle_Wonderful_King_Room.jpg
790 ms
W_Seattle_Spectacular_King_Room.jpg
1312 ms
W_Seattle_Cool_Corner_King_Room.jpg
1221 ms
W_Seattle_Fabulous_Corner_King_Room.jpg
990 ms
W_Seattle_WOW_Suite_Living_Room.jpg
1034 ms
W_Seattle_EWOW_Suite.jpg
967 ms
WSeattle-Lobby.jpg
1258 ms
whotels-play.jpg
1100 ms
who1154re-118737-TRACE-Restaurant.jpg
1395 ms
WSeattle-SpectacularRm.jpg
605 ms
WSeattle-Lobby.jpg
788 ms
whotels-play.jpg
850 ms
who1154re-118737-TRACE-Restaurant.jpg
1037 ms
infowindow-close.png
299 ms
bat.js
370 ms
collect
91 ms
W_Seattle_Wonderful_King_Room.jpg
591 ms
W_Seattle_Spectacular_King_Room.jpg
694 ms
W_Seattle_Cool_Corner_King_Room.jpg
836 ms
W_Seattle_Fabulous_Corner_King_Room.jpg
836 ms
W_Seattle_WOW_Suite_Living_Room.jpg
889 ms
W_Seattle_EWOW_Suite.jpg
888 ms
WSeattle-SpectacularRm.jpg
1023 ms
WSeattle-Lobby.jpg
1201 ms
whotels-play.jpg
962 ms
who1154re-118737-TRACE-Restaurant.jpg
1070 ms
300lo.json
144 ms
254 ms
s59575188083108
147 ms
sh.8e5f85691f9aaa082472a194.html
145 ms
xd_arbiter.php
294 ms
xd_arbiter.php
650 ms
onion.js
187 ms
openhand_8_8.cur
230 ms
infowindow.js
138 ms
css
405 ms
ViewportInfoService.GetViewportInfo
135 ms
stats.js
79 ms
controls.js
76 ms
like.php
227 ms
conversion_async.js
343 ms
ytc.js
322 ms
transparent.png
277 ms
qeKvIRsJabD.js
575 ms
LVx-xkvaJ0b.png
579 ms
map-marker.png
214 ms
marker-1.png
205 ms
marker-2.png
204 ms
marker-3.png
201 ms
marker-4.png
201 ms
vt
146 ms
vt
146 ms
vt
155 ms
vt
155 ms
vt
143 ms
vt
143 ms
vt
253 ms
vt
205 ms
vt
256 ms
vt
253 ms
vt
317 ms
vt
318 ms
vt
317 ms
vt
317 ms
vt
369 ms
vt
368 ms
vt
368 ms
vt
376 ms
vt
368 ms
vt
403 ms
vt
407 ms
vt
410 ms
vt
406 ms
vt
408 ms
vt
407 ms
vt
460 ms
vt
461 ms
vt
459 ms
vt
456 ms
vt
459 ms
vt
461 ms
vt
495 ms
google4.png
159 ms
mapcnt6.png
148 ms
sv5.png
249 ms
vt
578 ms
vt
505 ms
tmapctrl.png
135 ms
cb_scout5.png
143 ms
tmapctrl4.png
154 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
98 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
100 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
143 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
148 ms
258 ms
179 ms
135 ms
139 ms
57 ms
63 ms
51 ms
29 ms
AuthenticationService.Authenticate
176 ms
wseattle.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-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
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
wseattle.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
wseattle.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wseattle.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 Wseattle.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.
wseattle.com
Open Graph description is not detected on the main page of W Seattle. 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: