5.2 sec in total
1.2 sec
3.6 sec
434 ms
Visit 420sa.co.za now to see the best up-to-date 420SA content for South Africa and also check out these interesting facts you probably never knew about 420sa.co.za
420SA is a South African cannabis forum connecting cultivators, consumers and the cannabis industry as a whole. Learn how to grow cannabis in South Africa. Grow your own cannabis and make your own can...
Visit 420sa.co.zaWe analyzed 420sa.co.za page load time and found that the first response time was 1.2 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
420sa.co.za performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value10.3 s
0/100
25%
Value6.3 s
42/100
10%
Value440 ms
64/100
30%
Value0.006
100/100
15%
Value9.9 s
27/100
10%
1226 ms
76 ms
62 ms
232 ms
278 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 92% of them (65 requests) were addressed to the original 420sa.co.za, 6% (4 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain 420sa.co.za.
Page size can be reduced by 334.1 kB (28%)
1.2 MB
847.8 kB
In fact, the total size of 420sa.co.za main page is 1.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. 60% of websites need less resources to load. Images take 451.8 kB which makes up the majority of the site volume.
Potential reduce by 231.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. This page needs HTML code to be minified as it can gain 29.9 kB, which is 11% 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 231.0 kB or 88% of the original size.
Potential reduce by 32.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. 420SA images are well optimized though.
Potential reduce by 49.5 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 49.5 kB or 14% of the original size.
Potential reduce by 20.9 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. 420sa.co.za needs all CSS files to be minified and compressed as it can save up to 20.9 kB or 20% of the original size.
Number of requests can be reduced by 24 (38%)
64
40
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 420SA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.420sa.co.za
1226 ms
js
76 ms
css
62 ms
341e4a57816af3ba440d891ca87450ff_framework.css
232 ms
05e81b71abe4f22d6eb8d1a929494829_responsive.css
278 ms
90eb5adf50a8c640f633d47fd7eb1778_core.css
312 ms
5a0da001ccc2200dc5625c3f3934497d_core_responsive.css
318 ms
ec0c06d47f161faa24112e8cbf0665bc_chatbox.css
333 ms
1b84cc05a2744615b3fb195a791a579d_marktopic.css
387 ms
62e269ced0fdab7e30e026f1d30ae516_forums.css
370 ms
76e62c573090645fb99a15a363d8620e_forums_responsive.css
415 ms
885a2e418b87306e5ae0b62323d68d08_widgets.css
413 ms
37c6452ea623de41c991284837957128_gallery.css
422 ms
22e9af7d7c6ac7ddc7db0f1b0d471efc_gallery_responsive.css
431 ms
51a672ecd6862df2c2f1969522683ee9_calendar.css
459 ms
258adbb6e4f3e83cd3b355f84e3fa002_custom.css
517 ms
logo-web.png.384957fa3a2cb71e1c2aceb20f2303d2.png
820 ms
root_library.js
1188 ms
root_js_lang_1.js
715 ms
root_framework.js
727 ms
global_global_core.js
714 ms
plugins_plugins.js
717 ms
root_front.js
716 ms
front_front_core.js
728 ms
front_front_chatbox.js
728 ms
front_front_browse.js
769 ms
front_front_forum.js
854 ms
root_map.js
854 ms
phlizon_led_grow_light.jpg.87153fc26aac967261a68eaddb6c7790.jpg
854 ms
AvatarPostCovid.thumb.jpg.c5cb9998307b4212b80ff1171f5d381f.jpg
929 ms
chrisjaycharac.thumb.jpg.d867926473b49de3c4dd96428f3b4bb8.jpg
929 ms
IMG_20240811_112509.thumb.jpg.da45f5f21f3878ceabce05f110ccbb32.jpg
957 ms
896020403_YocanOfficial(1).png.a06b82950543715325a69ceb63792683.png
948 ms
1366579053_YocanOfficial-ProfilePic.thumb.png.5d8c60f08aa8bdb2d0a722c713050eb8.png
962 ms
phlizon_board_icon.png.eef84496c16af14ba86d5b0212387f2f.png
1028 ms
Phlizon_brand_logo_200x200.thumb.jpg.5875bb536eff5f93ca708f0cee921ce7.jpg
1013 ms
logo-trans-board.png.ef7221de2736060794f992697d938532.png
1039 ms
1675240523857_TOTEMICLOGO-2023.thumb.png.e08ab8496c4c04881ce65794b74cce72.png
1058 ms
JackGrealish.thumb.jpg.6257a53c686c156fc8e0ec44115ed76c.jpg
1074 ms
Image1620725712615.thumb.jpg.170bde6c1751ad3254883099ebce4570.jpg
883 ms
Image1563060291364.thumb.jpg.e814f801f82e78c1290afba92f1fbd42.jpg
897 ms
872988556_67197745_121372842499100_2967260220216512461_n.jpg_nc_htinstagram.fpry1-1_fna.fbcdn.thumb_net.a6e2817bac4df9975c751ccada1bd3f3
836 ms
Compress_20230521_171039_9678.thumb.jpg.23b5c2dc779ebedc3085b01db180d9da.jpg
860 ms
polar-bear-walking.thumb.gif.ab71b1486c8cde934d2d108c577e433b.gif
1321 ms
FullLogo.thumb.png.2a8761cd83b89392d5360a47a529ba21.png
930 ms
1483.thumb.jpg.396b4da00df933d4cfe2462676c9942f.jpg
913 ms
Jurrasic_minion_3.thumb.jpg.3dde2a1e3162740e67e25ccbf0ec04a5.jpg
909 ms
logo.thumb.jpg.9b2b00e8e0b5f18a6ca9e2d738edac91.jpg
886 ms
1286314540_WhatsAppImage2022-07-12at12_31_39PM.thumb.jpeg.bb477a123009efcaaf62603480d0ec67.jpeg
914 ms
923892078_6July(2).thumb.jpg.40fa3417bb8f746949f0efeca5d720c1.jpg
898 ms
Image7.thumb.jpg.8345dc0de19333c2bce01edb6b7a27aa.jpg
886 ms
PSX_20220822_212753.thumb.jpg.9622dc2cc987936402a6c8603aa156ff.jpg
649 ms
Image1620571203711.thumb.jpg.85214f0fd24f20283ba818822d522f50.jpg
705 ms
1f5ffdfc760dc451ecb6b5683e37e2f0.jpg.3bb6b187dd91e9de72ffe3c7e0871d9b.jpg
690 ms
lfe.thumb.png.dbf2a46cf1e6f6090ffbb503a39b2ab9.png
757 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjZ-Ek-_0ew.ttf
92 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjZ-Ek-_0ew.ttf
170 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjZ-Ek-_0ew.ttf
143 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYAZ9hjZ-Ek-_0ew.ttf
169 ms
fontawesome-webfont.woff
718 ms
1754573522_IkUJK5T1.thumb.png.3b6bab6250c1c0fdd4369180e3ca9ab1.png
748 ms
449109433_367405919786548_4019977333886263208_n.thumb.jpg.bbce7194954535ec8d84748b8b896a0a.jpg
769 ms
SevenDaysRegistered.svg
822 ms
91593109-beautiful-typography-design-of-city-cape-town-name-icon-with-red-heart-suitable-for-tourism-or-visit.cropped.jpg.b50187f7f8ee69e76b04e32b77b21688.jpg
771 ms
1483675535_rqsNLAuto-Day7-8Aug.JPG.c35cb42f8673329595ece2b1dc818506.JPG
770 ms
565827974_DragonLogoCLR.cropped.jpg.8cff1d01efa0af8115e76216082720a0.jpg
711 ms
indoor-logo.png.4e1660a5e681008b203d9da43d85dd6c.png
734 ms
outdoor-logo.png.52f9a2c151236096a8c13c6a53b47a54.png
788 ms
phlizon_led_grow_light.jpg.0d6a58f1e36e3ac8c0bde1e877ae99c1.jpg
749 ms
logo-web.png.442ffdf1b56c62de1123b1a35aaf07e1.png
929 ms
d0e70b4cbb9ab8afb1bc1065a3f8487a_subitem_stem.png
751 ms
420sa.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
420sa.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
420sa.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
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 420sa.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 420sa.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.
420sa.co.za
Open Graph description is not detected on the main page of 420SA. 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: