3.3 sec in total
842 ms
2.3 sec
152 ms
Visit 3g.co.za now to see the best up-to-date 3 G content for South Africa and also check out these interesting facts you probably never knew about 3g.co.za
Voice, Industrial IOT products and services
Visit 3g.co.zaWe analyzed 3g.co.za page load time and found that the first response time was 842 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
3g.co.za performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value9.6 s
0/100
25%
Value7.6 s
26/100
10%
Value280 ms
81/100
30%
Value0.138
79/100
15%
Value9.0 s
34/100
10%
842 ms
376 ms
192 ms
191 ms
663 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 90% of them (56 requests) were addressed to the original 3g.co.za, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (842 ms) belongs to the original domain 3g.co.za.
Page size can be reduced by 562.1 kB (40%)
1.4 MB
837.1 kB
In fact, the total size of 3g.co.za main page is 1.4 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. 40% of websites need less resources to load. Images take 757.3 kB which makes up the majority of the site volume.
Potential reduce by 71.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 71.5 kB or 83% of the original size.
Potential reduce by 96.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. Obviously, 3 G needs image optimization as it can save up to 96.0 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 389.4 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 389.4 kB or 73% of the original size.
Potential reduce by 5.2 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. 3g.co.za needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 22% of the original size.
Number of requests can be reduced by 43 (73%)
59
16
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 3 G. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
3g.co.za
842 ms
mootools-core.js
376 ms
core.js
192 ms
caption.js
191 ms
mootools-more.js
663 ms
s5_ls_fade.js
192 ms
jd.gallery.js
287 ms
jd.gallery.transitions.js
286 ms
css
32 ms
s5_flex_menu.js
474 ms
s5_flex_menu.css
285 ms
system.css
388 ms
general.css
388 ms
template_default.css
389 ms
template.css
470 ms
com_content.css
476 ms
editor.css
477 ms
thirdparty.css
480 ms
multibox.css
565 ms
ajax.css
568 ms
overlay.js
570 ms
multibox.js
689 ms
s5_font_adjuster.js
574 ms
s5_responsive_bars.css
688 ms
s5_responsive_hide_classes.css
687 ms
s5_responsive.css
687 ms
s5_info_slide.css
688 ms
s5_info_slide.js
753 ms
css
30 ms
s5_responsive_mobile_bar.js
754 ms
lazy_load.js
755 ms
s5_columns_equalizer.js
771 ms
system.css
97 ms
s5_background.png
96 ms
menu_light.png
97 ms
search_light.png
97 ms
goava_32x32.png
97 ms
3G_logo.png
194 ms
loading.gif
154 ms
AVL_slider.png
382 ms
rCell500_slide.jpg
287 ms
rCell100_slide.jpg
381 ms
goava_price_slide.jpg
379 ms
Call_Centre_infoslide.jpg
342 ms
Router_infoslide.jpg
289 ms
Modems_infoslide.jpg
382 ms
printButton.png
386 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
17 ms
background.png
432 ms
facebook.png
470 ms
google.png
471 ms
twitter.png
472 ms
rss.png
472 ms
s5_search.png
475 ms
s5_ls.css
526 ms
s5_menu_bg.png
117 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMQg.ttf
8 ms
s5_top_row1.png
111 ms
s5_scroll_arrow.png
96 ms
ga.js
62 ms
s5_menu_arrow.png
96 ms
__utm.gif
12 ms
3g.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
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
3g.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
3g.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
Links do not have descriptive text
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 doesn't use 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 3g.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 3g.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.
3g.co.za
Open Graph description is not detected on the main page of 3 G. 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: