Tools & Wizards About Us
waterlooinn.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

waterlooinn.com

Est Hotel Toronto, Canada — book Hotel, 2024 Prices

Page Load Speed

1.8 sec in total

First Response

247 ms

Resources Loaded

1 sec

Page Rendered

542 ms

waterlooinn.com screenshot

About Website

Click here to check amazing Waterlooinn content. Otherwise, check out these important facts you probably never knew about waterlooinn.com

Est Hotel Toronto - 4 star hotel. Featuring a cash machine and a lift, Est Hotel Toronto is situated 3.7 km from Paul Coffey Park. The hotel features Wi-Fi in public areas and parking on site.

Visit waterlooinn.com

Key Findings

We analyzed Waterlooinn.com page load time and found that the first response time was 247 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

waterlooinn.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.353

31/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

est-hotel.html

247 ms

css2

31 ms

common-ec00a397e0.pack.css

76 ms

htheme901-4510dc426c.pack.css

81 ms

sprite.svg

146 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Waterlooinn.com, 8% (3 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (468 ms) relates to the external source Torontohotelsincanada.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.1 kB (69%)

Content Size

263.9 kB

After Optimization

81.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waterlooinn.com main page is 263.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. HTML takes 192.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 166.0 kB

  • Original 192.4 kB
  • After minification 180.2 kB
  • After compression 26.4 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 166.0 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.5 kB
  • After minification 2.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. Waterlooinn images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 12 B

  • Original 3.0 kB
  • After minification 3.0 kB
  • After compression 3.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-24%

Potential reduce by 16.1 kB

  • Original 66.0 kB
  • After minification 66.0 kB
  • After compression 49.9 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. Waterlooinn.com needs all CSS files to be minified and compressed as it can save up to 16.1 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (31%)

Requests Now

36

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

est-hotel.html

est-hotel.html

247 ms

css2

css2

31 ms

common-ec00a397e0.pack.css

common-ec00a397e0.pack.css

76 ms

htheme901-4510dc426c.pack.css

htheme901-4510dc426c.pack.css

81 ms

sprite.svg

sprite.svg

146 ms

_.gif

_.gif

57 ms

booking-logo-76b4799ea3.svg

booking-logo-76b4799ea3.svg

104 ms

reviews-add-pros-568f2e41bb.svg

reviews-add-pros-568f2e41bb.svg

67 ms

reviews-add-cons-8f52720bf1.svg

reviews-add-cons-8f52720bf1.svg

103 ms

client-1.0.0.min.js

client-1.0.0.min.js

129 ms

polyfill.min.js

polyfill.min.js

101 ms

vendors-5c3e92ad7a.pack.js

vendors-5c3e92ad7a.pack.js

222 ms

calendar-f64cd72405.pack.js

calendar-f64cd72405.pack.js

161 ms

app-b85b920bf6.pack.js

app-b85b920bf6.pack.js

200 ms

piwik.js

piwik.js

189 ms

paypal-e405cfec66.svg

paypal-e405cfec66.svg

200 ms

mastercard-6f94b56212.svg

mastercard-6f94b56212.svg

161 ms

visa-logo-a12afce5ee.svg

visa-logo-a12afce5ee.svg

217 ms

icon-exit-popup-49c60f406f.svg

icon-exit-popup-49c60f406f.svg

203 ms

arrow-758f4bc1ad.svg

arrow-758f4bc1ad.svg

124 ms

arrow-circular-3d169fc3e7.svg

arrow-circular-3d169fc3e7.svg

237 ms

close.png

close.png

465 ms

loading.gif

loading.gif

467 ms

prev.png

prev.png

467 ms

next-80bfdf94f6.png

next-80bfdf94f6.png

468 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

68 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

81 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

93 ms

152 ms

static.php

static.php

80 ms

765798712.JPEG

765798712.JPEG

42 ms

968131783.JPEG

968131783.JPEG

51 ms

765794782.JPEG

765794782.JPEG

46 ms

765794908.JPEG

765794908.JPEG

45 ms

765794926.JPEG

765794926.JPEG

84 ms

765795115.JPEG

765795115.JPEG

87 ms

765798712.JPEG

765798712.JPEG

106 ms

968131783.JPEG

968131783.JPEG

123 ms

765794782.JPEG

765794782.JPEG

141 ms

piwik.php

piwik.php

127 ms

Accessibility Review

waterlooinn.com accessibility score

61

Accessibility Issues

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

Form elements do not have associated labels

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

waterlooinn.com best practices score

67

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

waterlooinn.com SEO score

93

Search Engine Optimization Advices

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

waterlooinn.com

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