Tools & Wizards About Us
mytorontohome.com screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 41

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

mytorontohome.com

Toronto Real Estate - Search Homes For Sale Toronto - Search Toronto Condos For Sale - Royal LePage Signature Realty, Brokerage

Page Load Speed

2.8 sec in total

First Response

999 ms

Resources Loaded

1.5 sec

Page Rendered

338 ms

mytorontohome.com screenshot

About Website

Welcome to mytorontohome.com homepage info - get ready to check My Toronto Home best content right away, or after learning these important things about mytorontohome.com

Toronto homes for sale. Search Toronto real estate for sale. Research Toronto schools and discover which Toronto neighbourhoods fit your lifestyle. Thousands of Toronto MLS real estate listings availa...

Visit mytorontohome.com

Key Findings

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

Performance Metrics

mytorontohome.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

mytorontohome.com

999 ms

css

55 ms

jquery-ui.custom.css

28 ms

colorbox.css

27 ms

style_2.css

26 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 90% of them (56 requests) were addressed to the original Mytorontohome.com, 5% (3 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (999 ms) belongs to the original domain Mytorontohome.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 242.0 kB (19%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mytorontohome.com main page is 1.3 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. 60% of websites need less resources to load. Images take 918.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 44.6 kB

  • Original 51.4 kB
  • After minification 45.3 kB
  • After compression 6.8 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 6.1 kB, which is 12% 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 44.6 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 11.4 kB

  • Original 918.4 kB
  • After minification 907.0 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. My Toronto Home images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 178.1 kB

  • Original 316.5 kB
  • After minification 316.0 kB
  • After compression 138.4 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 178.1 kB or 56% of the original size.

CSS Optimization

-36%

Potential reduce by 7.9 kB

  • Original 21.9 kB
  • After minification 21.9 kB
  • After compression 14.0 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. Mytorontohome.com needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (41%)

Requests Now

58

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mytorontohome.com

mytorontohome.com

999 ms

css

css

55 ms

jquery-ui.custom.css

jquery-ui.custom.css

28 ms

colorbox.css

colorbox.css

27 ms

style_2.css

style_2.css

26 ms

style.css

style.css

24 ms

newsfeed.css

newsfeed.css

26 ms

js

js

117 ms

jquery.js

jquery.js

39 ms

jquery.cookie.js

jquery.cookie.js

28 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

28 ms

jquery-ui.core.js

jquery-ui.core.js

28 ms

jquery-ui.effects.js

jquery-ui.effects.js

37 ms

jquery.cycle2.js

jquery.cycle2.js

37 ms

jquery.cycle2.carousel.js

jquery.cycle2.carousel.js

37 ms

jquery.cycle2.swipe.js

jquery.cycle2.swipe.js

36 ms

jquery.background.cycle_modified.js

jquery.background.cycle_modified.js

36 ms

jquery.quickpager.js

jquery.quickpager.js

40 ms

browser.js

browser.js

40 ms

sitesub.js

sitesub.js

38 ms

jquery-geomod.custom.js

jquery-geomod.custom.js

40 ms

js

js

78 ms

HOME-final_06.jpg

HOME-final_06.jpg

134 ms

royallepagesignature_logo.jpg

royallepagesignature_logo.jpg

45 ms

SplashTorontoNight.jpg

SplashTorontoNight.jpg

127 ms

arrow_icon.png

arrow_icon.png

41 ms

search_icon.png

search_icon.png

42 ms

red_arrow.jpg

red_arrow.jpg

41 ms

red_arrow_back.jpg

red_arrow_back.jpg

42 ms

previewdbblob.aspx

previewdbblob.aspx

131 ms

previewdbblob.aspx

previewdbblob.aspx

106 ms

previewdbblob.aspx

previewdbblob.aspx

93 ms

previewdbblob.aspx

previewdbblob.aspx

115 ms

previewdbblob.aspx

previewdbblob.aspx

135 ms

previewdbblob.aspx

previewdbblob.aspx

158 ms

previewdbblob.aspx

previewdbblob.aspx

175 ms

previewdbblob.aspx

previewdbblob.aspx

152 ms

previewdbblob.aspx

previewdbblob.aspx

191 ms

previewdbblob.aspx

previewdbblob.aspx

174 ms

previewdbblob.aspx

previewdbblob.aspx

192 ms

previewdbblob.aspx

previewdbblob.aspx

193 ms

previewdbblob.aspx

previewdbblob.aspx

200 ms

previewdbblob.aspx

previewdbblob.aspx

211 ms

previewdbblob.aspx

previewdbblob.aspx

204 ms

previewdbblob.aspx

previewdbblob.aspx

230 ms

previewdbblob.aspx

previewdbblob.aspx

223 ms

previewdbblob.aspx

previewdbblob.aspx

222 ms

previewdbblob.aspx

previewdbblob.aspx

240 ms

previewdbblob.aspx

previewdbblob.aspx

239 ms

neighbourhood_circle.jpg

neighbourhood_circle.jpg

228 ms

luxury_circle.jpg

luxury_circle.jpg

229 ms

condos_circle.jpg

condos_circle.jpg

231 ms

new_construction_circle.jpg

new_construction_circle.jpg

234 ms

facebook.png

facebook.png

236 ms

twitter.png

twitter.png

233 ms

linkedin.png

linkedin.png

234 ms

instagram.png

instagram.png

235 ms

jointeam.jpg

jointeam.jpg

236 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqh8ndeY9Z4.ttf

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqh8ndeY9Z4.ttf

65 ms

0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqh8ndeY9Z4.ttf

0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqh8ndeY9Z4.ttf

78 ms

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mfWc3ZyRTQ.ttf

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mfWc3ZyRTQ.ttf

103 ms

overlay.png

overlay.png

200 ms

Accessibility Review

mytorontohome.com accessibility score

41

Accessibility Issues

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

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

SEO Factors

mytorontohome.com SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    EN

  • Encoding

    UTF-8

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

mytorontohome.com

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