5.8 sec in total
1.4 sec
4.1 sec
309 ms
Click here to check amazing Sahara content for South Africa. Otherwise, check out these important facts you probably never knew about sahara.co.za
Visit sahara.co.zaWe analyzed Sahara.co.za page load time and found that the first response time was 1.4 sec and then it took 4.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.
sahara.co.za performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value3.3 s
68/100
25%
Value2.4 s
98/100
10%
Value220 ms
87/100
30%
Value0.014
100/100
15%
Value3.6 s
91/100
10%
1387 ms
527 ms
801 ms
1073 ms
800 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that all of those requests were addressed to Sahara.co.za and no external sources were called. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Sahara.co.za.
Page size can be reduced by 697.4 kB (44%)
1.6 MB
874.0 kB
In fact, the total size of Sahara.co.za main page is 1.6 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. 50% of websites need less resources to load. Javascripts take 721.4 kB which makes up the majority of the site volume.
Potential reduce by 47.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 47.3 kB or 54% of the original size.
Potential reduce by 61.4 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. Sahara images are well optimized though.
Potential reduce by 518.3 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 518.3 kB or 72% of the original size.
Potential reduce by 70.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. Sahara.co.za needs all CSS files to be minified and compressed as it can save up to 70.5 kB or 82% of the original size.
Number of requests can be reduced by 18 (42%)
43
25
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sahara. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
sahara.co.za
1387 ms
A.style.css+social-icons.css,Mcc.wVc_eoZG4h.css.pagespeed.cf.s0NcCgdzZt.css
527 ms
jquery-1.5.1.min.js.pagespeed.jm.A_xP-993uZ.js
801 ms
jquery-ui-1.8.13.custom.min.js.pagespeed.jm.rRwKMkFAUd.js
1073 ms
easing.js+jquery.scrollTo-1.4.2-min.js+jquery.cycle.all.js+custom.js+jquery.isotope.min.js.pagespeed.jc.09f_EQTD7L.js
800 ms
A.css,,_nivo-slider.css+css,,_tabs.css+js,,_prettyPhoto,,_css,,_prettyPhoto.css+css,,_superfish.css,Mcc.sFuTWM2TcS.css.pagespeed.cf.xWP8GdXVAV.css
530 ms
nivo-slider,_jquery.nivo.slider.js+tabs.js+prettyPhoto,_js,_jquery.prettyPhoto.js+superfish-1.4.8,_js,_hoverIntent.js+superfish-1.4.8,_js,_superfish.js+superfish-1.4.8,_js,_supersubs.js+poshytip-1.0,_src,_jquery.poshytip.min.js+tweet,_jquery.tweet.js.pagespeed.jc.VnjndzOnDj.js
800 ms
superfish-left.css
788 ms
A.tip-twitter,,_tip-twitter.css+tip-yellowsimple,,_tip-yellowsimple.css,Mcc.CE_GV4yOXA.css.pagespeed.cf.4R8P3lWh_Z.css
795 ms
jquery.tweet.css
1050 ms
A.jquery.fancybox-1.3.4.css.pagespeed.cf.T2Rn5S22RA.css
1063 ms
jquery.fancybox-1.3.4.pack.js.pagespeed.jm.TDnM90nhme.js
1067 ms
jquery.min.js.pagespeed.jm.f4hWFRbKbx.js
1340 ms
jquery-ui.min.js.pagespeed.jm.90fMFf4xc3.js
1349 ms
jquery.flip.min.js+script.js+messages.js.pagespeed.jc.0DyzEAlKEG.js
1314 ms
msg_arrow.gif
265 ms
xnoise.png.pagespeed.ic.kW-arK9fGP.png
267 ms
xheader-glow.png.pagespeed.ic.gly5Pus0U9.png
534 ms
223xNxoriginal.png.pagespeed.ic.mWZ9_sMf51.png
274 ms
xslide9.jpg.pagespeed.ic.2ls_vsNw8N.jpg
543 ms
xslide10.jpg.pagespeed.ic.0cmHhzyyCp.jpg
804 ms
xslide2.jpg.pagespeed.ic.FdF3kRVpOI.jpg
1065 ms
xslide3.jpg.pagespeed.ic.A5HN58Qbmj.jpg
802 ms
xslide5.jpg.pagespeed.ic.mA0lgboDXK.jpg
811 ms
xslide6.jpg.pagespeed.ic.vVySZQf6uw.jpg
1068 ms
xslide7.jpg.pagespeed.ic.wegpczoraw.jpg
815 ms
xslide8.jpg.pagespeed.ic.tKWR4b7CLv.jpg
1339 ms
40x30xhome.png.pagespeed.ic.ZPozUYSHbp.png
1078 ms
35x20xmail32.png.pagespeed.ic.kJlDVqK2rG.png
1084 ms
35x30xenvelope.gif.pagespeed.ic.v4UyfLiATM.png
1087 ms
35x20xtelephone.png.pagespeed.ic.yvdOMN56eJ.png
1338 ms
xmenu-bg.png.pagespeed.ic.L2cAPIcOfE.png
1253 ms
xmenu-arrow.png.pagespeed.ic.JxxmLH7XLt.png
1266 ms
slider-bg.png.pagespeed.ce.wqRteT8t6n.png
1270 ms
xslider-shadow.png.pagespeed.ic.p5yXLzEVlE.png
1281 ms
loading.gif.pagespeed.ce.lbK8X_yLzr.gif
1515 ms
xtabs-divider.png.pagespeed.ic.x5kyt5n3wF.png
1533 ms
xtabs.png.pagespeed.ic.MFUCVwQRWf.png
1535 ms
xfooter-glow.png.pagespeed.ic.2DjZL8rxTq.png
1540 ms
xfooter-bullet.png.pagespeed.ic.d1N5W-99eH.png
1534 ms
bottom-shadow.png.pagespeed.ce.aXgJgiNfXW.png
1541 ms
xfacebook_32.png.pagespeed.ic.ik8y631Z_2.png
1786 ms
xtwitter_32.png.pagespeed.ic.x3x_tyM0B3.png
1804 ms
xto-top.png.pagespeed.ic.qTIIplaLjI.png
1799 ms
xslider-arrows.png.pagespeed.ic.--SAOaNcR7.png
1808 ms
xslider-nav-buttons.png.pagespeed.ic.oWMhsisa64.png
1804 ms
background.jpg
1802 ms
sahara.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
<frame> or <iframe> elements do not have a title
sahara.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
sahara.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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sahara.co.za can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Sahara.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.
sahara.co.za
Open Graph description is not detected on the main page of Sahara. 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: