11 sec in total
759 ms
9.8 sec
388 ms
Click here to check amazing Funduro content for South Africa. Otherwise, check out these important facts you probably never knew about funduro.co.za
Up to date listings of all known funduro events in South Africa.
Visit funduro.co.zaWe analyzed Funduro.co.za page load time and found that the first response time was 759 ms and then it took 10.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.
funduro.co.za performance score
name
value
score
weighting
Value9.5 s
0/100
10%
Value15.6 s
0/100
25%
Value20.6 s
0/100
10%
Value1,440 ms
15/100
30%
Value0.13
81/100
15%
Value18.3 s
3/100
10%
759 ms
20 ms
50 ms
44 ms
45 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 47% of them (71 requests) were addressed to the original Funduro.co.za, 24% (36 requests) were made to Static.xx.fbcdn.net and 7% (10 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Funduro.co.za.
Page size can be reduced by 731.8 kB (63%)
1.2 MB
436.3 kB
In fact, the total size of Funduro.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 521.6 kB which makes up the majority of the site volume.
Potential reduce by 58.1 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 58.1 kB or 78% of the original size.
Potential reduce by 3.1 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. Funduro images are well optimized though.
Potential reduce by 344.1 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 344.1 kB or 66% of the original size.
Potential reduce by 326.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. Funduro.co.za needs all CSS files to be minified and compressed as it can save up to 326.5 kB or 74% of the original size.
Number of requests can be reduced by 114 (81%)
140
26
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funduro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 75 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
www.funduro.co.za
759 ms
wp-forecast-default.css
20 ms
cli-style.css
50 ms
style.css
44 ms
yasr.css
45 ms
jquery-ui.css
55 ms
dashicons.min.css
62 ms
yasr-table-dark.css
40 ms
public.css
45 ms
shortcodes.css
46 ms
thickbox.css
549 ms
front.css
48 ms
share-svg.css
571 ms
elements.css
49 ms
skin.css
544 ms
bootstrap.min.css
576 ms
bootstrap-responsive.min.css
59 ms
cyberchimps-responsive.min.css
67 ms
core.css
61 ms
style.css
62 ms
green.css
69 ms
jquery-ui-1.8.16.custom.css
70 ms
custom.css
72 ms
jquery.js
726 ms
jquery-migrate.min.js
709 ms
wpf_update.js
545 ms
cookielawinfo.js
1076 ms
general.js
1074 ms
common.js
1098 ms
sdk.js
582 ms
facebook.js
1142 ms
commenting.js
1235 ms
sharing.js
742 ms
gallery-lightbox.min.js
742 ms
jquery.slimbox.min.js
751 ms
jquery.jcarousel.min.js
1292 ms
jquery.mobile.custom.min.js
1650 ms
sdk.js
258 ms
swipe-call.min.js
1585 ms
core.min.js
1111 ms
script.js
1111 ms
cleantalk_nocache.js
1604 ms
form.js
1108 ms
jquery.rateit.min.js
1614 ms
yasr-front.js
1205 ms
core.min.js
1752 ms
widget.min.js
1780 ms
progressbar.min.js
1574 ms
position.min.js
2108 ms
tooltip.min.js
2106 ms
public-min.js
2150 ms
thickbox.js
2123 ms
jquery.elastislide.min.js
1740 ms
elements.min.js
2261 ms
bootstrap.min.js
2311 ms
retina-1.1.0.min.js
2631 ms
comment-reply.min.js
2162 ms
jquery.fullcalendar.min.js
1658 ms
jquery.simplemodal.1.4.3.min.js
2187 ms
jquery.mousewheel.min.js
2161 ms
jquery.jgrowl.min.js
2281 ms
datepicker.min.js
2385 ms
jquery.init_show_calendar.js
2535 ms
wp-embed.min.js
2480 ms
fb.js
2540 ms
wp-emoji-release.min.js
1996 ms
178 ms
analytics.js
39 ms
funduro-header-980x200.jpg
36 ms
b497c255312d51d617c8c018a9dcc9be
76 ms
26846b9c8d5c4d0d53b214af4b93e645
111 ms
24212635afc5f0d1bce49d3c78d8ec7b
129 ms
b30096b26ca3def2362d7ab57dad4dbd
132 ms
pdf.png
1606 ms
print.gif
1195 ms
loader.gif
1783 ms
98 ms
collect
17 ms
overlay.png
1531 ms
counter.js
16 ms
t.php
65 ms
xd_arbiter.php
163 ms
xd_arbiter.php
351 ms
follow-me.png
530 ms
loadingAnimation.gif
575 ms
comments.php
276 ms
xd_arbiter.php
233 ms
page.php
182 ms
VDcXWt2API5.css
244 ms
NKmY6djv5D1.css
285 ms
P89ct9-iEQC.css
329 ms
5PMOXdgTcuh.css
428 ms
SRSW8M763HA.js
465 ms
ullQFyhrQFI.js
494 ms
y97Ig99UVTs.js
388 ms
rR4Qw0p7TFQ.js
514 ms
ULtnh-HfQSw.js
391 ms
Cw6QosZRsiU.js
506 ms
FOagnU9QnXq.js
506 ms
O3W7iparFI2.js
508 ms
dt0QadAXRnm.js
506 ms
KanoMJZ9xtG.js
508 ms
ye4Amg-qrtc.js
574 ms
d_-F4IIjJo3.js
556 ms
3poIqqWXpbT.js
558 ms
KHAtULXOQuz.js
558 ms
ik8d09sCUBr.css
472 ms
h0O-5u1ruio.css
473 ms
3k9g4dfmgsB.js
621 ms
XokP-R2tSzH.js
620 ms
fav.png
83 ms
odA9sNLrE86.jpg
73 ms
wL6VQj7Ab77.png
73 ms
gm-8CYVMZ_l.png
72 ms
11224712_386250851581704_7111600899286375070_o.jpg
353 ms
10453373_388746931332096_6190284563300648582_n.jpg
437 ms
Wh-wXqXludh.png
67 ms
VXcANLwwL5J.js
41 ms
i8XO-4kv8i7.js
48 ms
R9GKCzjAnbk.js
29 ms
AWWjhOengNF.js
26 ms
YnSasnyq68i.js
20 ms
kQf_jlUv-kX.js
27 ms
107 ms
plusone.js
48 ms
comments.php
448 ms
http%3A%2F%2Fwww.funduro.co.za%2F
447 ms
comments.php
326 ms
cb=gapi.loaded_0
63 ms
cb=gapi.loaded_1
96 ms
comments
465 ms
xd_arbiter.php
138 ms
postmessageRelay
350 ms
page.php
383 ms
rs=AGLTcCOALUwapP9hhQIQnSObbRiQI3rggA
231 ms
1077434459-postmessagerelay.js
66 ms
rpc:shindig_random.js
66 ms
uFp_tsTJboUY7kue5XAsGA=s46
91 ms
R9GKCzjAnbk.js
73 ms
AWWjhOengNF.js
72 ms
YnSasnyq68i.js
158 ms
kQf_jlUv-kX.js
158 ms
comments.php
329 ms
fountain-72d8bab6fd088426374a15d7477489a4.png
31 ms
cb=gapi.loaded_0
33 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
335 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
340 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
588 ms
cb=gapi.loaded_0
29 ms
cb=gapi.loaded_1
318 ms
funduro.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
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
funduro.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
Browser errors were logged to the console
Page has valid source maps
funduro.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
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 Funduro.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 Funduro.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.
funduro.co.za
Open Graph data is detected on the main page of Funduro. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: