Analyze

Page load speed analysis

  • 64/100

    Normal result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    82 ms

  • Resources loaded

    1.2 sec

  • Page rendered

    283 ms

  • Total page load time

    1.6 sec

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

We 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 25% of websites can load faster.

Page optimization

  • HTML 253.5 kB
    Images 845.8 kB
    Javascripts 688.3 kB
    CSS 124.3 kB

    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. 65% of websites need less resources to load. Images take 845.8 kB which makes up the majority of the site volume.

    • Original 253.5 kB
    • After minification 164.9 kB
    • After compression 30.8 kB

    HTML optimization

    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.

    • Original 845.8 kB
    • After optimization 835.4 kB

    Image optimization

    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.

    • Original 688.3 kB
    • After minification 631.4 kB
    • After compression 213.4 kB

    JavaScript optimization

    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 474.9 kB or 69% of the original size.

    • Original 124.3 kB
    • After minification 113.7 kB
    • After compression 18.8 kB

    CSS optimization

    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.

Network requests diagram

  • waterfrontoronto.ca
  • www.waterfrontoronto.ca
  • chnuk_all_jun28.js
  • scripts.js
  • bridge
  • facebox.css
  • zoommap.css
  • addthis_widget.js
  • WFT_bluewave_background.gif
  • top_logo.jpg
  • mail_icon.jpg
  • rss_icon.jpg
  • nav.gif
  • second_nav_bg.gif
  • 2983_5__southside_simcoe_1_225_150_both_.jpg
  • 2709_east_bayfront_aerial_cropped_1_225_150_both_.jpg
  • 641_west_don_lands_west_don_lands_aerial_view_225_150_both_.jpg
  • 573_lower_don_lands_cherry_st_225_150_both_.jpg
  • 1712_9_21_2005_2_58_09_pm_1_225_150_both_.jpg
  • 1669_4aaa98166958d_1_225_150_both_.jpg
  • view_map.gif
  • btn_go_search.gif
  • ajax-loader.gif
  • video_waterfront_is_changing_banner03_1.jpg
  • 6684_wintertime_at_project_under_gardiner_near_fort_york_visitor_centre_1_100_67_both_.jpg
  • bullet.gif
  • btn_see_more_newsletters.gif
  • btn_submit.gif
  • two_bar_blue.gif
  • share_buttons_join.gif
  • 2053_report_to_the_community_2010_1_75_100_both_.jpg
  • 3249_sherbourne_common_north_at_night_2_1_200_200_both_.jpg
  • 6728_csrsr_1_200_200_both_.png
  • 5351_icy_temporary_1_200_200_both_.png
  • widgets.js
  • btn_view_more_on_twitter.gif
  • doc_lib_toggle.gif
  • view_more.gif
  • btn_view_calendar.gif
  • footer_share.gif
  • btn_contact_us.gif
  • logo_toronto.jpg
  • logo_ontario.jpg
  • logo_canada.jpg
  • clarendonltstdbold.woff
  • ga.js
  • timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
  • 300lo.json
  • __utm.gif
  • sh.8e5f85691f9aaa082472a194.html
  • syndication
  • 408344333834678274
  • proxy.jpg
  • proxy.jpg
  • timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
  • timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
  • e5276bf4518be671fd5c0b9fe94c56c1_normal.png
  • pnvZHXuS_normal.jpg
  • zo49-Hc2_normal.jpg
  • w6nayMKH_normal.jpeg
  • LC8NMNfu_normal.jpeg
  • At9xp-PG_normal.jpeg
  • AekuutN5_normal.jpg
  • CUoxkIpz_normal.jpg
  • CdwvjUvXEAEYmUt.jpg
  • Cdn9q0qUUAA-RFb.jpg
  • CdmCDTOWIAAbRx4.jpg:large
  • CdcwQdIUsAATRWL.jpg
  • Cdc4qDRW4AEdyT7.jpg:small
  • Cdc4qD6XEAAkAUB.jpg:small
  • syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
  • syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
  • proxy.jpg
  • print
  • proxy.jpg

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.

Additional info on waterfrontoronto.ca

Requests

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.

8

Javascripts

55

Images

8

CSS

2

AJAX

73

All

Possible request optimization

1

Javascripts

42

Images

1

CSS

2

AJAX

27

Optimized

46

All

Normal result

Redirects

As for redirects, our browser was forwarded to http://www.waterfrontoronto.ca/ before it reached this domain.

IP address

Waterfrontoronto.ca uses IP address which is currently shared with 1 other domain. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

waterfrontoronto.ca

blog.waterfrontoronto.ca

158.85.97.53

DNS records

Type Host Target/ip TTL Other
A

waterfrontoronto.ca

158.85.97.53 3595
NS

waterfrontoronto.ca

dns2.internic.ca 3599
NS

waterfrontoronto.ca

dns.internic.ca 3599
SOA

waterfrontoronto.ca

21599 Mname: dns.internic.ca
Rname: noc.internic.ca
Serial: 3
Refresh: 10800
Retry: 3600
Expire: 604800
Minimum-ttl: 3600
MX

waterfrontoronto.ca

waterfrontoronto-ca.mail.protection.outlook.com 3599 Pri: 25

Language and encoding

Good result

Language

EN en language flag

Detected

EN en language flag

Claimed

Encoding

UTF-8

Claimed

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.

HTTPS certificate

SSL Certificate

Waterfrontoronto.ca has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

Country of origin for 52.6% of all visits is Canada. It’s good for Waterfrontoronto.ca that their server is also located in Canada, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Poor result

Social Sharing Optimization

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:

waterfrontoronto.ca

Share this report in social media

Analyze another website

Analyze