8.4 sec in total
1.5 sec
6.7 sec
227 ms
Visit stmarys.co.za now to see the best up-to-date Stmarys content and also check out these interesting facts you probably never knew about stmarys.co.za
Visit stmarys.co.zaWe analyzed Stmarys.co.za page load time and found that the first response time was 1.5 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
stmarys.co.za performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value2.0 s
96/100
25%
Value2.5 s
98/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.0 s
99/100
10%
1467 ms
25 ms
273 ms
524 ms
538 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 84% of them (49 requests) were addressed to the original Stmarys.co.za, 10% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Stmarys.co.za.
Page size can be reduced by 866.5 kB (56%)
1.6 MB
688.9 kB
In fact, the total size of Stmarys.co.za main page is 1.6 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. 45% of websites need less resources to load. Javascripts take 858.8 kB which makes up the majority of the site volume.
Potential reduce by 20.5 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 20.5 kB or 80% of the original size.
Potential reduce by 25.8 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. Stmarys images are well optimized though.
Potential reduce by 623.5 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 623.5 kB or 73% of the original size.
Potential reduce by 196.8 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. Stmarys.co.za needs all CSS files to be minified and compressed as it can save up to 196.8 kB or 85% of the original size.
Number of requests can be reduced by 26 (51%)
51
25
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stmarys. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.stmarys.co.za
1467 ms
css
25 ms
layerslider.css
273 ms
custom_vc_layout.css
524 ms
style.css
538 ms
font-awesome.min.css
541 ms
stylesheet.min.css
812 ms
js_composer_front.css
547 ms
style_dynamic.php
828 ms
responsive.min.css
782 ms
style_dynamic_responsive.php
1050 ms
custom_css.php
1048 ms
style.css
825 ms
jquery.js
1566 ms
jquery-migrate.min.js
1078 ms
layerslider.kreaturamedia.jquery.js
1354 ms
jquery-easing-1.3.js
1082 ms
jquerytransit.js
1318 ms
layerslider.transitions.js
1318 ms
qode-like.js
1345 ms
plugins.js
2456 ms
default_dynamic.php
1834 ms
default.min.js
1588 ms
custom_js.php
1845 ms
comment-reply.min.js
1622 ms
js_composer_front.js
1825 ms
style.css
1034 ms
analytics.js
15 ms
logo.png
541 ms
supportus.png
819 ms
hospitals.png
270 ms
outpatents.png
263 ms
medicali.png
273 ms
clinicalv.png
524 ms
wishl.png
537 ms
fees.png
540 ms
bec.png
786 ms
ref.png
806 ms
eye.png
816 ms
cal.png
815 ms
shadow.jpg
817 ms
img1.png
2088 ms
HwcR1xy4rp5CQGMY8FhsNALUuEpTyoUstqEm5AMlJo4.ttf
29 ms
ZKwULyCG95tk6mOqHQfRBMDdSZkkecOE1hvV7ZHvhyU.ttf
29 ms
cbAbzEjxTdN5KKmS-gA0tcDdSZkkecOE1hvV7ZHvhyU.ttf
29 ms
collect
17 ms
soZfbn11PkChMcyPRwvf0evvDin1pK8aKteLpeZ5c0A.ttf
5 ms
l1cOQ90roY9yC7voEhngDCZ2oysoEQEeKwjgmXLRnTc.ttf
5 ms
dI-qzxlKVQA6TUC5RKSb3yZ2oysoEQEeKwjgmXLRnTc.ttf
13 ms
fontawesome-webfont.woff
1563 ms
skin.css
466 ms
portfolio_single_button_green.png
462 ms
flex_arrow_left_green.png
462 ms
flex_arrow_right_green.png
465 ms
social_share.png
722 ms
social_share_white.png
726 ms
bg1.jpg
817 ms
skin.png
276 ms
stmarys.co.za 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
Document doesn't have a <title> element
stmarys.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
stmarys.co.za SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stmarys.co.za can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Stmarys.co.za 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.
stmarys.co.za
Open Graph description is not detected on the main page of Stmarys. 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: