Tools & Wizards About Us
torontosuites.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

torontosuites.com

Furnished Apartments for Rent | Toronto Rentals - Toronto Suites

Page Load Speed

3.3 sec in total

First Response

722 ms

Resources Loaded

2.3 sec

Page Rendered

324 ms

torontosuites.com screenshot

About Website

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

Toronto Suites has the finest available Toronto Apartments for Rent. We make it easy to find executive suites, condos & Apartments to Rent in Toronto.

Visit torontosuites.com

Key Findings

We analyzed Torontosuites.com page load time and found that the first response time was 722 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster. This domain responded with an error, which can significantly jeopardize Torontosuites.com rating and web reputation

Performance Metrics

torontosuites.com performance score

0

Network Requests Diagram

torontosuites.com

722 ms

jquery-ui.css

168 ms

rokbox.css

90 ms

system.css

155 ms

bootstrap.css

224 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 47% of them (58 requests) were addressed to the original Torontosuites.com, 28% (34 requests) were made to Maps.googleapis.com and 10% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (876 ms) belongs to the original domain Torontosuites.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (39%)

Content Size

3.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Torontosuites.com main page is 3.2 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

-85%

Potential reduce by 58.7 kB

  • Original 69.1 kB
  • After minification 67.0 kB
  • After compression 10.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 58.7 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 64.1 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. Toronto Suites images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 812.4 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 355.6 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 812.4 kB or 70% of the original size.

CSS Optimization

-84%

Potential reduce by 315.9 kB

  • Original 375.3 kB
  • After minification 321.5 kB
  • After compression 59.4 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. Torontosuites.com needs all CSS files to be minified and compressed as it can save up to 315.9 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

107

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

torontosuites.com

torontosuites.com

722 ms

jquery-ui.css

jquery-ui.css

168 ms

rokbox.css

rokbox.css

90 ms

system.css

system.css

155 ms

bootstrap.css

bootstrap.css

224 ms

template.css

template.css

241 ms

megamenu.css

megamenu.css

161 ms

font-awesome.min.css

font-awesome.min.css

155 ms

css

css

62 ms

css

css

74 ms

docs.css

docs.css

156 ms

template.css

template.css

248 ms

animate.css

animate.css

248 ms

mod_jaslideshowlite.css

mod_jaslideshowlite.css

245 ms

mod_jaslideshowlite-fade.css

mod_jaslideshowlite-fade.css

246 ms

jquery.min.js

jquery.min.js

53 ms

jquerynoconflict.js

jquerynoconflict.js

295 ms

jquery-ui.min.js

jquery-ui.min.js

101 ms

caption.js

caption.js

308 ms

mootools-core.js

mootools-core.js

372 ms

core.js

core.js

309 ms

mootools-more.js

mootools-more.js

518 ms

rokbox.js

rokbox.js

388 ms

bootstrap.js

bootstrap.js

364 ms

jquery.tap.min.js

jquery.tap.min.js

372 ms

script.js

script.js

373 ms

menu.js

menu.js

435 ms

jquery.cookie.js

jquery.cookie.js

433 ms

jquery.isotope.min.js

jquery.isotope.min.js

435 ms

jquery.infinitescroll.min.js

jquery.infinitescroll.min.js

440 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

450 ms

script.js

script.js

499 ms

nav-collapse.js

nav-collapse.js

506 ms

script.js

script.js

523 ms

css

css

66 ms

css

css

71 ms

style.css

style.css

503 ms

script.js

script.js

512 ms

js

js

67 ms

system.css

system.css

449 ms

bg.gif

bg.gif

140 ms

toronto-suites.png

toronto-suites.png

111 ms

tslogo-mobile.png

tslogo-mobile.png

142 ms

slide10.jpg

slide10.jpg

449 ms

slide6.jpg

slide6.jpg

350 ms

slide8.jpg

slide8.jpg

573 ms

slide9.jpg

slide9.jpg

593 ms

furnished-4.jpg

furnished-4.jpg

284 ms

furnished-5.jpg

furnished-5.jpg

283 ms

en.gif

en.gif

429 ms

zh.gif

zh.gif

371 ms

fr.gif

fr.gif

447 ms

de.gif

de.gif

447 ms

ar.gif

ar.gif

494 ms

es.gif

es.gif

525 ms

it.gif

it.gif

529 ms

googleplus.png

googleplus.png

526 ms

facebook.png

facebook.png

563 ms

twitter.png

twitter.png

593 ms

img-mask-down.png

img-mask-down.png

580 ms

img-mask-up.png

img-mask-up.png

583 ms

subbody-bg.png

subbody-bg.png

625 ms

mainbody-bg-3.png

mainbody-bg-3.png

865 ms

map-bg.jpg

map-bg.jpg

876 ms

UAnF6lSK1JNc1tqTiG8pNALUuEpTyoUstqEm5AMlJo4.ttf

UAnF6lSK1JNc1tqTiG8pNALUuEpTyoUstqEm5AMlJo4.ttf

25 ms

CcKI4k9un7TZVWzRVT-T88DdSZkkecOE1hvV7ZHvhyU.ttf

CcKI4k9un7TZVWzRVT-T88DdSZkkecOE1hvV7ZHvhyU.ttf

26 ms

-_Ctzj9b56b8RgXW8FAricDdSZkkecOE1hvV7ZHvhyU.ttf

-_Ctzj9b56b8RgXW8FAricDdSZkkecOE1hvV7ZHvhyU.ttf

25 ms

xkvoNo9fC8O2RDydKj12b8DdSZkkecOE1hvV7ZHvhyU.ttf

xkvoNo9fC8O2RDydKj12b8DdSZkkecOE1hvV7ZHvhyU.ttf

25 ms

JbtMzqLaYbbbCL9X6EvaI8DdSZkkecOE1hvV7ZHvhyU.ttf

JbtMzqLaYbbbCL9X6EvaI8DdSZkkecOE1hvV7ZHvhyU.ttf

26 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

643 ms

common.js

common.js

51 ms

map.js

map.js

67 ms

util.js

util.js

98 ms

geocoder.js

geocoder.js

97 ms

geometry.js

geometry.js

96 ms

directions.js

directions.js

98 ms

y7lebkjgREBJK96VQi37ZiwlidHJgAgmTjOEEzwu1L8.ttf

y7lebkjgREBJK96VQi37ZiwlidHJgAgmTjOEEzwu1L8.ttf

86 ms

dazS1PrQQuCxC3iOAJFEJd6Naowg1QhaIq8kLGtQSos.ttf

dazS1PrQQuCxC3iOAJFEJd6Naowg1QhaIq8kLGtQSos.ttf

86 ms

dazS1PrQQuCxC3iOAJFEJTdGNerWpg2Hn6A-BxWgZ_I.ttf

dazS1PrQQuCxC3iOAJFEJTdGNerWpg2Hn6A-BxWgZ_I.ttf

86 ms

analytics.js

analytics.js

75 ms

slideloading.gif

slideloading.gif

586 ms

onion.js

onion.js

18 ms

openhand_8_8.cur

openhand_8_8.cur

83 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

66 ms

GeocodeService.Search

GeocodeService.Search

87 ms

collect

collect

21 ms

collect

collect

108 ms

infowindow.js

infowindow.js

17 ms

css

css

70 ms

marker.js

marker.js

14 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

82 ms

stats.js

stats.js

15 ms

controls.js

controls.js

11 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

60 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

60 ms

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

80 ms

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

138 ms

transparent.png

transparent.png

41 ms

google4.png

google4.png

82 ms

mapcnt6.png

mapcnt6.png

100 ms

sv5.png

sv5.png

104 ms

spotlight-poi.png

spotlight-poi.png

103 ms

cb_scout5.png

cb_scout5.png

90 ms

tmapctrl4.png

tmapctrl4.png

91 ms

vt

vt

119 ms

vt

vt

145 ms

vt

vt

81 ms

vt

vt

86 ms

vt

vt

82 ms

vt

vt

83 ms

vt

vt

137 ms

vt

vt

134 ms

vt

vt

138 ms

vt

vt

142 ms

vt

vt

142 ms

vt

vt

181 ms

vt

vt

186 ms

vt

vt

190 ms

vt

vt

192 ms

vt

vt

205 ms

vt

vt

198 ms

vt

vt

230 ms

vt

vt

237 ms

SEO Factors

torontosuites.com SEO score

0

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

torontosuites.com

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