Tools & Wizards About Us
terrasse-royale.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

terrasse-royale.com

Hotel located in Montreal, in the heart of Côte-des-Neiges district.

Page Load Speed

2.7 sec in total

First Response

283 ms

Resources Loaded

2.1 sec

Page Rendered

352 ms

terrasse-royale.com screenshot

About Website

Click here to check amazing Terrasse Royale content. Otherwise, check out these important facts you probably never knew about terrasse-royale.com

Located in the heart of Côte des Neiges, Hotel Terrasse Royale is the ideal location where to stay in Montreal. We are 10 minutes away from downtown and two steps away from the Saint-Joseph Oratory.

Visit terrasse-royale.com

Key Findings

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

Performance Metrics

terrasse-royale.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value2,810 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value40.1 s

0/100

10%

Network Requests Diagram

terrasse-royale.com

283 ms

bootstrap.css

125 ms

bootstrap-datepicker3.min.css

183 ms

jquery.fancybox.css

180 ms

fotorama.css

186 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 71% of them (52 requests) were addressed to the original Terrasse-royale.com, 7% (5 requests) were made to Youtube.com and 7% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (769 ms) belongs to the original domain Terrasse-royale.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.8 kB (5%)

Content Size

9.9 MB

After Optimization

9.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Terrasse-royale.com main page is 9.9 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 8.9 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 19.5 kB

  • Original 25.9 kB
  • After minification 24.1 kB
  • After compression 6.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 19.5 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 143.0 kB

  • Original 8.9 MB
  • After minification 8.8 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. Terrasse Royale images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 271.0 kB

  • Original 765.9 kB
  • After minification 765.9 kB
  • After compression 494.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 271.0 kB or 35% of the original size.

CSS Optimization

-13%

Potential reduce by 14.3 kB

  • Original 111.4 kB
  • After minification 111.4 kB
  • After compression 97.1 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. Terrasse-royale.com needs all CSS files to be minified and compressed as it can save up to 14.3 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (38%)

Requests Now

65

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

terrasse-royale.com

terrasse-royale.com

283 ms

bootstrap.css

bootstrap.css

125 ms

bootstrap-datepicker3.min.css

bootstrap-datepicker3.min.css

183 ms

jquery.fancybox.css

jquery.fancybox.css

180 ms

fotorama.css

fotorama.css

186 ms

style8.css

style8.css

187 ms

font-awesome.min.css

font-awesome.min.css

30 ms

jquery.min.js

jquery.min.js

302 ms

jquery-ui.custom.min.js

jquery-ui.custom.min.js

256 ms

bootstrap.min.js

bootstrap.min.js

305 ms

jquery.fotorama.js

jquery.fotorama.js

302 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

249 ms

kernel64.js

kernel64.js

251 ms

js

js

78 ms

js

js

81 ms

bootstrap-datepicker.min.js

bootstrap-datepicker.min.js

315 ms

bootstrap-datepicker.en.min.js

bootstrap-datepicker.en.min.js

312 ms

style_font_awesome.css

style_font_awesome.css

134 ms

css

css

28 ms

fbevents.js

fbevents.js

51 ms

award.png

award.png

139 ms

bg_arka.png

bg_arka.png

137 ms

bg_town.png

bg_town.png

137 ms

logo.png

logo.png

138 ms

large_best_hotel.png

large_best_hotel.png

137 ms

2.jpg

2.jpg

769 ms

arrow_left.png

arrow_left.png

175 ms

arrow_right.png

arrow_right.png

181 ms

index.html

index.html

131 ms

XsLTWmH_Vu0

XsLTWmH_Vu0

137 ms

dots.png

dots.png

126 ms

bg_bottom_left.png

bg_bottom_left.png

158 ms

bg_bottom_right.png

bg_bottom_right.png

398 ms

duga.png

duga.png

398 ms

NaPecZTIAOhVxoMyOr9n_E7fdM3mCA.ttf

NaPecZTIAOhVxoMyOr9n_E7fdM3mCA.ttf

94 ms

NaPDcZTIAOhVxoMyOr9n_E7ffHjDGIVzZg.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffHjDGIVzZg.ttf

99 ms

NaPDcZTIAOhVxoMyOr9n_E7ffEDBGIVzZg.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffEDBGIVzZg.ttf

102 ms

ajax-room.html

ajax-room.html

341 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

40 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

642 ms

jquery-2.0.3.min.js

jquery-2.0.3.min.js

592 ms

index.js

index.js

599 ms

www-player.css

www-player.css

6 ms

www-embed-player.js

www-embed-player.js

26 ms

base.js

base.js

53 ms

ad_status.js

ad_status.js

479 ms

Q_BtBDv5dYOJzhRCKxAP2e8Htmv8FmyjEtTc2-mDxbE.js

Q_BtBDv5dYOJzhRCKxAP2e8Htmv8FmyjEtTc2-mDxbE.js

457 ms

embed.js

embed.js

392 ms

154.jpg

154.jpg

265 ms

155.jpg

155.jpg

278 ms

156.jpg

156.jpg

350 ms

157.jpg

157.jpg

357 ms

158.jpg

158.jpg

278 ms

159.jpg

159.jpg

262 ms

160.jpg

160.jpg

279 ms

161.jpg

161.jpg

306 ms

162.jpg

162.jpg

358 ms

163.jpg

163.jpg

359 ms

164.jpg

164.jpg

309 ms

165.jpg

165.jpg

371 ms

166.jpg

166.jpg

374 ms

167.jpg

167.jpg

412 ms

168.jpg

168.jpg

418 ms

169.jpg

169.jpg

422 ms

man.png

man.png

421 ms

bed.png

bed.png

432 ms

icons.png

icons.png

434 ms

fotorama.png

fotorama.png

474 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

38 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

38 ms

id

id

92 ms

Create

Create

84 ms

GenerateIT

GenerateIT

14 ms

Accessibility Review

terrasse-royale.com accessibility score

71

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

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

terrasse-royale.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

terrasse-royale.com SEO score

89

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

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Terrasse-royale.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 Terrasse-royale.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

terrasse-royale.com

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