1.6 sec in total
82 ms
1.2 sec
283 ms
Visit waterfrontoronto.ca now to see the best up-to-date Waterfront Oronto content for Canada and also check out these interesting facts you probably never knew about waterfrontoronto.ca
Visit waterfrontoronto.caWe analyzed Waterfrontoronto.ca page load time and found that the first response time was 82 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
waterfrontoronto.ca performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value10.9 s
0/100
25%
Value4.6 s
71/100
10%
Value470 ms
61/100
30%
Value0.366
29/100
15%
Value9.8 s
28/100
10%
82 ms
209 ms
227 ms
158 ms
145 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 59% of them (44 requests) were addressed to the original Waterfrontoronto.ca, 19% (14 requests) were made to Pbs.twimg.com and 5% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (529 ms) belongs to the original domain Waterfrontoronto.ca.
Page size can be reduced by 786.5 kB (42%)
1.9 MB
1.1 MB
In fact, the total size of Waterfrontoronto.ca main page is 1.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. 60% of websites need less resources to load. Images take 845.8 kB which makes up the majority of the site volume.
Potential reduce by 222.7 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 88.6 kB, which is 35% 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 222.7 kB or 88% of the original size.
Potential reduce by 10.5 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. Waterfront Oronto images are well optimized though.
Potential reduce by 447.8 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 447.8 kB or 68% of the original size.
Potential reduce by 105.5 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. Waterfrontoronto.ca needs all CSS files to be minified and compressed as it can save up to 105.5 kB or 85% of the original size.
Number of requests can be reduced by 27 (37%)
73
46
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waterfront Oronto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
waterfrontoronto.ca
82 ms
www.waterfrontoronto.ca
209 ms
chnuk_all_jun28.js
227 ms
scripts.js
158 ms
bridge
145 ms
facebox.css
75 ms
zoommap.css
112 ms
addthis_widget.js
10 ms
WFT_bluewave_background.gif
195 ms
top_logo.jpg
195 ms
mail_icon.jpg
191 ms
rss_icon.jpg
191 ms
nav.gif
194 ms
second_nav_bg.gif
192 ms
2983_5__southside_simcoe_1_225_150_both_.jpg
195 ms
2709_east_bayfront_aerial_cropped_1_225_150_both_.jpg
197 ms
641_west_don_lands_west_don_lands_aerial_view_225_150_both_.jpg
191 ms
573_lower_don_lands_cherry_st_225_150_both_.jpg
229 ms
1712_9_21_2005_2_58_09_pm_1_225_150_both_.jpg
196 ms
1669_4aaa98166958d_1_225_150_both_.jpg
194 ms
view_map.gif
193 ms
btn_go_search.gif
251 ms
ajax-loader.gif
244 ms
video_waterfront_is_changing_banner03_1.jpg
343 ms
6684_wintertime_at_project_under_gardiner_near_fort_york_visitor_centre_1_100_67_both_.jpg
290 ms
bullet.gif
274 ms
btn_see_more_newsletters.gif
274 ms
btn_submit.gif
311 ms
two_bar_blue.gif
311 ms
share_buttons_join.gif
341 ms
2053_report_to_the_community_2010_1_75_100_both_.jpg
338 ms
3249_sherbourne_common_north_at_night_2_1_200_200_both_.jpg
378 ms
6728_csrsr_1_200_200_both_.png
470 ms
5351_icy_temporary_1_200_200_both_.png
428 ms
widgets.js
10 ms
btn_view_more_on_twitter.gif
392 ms
doc_lib_toggle.gif
394 ms
view_more.gif
395 ms
btn_view_calendar.gif
418 ms
footer_share.gif
394 ms
btn_contact_us.gif
455 ms
logo_toronto.jpg
455 ms
logo_ontario.jpg
458 ms
logo_canada.jpg
464 ms
clarendonltstdbold.woff
529 ms
ga.js
21 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
65 ms
300lo.json
49 ms
__utm.gif
43 ms
sh.8e5f85691f9aaa082472a194.html
39 ms
syndication
81 ms
408344333834678274
162 ms
proxy.jpg
42 ms
proxy.jpg
22 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
9 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
11 ms
e5276bf4518be671fd5c0b9fe94c56c1_normal.png
52 ms
pnvZHXuS_normal.jpg
61 ms
zo49-Hc2_normal.jpg
85 ms
w6nayMKH_normal.jpeg
85 ms
LC8NMNfu_normal.jpeg
84 ms
At9xp-PG_normal.jpeg
60 ms
AekuutN5_normal.jpg
84 ms
CUoxkIpz_normal.jpg
85 ms
CdwvjUvXEAEYmUt.jpg
89 ms
Cdn9q0qUUAA-RFb.jpg
93 ms
CdmCDTOWIAAbRx4.jpg:large
94 ms
CdcwQdIUsAATRWL.jpg
92 ms
Cdc4qDRW4AEdyT7.jpg:small
88 ms
Cdc4qD6XEAAkAUB.jpg:small
92 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
38 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
67 ms
proxy.jpg
14 ms
70 ms
proxy.jpg
4 ms
waterfrontoronto.ca accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
waterfrontoronto.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
waterfrontoronto.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waterfrontoronto.ca 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 Waterfrontoronto.ca 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.
waterfrontoronto.ca
Open Graph description is not detected on the main page of Waterfront Oronto. 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: