Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

fr.tupperware.ca

Tupperware® Official Site - Produits innovants pour la cuisine et plus encore - Tupperware CA

Page Load Speed

14.8 sec in total

First Response

974 ms

Resources Loaded

12 sec

Page Rendered

1.8 sec

About Website

Click here to check amazing Fr Tupperware content for Canada. Otherwise, check out these important facts you probably never knew about fr.tupperware.ca

Des produits de cuisine innovants à une opportunité commerciale flexible et amusante. Rejoignez-nous, organisez une fête, faites des achats en ligne, trouvez de bonnes recettes et plus encore.

Visit fr.tupperware.ca

Key Findings

We analyzed Fr.tupperware.ca page load time and found that the first response time was 974 ms and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

fr.tupperware.ca performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value22.4 s

0/100

10%

TBT (Total Blocking Time)

Value57,180 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value78.8 s

0/100

10%

Network Requests Diagram

fr.tupperware.ca

974 ms

pws-bar-@css-bundle.min.css

202 ms

header-@css-bundle.min.css

95 ms

lazyload-images-@js-bundle.min.js

124 ms

header-@js-bundle.min.js

123 ms

Our browser made a total of 189 requests to load all elements on the main page. We found that 89% of them (168 requests) were addressed to the original Fr.tupperware.ca, 3% (6 requests) were made to Cdnjs.cloudflare.com and 1% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (8.5 sec) relates to the external source Swymstore-v3free-01.swymrelay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 707.7 kB (23%)

Content Size

3.1 MB

After Optimization

2.4 MB

In fact, the total size of Fr.tupperware.ca main page is 3.1 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. 80% 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. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 588.8 kB

  • Original 724.5 kB
  • After minification 638.5 kB
  • After compression 135.7 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 86.0 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 588.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 4.6 kB

  • Original 1.5 MB
  • After minification 1.5 MB

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. Fr Tupperware images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 109.7 kB

  • Original 796.5 kB
  • After minification 796.5 kB
  • After compression 686.8 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 109.7 kB or 14% of the original size.

CSS Optimization

-11%

Potential reduce by 4.6 kB

  • Original 41.1 kB
  • After minification 41.1 kB
  • After compression 36.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. Fr.tupperware.ca needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (37%)

Requests Now

187

After Optimization

117

The browser has sent 187 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fr 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 36 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

fr.tupperware.ca accessibility score

72

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fr.tupperware.ca best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

fr.tupperware.ca SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fr.tupperware.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Fr.tupperware.ca 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

Open Graph data is detected on the main page of Fr Tupperware. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: