3.1 sec in total
59 ms
2.7 sec
303 ms
Welcome to nestle.co.nz homepage info - get ready to check Nestle best content for New Zealand right away, or after learning these important things about nestle.co.nz
Nestlé, the world's largest food and beverage company, is committed to enhancing quality of life and contributing to a healthier future.
Visit nestle.co.nzWe analyzed Nestle.co.nz page load time and found that the first response time was 59 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
nestle.co.nz performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value14.4 s
0/100
25%
Value11.7 s
4/100
10%
Value2,200 ms
6/100
30%
Value0.03
100/100
15%
Value20.9 s
1/100
10%
59 ms
469 ms
52 ms
61 ms
138 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 86% of them (50 requests) were addressed to the original Nestle.co.nz, 9% (5 requests) were made to Unpkg.com and 3% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Nestle.co.nz.
Page size can be reduced by 206.0 kB (12%)
1.7 MB
1.5 MB
In fact, the total size of Nestle.co.nz main page is 1.7 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 992.2 kB which makes up the majority of the site volume.
Potential reduce by 187.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. This page needs HTML code to be minified as it can gain 36.3 kB, which is 15% 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 187.1 kB or 79% of the original size.
Potential reduce by 0 B
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 423 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 18.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. Nestle.co.nz has all CSS files already compressed.
Number of requests can be reduced by 32 (62%)
52
20
The browser has sent 52 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 18 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
nestle.co.nz
59 ms
www.nestle.co.nz
469 ms
css_JLOkg0ZUxn5HX6rnu-dOEoHCrSuenzJSNWFtjjPDmLc.css
52 ms
bootstrap.min.css
61 ms
drupal-bootstrap.min.css
138 ms
css_UfwCax97XZyHBUPrr6b-nD6t5_2pLsTzZFlels9-OC4.css
67 ms
jquery.mCustomScrollbar.css
44 ms
darkmode.css
426 ms
js_gUlydku8aP79USS-eUKMCMd_kQVMl8RB9NufoGu5lgQ.js
140 ms
darkreader.min.js
459 ms
js_HoXMStwt2SWgvgeREsLT6q7VJu7VQCb_ONXwjAC_ftE.js
65 ms
dark_mode.js
457 ms
js_CQNULn28xValB1JOIidphw58AtdlatRUqyLXWeA8Zz8.js
139 ms
seckit.document_write.js
466 ms
seckit.no_body.css
630 ms
esw.min.js
57 ms
js_sU4-27PUPdAHf8S6n_BlyAXsdT_l3FgnDJQ_L0xVq6s.js
132 ms
popper.js
131 ms
tippy-bundle.umd.js
129 ms
js_aSROkfjzWGcOA5J4rZQR_LNQuxH8aSL3BhOzSRoxe2s.js
132 ms
jquery.waypoints.min.js
128 ms
js_V6NQptyz5OG5ZchvUUlsSuNN4vA4g-9OKn0o-4xDYCw.js
154 ms
gtm.js
620 ms
gtag.js
798 ms
js_3ldI8UJcxGd8Ho5tWEBu7ozKEAS9o3LnDLENSXlmCiQ.js
565 ms
bootstrap.min.js
127 ms
js_H17h5EnrGYhE1BYU6qhw5cfHmwYc0RTSR0Ep7bbKzmk.js
619 ms
circular_button_close_white.svg
394 ms
icon-downarrow.png
403 ms
logo.svg
461 ms
Search-Icon.svg
400 ms
sprite-image.png
407 ms
home-icon-dark.svg
645 ms
icon-x.png
774 ms
chevron-right--white.svg
788 ms
about-us-featured_v2.jpg
428 ms
brands-landing.jpg
425 ms
1_future-food-homepage_0_0.jpg
463 ms
menu-image-si-featured.jpg
901 ms
1_deforestation-free-supply-chain-homepage.jpg
496 ms
starbucks-global-coffee-alliance-banner.jpg
486 ms
Nestle-NZFN-banner.jpg
514 ms
coffee_farming_lady.jpg
525 ms
KIT_KAT_LIGHT_homepage_banner.jpg
536 ms
Homepage%20banner-GRgen.jpg
561 ms
carousel--blue-left.svg
918 ms
carousel--blue-right.svg
675 ms
icon-external.svg
1041 ms
report-homepage-box-sml.jpg
710 ms
impact-areas-box-homepage-new.png
747 ms
contact-us-box-homepage.png
788 ms
homepage-jobs.jpg
821 ms
arrow-right--white.svg
1185 ms
www.nestle.co.nz
834 ms
Nestle_Text-Book.woff
1347 ms
Nestle_Text-Light.woff
1306 ms
Nestle_Text-Bold.woff
1409 ms
NestleBrush-Regular.woff
1522 ms
nestle.co.nz 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
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.nz 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
Page has valid source maps
nestle.co.nz 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
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 doesn't use 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.nz 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.nz 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.nz
Open Graph description is not detected on the main page of Nestle. 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: