Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

westinharbourcastletoronto.com

Toronto Waterfront Hotel | The Westin Harbour Castle, Toronto

Page Load Speed

6.7 sec in total

First Response

12 ms

Resources Loaded

5.1 sec

Page Rendered

1.6 sec

westinharbourcastletoronto.com screenshot

About Website

Visit westinharbourcastletoronto.com now to see the best up-to-date Westin Harbour Castle Toronto content for Canada and also check out these interesting facts you probably never knew about westinharbourcastletoronto.com

Reserve your stay at The Westin Harbour Castle, Toronto. Located on the scenic waterfront, our downtown Toronto hotel provides friendly service, superb hotel amenities and stunning harbour views.

Visit westinharbourcastletoronto.com

Key Findings

We analyzed Westinharbourcastletoronto.com page load time and found that the first response time was 12 ms and then it took 6.7 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

westinharbourcastletoronto.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value22.2 s

0/100

25%

SI (Speed Index)

Value23.6 s

0/100

10%

TBT (Total Blocking Time)

Value23,520 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value63.7 s

0/100

10%

Network Requests Diagram

westinharbourcastletoronto.com

12 ms

www.westinharbourcastletoronto.com

40 ms

974 ms

marriottCommon.js

453 ms

f18a856994406f938b23f5e9f0ee55b0f0aafa2feb045

109 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Westinharbourcastletoronto.com, 52% (33 requests) were made to Cache.marriott.com and 41% (26 requests) were made to Marriott.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Cache.marriott.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (16%)

Content Size

6.8 MB

After Optimization

5.7 MB

In fact, the total size of Westinharbourcastletoronto.com main page is 6.8 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. Only a small number of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 268.8 kB

  • Original 312.7 kB
  • After minification 262.8 kB
  • After compression 43.9 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 49.9 kB, which is 16% 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 268.8 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 2.0 kB

  • Original 5.3 MB
  • After minification 5.3 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. Westin Harbour Castle Toronto images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 833.2 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 324.9 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 833.2 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (42%)

Requests Now

55

After Optimization

32

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Westin Harbour Castle Toronto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

westinharbourcastletoronto.com accessibility score

72

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

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

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

westinharbourcastletoronto.com SEO score

83

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

High

Tap targets are not sized appropriately

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

Open Graph description is not detected on the main page of Westin Harbour Castle Toronto. 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: