3.7 sec in total
860 ms
2.6 sec
247 ms
Click here to check amazing Nestle content for South Africa. Otherwise, check out these important facts you probably never knew about nestle.co.za
"Good Food Good Life", the quote stands true as the quality of food that you consume plays a vital role in the overall well-being. Explore more about it here.
Visit nestle.co.zaWe analyzed Nestle.co.za page load time and found that the first response time was 860 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
nestle.co.za performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value29.9 s
0/100
25%
Value14.1 s
1/100
10%
Value1,510 ms
14/100
30%
Value0.14
79/100
15%
Value31.3 s
0/100
10%
860 ms
7 ms
9 ms
8 ms
14 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 49% of them (55 requests) were addressed to the original Nestle.co.za, 9% (10 requests) were made to Google-analytics.com and 6% (7 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (860 ms) belongs to the original domain Nestle.co.za.
Page size can be reduced by 368.6 kB (27%)
1.4 MB
987.2 kB
In fact, the total size of Nestle.co.za main page is 1.4 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. 70% of websites need less resources to load. Images take 858.9 kB which makes up the majority of the site volume.
Potential reduce by 57.2 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 8.7 kB, which is 12% 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 57.2 kB or 81% of the original size.
Potential reduce by 23.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. Nestle images are well optimized though.
Potential reduce by 132.0 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 132.0 kB or 56% of the original size.
Potential reduce by 155.6 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. Nestle.co.za needs all CSS files to be minified and compressed as it can save up to 155.6 kB or 81% of the original size.
Number of requests can be reduced by 56 (54%)
103
47
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nestle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.nestle.co.za
860 ms
select2.min.css
7 ms
nestle-commun.min.css
9 ms
nestle-migration.min.css
8 ms
nestle-widgets.min.css
14 ms
nestle-corporate.min.css
12 ms
TableLayout.min.css
19 ms
owl.carousel.min.css
19 ms
jquery-1.7.1.min.js
21 ms
modernizr.min.js
33 ms
jquery.cycle2.min.js
30 ms
jquery.cycle2.carousel.min.js
30 ms
owl.carousel.min.js
30 ms
shortcut.min.js
37 ms
analytics.js
29 ms
bfbs.js
30 ms
livetwitterfeed.js
195 ms
ga.js
28 ms
gtm.js
84 ms
100years_SA.jpg
10 ms
960x540_babymonth_banner.jpg
192 ms
20160114_nespray_.jpg
200 ms
960x540-wellness-banner.jpg
194 ms
KitKat_Cocoa_Plan_Homepage_Highlight.jpg
200 ms
competition.jpg
141 ms
start_healthy_stay_healthy_5.jpg
237 ms
good_food.jpg
262 ms
v2_layout_design.png
185 ms
spt_social.png
273 ms
Roboto-Regular-webfont.woff
208 ms
Roboto-Medium-webfont.woff
214 ms
__utm.gif
24 ms
select2.min.js
141 ms
featurestory.min.js
217 ms
jquery.reveal.min.js
147 ms
behavior-design.min.js
148 ms
nestlecorporate.min.js
149 ms
__utm.gif
12 ms
NHW_logo.jpg
265 ms
Materna_logo.jpg
262 ms
CWL_logo.jpg
266 ms
20151207_nido.jpg
307 ms
contact-us-smallbox2.jpg
309 ms
collect
77 ms
Roboto-Light-webfont.woff
259 ms
analytics.js
23 ms
collect
11 ms
collect
16 ms
collect
34 ms
collect
39 ms
collect
49 ms
collect
50 ms
popUpVideoTop.png
172 ms
loading.gif
172 ms
iconArrowDownStock.png
178 ms
twitter_off.png
172 ms
twitter_on.png
174 ms
facebook_off.png
176 ms
facebook_on.png
174 ms
linkedin_off.png
175 ms
linkedin_on.png
176 ms
youtube_off.png
175 ms
youtube_on.png
176 ms
_Incapsula_Resource
44 ms
plusone.js
74 ms
all.js
171 ms
widgets.js
35 ms
in.js
35 ms
Roboto-Black-webfont.woff
119 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
29 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
47 ms
secureAnonymousFramework
55 ms
_Incapsula_Resource
16 ms
cb=gapi.loaded_0
152 ms
cb=gapi.loaded_1
197 ms
sharebutton
296 ms
syndication
193 ms
672333242683555840
359 ms
share
81 ms
sprite_connect_v14.png
232 ms
print.min.css
32 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
31 ms
249 ms
xd_arbiter.php
169 ms
xd_arbiter.php
302 ms
postmessageRelay
46 ms
api.js
51 ms
core:rpc:shindig.random:shindig.sha1.js
126 ms
2536007149-postmessagerelay.js
119 ms
rs=AGLTcCPhDrHY2vagSjsLFOxeufqSzVU3ow
32 ms
rs=AGLTcCMKQ6e_hqZOeATvsIASCkrCT4ec7w
29 ms
vxNK-E6B13CyehuDCmvQvw.woff
141 ms
grlryt2bdKIyfMSOhzd1eA.woff
203 ms
1f609.png
99 ms
1f600.png
98 ms
1f64f-1f3fe.png
99 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
29 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
51 ms
0_o7PsMs_normal.png
208 ms
ProudlySA_Member_Logo_normal.png
235 ms
S1pghJNF_normal.jpeg
371 ms
3ggHz5_e_normal.jpg
315 ms
CcI2Q2PUkAEydzQ.jpg:small
323 ms
Cb-vFYGWEAACgmn.jpg:small
329 ms
Cbj0xDPUcAAC_hD.jpg:small
348 ms
collect
22 ms
collect
15 ms
collect
15 ms
like.php
132 ms
jot.html
2 ms
vpc6VNjRPXV.js
297 ms
LVx-xkvaJ0b.png
336 ms
nestle.co.za accessibility score
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
nestle.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
nestle.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
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 Nestle.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 Nestle.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.
nestle.co.za
Open Graph data is detected on the main page of Nestle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: