Tools & Wizards About Us
westinprincetoronto.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

westinprincetoronto.com

Hotel Directory

Page Load Speed

5.8 sec in total

First Response

375 ms

Resources Loaded

4.5 sec

Page Rendered

937 ms

westinprincetoronto.com screenshot

About Website

Click here to check amazing Westinprincetoronto content for Canada. Otherwise, check out these important facts you probably never knew about westinprincetoronto.com

Browse Marriott's hotel directory to search for hotels that are designed to satisfy your every need. See our complete list of hotels at Marriott.com.

Visit westinprincetoronto.com

Key Findings

We analyzed Westinprincetoronto.com page load time and found that the first response time was 375 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

westinprincetoronto.com performance score

0

Network Requests Diagram

westinprincetoronto.com

375 ms

www.westinprincetoronto.com

178 ms

normalize.css

56 ms

lps.css

15 ms

westin.css

57 ms

Our browser made a total of 170 requests to load all elements on the main page. We found that 18% of them (30 requests) were addressed to the original Westinprincetoronto.com, 23% (39 requests) were made to Maps.googleapis.com and 14% (23 requests) were made to Assets.westinprincetoronto.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Assets.westinprincetoronto.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (13%)

Content Size

11.7 MB

After Optimization

10.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Westinprincetoronto.com main page is 11.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 9.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 317.9 kB

  • Original 368.8 kB
  • After minification 321.6 kB
  • After compression 50.9 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 47.2 kB, which is 13% 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 317.9 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 17.5 kB

  • Original 9.5 MB
  • After minification 9.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. Westinprincetoronto images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 1.0 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 541.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 1.0 MB or 66% of the original size.

CSS Optimization

-86%

Potential reduce by 180.0 kB

  • Original 210.1 kB
  • After minification 195.4 kB
  • After compression 30.2 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. Westinprincetoronto.com needs all CSS files to be minified and compressed as it can save up to 180.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 80 (52%)

Requests Now

154

After Optimization

74

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

westinprincetoronto.com

westinprincetoronto.com

375 ms

www.westinprincetoronto.com

www.westinprincetoronto.com

178 ms

normalize.css

normalize.css

56 ms

lps.css

lps.css

15 ms

westin.css

westin.css

57 ms

modernizr-2.6.2-respond-1.1.0.min.js

modernizr-2.6.2-respond-1.1.0.min.js

46 ms

picturefill.js

picturefill.js

49 ms

BrightcoveExperiences.js

BrightcoveExperiences.js

11 ms

home.min.js

home.min.js

48 ms

js

js

388 ms

addthis_widget.js

addthis_widget.js

40 ms

infobubble.js

infobubble.js

52 ms

s_code.js

s_code.js

410 ms

s_code_library.js

s_code_library.js

38 ms

s_code_webcanada.js

s_code_webcanada.js

45 ms

normalize.css

normalize.css

50 ms

tag.js

tag.js

319 ms

wes1085ex.138854_tb-1.4.jpg

wes1085ex.138854_tb-1.4.jpg

1835 ms

tag.js

tag.js

235 ms

logo-westin-header.png

logo-westin-header.png

121 ms

trust_mark.png

trust_mark.png

121 ms

sf-icon-divider.png

sf-icon-divider.png

122 ms

wes1085de-78809-Front-Desk-Detail.jpg

wes1085de-78809-Front-Desk-Detail.jpg

832 ms

wes1085wn-138862-View-from-Property.jpg

wes1085wn-138862-View-from-Property.jpg

1055 ms

1085_Lobby22.jpg

1085_Lobby22.jpg

1249 ms

1085_Lobby.jpg

1085_Lobby.jpg

1246 ms

wes1085de-82592-Restaurant-Detail.jpg

wes1085de-82592-Restaurant-Detail.jpg

1054 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

740 ms

wes1085cl.138852_tb-1.jpg

wes1085cl.138852_tb-1.jpg

1231 ms

wes1085de.82592_tb-1.jpg

wes1085de.82592_tb-1.jpg

1280 ms

wes1085br.139780_tb-1.jpg

wes1085br.139780_tb-1.jpg

1326 ms

GalaxieCopernicus-Medium.woff

GalaxieCopernicus-Medium.woff

934 ms

GalaxieCopernicus-Book.woff

GalaxieCopernicus-Book.woff

935 ms

lps.ttf

lps.ttf

934 ms

social.ttf

social.ttf

932 ms

Starwood.woff

Starwood.woff

935 ms

sdk.js

sdk.js

1126 ms

analytics.js

analytics.js

907 ms

localtime

localtime

1296 ms

weather

weather

1297 ms

Westin-Hotels-AAA.jpg

Westin-Hotels-AAA.jpg

1634 ms

common.js

common.js

817 ms

map.js

map.js

839 ms

util.js

util.js

906 ms

marker.js

marker.js

842 ms

overlay.js

overlay.js

817 ms

geometry.js

geometry.js

793 ms

directions.js

directions.js

796 ms

infowindow-close.png

infowindow-close.png

231 ms

TraditionalGuestRoom.jpg

TraditionalGuestRoom.jpg

791 ms

1085_Guestroom.jpg

1085_Guestroom.jpg

790 ms

Photo-Gallery_Workout_Yoga.jpg

Photo-Gallery_Workout_Yoga.jpg

1614 ms

Photo-Gallery_Heavenly-Bed.jpg

Photo-Gallery_Heavenly-Bed.jpg

788 ms

1085_Guestroom22.jpg

1085_Guestroom22.jpg

887 ms

wes1085de-82592-Restaurant-Detail.jpg

wes1085de-82592-Restaurant-Detail.jpg

1053 ms

Westin-Birthday.jpg

Westin-Birthday.jpg

1209 ms

Westin-Hotels-AAA.jpg

Westin-Hotels-AAA.jpg

1239 ms

Westin-Birthday.jpg

Westin-Birthday.jpg

1208 ms

tag

tag

181 ms

TraditionalGuestRoom.jpg

TraditionalGuestRoom.jpg

687 ms

1085_Guestroom.jpg

1085_Guestroom.jpg

687 ms

Photo-Gallery_Workout_Yoga.jpg

Photo-Gallery_Workout_Yoga.jpg

774 ms

Photo-Gallery_Heavenly-Bed.jpg

Photo-Gallery_Heavenly-Bed.jpg

758 ms

1085_Guestroom22.jpg

1085_Guestroom22.jpg

759 ms

wes1085de-82592-Restaurant-Detail.jpg

wes1085de-82592-Restaurant-Detail.jpg

835 ms

Westin-Hotels-AAA.jpg

Westin-Hotels-AAA.jpg

1069 ms

Westin-Birthday.jpg

Westin-Birthday.jpg

1053 ms

collect

collect

39 ms

s04184922501444

s04184922501444

68 ms

9df31eb8428f2f2e8d242309efbd49e0cdb3c6d5.js

9df31eb8428f2f2e8d242309efbd49e0cdb3c6d5.js

62 ms

onion.js

onion.js

39 ms

openhand_8_8.cur

openhand_8_8.cur

166 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

186 ms

stats.js

stats.js

136 ms

controls.js

controls.js

130 ms

infowindow.js

infowindow.js

101 ms

css

css

187 ms

abb5af81099611c078c8d31d574d570cf624f04a.js

abb5af81099611c078c8d31d574d570cf624f04a.js

69 ms

143 ms

xd_arbiter.php

xd_arbiter.php

259 ms

xd_arbiter.php

xd_arbiter.php

419 ms

map-marker.png

map-marker.png

89 ms

marker-1.png

marker-1.png

88 ms

marker-2.png

marker-2.png

84 ms

marker-3.png

marker-3.png

88 ms

marker-4.png

marker-4.png

114 ms

marker-5.png

marker-5.png

178 ms

marker-6.png

marker-6.png

223 ms

marker-7.png

marker-7.png

168 ms

transparent.png

transparent.png

62 ms

bat.js

bat.js

176 ms

google4.png

google4.png

142 ms

mapcnt6.png

mapcnt6.png

143 ms

sv5.png

sv5.png

143 ms

vt

vt

97 ms

vt

vt

83 ms

vt

vt

82 ms

vt

vt

89 ms

vt

vt

82 ms

vt

vt

82 ms

vt

vt

152 ms

vt

vt

151 ms

vt

vt

150 ms

vt

vt

151 ms

vt

vt

151 ms

vt

vt

150 ms

vt

vt

154 ms

vt

vt

158 ms

vt

vt

155 ms

vt

vt

153 ms

vt

vt

156 ms

vt

vt

153 ms

vt

vt

204 ms

vt

vt

213 ms

vt

vt

204 ms

vt

vt

205 ms

vt

vt

211 ms

vt

vt

209 ms

tmapctrl.png

tmapctrl.png

69 ms

vt

vt

205 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

80 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

103 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

140 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

141 ms

cb_scout5.png

cb_scout5.png

41 ms

tmapctrl4.png

tmapctrl4.png

28 ms

tag

tag

80 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

126 ms

nr-885.min.js

nr-885.min.js

125 ms

300lo.json

300lo.json

86 ms

FM_Pages_Westin

FM_Pages_Westin

76 ms

conversion_async.js

conversion_async.js

145 ms

wes1085wn.138862_tb-1.jpg

wes1085wn.138862_tb-1.jpg

497 ms

wes1085lo.139783_tb-1.2.jpg

wes1085lo.139783_tb-1.2.jpg

484 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

67 ms

tre

tre

73 ms

lb

lb

124 ms

448c072440

448c072440

95 ms

ps

ps

49 ms

like.php

like.php

93 ms

64 ms

Pug

Pug

86 ms

ta.bfp;dc_seg=19666690;ord=407535249833.0176

ta.bfp;dc_seg=19666690;ord=407535249833.0176

82 ms

tre

tre

84 ms

activity;src=4161152;type=invmedia;cat=wn2r01pn;ord=5293801422230.899;prd=

activity;src=4161152;type=invmedia;cat=wn2r01pn;ord=5293801422230.899;prd=

158 ms

ytc.js

ytc.js

120 ms

uat_homepage_westin

uat_homepage_westin

97 ms

beacon

beacon

97 ms

75 ms

125 ms

116 ms

105 ms

104 ms

290 ms

Pix-1x1.gif

Pix-1x1.gif

99 ms

tap.php

tap.php

55 ms

demconf.jpg

demconf.jpg

55 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

323 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

356 ms

tre

tre

38 ms

tre

tre

68 ms

sd

sd

31 ms

sync

sync

79 ms

cmap

cmap

61 ms

lb

lb

30 ms

516 ms

651 ms

787 ms

885 ms

pixel

pixel

15 ms

SEO Factors

westinprincetoronto.com SEO score

0

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

westinprincetoronto.com

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