5.7 sec in total
1.2 sec
4.1 sec
369 ms
Click here to check amazing Phsa content for Canada. Otherwise, check out these important facts you probably never knew about phsa.ca
Visit phsa.caWe analyzed Phsa.ca page load time and found that the first response time was 1.2 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
phsa.ca performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value10.0 s
0/100
25%
Value9.9 s
10/100
10%
Value420 ms
66/100
30%
Value0.031
100/100
15%
Value14.8 s
8/100
10%
1206 ms
502 ms
340 ms
269 ms
190 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 67% of them (61 requests) were addressed to the original Phsa.ca, 29% (26 requests) were made to Ewiapps.phsa.ca and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Phsa.ca.
Page size can be reduced by 1.5 MB (68%)
2.3 MB
730.7 kB
In fact, the total size of Phsa.ca main page is 2.3 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. 55% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 77.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 77.9 kB or 77% of the original size.
Potential reduce by 80.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. Obviously, Phsa needs image optimization as it can save up to 80.5 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 888.0 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 888.0 kB or 69% of the original size.
Potential reduce by 484.3 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. Phsa.ca needs all CSS files to be minified and compressed as it can save up to 484.3 kB or 85% of the original size.
Number of requests can be reduced by 48 (62%)
77
29
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phsa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.phsa.ca
1206 ms
corev15.css
502 ms
searchv15.css
340 ms
controls15.css
269 ms
system.css
190 ms
font-styles.css
202 ms
modal.min.css
292 ms
phsa.css
523 ms
fixes.css
305 ms
print.css
375 ms
init.js
700 ms
ScriptResource.axd
426 ms
blank.js
423 ms
ScriptResource.axd
574 ms
sp.init.js
529 ms
clientrenderer.js
516 ms
ScriptResx.ashx
593 ms
search.clientcontrols.js
735 ms
search.cbs.js
623 ms
previews.js
619 ms
item_highlight.js
680 ms
group_content.js
652 ms
control_highlight.js
703 ms
html5shiv-printshiv.min.js
726 ms
WebResource.axd
753 ms
all.js
729 ms
footer.js
633 ms
master.js
635 ms
fixes.js
635 ms
modal.min.js
653 ms
favicon.ico
254 ms
spcommon.png
254 ms
phsa-logo.png
152 ms
logo.png
153 ms
searchresultui.png
265 ms
friendly-doctor.jpg
266 ms
phsa-logo.png
265 ms
british-columbia.png
266 ms
patient-care-quality-office.png
266 ms
ce6f5b38-1cb5-4a27-8182-583aa68b2436.woff
256 ms
07173950-fa69-4b65-9c71-0cf2ec00b51d.woff
277 ms
588c9ba8-1d28-4ad6-bf18-7128152d84c4.woff
359 ms
analytics.js
19 ms
trackingCode.js
42 ms
collect
30 ms
collect
60 ms
circle_button_bg_2x.png
297 ms
branded_background_2x.png
465 ms
standard_button_bg_2x.png
300 ms
appredirect.aspx
281 ms
phsa-icons.woff
267 ms
c4f4af3e-b5b8-4fb3-b707-670bbc765c69.woff
288 ms
appredirect.aspx
296 ms
customstrings.js
120 ms
footer.xml
145 ms
items
193 ms
sep_line-1_2x.png
128 ms
ServicesSearch
915 ms
CachedRss
887 ms
ACCOMPLISHMENTS-IMAGE-FOR-FRONT-WEBPAGE.JPG
99 ms
THINKSTOCKPHOTOS-479303354.JPG
108 ms
TOP%20100.JPG
118 ms
sep_line-2_2x.png
107 ms
initstrings.js
182 ms
strings.js
122 ms
core.js
253 ms
corev15.css
144 ms
jquery-1.10.2.min.js
382 ms
phsaClean.min.css
302 ms
sharedFrame.css
234 ms
threeTabSearch.css
230 ms
respond.min.js
303 ms
hostwebQueryString.js
259 ms
resize.js
312 ms
phsa-rss.css
365 ms
modernizr
431 ms
jquery
418 ms
bootstrap
484 ms
spcontext
367 ms
rss.js
430 ms
threeTabServicesSearch.js
434 ms
07173950-fa69-4b65-9c71-0cf2ec00b51d.woff
98 ms
ce6f5b38-1cb5-4a27-8182-583aa68b2436.woff
111 ms
588c9ba8-1d28-4ad6-bf18-7128152d84c4.woff
227 ms
phsa-icons.woff
95 ms
circle_button_bg_2x.png
97 ms
square_button_bg_2x.png
96 ms
ce6f5b38-1cb5-4a27-8182-583aa68b2436.woff
155 ms
07173950-fa69-4b65-9c71-0cf2ec00b51d.woff
91 ms
588c9ba8-1d28-4ad6-bf18-7128152d84c4.woff
126 ms
phsa-icons.woff
124 ms
phsa.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
phsa.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
phsa.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phsa.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 Phsa.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.
phsa.ca
Open Graph description is not detected on the main page of Phsa. 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: