7.4 sec in total
1.1 sec
5.9 sec
311 ms
Visit freshive.co.za now to see the best up-to-date Freshive content for South Africa and also check out these interesting facts you probably never knew about freshive.co.za
Visit freshive.co.zaWe analyzed Freshive.co.za page load time and found that the first response time was 1.1 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
freshive.co.za performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value25.1 s
0/100
25%
Value28.2 s
0/100
10%
Value9,830 ms
0/100
30%
Value0.279
43/100
15%
Value28.9 s
0/100
10%
1115 ms
281 ms
814 ms
546 ms
550 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 43% of them (48 requests) were addressed to the original Freshive.co.za, 28% (31 requests) were made to Maps.google.com and 10% (11 requests) were made to Staging2.freshive.co.za. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Freshive.co.za.
Page size can be reduced by 819.9 kB (26%)
3.2 MB
2.3 MB
In fact, the total size of Freshive.co.za main page is 3.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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 49.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 49.5 kB or 85% of the original size.
Potential reduce by 15.2 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. Freshive images are well optimized though.
Potential reduce by 604.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 604.4 kB or 68% of the original size.
Potential reduce by 150.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. Freshive.co.za needs all CSS files to be minified and compressed as it can save up to 150.7 kB or 83% of the original size.
Number of requests can be reduced by 49 (47%)
104
55
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freshive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
freshive.co.za
1115 ms
normalize.css
281 ms
bootstrap.min.css
814 ms
font-awesome.min.css
546 ms
jquery.bxslider.css
550 ms
isotope.css
555 ms
owl.carousel.css
558 ms
owl.theme.css
558 ms
style.css
823 ms
style-responsive.css
829 ms
css
25 ms
dynamic.css
829 ms
html5.js
36 ms
respond.js
832 ms
jquery.js
1395 ms
jquery-migrate.min.js
1078 ms
modernizr.js
1083 ms
jquery.mb.YTPlayer.js
1089 ms
jquery.sticky.js
1102 ms
jquery.fitvids.js
1108 ms
jquery.easing-1.3.pack.js
1350 ms
bootstrap-modal.js
1353 ms
bootstrap.min.js
1362 ms
jquery.parallax-1.1.3.js
1377 ms
jquery-countTo.js
1386 ms
jquery.appear.js
1617 ms
jquery.easy-pie-chart.js
1622 ms
jquery.cycle.all.js
1635 ms
jquery.maximage.js
1653 ms
imagesloaded.pkgd.min.js
1663 ms
jquery.isotope.min.js
1670 ms
skrollr.js
1888 ms
jquery.hoverdir.js
1893 ms
jquery.validate.min.js
1907 ms
portfolio_custom.js
1927 ms
jquery.bxslider.min.js
1941 ms
owl.carousel.min.js
1947 ms
script.js
2158 ms
js
22 ms
282-2.gif
883 ms
Logo32.png
609 ms
fresh_07.jpg
2520 ms
kia1.jpg
609 ms
ba.jpg
613 ms
daytona.jpg
610 ms
tourvest.jpg
879 ms
pepsi.jpg
879 ms
visa.jpg
887 ms
guess.jpg
889 ms
fresh_08.jpg
2542 ms
fresh_09.jpg
2899 ms
refresh.png
784 ms
fresh_10.jpg
2716 ms
fresh_00.jpg
2755 ms
royalcanin.jpg
799 ms
ram.jpg
1001 ms
clientele.jpg
1023 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
11 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
12 ms
fontawesome-webfont.woff
1893 ms
ga.js
11 ms
__utm.gif
13 ms
common.js
29 ms
map.js
29 ms
util.js
28 ms
marker.js
28 ms
arrow_left.png
283 ms
arrow_right.png
283 ms
pattern.png
271 ms
onion.js
34 ms
openhand_8_8.cur
49 ms
ViewportInfoService.GetViewportInfo
85 ms
stats.js
22 ms
controls.js
16 ms
infowindow.js
61 ms
transparent.png
31 ms
css
46 ms
google4.png
38 ms
marker.png
278 ms
mapcnt6.png
45 ms
sv5.png
45 ms
tmapctrl.png
21 ms
cb_scout5.png
22 ms
tmapctrl4.png
21 ms
vt
36 ms
vt
55 ms
vt
29 ms
vt
35 ms
vt
35 ms
vt
34 ms
vt
53 ms
vt
59 ms
vt
60 ms
vt
64 ms
vt
62 ms
vt
76 ms
vt
87 ms
vt
87 ms
vt
85 ms
vt
91 ms
vt
93 ms
vt
99 ms
vt
117 ms
vt
124 ms
vt
113 ms
vt
121 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
6 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
15 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
15 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
15 ms
AuthenticationService.Authenticate
66 ms
freshive.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.
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
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.
freshive.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
freshive.co.za SEO score
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 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 Freshive.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 Freshive.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.
freshive.co.za
Open Graph description is not detected on the main page of Freshive. 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: