5.3 sec in total
98 ms
4.5 sec
689 ms
Welcome to duracycles.co.za homepage info - get ready to check Duracycles best content right away, or after learning these important things about duracycles.co.za
Visit duracycles.co.zaWe analyzed Duracycles.co.za page load time and found that the first response time was 98 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
duracycles.co.za performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value12.7 s
0/100
25%
Value11.2 s
5/100
10%
Value360 ms
72/100
30%
Value0.061
97/100
15%
Value10.7 s
22/100
10%
98 ms
112 ms
70 ms
78 ms
97 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Duracycles.co.za, 28% (44 requests) were made to Static.wixstatic.com and 24% (38 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 3.1 MB (60%)
5.1 MB
2.0 MB
In fact, the total size of Duracycles.co.za main page is 5.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. 85% 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 3.2 MB which makes up the majority of the site volume.
Potential reduce by 243.3 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 243.3 kB or 90% of the original size.
Potential reduce by 46.9 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. Duracycles images are well optimized though.
Potential reduce by 2.4 MB
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 2.4 MB or 75% of the original size.
Potential reduce by 377.7 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. Duracycles.co.za needs all CSS files to be minified and compressed as it can save up to 377.7 kB or 83% of the original size.
Number of requests can be reduced by 79 (54%)
147
68
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Duracycles. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
duracycles.co.za
98 ms
www.duracycles.co.za
112 ms
bt
70 ms
require.min.js
78 ms
main-r.min.js
97 ms
viewer.css
59 ms
ugc-viewer
52 ms
dynamicmodel
25 ms
18ff78_8012cc28f68d18fe8f1bf0f67c8a9993_238.json.z
517 ms
18ff78_ba40b315b361c01baf740cd6b230b304_225.json.z
556 ms
bt
115 ms
skins.min.js
110 ms
components.min.js
75 ms
utils.min.js
34 ms
core.min.js
111 ms
react-with-addons.min.js
104 ms
lodash.min.js
103 ms
TweenMax.min.js
116 ms
layout.min.js
103 ms
tpa.min.js
315 ms
fonts.min.js
102 ms
animations.min.js
103 ms
swfobject.min.js
103 ms
mousetrap.min.js
102 ms
tweenEngine.min.js
105 ms
DrawSVGPlugin.min.js
309 ms
react-dom.min.js
101 ms
ScrollToPlugin.min.js
100 ms
widgets.min.js
103 ms
experiment.js
102 ms
render.min.js
103 ms
wixappsCore.min.js
305 ms
wixappsClassics.min.js
304 ms
wixappsBuilder.min.js
302 ms
zepto.min.js
299 ms
color.min.js
299 ms
react-dom-server.min.js
225 ms
bt
191 ms
dc.js
190 ms
bt
699 ms
ironpatern.png
366 ms
css
362 ms
latin.css
357 ms
18ff78_3a22f88b4c6694d1672910eec0c03e19.html
385 ms
twitter.html
382 ms
index.html
532 ms
18ff78_79479ed2a0587de4ead0d3cf90e479ab.html
377 ms
bt
259 ms
bt
259 ms
bt
476 ms
18ff78_76be78982e22422a86d319317e6eef9e.jpg
257 ms
da00086a27cc2c52ec7a11ec468c4d29.wix_mp
109 ms
89b1d2497b29ccbb7d37be1ec6ef0052.png
255 ms
18ff78_bf7609ca271a48a5b178793594427d00.png
472 ms
18ff78_6464246d68e0468eaeb871e5e3749f01.jpg
529 ms
18ff78_b91063b9d5ad44b79a6f80782493f19b.jpg
585 ms
41d000_6f13111cf41c7107099b5e3c2657ac69.png
733 ms
41d000_58f23276fbfef882e60857fea28314d9.png
733 ms
41d000_89ae7c127b377e5ac1daa47861ecc0b7.png
854 ms
41d000_011a69c213bb15c535e11ed7d915eece.png
848 ms
41d000_30b5e063630833d20b240840b835719f.png
738 ms
41d000_30b5e063630833d20b240840b835719f.png
844 ms
41d000_c227096f2b9726350c64d9427b3094ea.jpg
1069 ms
18ff78_2977011fd52a49139210f939f1c99bce.png
1068 ms
18ff78_7f925462a20a40e1b7e6484d128ee9c3.jpg
1028 ms
41d000_b83fc3795e1fbee50ad2bf93f35919b5.png
844 ms
18ff78_1ab3b672b459473296de32b3fe3ee4ee.gif
1109 ms
18ff78_6464246d68e0468eaeb871e5e3749f01.jpg
1109 ms
18ff78_d05f7f6f7da0494f87ab889c73286d26.jpg
1244 ms
18ff78_0ec81ad64f964348a048a8363e0ee194.jpg
1564 ms
18ff78_5798dda6ea2742908f6b64843da99214.jpg
1568 ms
18ff78_e5bd9b88cc0d416e86a590d72947fd42.png
1566 ms
18ff78_f738014b838e422bb55c760a7c1fdade.jpg
1567 ms
18ff78_0490429a67f949469ab321171cd88531.jpg
1657 ms
18ff78_7f925462a20a40e1b7e6484d128ee9c3.jpg
1658 ms
18ff78_64c46b6b7d724fb88232355084c40cc8.jpg
1658 ms
18ff78_8bfc952000ab47918251dbe5f73b219e.gif
1658 ms
18ff78_4ab89849524e4dfc996ff652a190a6e6.gif
1657 ms
18ff78_624cd6152f754f3792b7992dc7d93a77.gif
1656 ms
18ff78_87a02d7c4e444bba8457ef3b792f8ec0.jpg
2133 ms
18ff78_f5cfec06635d40919b5f0fdaed2332fa.jpg
1986 ms
18ff78_d9ff21955a254573911484f20b1b24ba.jpg
1979 ms
18ff78_a2068d0f8df74636866987be853d02b8.jpg
1981 ms
18ff78_7cae3c24015c45ea9ebb5d9b92479d3f.png
2128 ms
18ff78_8a9671a50ddc4bcd84499a7011f11bdd.jpg
1977 ms
sloppyhoriz.png
377 ms
sloppyvertical.png
407 ms
arrows_white_new3.png
421 ms
__utm.gif
338 ms
18ff78_82a4ed0547764b5096ff2e352c79e003.gif
2071 ms
like.php
658 ms
IWrDb9FLm0w
747 ms
count.php
632 ms
widgets.js
362 ms
18ff78_78003c20425848a881e2ecf6013660a8.jpg
2036 ms
tweet_button.html
549 ms
5t8vP9Hx2udzw372glmOxA.ttf
308 ms
opensans-regular-webfont.woff
308 ms
opensans-bold-webfont.woff
253 ms
bootstrap.min.css
165 ms
modernizr.custom.js
175 ms
main.css
192 ms
mobile.css
206 ms
jquery.min.js
296 ms
bootstrap.min.js
241 ms
typeahead.custom.js
240 ms
wix.min.js
237 ms
angular.min.js
239 ms
angular-resource.min.js
237 ms
jquery.placeholder.js
239 ms
index.js
350 ms
settings.js
355 ms
moment.min.js
354 ms
translation.js
354 ms
filters.js
353 ms
wix.js
359 ms
weatherappscpecificdirectives.js
486 ms
app.js
499 ms
18ff78_2798972008934b80a5e98e75c302dc80.png
2285 ms
41d000_38cdb763380ae86155438b684da06377.jpg
1746 ms
ugc-viewer
321 ms
ga-audiences
457 ms
41d000_c227096f2b9726350c64d9427b3094ea.jpg
1683 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
266 ms
41d000_38cdb763380ae86155438b684da06377.jpg
1956 ms
TY3MhkXpWJ-.js
1242 ms
LVx-xkvaJ0b.png
1265 ms
jot
266 ms
get.json
439 ms
text_en.json
42 ms
index.html
39 ms
nr-885.min.js
41 ms
477095207557537793
641 ms
syndication
227 ms
www-embed-player-vflfNyN_r.css
230 ms
www-embed-player.js
279 ms
7800adffd0
225 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
255 ms
ad_status.js
494 ms
analytics.js
411 ms
widget-anim.gif
505 ms
icon.png
194 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
490 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
495 ms
chancerain.svg
232 ms
partlycloudy.svg
195 ms
clear.svg
208 ms
proxy.jpg
658 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
230 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
172 ms
Z_9W_02T_normal.jpg
488 ms
collect
411 ms
btiLLgzM_normal.jpg
447 ms
CchUSPnW8AEAYV8.jpg:small
446 ms
CchUSPvWIAEaKke.jpg:small
447 ms
CchUSQDWEAAmr8x.jpg:small
531 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
422 ms
41d000_011a69c213bb15c535e11ed7d915eece.png
423 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
364 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
26 ms
duracycles.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.
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.
duracycles.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
Page has valid source maps
duracycles.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duracycles.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Duracycles.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.
duracycles.co.za
Open Graph description is not detected on the main page of Duracycles. 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: