6.2 sec in total
488 ms
5.5 sec
280 ms
Welcome to tupperware.co.nz homepage info - get ready to check Tupperware best content for New Zealand right away, or after learning these important things about tupperware.co.nz
An important message to our valued Tupperware customers in New Zealand: “We will be back!” Thank you for your support over the last (almost) 50 years of purchasing Tupperware right across New Zealand....
Visit tupperware.co.nzWe analyzed Tupperware.co.nz page load time and found that the first response time was 488 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tupperware.co.nz performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value11.1 s
0/100
25%
Value17.6 s
0/100
10%
Value13,810 ms
0/100
30%
Value0.001
100/100
15%
Value23.0 s
1/100
10%
488 ms
2069 ms
93 ms
1180 ms
612 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 42% of them (22 requests) were addressed to the original Tupperware.co.nz, 10% (5 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Tupperware.co.nz.
Page size can be reduced by 173.8 kB (15%)
1.2 MB
982.7 kB
In fact, the total size of Tupperware.co.nz main page is 1.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 749.4 kB which makes up the majority of the site volume.
Potential reduce by 133.9 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 133.9 kB or 84% 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. Tupperware images are well optimized though.
Potential reduce by 820 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 39.0 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. Tupperware.co.nz needs all CSS files to be minified and compressed as it can save up to 39.0 kB or 20% of the original size.
Number of requests can be reduced by 31 (70%)
44
13
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tupperware. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
tupperware.co.nz
488 ms
tupperware.co.nz
2069 ms
gtm.js
93 ms
head-0c93fc15f212a11f270c483813aeb08a00de5907.css
1180 ms
css
612 ms
font-awesome.min.css
862 ms
style.css
1182 ms
all.css
985 ms
v4-shims.css
1041 ms
smartslider.min.css
1180 ms
jquery-3.6.0.min.js
876 ms
4aadb5ed845c0e00c1f6b673c5460e39-v8f28e3d12883d5291cc9fb60bb1f481b214bfa24.js
1179 ms
jquery.cookie.min.js
1179 ms
head-1b01ef5d588fcfceded40f478adef32979939245.js
1209 ms
select2.min.js
927 ms
6ead5cd1b97c5aa66ed3a3095f26af0b-v7396300ecc720330f10e093ff22f9c176e35f64b.js
1239 ms
head-14848ae3726f313e6593ed43f1fb49082df72275.js
1253 ms
n2.min.js
1468 ms
smartslider-frontend.min.js
1468 ms
ss-simple.min.js
1271 ms
smartslider-backgroundanimation.min.js
1272 ms
fbevents.js
552 ms
conversion_async.js
588 ms
js
179 ms
identity.js
23 ms
1316505892018586
131 ms
36 ms
110 ms
245 ms
193 ms
50 ms
analytics.js
54 ms
cropped-logotw.png
225 ms
thank-you-4.png
1204 ms
Shop-Quality-Sustainable-Products_Plant-Square.png
1202 ms
instagram-new-1.png
223 ms
pinterest-circled-1.png
401 ms
facebook-circled.png
400 ms
ec.js
20 ms
pxiEyp8kv8JHgFVrJJfedHFHGPc.woff
42 ms
pxiByp8kv8JHgFVrLGT9Z1xlE92JQEk.woff
64 ms
pxiByp8kv8JHgFVrLDz8Z1xlE92JQEk.woff
75 ms
pxiByp8kv8JHgFVrLEj6Z1xlE92JQEk.woff
75 ms
pxiByp8kv8JHgFVrLCz7Z1xlE92JQEk.woff
75 ms
diffuser.js
83 ms
collect
38 ms
collect
73 ms
prism.app-us1.com
153 ms
ga-audiences
24 ms
wp-controller.js
49 ms
woocommerce-smallscreen.css
200 ms
woocommerce-mobile.min.css
200 ms
tupperware.co.nz 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
Links do not have a discernible name
tupperware.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
tupperware.co.nz 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
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 Tupperware.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 Tupperware.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.
tupperware.co.nz
Open Graph data is detected on the main page of Tupperware. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: