4.7 sec in total
772 ms
3.7 sec
150 ms
Click here to check amazing Sto content for South Africa. Otherwise, check out these important facts you probably never knew about sto.co.za
STO aims to empower the Sectional Title community through the open and free sharing of knowledge resources.
Visit sto.co.zaWe analyzed Sto.co.za page load time and found that the first response time was 772 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
sto.co.za performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value3.0 s
78/100
25%
Value2.5 s
98/100
10%
Value180 ms
91/100
30%
Value0.014
100/100
15%
Value3.6 s
91/100
10%
772 ms
1158 ms
1017 ms
523 ms
519 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 63% of them (25 requests) were addressed to the original Sto.co.za, 10% (4 requests) were made to Google-analytics.com and 8% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Sto.co.za.
Page size can be reduced by 128.5 kB (46%)
279.3 kB
150.8 kB
In fact, the total size of Sto.co.za main page is 279.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 178.9 kB which makes up the majority of the site volume.
Potential reduce by 12.1 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 2.1 kB, which is 13% 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 12.1 kB or 75% of the original size.
Potential reduce by 10.4 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, Sto needs image optimization as it can save up to 10.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 94.9 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 94.9 kB or 53% of the original size.
Potential reduce by 11.1 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. Sto.co.za needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 81% of the original size.
Number of requests can be reduced by 21 (64%)
33
12
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
sto.co.za
772 ms
www.sto.co.za
1158 ms
mootools.js
1017 ms
caption.js
523 ms
all.css
519 ms
common.js
531 ms
footer_positioning.js
531 ms
validator.js
539 ms
conversion.js
14 ms
woopra.v2.js
58 ms
analytics.js
22 ms
ui-body-bg.png
252 ms
ui-bg.png
245 ms
ui-header.jpg
763 ms
presented-by-paddocks.png
264 ms
ui-main-menu-header.png
254 ms
ui-main-menu-bottom.png
252 ms
ui-main-menu-item-bottom-out.png
487 ms
find-us-on-facebook.png
509 ms
follow-us-on-twitter.png
510 ms
css_rounded_button_right.png
505 ms
css_rounded_button.png
515 ms
ui-latest-forum-topics-bottom.png
730 ms
ui-latest-forum-topics-header.png
758 ms
sto_new_courses_1.png
1018 ms
ui-advertisements-header.png
759 ms
1406_private_consulting.png
1020 ms
ui-footer-rss.png
973 ms
61 ms
collect
15 ms
collect
62 ms
46 ms
ga.js
19 ms
84 ms
32 ms
__utm.gif
26 ms
57 ms
63 ms
15 ms
20 ms
sto.co.za accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
sto.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
sto.co.za SEO score
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
N/A
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sto.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Sto.co.za main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
sto.co.za
Open Graph description is not detected on the main page of Sto. 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: