Tools & Wizards About Us
1111atwater.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

1111atwater.com

Luxury Penthouse Apartments in Downtown Montreal | 1111 Atwater

Page Load Speed

1.4 sec in total

First Response

56 ms

Resources Loaded

1.1 sec

Page Rendered

195 ms

1111atwater.com screenshot

About Website

Welcome to 1111atwater.com homepage info - get ready to check 1111 Atwater best content right away, or after learning these important things about 1111atwater.com

1111 Atwater, Montreal’s most exclusive residential real estate project, has become the benchmark for upscale penthouses for sale in Montreal.

Visit 1111atwater.com

Key Findings

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

Performance Metrics

1111atwater.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value2,590 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.074

95/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

1111atwater.com

56 ms

www.1111atwater.com

136 ms

fbevents.js

58 ms

scrollreveal.min.js

93 ms

magnific-popup.css

124 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 50% of them (28 requests) were addressed to the original 1111atwater.com, 9% (5 requests) were made to Gstatic.com and 7% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (561 ms) belongs to the original domain 1111atwater.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 186.5 kB (9%)

Content Size

2.1 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1111atwater.com main page is 2.1 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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 26.4 kB

  • Original 35.6 kB
  • After minification 33.5 kB
  • After compression 9.2 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 26.4 kB or 74% of the original size.

Image Optimization

-5%

Potential reduce by 86.7 kB

  • Original 1.6 MB
  • After minification 1.5 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. 1111 Atwater images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 67.8 kB

  • Original 410.5 kB
  • After minification 410.5 kB
  • After compression 342.7 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 67.8 kB or 17% of the original size.

CSS Optimization

-10%

Potential reduce by 5.6 kB

  • Original 54.4 kB
  • After minification 52.7 kB
  • After compression 48.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. 1111atwater.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

42

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1111 Atwater. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

1111atwater.com

1111atwater.com

56 ms

www.1111atwater.com

www.1111atwater.com

136 ms

fbevents.js

fbevents.js

58 ms

scrollreveal.min.js

scrollreveal.min.js

93 ms

magnific-popup.css

magnific-popup.css

124 ms

ibs6qhx.css

ibs6qhx.css

154 ms

css_V72y3LbUnooSGMppTJFykya0cZs4kXOMy3Y1tw6B2FA.css

css_V72y3LbUnooSGMppTJFykya0cZs4kXOMy3Y1tw6B2FA.css

43 ms

css_vpuu6kOIfcGmNqXF6HviSi2QnIjck4EL6bXiJD0nwrU.css

css_vpuu6kOIfcGmNqXF6HviSi2QnIjck4EL6bXiJD0nwrU.css

99 ms

api.js

api.js

100 ms

js_I4-poNddJVatMV9nroNiZQEadu3wzSxpxg0tnFnbwUM.js

js_I4-poNddJVatMV9nroNiZQEadu3wzSxpxg0tnFnbwUM.js

150 ms

jquery.min.js

jquery.min.js

136 ms

magnific-popup.js

magnific-popup.js

124 ms

magnific-popup.css

magnific-popup.css

17 ms

magnific-popup.js

magnific-popup.js

41 ms

p.css

p.css

25 ms

css_kvOCFAVEPj0T58rvIq3dXhT3wgbzKI24jgk_7Dqf73M.css

css_kvOCFAVEPj0T58rvIq3dXhT3wgbzKI24jgk_7Dqf73M.css

165 ms

gtm.js

gtm.js

224 ms

recaptcha__en.js

recaptcha__en.js

308 ms

1111-pop-up-20230420-decouvrir-penthouse-modele.jpg

1111-pop-up-20230420-decouvrir-penthouse-modele.jpg

313 ms

1111-pop-up-20230420-discover-penthouse-model.jpg

1111-pop-up-20230420-discover-penthouse-model.jpg

330 ms

close.png

close.png

145 ms

logo.png

logo.png

145 ms

bg-second-menu-header.jpg

bg-second-menu-header.jpg

328 ms

home_btn_play.png

home_btn_play.png

239 ms

home_title_bg.png

home_title_bg.png

385 ms

btn-form-2.jpg

btn-form-2.jpg

328 ms

footer_form_bg.jpg

footer_form_bg.jpg

561 ms

facebook.png

facebook.png

328 ms

instagram.png

instagram.png

384 ms

PAD-Award_1111Atwater-EN.png

PAD-Award_1111Atwater-EN.png

398 ms

Interstate-light.ttf

Interstate-light.ttf

439 ms

Interstate-thin.ttf

Interstate-thin.ttf

378 ms

Interstate-regular.ttf

Interstate-regular.ttf

439 ms

d

d

137 ms

Interstate-bold.ttf

Interstate-bold.ttf

549 ms

d

d

149 ms

titleFont.otf

titleFont.otf

472 ms

js

js

110 ms

hotjar-2850229.js

hotjar-2850229.js

353 ms

destination

destination

169 ms

swap.js

swap.js

210 ms

events.js

events.js

212 ms

js

js

167 ms

anchor

anchor

77 ms

styles__ltr.css

styles__ltr.css

60 ms

recaptcha__en.js

recaptcha__en.js

133 ms

sa.css

sa.css

99 ms

IDLZ5bdCrEGdGR5FKKZfiIWvV7rMSlbAHUEzxUIOBQg.js

IDLZ5bdCrEGdGR5FKKZfiIWvV7rMSlbAHUEzxUIOBQg.js

51 ms

webworker.js

webworker.js

48 ms

logo_48.png

logo_48.png

36 ms

saq_pxl

saq_pxl

38 ms

modules.a4fd7e5489291affcf56.js

modules.a4fd7e5489291affcf56.js

30 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

33 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

36 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

39 ms

recaptcha__en.js

recaptcha__en.js

25 ms

Accessibility Review

1111atwater.com accessibility score

84

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

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

Image elements do not have [alt] attributes

Best Practices

1111atwater.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

1111atwater.com SEO score

86

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

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

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 1111atwater.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 1111atwater.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

1111atwater.com

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