4.9 sec in total
843 ms
3.9 sec
242 ms
Welcome to locost.co.za homepage info - get ready to check Locost best content for South Africa right away, or after learning these important things about locost.co.za
Locost SA, the South African Locost Site
Visit locost.co.zaWe analyzed Locost.co.za page load time and found that the first response time was 843 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
locost.co.za performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value1.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
843 ms
269 ms
1339 ms
1351 ms
313 ms
Our browser made a total of 19 requests to load all elements on the main page. We found that all of those requests were addressed to Locost.co.za and no external sources were called. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Locost.co.za.
Page size can be reduced by 9.8 kB (3%)
360.7 kB
350.9 kB
In fact, the total size of Locost.co.za main page is 360.7 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. Images take 359.4 kB which makes up the majority of the site volume.
Potential reduce by 714 B
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 714 B or 56% of the original size.
Potential reduce by 9.0 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. Locost images are well optimized though.
We found no issues to fix!
18
18
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Locost. According to our analytics all requests are already optimized.
locost.co.za
843 ms
Header01.htm
269 ms
Contents01.htm
1339 ms
Main01.htm
1351 ms
seven.gif
313 ms
chassis.gif
296 ms
Locost%20Position.jpg
1387 ms
BradWoolley1.jpg
579 ms
P1060390.JPG
1332 ms
P1050798.JPG
1351 ms
SAFlag.gif
843 ms
P1040460small.jpg
575 ms
Westfield%20157.jpg
847 ms
P0000010small.jpg
855 ms
Midvaal_sm.jpg
1122 ms
Stig.jpg
1389 ms
sidebar.jpg
1146 ms
XTR2.gif
1660 ms
Luego2.gif
1408 ms
locost.co.za accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
locost.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
locost.co.za SEO score
EN
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Locost.co.za 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 Locost.co.za main page’s claimed encoding is windows-1252. 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.
locost.co.za
Open Graph description is not detected on the main page of Locost. 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: