Torontohealthprofiles.Ca - Info torontohealthprofiles.ca

torontohealthprofiles.ca receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank torontohealthprofiles.ca is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in Vancouver, British Columbia, V6H, Canada and links to network IP address 209.15.37.36. This server doesn't support HTTPS and doesn't support HTTP/2.

About - torontohealthprofiles.ca


Technologies used on Website

JavaScript Libraries
Lightbox
Hosting Panels
Plesk

torontohealthprofiles.ca Profile

Title: Toronto Community Health Profiles Partnership-Home
Last update was 238 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with torontohealthprofiles.ca in any way. Only publicly available statistics data are displayed.

How popular is torontohealthprofiles.ca?

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Unique Visitors:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  torontohealthprofiles.ca
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is torontohealthprofiles.ca?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
torontohealthprofiles.ca
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
torontohealthprofiles.ca
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much torontohealthprofiles.ca can earn?

Daily Revenue:
n/a
Monthly Revenue:
n/a
Yearly Revenue:
n/a
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do torontohealthprofiles.ca lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is torontohealthprofiles.ca worth?

Website Value:
n/a

+ Where is torontohealthprofiles.ca hosted?

Server IP:
209.15.37.36
ASN:
AS13768 
ISP:
Cogeco Peer 1 
Server Location:
Vancouver
British Columbia, BC
V6H
Canada, CA
 

Other sites hosted on 209.15.37.36

+ How fast does torontohealthprofiles.ca load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
272 ms
7 ms
281 ms
6 ms
555 ms
18 ms
581 ms
27 ms
610 ms
43 ms
654 ms
5 ms
667 ms
28 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
148 ms3 ms1 ms
http://torontohealthprofiles.ca/js/jquery.js
57 ms22 ms2 ms
Remove unused CSS - Potential savings of 4 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL
SizePotential Savings
http://torontohealthprofiles.ca/a_stylesheet/tchpp.css
5 KB4 KB
Avoids enormous network payloads - Total size was 970 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://torontohealthprofiles.ca/a_images/logo_WellesleyInstitute.jpg
575 KB
http://torontohealthprofiles.ca/photos/thumb_image2.jpg
57 KB
http://torontohealthprofiles.ca/photos/thumb_image1.jpg
46 KB
http://torontohealthprofiles.ca/photos/thumb_image3.jpg
44 KB
http://torontohealthprofiles.ca/a_images/logo_AccessAlliance.jpg
36 KB
http://torontohealthprofiles.ca/a_images/logo_WellbeingToronto.jpg
36 KB
http://torontohealthprofiles.ca/js/jquery.js
32 KB
http://torontohealthprofiles.ca/a_images/logo_LHIN_8_Central.jpg
28 KB
http://torontohealthprofiles.ca/a_images/logo_ICES.jpg
24 KB
http://torontohealthprofiles.ca/a_stylesheet/banner2.gif
18 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
58 ms
Other
54 ms
Rendering
53 ms
Script Evaluation
26 ms
Parse HTML & CSS
12 ms
Script Parsing & Compilation
5 ms
Serve images in next-gen formats - Potential savings of 818 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://torontohealthprofiles.ca/a_images/logo_WellesleyInstitute.jpg
575 KB572 KB
http://torontohealthprofiles.ca/photos/thumb_image2.jpg
56 KB47 KB
http://torontohealthprofiles.ca/photos/thumb_image1.jpg
46 KB40 KB
http://torontohealthprofiles.ca/photos/thumb_image3.jpg
44 KB38 KB
http://torontohealthprofiles.ca/a_images/logo_AccessAlliance.jpg
36 KB34 KB
http://torontohealthprofiles.ca/a_images/logo_WellbeingToronto.jpg
35 KB32 KB
http://torontohealthprofiles.ca/a_images/logo_LHIN_8_Central.jpg
27 KB24 KB
http://torontohealthprofiles.ca/a_images/logo_ICES.jpg
23 KB22 KB
http://torontohealthprofiles.ca/a_images/logo_TorontoCentralLHIN.JPG
13 KB10 KB
Avoids an excessive DOM size - 248 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
248
Maximum DOM Depth
11
Maximum Child Elements
64
Minify JavaScript - Potential savings of 3 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://torontohealthprofiles.ca/js/jquery.lightbox-0.5.js
5 KB3 KB
Keep request counts low and transfer sizes small - 28 requests • 970 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
28970 KB
Image
20918 KB
Script
338 KB
Stylesheet
48 KB
Document
16 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 520 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://torontohealthprofiles.ca/js/jquery.js
32 KB190
http://torontohealthprofiles.ca/js/jquery.lightbox-0.5.js
5 KB110
http://torontohealthprofiles.ca/css/jquery.lightbox-0.5.css
1 KB110
http://torontohealthprofiles.ca/a_stylesheet/tchpp.css
5 KB110
http://torontohealthprofiles.ca/a_javascript/menu_dropdown.js
1 KB110
http://torontohealthprofiles.ca/a_menu_dropdown.css
2 KB110
http://torontohealthprofiles.ca/searchByTopic.css
1 KB70
Efficiently encode images - Potential savings of 794 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://torontohealthprofiles.ca/a_images/logo_WellesleyInstitute.jpg
575 KB570 KB
http://torontohealthprofiles.ca/photos/thumb_image2.jpg
56 KB38 KB
http://torontohealthprofiles.ca/photos/thumb_image1.jpg
46 KB36 KB
http://torontohealthprofiles.ca/photos/thumb_image3.jpg
44 KB35 KB
http://torontohealthprofiles.ca/a_images/logo_AccessAlliance.jpg
36 KB32 KB
http://torontohealthprofiles.ca/a_images/logo_WellbeingToronto.jpg
35 KB30 KB
http://torontohealthprofiles.ca/a_images/logo_LHIN_8_Central.jpg
27 KB22 KB
http://torontohealthprofiles.ca/a_images/logo_ICES.jpg
23 KB21 KB
http://torontohealthprofiles.ca/a_images/logo_TorontoCentralLHIN.JPG
13 KB8 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://torontohealthprofiles.ca/
0 ms250 ms6 KB22 KB200text/htmlDocument
http://torontohealthprofiles.ca/js/jquery.js
262 ms528 ms32 KB92 KB200application/javascriptScript
http://torontohealthprofiles.ca/js/jquery.lightbox-0.5.js
263 ms452 ms5 KB19 KB200application/javascriptScript
http://torontohealthprofiles.ca/css/jquery.lightbox-0.5.css
263 ms452 ms1 KB2 KB200text/cssStylesheet
http://torontohealthprofiles.ca/a_stylesheet/tchpp.css
264 ms453 ms5 KB25 KB200text/cssStylesheet
http://torontohealthprofiles.ca/a_javascript/menu_dropdown.js
264 ms451 ms1 KB1 KB200application/javascriptScript
http://torontohealthprofiles.ca/a_menu_dropdown.css
264 ms445 ms2 KB6 KB200text/cssStylesheet
http://torontohealthprofiles.ca/searchByTopic.css
264 ms536 ms1 KB1 KB200text/cssStylesheet
http://torontohealthprofiles.ca/a_stylesheet/banner.gif
265 ms546 ms10 KB10 KB200image/gifImage
http://torontohealthprofiles.ca/a_stylesheet/banner2.gif
265 ms638 ms18 KB17 KB200image/gifImage
http://torontohealthprofiles.ca/photos/thumb_image1.jpg
555 ms819 ms46 KB46 KB200image/jpegImage
http://torontohealthprofiles.ca/photos/thumb_image2.jpg
559 ms749 ms57 KB56 KB200image/jpegImage
http://torontohealthprofiles.ca/photos/thumb_image3.jpg
560 ms842 ms44 KB44 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/ONMarg_small_98-54.gif
560 ms750 ms4 KB4 KB200image/gifImage
http://torontohealthprofiles.ca/urbanheartattoronto/UrbanHeart_atToronto_Logo_sm.jpg
560 ms659 ms6 KB5 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_SMH_CentreForUrbanHealthSolutions.jpg
560 ms727 ms7 KB7 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_TorontoPublicHealth.jpg
560 ms835 ms4 KB3 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_AccessAlliance.jpg
561 ms817 ms36 KB36 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_SETo.jpg
561 ms934 ms7 KB7 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_WellesleyInstitute.jpg
561 ms1311 ms575 KB575 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_TorontoCentralLHIN.JPG
561 ms908 ms14 KB13 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_ICES.jpg
562 ms1056 ms24 KB23 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_WellbeingToronto.jpg
562 ms926 ms36 KB35 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_LHIN_8_Central.jpg
562 ms948 ms28 KB27 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/tw_logo.gif
562 ms1007 ms1 KB1 KB200image/gifImage
http://torontohealthprofiles.ca/a_images/btn_111_25off.gif
564 ms1103 ms1 KB0 KB200image/gifImage
http://torontohealthprofiles.ca/a_images/btn_111_25on.gif
564 ms1024 ms1 KB0 KB200image/gifImage
http://torontohealthprofiles.ca/a_images/btn_190_25on.gif
564 ms1134 ms1 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 27 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://torontohealthprofiles.ca/a_images/logo_WellesleyInstitute.jpg
604800000 ms575 KB
http://torontohealthprofiles.ca/photos/thumb_image2.jpg
604800000 ms57 KB
http://torontohealthprofiles.ca/photos/thumb_image1.jpg
604800000 ms46 KB
http://torontohealthprofiles.ca/photos/thumb_image3.jpg
604800000 ms44 KB
http://torontohealthprofiles.ca/a_images/logo_AccessAlliance.jpg
604800000 ms36 KB
http://torontohealthprofiles.ca/a_images/logo_WellbeingToronto.jpg
604800000 ms36 KB
http://torontohealthprofiles.ca/js/jquery.js
604800000 ms32 KB
http://torontohealthprofiles.ca/a_images/logo_LHIN_8_Central.jpg
604800000 ms28 KB
http://torontohealthprofiles.ca/a_images/logo_ICES.jpg
604800000 ms24 KB
http://torontohealthprofiles.ca/a_stylesheet/banner2.gif
604800000 ms18 KB
http://torontohealthprofiles.ca/a_images/logo_TorontoCentralLHIN.JPG
604800000 ms14 KB
http://torontohealthprofiles.ca/a_stylesheet/banner.gif
604800000 ms10 KB
http://torontohealthprofiles.ca/a_images/logo_SMH_CentreForUrbanHealthSolutions.jpg
604800000 ms7 KB
http://torontohealthprofiles.ca/a_images/logo_SETo.jpg
604800000 ms7 KB
http://torontohealthprofiles.ca/urbanheartattoronto/UrbanHeart_atToronto_Logo_sm.jpg
604800000 ms6 KB
http://torontohealthprofiles.ca/js/jquery.lightbox-0.5.js
604800000 ms5 KB
http://torontohealthprofiles.ca/a_stylesheet/tchpp.css
604800000 ms5 KB
http://torontohealthprofiles.ca/a_images/ONMarg_small_98-54.gif
604800000 ms4 KB
http://torontohealthprofiles.ca/a_images/logo_TorontoPublicHealth.jpg
604800000 ms4 KB
http://torontohealthprofiles.ca/a_menu_dropdown.css
604800000 ms2 KB
http://torontohealthprofiles.ca/css/jquery.lightbox-0.5.css
604800000 ms1 KB
http://torontohealthprofiles.ca/a_javascript/menu_dropdown.js
604800000 ms1 KB
http://torontohealthprofiles.ca/a_images/tw_logo.gif
604800000 ms1 KB
http://torontohealthprofiles.ca/searchByTopic.css
604800000 ms1 KB
http://torontohealthprofiles.ca/a_images/btn_190_25on.gif
604800000 ms1 KB
http://torontohealthprofiles.ca/a_images/btn_111_25off.gif
604800000 ms1 KB
http://torontohealthprofiles.ca/a_images/btn_111_25on.gif
604800000 ms1 KB
Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Minimize Critical Requests Depth - 7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 250 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Contentful Paint (3G) 3497 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 70 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

JavaScript execution time - 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
620 ms17 ms5 ms
http://torontohealthprofiles.ca/js/jquery.js
306 ms109 ms13 ms
Remove unused CSS - Potential savings of 4 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL
SizePotential Savings
http://torontohealthprofiles.ca/a_stylesheet/tchpp.css
5 KB4 KB
Avoids enormous network payloads - Total size was 970 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://torontohealthprofiles.ca/a_images/logo_WellesleyInstitute.jpg
575 KB
http://torontohealthprofiles.ca/photos/thumb_image2.jpg
57 KB
http://torontohealthprofiles.ca/photos/thumb_image1.jpg
46 KB
http://torontohealthprofiles.ca/photos/thumb_image3.jpg
44 KB
http://torontohealthprofiles.ca/a_images/logo_AccessAlliance.jpg
36 KB
http://torontohealthprofiles.ca/a_images/logo_WellbeingToronto.jpg
36 KB
http://torontohealthprofiles.ca/js/jquery.js
32 KB
http://torontohealthprofiles.ca/a_images/logo_LHIN_8_Central.jpg
28 KB
http://torontohealthprofiles.ca/a_images/logo_ICES.jpg
24 KB
http://torontohealthprofiles.ca/a_stylesheet/banner2.gif
18 KB
Minimizes main-thread work - 0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
293 ms
Other
257 ms
Rendering
169 ms
Script Evaluation
130 ms
Parse HTML & CSS
62 ms
Script Parsing & Compilation
27 ms
Serve images in next-gen formats - Potential savings of 818 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://torontohealthprofiles.ca/a_images/logo_WellesleyInstitute.jpg
575 KB572 KB
http://torontohealthprofiles.ca/photos/thumb_image2.jpg
56 KB47 KB
http://torontohealthprofiles.ca/photos/thumb_image1.jpg
46 KB40 KB
http://torontohealthprofiles.ca/photos/thumb_image3.jpg
44 KB38 KB
http://torontohealthprofiles.ca/a_images/logo_AccessAlliance.jpg
36 KB34 KB
http://torontohealthprofiles.ca/a_images/logo_WellbeingToronto.jpg
35 KB32 KB
http://torontohealthprofiles.ca/a_images/logo_LHIN_8_Central.jpg
27 KB24 KB
http://torontohealthprofiles.ca/a_images/logo_ICES.jpg
23 KB22 KB
http://torontohealthprofiles.ca/a_images/logo_TorontoCentralLHIN.JPG
13 KB10 KB
Avoids an excessive DOM size - 248 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
248
Maximum DOM Depth
11
Maximum Child Elements
64
Minify JavaScript - Potential savings of 3 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://torontohealthprofiles.ca/js/jquery.lightbox-0.5.js
5 KB3 KB
Keep request counts low and transfer sizes small - 28 requests • 970 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
28970 KB
Image
20918 KB
Script
338 KB
Stylesheet
48 KB
Document
16 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 1,350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://torontohealthprofiles.ca/js/jquery.js
32 KB780
http://torontohealthprofiles.ca/js/jquery.lightbox-0.5.js
5 KB480
http://torontohealthprofiles.ca/css/jquery.lightbox-0.5.css
1 KB330
http://torontohealthprofiles.ca/a_stylesheet/tchpp.css
5 KB480
http://torontohealthprofiles.ca/a_javascript/menu_dropdown.js
1 KB330
http://torontohealthprofiles.ca/a_menu_dropdown.css
2 KB330
http://torontohealthprofiles.ca/searchByTopic.css
1 KB180
Efficiently encode images - Potential savings of 794 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://torontohealthprofiles.ca/a_images/logo_WellesleyInstitute.jpg
575 KB570 KB
http://torontohealthprofiles.ca/photos/thumb_image2.jpg
56 KB38 KB
http://torontohealthprofiles.ca/photos/thumb_image1.jpg
46 KB36 KB
http://torontohealthprofiles.ca/photos/thumb_image3.jpg
44 KB35 KB
http://torontohealthprofiles.ca/a_images/logo_AccessAlliance.jpg
36 KB32 KB
http://torontohealthprofiles.ca/a_images/logo_WellbeingToronto.jpg
35 KB30 KB
http://torontohealthprofiles.ca/a_images/logo_LHIN_8_Central.jpg
27 KB22 KB
http://torontohealthprofiles.ca/a_images/logo_ICES.jpg
23 KB21 KB
http://torontohealthprofiles.ca/a_images/logo_TorontoCentralLHIN.JPG
13 KB8 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://torontohealthprofiles.ca/
0 ms222 ms6 KB22 KB200text/htmlDocument
http://torontohealthprofiles.ca/js/jquery.js
238 ms471 ms32 KB92 KB200application/javascriptScript
http://torontohealthprofiles.ca/js/jquery.lightbox-0.5.js
238 ms423 ms5 KB19 KB200application/javascriptScript
http://torontohealthprofiles.ca/css/jquery.lightbox-0.5.css
239 ms345 ms1 KB2 KB200text/cssStylesheet
http://torontohealthprofiles.ca/a_stylesheet/tchpp.css
240 ms520 ms5 KB25 KB200text/cssStylesheet
http://torontohealthprofiles.ca/a_javascript/menu_dropdown.js
240 ms400 ms1 KB1 KB200application/javascriptScript
http://torontohealthprofiles.ca/a_menu_dropdown.css
240 ms332 ms2 KB6 KB200text/cssStylesheet
http://torontohealthprofiles.ca/searchByTopic.css
241 ms427 ms1 KB1 KB200text/cssStylesheet
http://torontohealthprofiles.ca/a_stylesheet/banner.gif
241 ms448 ms10 KB10 KB200image/gifImage
http://torontohealthprofiles.ca/a_stylesheet/banner2.gif
241 ms577 ms18 KB17 KB200image/gifImage
http://torontohealthprofiles.ca/photos/thumb_image1.jpg
449 ms718 ms46 KB46 KB200image/jpegImage
http://torontohealthprofiles.ca/photos/thumb_image2.jpg
524 ms705 ms57 KB56 KB200image/jpegImage
http://torontohealthprofiles.ca/photos/thumb_image3.jpg
524 ms795 ms44 KB44 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/ONMarg_small_98-54.gif
524 ms618 ms4 KB4 KB200image/gifImage
http://torontohealthprofiles.ca/urbanheartattoronto/UrbanHeart_atToronto_Logo_sm.jpg
525 ms624 ms6 KB5 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_SMH_CentreForUrbanHealthSolutions.jpg
525 ms678 ms7 KB7 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_TorontoPublicHealth.jpg
525 ms728 ms4 KB3 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_AccessAlliance.jpg
525 ms804 ms36 KB36 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_SETo.jpg
525 ms764 ms7 KB7 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_WellesleyInstitute.jpg
526 ms1267 ms575 KB575 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_TorontoCentralLHIN.JPG
526 ms819 ms14 KB13 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_ICES.jpg
526 ms814 ms24 KB23 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_WellbeingToronto.jpg
526 ms958 ms36 KB35 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/logo_LHIN_8_Central.jpg
526 ms978 ms28 KB27 KB200image/jpegImage
http://torontohealthprofiles.ca/a_images/tw_logo.gif
527 ms903 ms1 KB1 KB200image/gifImage
http://torontohealthprofiles.ca/a_images/btn_111_25off.gif
529 ms904 ms1 KB0 KB200image/gifImage
http://torontohealthprofiles.ca/a_images/btn_111_25on.gif
529 ms909 ms1 KB0 KB200image/gifImage
http://torontohealthprofiles.ca/a_images/btn_190_25on.gif
530 ms997 ms1 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 27 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://torontohealthprofiles.ca/a_images/logo_WellesleyInstitute.jpg
604800000 ms575 KB
http://torontohealthprofiles.ca/photos/thumb_image2.jpg
604800000 ms57 KB
http://torontohealthprofiles.ca/photos/thumb_image1.jpg
604800000 ms46 KB
http://torontohealthprofiles.ca/photos/thumb_image3.jpg
604800000 ms44 KB
http://torontohealthprofiles.ca/a_images/logo_AccessAlliance.jpg
604800000 ms36 KB
http://torontohealthprofiles.ca/a_images/logo_WellbeingToronto.jpg
604800000 ms36 KB
http://torontohealthprofiles.ca/js/jquery.js
604800000 ms32 KB
http://torontohealthprofiles.ca/a_images/logo_LHIN_8_Central.jpg
604800000 ms28 KB
http://torontohealthprofiles.ca/a_images/logo_ICES.jpg
604800000 ms24 KB
http://torontohealthprofiles.ca/a_stylesheet/banner2.gif
604800000 ms18 KB
http://torontohealthprofiles.ca/a_images/logo_TorontoCentralLHIN.JPG
604800000 ms14 KB
http://torontohealthprofiles.ca/a_stylesheet/banner.gif
604800000 ms10 KB
http://torontohealthprofiles.ca/a_images/logo_SMH_CentreForUrbanHealthSolutions.jpg
604800000 ms7 KB
http://torontohealthprofiles.ca/a_images/logo_SETo.jpg
604800000 ms7 KB
http://torontohealthprofiles.ca/urbanheartattoronto/UrbanHeart_atToronto_Logo_sm.jpg
604800000 ms6 KB
http://torontohealthprofiles.ca/js/jquery.lightbox-0.5.js
604800000 ms5 KB
http://torontohealthprofiles.ca/a_stylesheet/tchpp.css
604800000 ms5 KB
http://torontohealthprofiles.ca/a_images/ONMarg_small_98-54.gif
604800000 ms4 KB
http://torontohealthprofiles.ca/a_images/logo_TorontoPublicHealth.jpg
604800000 ms4 KB
http://torontohealthprofiles.ca/a_menu_dropdown.css
604800000 ms2 KB
http://torontohealthprofiles.ca/css/jquery.lightbox-0.5.css
604800000 ms1 KB
http://torontohealthprofiles.ca/a_javascript/menu_dropdown.js
604800000 ms1 KB
http://torontohealthprofiles.ca/a_images/tw_logo.gif
604800000 ms1 KB
http://torontohealthprofiles.ca/searchByTopic.css
604800000 ms1 KB
http://torontohealthprofiles.ca/a_images/btn_190_25on.gif
604800000 ms1 KB
http://torontohealthprofiles.ca/a_images/btn_111_25off.gif
604800000 ms1 KB
http://torontohealthprofiles.ca/a_images/btn_111_25on.gif
604800000 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
254 ms
10 ms
267 ms
7 ms
510 ms
24 ms
556 ms
32 ms
590 ms
58 ms
648 ms
7 ms
659 ms
19 ms
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Minimize Critical Requests Depth - 7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 220 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 831.9KiB (92% reduction).

Compressing http://torontohealthprofiles.ca/a_images/logo_WellesleyInstitute.jpg could save 570.9KiB (99% reduction).
Compressing http://torontohealthprofiles.ca/photos/thumb_image2.jpg could save 43.3KiB (76% reduction).
Compressing http://torontohealthprofiles.ca/photos/thumb_image1.jpg could save 38.5KiB (83% reduction).
Compressing http://torontohealthprofiles.ca/photos/thumb_image3.jpg could save 36.9KiB (84% reduction).
Compressing http://torontohealthprofiles.ca/a_images/logo_AccessAlliance.jpg could save 33KiB (91% reduction).
Compressing http://torontohealthprofiles.ca/a_images/logo_WellbeingToronto.jpg could save 31.4KiB (88% reduction).
Compressing http://torontohealthprofiles.ca/a_images/logo_LHIN_8_Central.jpg could save 23.2KiB (84% reduction).
Compressing http://torontohealthprofiles.ca/a_images/logo_ICES.jpg could save 21.4KiB (91% reduction).
Compressing http://torontohealthprofiles.ca/a_stylesheet/banner2.gif could save 12.7KiB (72% reduction).
Compressing http://torontohealthprofiles.ca/a_images/logo_TorontoCentralLHIN.JPG could save 9.4KiB (70% reduction).
Compressing http://torontohealthprofiles.ca/a_images/logo_SETo.jpg could save 4.2KiB (63% reduction).
Compressing http://torontohealthprofiles.ca/urbanheartattoronto/UrbanHeart_atToronto_Logo_sm.jpg could save 3.4KiB (63% reduction).
Compressing http://torontohealthprofiles.ca/a_images/logo_SMH_CentreForUrbanHealthSolutions.jpg could save 2.6KiB (38% reduction).
Compressing http://torontohealthprofiles.ca/a_images/logo_TorontoPublicHealth.jpg could save 904B (28% reduction).
Compressing http://torontohealthprofiles.ca/a_images/tw_logo.gif could save 187B (33% reduction).

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

goal of produc…inequalities. and 2 others render only 4 pixels tall (10 CSS pixels) .
Data, Maps and Charts and 6 others render only 4 pixels tall (11 CSS pixels) .
* Notes renders only 6 pixels tall (16 CSS pixels) .
This site is n…Partnership ( and 1 others render only 6 pixels tall (16 CSS pixels) .
www.OntarioHealthProfiles.ca renders only 6 pixels tall (16 CSS pixels) .
Data on This Site and 1 others render only 5 pixels tall (14 CSS pixels) .
Urban HEART @T…lation health. and 1 others render only 5 pixels tall (12 CSS pixels) .
Diabetes Atlas…of Peel, 2013 and 24 others render only 5 pixels tall (12 CSS pixels) .
•  Emergency D…13/14, Ontario and 29 others render only 5 pixels tall (12 CSS pixels) .
Please read th…refully before and 5 others render only 5 pixels tall (12 CSS pixels) .
Archived Data and 1 others render only 5 pixels tall (12 CSS pixels) .
What Informati…You Find Here? renders only 5 pixels tall (14 CSS pixels) .
Community-leve…table format. and 10 others render only 5 pixels tall (12 CSS pixels) .
Data, Maps and Charts and 1 others render only 5 pixels tall (12 CSS pixels) .
We provide hea…e basic forms: renders only 5 pixels tall (12 CSS pixels) .
[Click on an i…ow to enlarge] renders only 4 pixels tall (10 CSS pixels) .
Health Data Maps and 2 others render only 5 pixels tall (12 CSS pixels) .
Toronto Walkability Index: and 5 others render only 5 pixels tall (12 CSS pixels) .
Ontario Marginalization Index and 1 others render only 5 pixels tall (12 CSS pixels) .
| and 10 others render only 5 pixels tall (12 CSS pixels) .
Data, Maps and Charts and 9 others render only 5 pixels tall (12 CSS pixels) .
©Toronto Commu…ghts reserved. renders only 4 pixels tall (10 CSS pixels) .
The following text fragments have a small line height. Increase the line height to make them more legible.

Urban HEART @T…lation health. and 1 others have a line height of only 108% of the font size .

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

http://torontohealthprofiles.ca/js/jquery.js
http://torontohealthprofiles.ca/js/jquery.lightbox-0.5.js
http://torontohealthprofiles.ca/a_javascript/menu_dropdown.js
Optimize CSS Delivery of the following:

http://torontohealthprofiles.ca/css/jquery.lightbox-0.5.css
http://torontohealthprofiles.ca/a_stylesheet/tchpp.css
http://torontohealthprofiles.ca/a_menu_dropdown.css
http://torontohealthprofiles.ca/searchByTopic.css

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="index.php?varTab=HPDtbl"></a> and 1 others are close to other tap targets .
The tap target <a href="a_aboutUs.php?varTab=HPDtbl" class="menulink ddmenu">About Us</a> and 2 others are close to other tap targets .
The tap target <a href="a_dataTables.php?varTab=HPDtbl" class="menulink1 ddmenu">Data, Maps and Charts</a> is close to 1 other tap targets .
The tap target <a href="a_dataTables.php?varTab=HPDtbl">data</a> and 11 others are close to other tap targets .
The tap target <a href="http://www.wel…yinstitute.com"></a> and 1 others are close to other tap targets .
The tap target <a href="index.php?varTab=HPDtbl">Home</a> and 9 others are close to other tap targets .
The tap target <a href="https://twitte…m/TCHPP_Health"></a> is close to 1 other tap targets .

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 2.9KiB (56% reduction).

Minifying http://torontohealthprofiles.ca/js/jquery.lightbox-0.5.js could save 2.9KiB (56% reduction) after compression.

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 2.8KiB (40% reduction).

Minifying http://torontohealthprofiles.ca/a_stylesheet/tchpp.css could save 1.8KiB (37% reduction) after compression.
Minifying http://torontohealthprofiles.ca/a_menu_dropdown.css could save 630B (48% reduction) after compression.
Minifying http://torontohealthprofiles.ca/css/jquery.lightbox-0.5.css could save 402B (45% reduction) after compression.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 1.4KiB (25% reduction).

Minifying http://torontohealthprofiles.ca/ could save 1.4KiB (25% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Enable compression
You have compression enabled. Learn more about enabling compression.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does torontohealthprofiles.ca use compression?

torontohealthprofiles.ca use br compression.
Original size: 21.68 KB
Compressed size: 5.65 KB
File reduced by: 16.03 KB (73%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

torontohealthprofiles.ca does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

torontohealthprofiles.ca does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Content-Encoding: br
Vary: Accept-Encoding
Date: Fri, 04 Oct 2019 06:12:02 GMT
X-Powered-By: PleskLin
Connection: close

+ DNS Lookup

Type Ip Target TTL
SOA 3600
Mname ns1.webnames.ca
Rname hosting.webnames.ca
Serial Number 1562367235
Refresh 21600
Retry 180
Expire 1209600
Minimum TTL 0
TXT 3600
MX smtp.webnames.ca 3600
A 209.15.37.36 3600
NS ns2.webnames.ca 3600
NS ns1.webnames.ca 3600
NS ns3.webnames.ca 3600

+ Whois Lookup

Domain Created:
2004-12-22
Domain Age:
14 years 9 months 13 days  
WhoIs:
 

whois lookup at whois.cira.ca...
Domain Name: torontohealthprofiles.ca
Registry Domain ID: D254342-CIRA
Registrar WHOIS Server: whois.ca.fury.ca
Registrar URL: www.webnames.ca
Updated Date: 2019-08-22T15:02:20Z
Creation Date: 2004-12-22T20:57:10Z
Registry Expiry Date: 2020-12-22T05:00:00Z
Registrar: Webnames.ca Inc.
Registrar IANA ID: 456
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Redacted for Privacy Purposes
Registrant Name: Redacted for Privacy Purposes
Registrant Organization: Redacted for Privacy Purposes
Registrant Street: Redacted for Privacy Purposes
Registrant City: Redacted for Privacy Purposes
Registrant State/Province: Redacted for Privacy Purposes
Registrant Postal Code: Redacted for Privacy Purposes
Registrant Country: Redacted for Privacy Purposes
Registrant Phone: Redacted for Privacy Purposes
Registrant Phone Ext: Redacted for Privacy Purposes
Registrant Fax: Redacted for Privacy Purposes
Registrant Fax Ext: Redacted for Privacy Purposes
Registrant Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Admin ID: Redacted for Privacy Purposes
Admin Name: Redacted for Privacy Purposes
Admin Organization: Redacted for Privacy Purposes
Admin Street: Redacted for Privacy Purposes
Admin City: Redacted for Privacy Purposes
Admin State/Province: Redacted for Privacy Purposes
Admin Postal Code: Redacted for Privacy Purposes
Admin Country: Redacted for Privacy Purposes
Admin Phone: Redacted for Privacy Purposes
Admin Phone Ext: Redacted for Privacy Purposes
Admin Fax: Redacted for Privacy Purposes
Admin Fax Ext: Redacted for Privacy Purposes
Admin Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Tech ID: Redacted for Privacy Purposes
Tech Name: Redacted for Privacy Purposes
Tech Organization: Redacted for Privacy Purposes
Tech Street: Redacted for Privacy Purposes
Tech City: Redacted for Privacy Purposes
Tech State/Province: Redacted for Privacy Purposes
Tech Postal Code: Redacted for Privacy Purposes
Tech Country: Redacted for Privacy Purposes
Tech Phone: Redacted for Privacy Purposes
Tech Phone Ext: Redacted for Privacy Purposes
Tech Fax: Redacted for Privacy Purposes
Tech Fax Ext: Redacted for Privacy Purposes
Tech Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Billing ID: Redacted for Privacy Purposes
Billing Name: Redacted for Privacy Purposes
Billing Organization: Redacted for Privacy Purposes
Billing Street: Redacted for Privacy Purposes
Billing City: Redacted for Privacy Purposes
Billing State/Province: Redacted for Privacy Purposes
Billing Postal Code: Redacted for Privacy Purposes
Billing Country: Redacted for Privacy Purposes
Billing Phone: Redacted for Privacy Purposes
Billing Phone Ext: Redacted for Privacy Purposes
Billing Fax: Redacted for Privacy Purposes
Billing Fax Ext: Redacted for Privacy Purposes
Billing Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Name Server: ns1.webnames.ca
Name Server: ns2.webnames.ca
Name Server: ns3.webnames.ca
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-10-04T06:10:17Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

%
% Use of CIRA's WHOIS service is governed by the Terms of Use in its Legal
% Notice, available at http://www.cira.ca/legal-notice/?lang=en
%
% (c) 2019 Canadian Internet Registration Authority, (http://www.cira.ca/)
Last update was 238 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with torontohealthprofiles.ca in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

tribunbanjarmasin.com
11 secs
wefinex.net
21 secs
cryptobite.site
22 secs
jp.***.com
1 min
phornhub.com
1 min
cpamafia.top
2 mins
cmp24.com.ua
3 mins
eghtesadotejarat.ir
3 mins
bestboost.club
4 mins
fptasia.wordpress.com
5 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
torontohealthprofiles.ca widget