7.8 sec in total
1 sec
6.3 sec
402 ms
Click here to check amazing Eighty20 content for South Africa. Otherwise, check out these important facts you probably never knew about eighty20.co.za
Eighty20 uses the power of research and analytics to help our clients deliver customer centric strategies.
Visit eighty20.co.zaWe analyzed Eighty20.co.za page load time and found that the first response time was 1 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
eighty20.co.za performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value12.8 s
0/100
25%
Value8.7 s
16/100
10%
Value940 ms
30/100
30%
Value0.045
99/100
15%
Value11.0 s
21/100
10%
1035 ms
488 ms
488 ms
1003 ms
491 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 52% of them (32 requests) were addressed to the original Eighty20.co.za, 39% (24 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Eighty20.co.za.
Page size can be reduced by 1.7 MB (76%)
2.2 MB
518.2 kB
In fact, the total size of Eighty20.co.za main page is 2.2 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. 70% of websites need less resources to load. CSS take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 288.0 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 288.0 kB or 92% of the original size.
Potential reduce by 35.7 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, Eighty20 needs image optimization as it can save up to 35.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 299.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 299.0 kB or 68% of the original size.
Potential reduce by 1.0 MB
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. Eighty20.co.za needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 89% of the original size.
Number of requests can be reduced by 23 (64%)
36
13
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eighty20. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.eighty20.co.za
1035 ms
widget.css
488 ms
theme-my-login.css
488 ms
js_composer.min.css
1003 ms
style.min.css
491 ms
link-buttons.min.css
501 ms
perfect-scrollbar-0.4.6.min.css
506 ms
animate.min.css
733 ms
css
23 ms
main-b7eb33dd.css
1236 ms
owl.carousel-c6583616.css
736 ms
addtoany.min.css
750 ms
jquery.js
1270 ms
jquery-migrate.min.js
977 ms
css
34 ms
anti-spam-4.2.js
743 ms
main-42912801.js
1027 ms
vc-bootstrap-templates.js
985 ms
script.min.js
988 ms
perfect-scrollbar-0.4.6.with-mousewheel.min.js
1025 ms
modernizr-45f0e1f4.js
1233 ms
isotope.pkgd.min.js
1396 ms
owl.carousel-83c7a98c.js
1430 ms
js_composer_front.min.js
1433 ms
analytics.js
120 ms
logo.png
357 ms
bg-carousel.png
526 ms
big-data.png
643 ms
consumer-markets.png
651 ms
africa.png
657 ms
loyalty.png
508 ms
financial-services.png
1004 ms
Powered-by-Tritech-Media-Logo.png
672 ms
page.js
14 ms
ODelI1aHBYDBqgeIAH2zlFzCdIATDt8zXO3QNtzVeJ8.ttf
43 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
73 ms
toadOcfmlt9b38dHJxOBGEBls_1aQwi4AfipSOlE3SU.ttf
85 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
85 ms
toadOcfmlt9b38dHJxOBGAKTmyy2N_c1g4QjPYxpyoM.ttf
86 ms
toadOcfmlt9b38dHJxOBGGvd-IutAbwf5FQ8ZpuI2w4.ttf
86 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
86 ms
toadOcfmlt9b38dHJxOBGGAlZ1PukdtTN2z-JxSzbe8.ttf
84 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
248 ms
toadOcfmlt9b38dHJxOBGOmWm5x7AGfSS0YwqQKRPBc.ttf
249 ms
zpv3sOKAbMf4wff105oLjw.ttf
284 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
283 ms
5pEc4QKTMA2oB4Hi9NkS4w.ttf
285 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
284 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
285 ms
BTu4SsVveqk58cdYjlaM9g.ttf
286 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
285 ms
vDvcuXwZxUMLuTfuLrSLpA.ttf
286 ms
fontawesome-webfont.woff
1208 ms
fontello.woff
1303 ms
M2Jd71oPJhLKp0zdtTvoM6xot8ENfkYez2Lz7rcrw70.ttf
285 ms
fpTVHK8qsXbIeTHTrnQH6I48KljrVa8Zcyi9xGGohEU.ttf
285 ms
fpTVHK8qsXbIeTHTrnQH6MtI7l28c1iVM3aK-UyzB28.ttf
286 ms
fpTVHK8qsXbIeTHTrnQH6KjMMkbXdLGS8FpAnMJn5J0.ttf
286 ms
fpTVHK8qsXbIeTHTrnQH6KQ4IK8jcFikBX2R8jKe4LU.ttf
286 ms
fpTVHK8qsXbIeTHTrnQH6NMYubg6_A1wiElARQzzeJ4.ttf
286 ms
collect
233 ms
eighty20.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
eighty20.co.za 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
eighty20.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eighty20.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 Eighty20.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.
eighty20.co.za
Open Graph description is not detected on the main page of Eighty20. 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: