Tools & Wizards About Us
tupperware.co.nz screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

tupperware.co.nz

TupperwareNZ – Tupperware Australia

Page Load Speed

21.6 sec in total

First Response

307 ms

Resources Loaded

21.1 sec

Page Rendered

137 ms

tupperware.co.nz screenshot

About Website

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.nz

Key Findings

We analyzed Tupperware.co.nz page load time and found that the first response time was 307 ms and then it took 21.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

tupperware.co.nz performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value3,380 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value31.8 s

0/100

10%

Network Requests Diagram

tupperwarenz

307 ms

events.js

101 ms

hotjar-2472223.js

107 ms

preloads.js

56 ms

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

45 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Tupperware.co.nz, 4% (2 requests) were made to Cdn.shopify.com and 4% (2 requests) were made to Sdk.loyaltylion.net. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Cdn.polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 224.0 kB (18%)

Content Size

1.2 MB

After Optimization

998.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 839.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 207.2 kB

  • Original 268.5 kB
  • After minification 251.0 kB
  • After compression 61.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 207.2 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 33.5 kB
  • After minification 33.5 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. Tupperware images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 16.7 kB

  • Original 839.0 kB
  • After minification 839.0 kB
  • After compression 822.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 161 B

  • Original 81.2 kB
  • After minification 81.2 kB
  • After compression 81.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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (88%)

Requests Now

49

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 49 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 40 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tupperwarenz

tupperwarenz

307 ms

events.js

events.js

101 ms

hotjar-2472223.js

hotjar-2472223.js

107 ms

preloads.js

preloads.js

56 ms

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

45 ms

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

68 ms

theme.scss.css

theme.scss.css

70 ms

vendor.scss.css

vendor.scss.css

50 ms

custom-styles.min.css

custom-styles.min.css

56 ms

option_selection-86cdd286ddf3be7e25d68b9fc5965d7798a3ff6228ff79af67b3f4e41d6a34be.js

option_selection-86cdd286ddf3be7e25d68b9fc5965d7798a3ff6228ff79af67b3f4e41d6a34be.js

68 ms

polyfill.min.js

polyfill.min.js

19619 ms

libs.min.js

libs.min.js

83 ms

lazyload-libraries.min.js

lazyload-libraries.min.js

81 ms

vendor.min.js

vendor.min.js

89 ms

theme.js

theme.js

90 ms

custom.js

custom.js

92 ms

bc-sf-filter.scss.css

bc-sf-filter.scss.css

89 ms

e6R9T9rkI1t5yK0hoZoLZUYJvMVUiwjYqNG5Nf4C

e6R9T9rkI1t5yK0hoZoLZUYJvMVUiwjYqNG5Nf4C

65 ms

globo.formbuilder.index.js

globo.formbuilder.index.js

54 ms

bc-sf-filter-lib.js

bc-sf-filter-lib.js

228 ms

bc-sf-search.js

bc-sf-search.js

222 ms

bc-sf-filter-init.js

bc-sf-filter-init.js

222 ms

css2

css2

34 ms

modules.349061f2d87d84c4c336.js

modules.349061f2d87d84c4c336.js

155 ms

loader.js

loader.js

231 ms

683776f37023db477b35c5147aa3a41b.js

683776f37023db477b35c5147aa3a41b.js

282 ms

trekkie.storefront.99bdfbca815ea24ab1705979a783df6e7810b51d.min.js

trekkie.storefront.99bdfbca815ea24ab1705979a783df6e7810b51d.min.js

134 ms

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

141 ms

shopify-boomerang-1.0.0.min.js

shopify-boomerang-1.0.0.min.js

137 ms

NZ_Web_banner_options_480x480.jpg

NZ_Web_banner_options_480x480.jpg

86 ms

jquery.min.js

jquery.min.js

127 ms

Badge.svg

Badge.svg

81 ms

EarlSans-Regular.woff

EarlSans-Regular.woff

34 ms

EarlSans-Light.woff

EarlSans-Light.woff

82 ms

EarlSans-Bold.woff

EarlSans-Bold.woff

82 ms

tracking.js

tracking.js

32 ms

dynamic-checkout-cart.en.js

dynamic-checkout-cart.en.js

34 ms

reviewsWidget.min.js

reviewsWidget.min.js

73 ms

section-feed.js

section-feed.js

56 ms

skeletopapp.js

skeletopapp.js

89 ms

eventpromotionbar.js

eventpromotionbar.js

63 ms

swym-shopify.js

swym-shopify.js

96 ms

gbvXRmm_kWn-eowECESwag.js

gbvXRmm_kWn-eowECESwag.js

110 ms

blank-script.js

blank-script.js

306 ms

subscription.js

subscription.js

62 ms

lo.js

lo.js

79 ms

smsbump_timer.js

smsbump_timer.js

70 ms

returngo.min.js

returngo.min.js

62 ms

collector.js

collector.js

79 ms

1100l287.js

1100l287.js

391 ms

widget.min.js

widget.min.js

80 ms

lo.legacy.js

lo.legacy.js

45 ms

app.v1.0.368.js

app.v1.0.368.js

140 ms

b675a41e

b675a41e

38 ms

Accessibility Review

tupperware.co.nz accessibility score

89

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tupperware.co.nz best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

tupperware.co.nz SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: