17 sec in total
5.8 sec
11 sec
181 ms
Visit aletheia.co.za now to see the best up-to-date Aletheia content and also check out these interesting facts you probably never knew about aletheia.co.za
The domain name aletheia.co.za is for sale. Make an offer or buy it now at a set price.
Visit aletheia.co.zaWe analyzed Aletheia.co.za page load time and found that the first response time was 5.8 sec and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
aletheia.co.za performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value5.1 s
25/100
25%
Value4.5 s
73/100
10%
Value160 ms
93/100
30%
Value0.039
100/100
15%
Value6.8 s
55/100
10%
5810 ms
25 ms
547 ms
522 ms
537 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 96% of them (43 requests) were addressed to the original Aletheia.co.za, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Aletheia.co.za.
Page size can be reduced by 1.5 MB (72%)
2.1 MB
583.0 kB
In fact, the total size of Aletheia.co.za main page is 2.1 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. 50% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 35.6 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 35.6 kB or 83% of the original size.
Potential reduce by 23.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, Aletheia needs image optimization as it can save up to 23.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 958.7 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 958.7 kB or 74% of the original size.
Potential reduce by 461.5 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. Aletheia.co.za needs all CSS files to be minified and compressed as it can save up to 461.5 kB or 86% of the original size.
Number of requests can be reduced by 28 (65%)
43
15
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aletheia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
aletheia.co.za
5810 ms
css
25 ms
settings.css
547 ms
style.css
522 ms
font-awesome.min.css
537 ms
stylesheet.min.css
1074 ms
style_dynamic.css
658 ms
responsive.min.css
759 ms
style_dynamic_responsive.css
1047 ms
js_composer.css
1100 ms
custom_css.css
1095 ms
jquery.js
1672 ms
jquery-migrate.min.js
1706 ms
jquery.themepunch.tools.min.js
1878 ms
jquery.themepunch.revolution.min.js
1892 ms
html5.js
1639 ms
entrymetastyle.css
1788 ms
qode-like.js
2183 ms
plugins.js
3523 ms
jquery.carouFredSel-6.2.1.js
2522 ms
lemmon-slider.js
2327 ms
jquery.fullPage.min.js
2392 ms
jquery.mousewheel.min.js
2401 ms
jquery.touchSwipe.min.js
2714 ms
isotope.pkgd.min.js
2868 ms
js
78 ms
default_dynamic.js
2927 ms
default.min.js
3196 ms
custom_js.js
3055 ms
comment-reply.min.js
3254 ms
js_composer_front.js
3396 ms
logo1.svg
1573 ms
logo.png
1706 ms
logo_black.png
1826 ms
backaletheia3.jpg
2671 ms
1.jpg
2301 ms
2.jpg
2367 ms
3.jpg
2412 ms
separator3.png
2209 ms
poly1.jpg
2361 ms
fontawesome-webfont.woff
3234 ms
loader.gif
1087 ms
shadow1.png
1138 ms
small_left.png
1144 ms
small_right.png
1183 ms
aletheia.co.za accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
Links do not have a discernible name
aletheia.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
aletheia.co.za SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Aletheia.co.za 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 Aletheia.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.
aletheia.co.za
Open Graph description is not detected on the main page of Aletheia. 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: