Tools & Wizards About Us
wtaipei.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

wtaipei.com

Taipei Xinyi District Hotels | W Taipei

Page Load Speed

4.9 sec in total

First Response

18 ms

Resources Loaded

3.1 sec

Page Rendered

1.8 sec

wtaipei.com screenshot

About Website

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.com

Key Findings

We analyzed Wtaipei.com page load time and found that the first response time was 18 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

wtaipei.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value22.6 s

0/100

25%

SI (Speed Index)

Value26.9 s

0/100

10%

TBT (Total Blocking Time)

Value26,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value59.9 s

0/100

10%

Network Requests Diagram

wtaipei.com

18 ms

www.wtaipei.com

14 ms

206 ms

marriottCommon.js

75 ms

2f7b7a8dfc406f938b23f5e9f0ee55b0f0aafa2feb045

148 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Wtaipei.com, 50% (24 requests) were made to Marriott.com and 40% (19 requests) were made to Cache.marriott.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Cache.marriott.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 415.2 kB (8%)

Content Size

5.5 MB

After Optimization

5.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wtaipei.com main page is 5.5 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. 80% 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 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 281.8 kB

  • Original 332.4 kB
  • After minification 281.3 kB
  • After compression 50.6 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 51.1 kB, which is 15% 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 281.8 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 240 B

  • Original 4.7 MB
  • After minification 4.7 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 Taipei images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 133.2 kB

  • Original 461.5 kB
  • After minification 460.7 kB
  • After compression 328.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 133.2 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (54%)

Requests Now

39

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 39 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 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wtaipei.com

wtaipei.com

18 ms

www.wtaipei.com

www.wtaipei.com

14 ms

206 ms

marriottCommon.js

marriottCommon.js

75 ms

2f7b7a8dfc406f938b23f5e9f0ee55b0f0aafa2feb045

2f7b7a8dfc406f938b23f5e9f0ee55b0f0aafa2feb045

148 ms

ruxitagentjs_ICA7NQVfhqrux_10293240704151944.js

ruxitagentjs_ICA7NQVfhqrux_10293240704151944.js

40 ms

datalayer

datalayer

375 ms

clientlib-base.min.569a20d572bd560535b3c0a54ddfbdfc.css

clientlib-base.min.569a20d572bd560535b3c0a54ddfbdfc.css

34 ms

clientlib-firstpaint.min.209c189097645983c5c968e7bb26cdc6.css

clientlib-firstpaint.min.209c189097645983c5c968e7bb26cdc6.css

34 ms

clientlib-firstpaint.min.2fbb5f7120a2d3f267d334f4ef2940d4.js

clientlib-firstpaint.min.2fbb5f7120a2d3f267d334f4ef2940d4.js

66 ms

clientlib-sitev2.min.9af61f69888ee052f09b6b16b836d36d.css

clientlib-sitev2.min.9af61f69888ee052f09b6b16b836d36d.css

63 ms

clientlib-bptv2.min.6b3d0a3536455c94aaa9d7f9dd6d7adb.css

clientlib-bptv2.min.6b3d0a3536455c94aaa9d7f9dd6d7adb.css

67 ms

clientlibs.d317a5d9bbba6e3a517179296858ca98.css

clientlibs.d317a5d9bbba6e3a517179296858ca98.css

99 ms

clientlib-hws-jquery.min.4709cf7b87b5f9ad6240b012a8445143.js

clientlib-hws-jquery.min.4709cf7b87b5f9ad6240b012a8445143.js

90 ms

launch-EN1ce795381cea451fa40478e502ecce2f.min.js

launch-EN1ce795381cea451fa40478e502ecce2f.min.js

50 ms

clientlibs.min.d317a5d9bbba6e3a517179296858ca98.css

clientlibs.min.d317a5d9bbba6e3a517179296858ca98.css

87 ms

clientlibs.min.e2c9f39a0dca08809b2f13e1a4ac6a83.js

clientlibs.min.e2c9f39a0dca08809b2f13e1a4ac6a83.js

101 ms

clientlibs.e2c9f39a0dca08809b2f13e1a4ac6a83.js

clientlibs.e2c9f39a0dca08809b2f13e1a4ac6a83.js

109 ms

clientlib-base.min.97809428e8a7697927b484e808804291.js

clientlib-base.min.97809428e8a7697927b484e808804291.js

109 ms

clientlib-sitev2.min.ceeab1b5874c4dbe696d6ce084ee3939.js

clientlib-sitev2.min.ceeab1b5874c4dbe696d6ce084ee3939.js

184 ms

clientlib-bptv2.min.2a7e11b9ee054b4d29e721b81be561a6.js

clientlib-bptv2.min.2a7e11b9ee054b4d29e721b81be561a6.js

119 ms

polyfill.min.js

polyfill.min.js

5 ms

bundle.js

bundle.js

132 ms

bv.js

bv.js

25 ms

g9SiY

g9SiY

126 ms

marriottCommon.js

marriottCommon.js

123 ms

wh-logo-white-hws-12325.png

wh-logo-white-hws-12325.png

1010 ms

wh-logo-fullcolor-hws-13225.png

wh-logo-fullcolor-hws-13225.png

997 ms

tpewh-suite-1446-hor-clsc.jpg

tpewh-suite-1446-hor-clsc.jpg

997 ms

tpewh-pool-2413-hor-clsc.jpg

tpewh-pool-2413-hor-clsc.jpg

1001 ms

tpewh-fireplace-6915-hor-clsc.jpg

tpewh-fireplace-6915-hor-clsc.jpg

999 ms

tpewh-wet-1460-hor-clsc.jpg

tpewh-wet-1460-hor-clsc.jpg

1000 ms

tpewh-restaurant-1844-hor-clsc.jpg

tpewh-restaurant-1844-hor-clsc.jpg

1004 ms

tpewh-woobar-6921-hor-clsc.jpg

tpewh-woobar-6921-hor-clsc.jpg

1006 ms

tpewh-bar-1832-hor-clsc.jpg

tpewh-bar-1832-hor-clsc.jpg

1002 ms

tpewh-desk-1463-hor-clsc.jpg

tpewh-desk-1463-hor-clsc.jpg

1000 ms

tpewh-library-1810-hor-clsc.jpg

tpewh-library-1810-hor-clsc.jpg

1746 ms

tpewh-outdoors-6949-hor-clsc.jpg

tpewh-outdoors-6949-hor-clsc.jpg

1002 ms

tpewh-entry-2397-hor-clsc.jpg

tpewh-entry-2397-hor-clsc.jpg

1745 ms

tpewh-wonderful-roomview-8571-hor-wide.jpg

tpewh-wonderful-roomview-8571-hor-wide.jpg

2315 ms

Swiss721BT-Medium.woff

Swiss721BT-Medium.woff

911 ms

Swiss721BT-Bold.woff

Swiss721BT-Bold.woff

913 ms

Swiss721BT-Regular.woff

Swiss721BT-Regular.woff

1188 ms

mi-icons.woff

mi-icons.woff

1189 ms

mi-brand-logo-icons.woff

mi-brand-logo-icons.woff

1188 ms

661 ms

bundle.js

bundle.js

224 ms

bundle.js

bundle.js

223 ms

Accessibility Review

wtaipei.com accessibility score

76

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

[aria-*] attributes do not match their roles

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

wtaipei.com best practices score

75

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

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

wtaipei.com SEO score

86

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

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

    EN

  • Encoding

    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 it matches the claimed language. 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.

Social Sharing Optimization

wtaipei.com

Open Graph data is detected on the main page of W Taipei. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: