3.2 sec in total
232 ms
2.8 sec
139 ms
Welcome to ehealthontario.ca homepage info - get ready to check EHealth Ontario best content for Canada right away, or after learning these important things about ehealthontario.ca
Visit ehealthontario.caWe analyzed Ehealthontario.ca page load time and found that the first response time was 232 ms and then it took 2.9 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 Ehealthontario.ca rating and web reputation
ehealthontario.ca performance score
232 ms
73 ms
149 ms
513 ms
42 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 96% of them (86 requests) were addressed to the original Ehealthontario.ca, 3% (3 requests) were made to Ssl.google-analytics.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (710 ms) belongs to the original domain Ehealthontario.ca.
Page size can be reduced by 1.2 MB (74%)
1.7 MB
430.1 kB
In fact, the total size of Ehealthontario.ca main page is 1.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. 40% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 72.0 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 15.3 kB, which is 18% 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 72.0 kB or 83% of the original size.
Potential reduce by 29.9 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. Obviously, EHealth Ontario needs image optimization as it can save up to 29.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 920.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 920.6 kB or 81% of the original size.
Potential reduce by 224.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. Ehealthontario.ca needs all CSS files to be minified and compressed as it can save up to 224.4 kB or 89% of the original size.
Number of requests can be reduced by 28 (33%)
85
57
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EHealth Ontario. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.ehealthontario.ca
232 ms
server.pt
73 ms
login.aspx
149 ms
3090
513 ms
PTIncluder.js
42 ms
mainstyleehealthuxportal-en.css
87 ms
mainstyle.css
127 ms
ehopagelayout.css
143 ms
dojo.js
185 ms
ptcommonopener.js
162 ms
ehealth.css
153 ms
superfish.css
175 ms
jquery-1.9.1.js
259 ms
jquery-ui-1.10.2.js
448 ms
jQuery.cookies.js
208 ms
general.js
356 ms
textSize.js
222 ms
superfish.js
242 ms
ehoportletlayout.css
264 ms
ehonew.css
280 ms
jQuery.cookies.js
294 ms
jquery.rotatingbanners.js
294 ms
ehopagelayout.css
355 ms
component.js
286 ms
PTU-Date-en.js
39 ms
PTU-Number-en.js
69 ms
PTUtil.js
68 ms
PTDateFormats.js
76 ms
PTXML.js
224 ms
PTPortletServices.js
325 ms
component.js
42 ms
PTRoboHelp.js
43 ms
body_bg.jpg
85 ms
ehealthportal_logo.png
85 ms
btnSearch.gif
84 ms
info.png
84 ms
home.jpg
79 ms
icon_documents.gif
84 ms
emergency_room.jpg
145 ms
lab.jpg
139 ms
vaccinations.jpg
123 ms
infant.jpg
126 ms
dental_tools.jpg
123 ms
graph.jpg
125 ms
ehealth_ontario_logo.png
197 ms
up_arrow.png
198 ms
gtm.js
99 ms
login_top.jpg
182 ms
tl.png
182 ms
tc.png
360 ms
tr.png
181 ms
cl.png
206 ms
cc.png
366 ms
cr.png
561 ms
bl.png
205 ms
bc.png
216 ms
br.png
219 ms
mainNav.jpg
204 ms
dd_bottom.png
209 ms
breadcrumb_bg.jpg
220 ms
health_professional.jpg
285 ms
tl.png
266 ms
tc.png
299 ms
tr.png
335 ms
cl.png
710 ms
cc.png
341 ms
login_btn-en.png
347 ms
cr.png
347 ms
bl.png
362 ms
bc.png
497 ms
br.png
386 ms
tl.png
395 ms
tc.png
421 ms
tr.png
427 ms
cl.png
460 ms
cc.png
448 ms
cr.png
477 ms
bl.png
669 ms
ga.js
65 ms
bc.png
486 ms
br.png
491 ms
bannerNavLeft.jpg
494 ms
banner_bg.jpg
457 ms
banner_image_bg
475 ms
bannerNavRight.jpg
477 ms
footer_bg.jpg
493 ms
__utm.gif
13 ms
dd_bg.png
481 ms
__utm.gif
16 ms
dd_custom.png
661 ms
ehealthontario.ca SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ehealthontario.ca 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 Ehealthontario.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.
ehealthontario.ca
Open Graph description is not detected on the main page of EHealth Ontario. 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: