9.6 sec in total
165 ms
8.1 sec
1.4 sec
Visit wtaipei.com now to see the best up-to-date W Taipei content for Taiwan and also check out these interesting facts you probably never knew about wtaipei.com
Transform travel at W Taipei, offering family-friendly hotel rooms, fab dining and ultra-modern venues in the Xinyi District next to the iconic Taipei 101.
Visit wtaipei.comWe analyzed Wtaipei.com page load time and found that the first response time was 165 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wtaipei.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value15.5 s
0/100
25%
Value20.2 s
0/100
10%
Value19,320 ms
0/100
30%
Value0.27
45/100
15%
Value63.1 s
0/100
10%
165 ms
224 ms
101 ms
70 ms
4089 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 19% of them (30 requests) were addressed to the original Wtaipei.com, 29% (47 requests) were made to Maps.googleapis.com and 8% (12 requests) were made to Assets.wtaipei.com.tw. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Apps.bdimg.com.
Page size can be reduced by 2.2 MB (24%)
9.2 MB
6.9 MB
In fact, the total size of Wtaipei.com main page is 9.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 6.3 MB which makes up the majority of the site volume.
Potential reduce by 411.1 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 56.8 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 411.1 kB or 84% of the original size.
Potential reduce by 153.4 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 Taipei images are well optimized though.
Potential reduce by 1.5 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.5 MB or 68% of the original size.
Potential reduce by 188.2 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. Wtaipei.com needs all CSS files to be minified and compressed as it can save up to 188.2 kB or 86% of the original size.
Number of requests can be reduced by 69 (48%)
145
76
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of W Taipei. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
wtaipei.com
165 ms
www.wtaipei.com
224 ms
dc.js
101 ms
conversion.js
70 ms
lightapp.js
4089 ms
normalize.css
18 ms
lps.css
18 ms
whotels.css
21 ms
modernizr-2.6.2-respond-1.1.0.min.js
19 ms
picturefill.js
20 ms
BrightcoveExperiences.js
393 ms
home.min.js
13 ms
js
150 ms
addthis_widget.js
119 ms
infobubble.js
9 ms
s_code.js
158 ms
s_code_library.js
9 ms
s_code_webcanada.js
9 ms
86 ms
logo-whotels-header.png
44 ms
WonderfulTwin2_550x369_lg.jpg
365 ms
trust_mark.png
51 ms
FabulousTwin2_550x369_lg.jpg
482 ms
SpectacularRoom_550x369_lg.jpg
613 ms
who3573gr.101433_lg.jpg
508 ms
who3573gr104645_lg.jpg
544 ms
who3573cl.101446_lg.jpg
590 ms
WOWSuite4550_369_lg.jpg
1014 ms
EWOW4550_369_lg.jpg
937 ms
__utm.gif
21 ms
39 ms
fbevents.js
85 ms
normalize.css
45 ms
lines_lg_white.png
298 ms
tag.js
47 ms
NewLPS_Background_01-1.jpg
284 ms
156 ms
tag
94 ms
WSansNew-Bold.woff
92 ms
WSansNew-Book.woff
92 ms
WSansNew-Light.woff
89 ms
lps.ttf
90 ms
9df31eb8428f2f2e8d242309efbd49e0cdb3c6d5.js
15 ms
sf-icon-divider.png
115 ms
abb5af81099611c078c8d31d574d570cf624f04a.js
59 ms
tag.js
41 ms
social.ttf
114 ms
bat.js
69 ms
Starwood.woff
300 ms
jquery.mousewheel.min.js
165 ms
who3573re.104657_tb-2.jpg
1374 ms
who3573br.101784_tb.jpg
187 ms
who3573mf.142406_tb.jpg
1261 ms
who3573mf.142415_tb.jpg
1258 ms
who3573re.104660_tb-2.jpg
1638 ms
who3573cl.104626_tb-2.jpg
2494 ms
who3573re.101831_tb-2.jpg
2345 ms
who3573re.106915_tb-2.jpg
2259 ms
who3573mf.142399_tb-2.jpg
2343 ms
tag
30 ms
sdk.js
1170 ms
analytics.js
1042 ms
fp.js
1147 ms
ytc.js
1113 ms
conversion_async.js
1310 ms
localtime
2070 ms
weather
1298 ms
toll-free
1915 ms
index.min.js
1494 ms
common.js
1068 ms
map.js
1145 ms
util.js
1148 ms
marker.js
1142 ms
overlay.js
1121 ms
geometry.js
1095 ms
directions.js
1098 ms
300lo.json
392 ms
infowindow-close.png
112 ms
Spectacular-Room-2048x1536.jpg
960 ms
sh.7c7179124ea24ac6ba46caac.html
56 ms
tr
295 ms
collect
282 ms
123-room-package_2048x1536_2.jpg
1130 ms
WiredPlus_2048x1536.jpg
1290 ms
offsite_event.php
322 ms
292 ms
xd_arbiter.php
303 ms
xd_arbiter.php
771 ms
37 ms
128 ms
s59565340685658
127 ms
124 ms
onion.js
90 ms
openhand_8_8.cur
558 ms
infowindow.js
186 ms
css
740 ms
499 ms
518 ms
496 ms
like.php
502 ms
ViewportInfoService.GetViewportInfo
450 ms
stats.js
446 ms
controls.js
438 ms
241 ms
307 ms
rU2ubZ6l1Q5.js
304 ms
LVx-xkvaJ0b.png
296 ms
i18q8D9ZxSOcj8oY8iVPjZBBU2+kGIIypokuqTI+cx3qXMq7Z6PQIsx1DYGrQxtLul50YV50rVcCiNJc0enX4qdkNRYe8j2g46+SIMHapXJw1GFdIWH2DfalQknZeTDWsRW2bqlBK3ORIz9AqJUapQAAAA=
57 ms
8AAAAVeAAAAAAVeAAEAAAAAAAAAAAAAAAAAAAAWAAAAAAAAAAAAAAAAAgAAAAQAAAAEAADABAAAgAQAAAAEAAAABAAAAARAAAAEAADABV4AAAQAAIAEAAA4BAAAAAQAAAAEAAAABAAAAAQAACAEAAAABAAAAAAAUAAAFgAAAAAADgCuAAEAAAAAAAEADgAAAAEAAAAAAAIADgBHAAEAAAAAAAMADgAkAAEAAAAAAAQADgBVAAEAAAAAAAUAFgAOAAEAAAAAAAYABwAyAAEAAAAAAAoAKABjAAMAAQQJAAEADgAAAAMAAQQJAAIADgBHAAMAAQQJAAMADgAkAAMAAQQJAAQADgBVAAMAAQQJAAUAFgAOAAMAAQQJAAYADgA5AAMAAQQJAAoAKABjAGkAYwBvAG0AbwBvAG4AVgBlAHIAcwBpAG8AbgAgADEALgAwAGkAYwBvAG0AbwBvAG5pY29tb29uAGkAYwBvAG0AbwBvAG4AUgBlAGcAdQBsAGEAcgBpAGMAbwBtAG8AbwBuAEcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
57 ms
vjs.woff
279 ms
map-marker.png
186 ms
marker-1.png
278 ms
marker-2.png
201 ms
marker-3.png
199 ms
marker-4.png
198 ms
transparent.png
200 ms
vt
157 ms
vt
157 ms
vt
148 ms
vt
148 ms
vt
154 ms
vt
153 ms
vt
175 ms
vt
174 ms
vt
174 ms
vt
174 ms
vt
176 ms
vt
174 ms
vt
188 ms
vt
194 ms
vt
186 ms
vt
187 ms
vt
191 ms
vt
191 ms
vt
238 ms
vt
197 ms
vt
196 ms
vt
200 ms
vt
197 ms
vt
200 ms
vt
209 ms
vt
210 ms
vt
209 ms
vt
232 ms
vt
230 ms
vt
234 ms
vt
236 ms
vt
234 ms
google4.png
144 ms
mapcnt6.png
165 ms
sv5.png
169 ms
vt
275 ms
vt
197 ms
tmapctrl.png
92 ms
cb_scout5.png
127 ms
tmapctrl4.png
111 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
77 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
103 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
182 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
183 ms
wtaipei.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
wtaipei.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
Missing source maps for large first-party JavaScript
wtaipei.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 Wtaipei.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 Wtaipei.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.
wtaipei.com
Open Graph description is not detected on the main page of W Taipei. 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: