Programmable

Website review, no card needed

tupperware.co.il logo

tupperware.co.il website review

Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 82 checks

This review found 29 issues worth fixing on tupperware.co.il, 9 of them high impact, across 82 checks. The most urgent: main-thread work: 7.5 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

81B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.6 s1.2 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
133 ms113 msMay 16Oct 31129 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026115 ms
May 23, 2026118 ms
May 30, 2026121 ms
Jun 6, 2026122 ms
Jun 13, 2026125 ms
Jun 20, 2026127 ms
Jun 27, 2026128 ms
Jul 4, 2026130 ms
Jul 11, 2026131 ms
Jul 18, 2026130 ms
Jul 25, 2026130 ms
Aug 1, 2026129 ms
Aug 8, 2026129 ms
Aug 15, 2026129 ms
Aug 22, 2026127 ms
Aug 29, 2026121 ms
Sep 5, 2026126 ms
Sep 12, 2026129 ms
Sep 19, 2026129 ms
Sep 26, 2026131 ms
Oct 3, 2026130 ms
Oct 10, 2026128 ms
Oct 17, 2026129 ms
Oct 24, 2026129 ms
Oct 31, 2026129 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

tupperware.co.il (opens in a new tab)
Full-page screenshot of tupperware.co.il (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tupperware.co.il at 1.1 s1.1 s
  2. tupperware.co.il at 2.1 s2.1 s
  3. tupperware.co.il at 3.2 s3.2 s
  4. tupperware.co.il at 4.3 s4.3 s
  5. tupperware.co.il at 5.4 s5.4 s
  6. tupperware.co.il at 6.4 s6.4 s
  7. tupperware.co.il at 7.5 s7.5 s
  8. tupperware.co.il at 8.6 s8.6 s

Speed

8 to fix67

  • Main-thread work: 7.5 s

    A phone's processor spends 7.5 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Clarity and Yotpo and others), adding 691 KiB and 713 ms of main-thread time.

  • Render-blocking requests

    750 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Reduce unused JavaScript

    330 ms · 69 KiB

    About 69 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 330 ms faster on a phone.

  • Use efficient cache lifetimes

    370 KiB

    28 files are served with short cache lifetimes, so returning visitors download them again (370 KiB).

  • 2,787 HTML elements

    The page has 2,787 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Shopify adds 214 ms

    214 ms

    Shopify costs a phone 214 ms of main-thread work and 298 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused CSS

    150 ms · 77 KiB

    About 77 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    195 KiB

    9 images could be 195 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 7 long tasks on the main thread

    7 long tasks block the main thread while loading, the longest for 149 ms. During a long task the page ignores taps.

  • Minify JavaScript

    30 ms · 12 KiB

    12 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed

  • Server response: 8 ms

    8 ms

    Your server sent the HTML in 8 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100

  • Largest Contentful Paint: 7.0 s

    7.0 s

    Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 7.8 s

    7.8 s

    Visually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 9.9 s

    9.9 s

    The page becomes fully interactive after 9.9 s. Good is under 3.8 s.

  • Tap response (INP) got 11% slower for real visitors

    +11%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 115 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed

  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

    Real visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 136 ms

    136 ms

    Real visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 670 ms

    670 ms

    Real visitors wait 670 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 163 ms

    163 ms

    Scripts block the page for only 163 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.011

    0.011

    The layout barely moves while loading (CLS 0.011, good is under 0.1).

Images and page weight

1 to fix85

  • Page weight: 2.9 MB in 330 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 330 requests on a phone: other files 1.1 MB (211), images 1.0 MB (42) and scripts 675 KiB (63). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.83 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8493

  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (2 elements).

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed

  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9295

  • Meta description is long (222 characters)

    Your meta description is 222 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 142 internal links, 7 external

    The homepage links to 142 pages on tupperware.co.il and 7 external pages.

7 checks passed

  • One H1 headline

    Your main headline reads: “Tupperware Israel”.

  • Title: 31 characters

    Your title is a healthy 31 characters: “Tupperware Israel טאפרוור ישראל”.

  • Canonical URL set

    The canonical URL is https://tupperware.co.il/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://tupperware.co.il/sitemap.xml.

AI search readiness

100
4 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (101 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://tupperware.co.il/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix85

  • 15 pages without a meta description

    https://tupperware.co.il/collections/40-shopping-il-2026, https://tupperware.co.il/collections/30-shopping-il-2026, https://tupperware.co.il/collections/20-shopping-il-2026, https://tupperware.co.il/collections/10-shopping-il-2026, https://tupperware.co.il/collections/%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D-%D7%97%D7%93%D7%A9%D7%99%D7%9D and https://tupperware.co.il/collections/%D7%90%D7%97%D7%A1%D7%95%D7%9F-%D7%91%D7%9E%D7%96%D7%95%D7%95%D7%94 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 links to non-canonical URLs

    Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://tupperware.co.il/collections/%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D-%D7%97%D7%93%D7%A9%D7%99%D7%9D, whose canonical is https://tupperware.co.il/collections/%d7%9e%d7%95%d7%a6%d7%a8%d7%99%d7%9d-%d7%97%d7%93%d7%a9%d7%99%d7%9d. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://tupperware.co.il/collections/40-shopping-il-2026, https://tupperware.co.il/collections/30-shopping-il-2026, https://tupperware.co.il/collections/20-shopping-il-2026, https://tupperware.co.il/collections/10-shopping-il-2026, https://tupperware.co.il/collections/%D7%9E%D7%95%D7%A6%D7%A8%D7%99%D7%9D-%D7%97%D7%93%D7%A9%D7%99%D7%9D and https://tupperware.co.il/collections/%D7%90%D7%97%D7%A1%D7%95%D7%9F-%D7%91%D7%9E%D7%96%D7%95%D7%95%D7%94 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages with very little text

    https://tupperware.co.il/collections/10-shopping-il-2026, https://tupperware.co.il/collections/%D7%90%D7%97%D7%A1%D7%95%D7%9F-%D7%91%D7%9E%D7%A7%D7%A4%D7%99%D7%90, https://tupperware.co.il/collections/%D7%A7%D7%A2%D7%A8%D7%95%D7%AA-%D7%94%D7%AA%D7%A4%D7%97%D7%94, https://tupperware.co.il/collections/%D7%9B%D7%9C%D7%99%D7%9D-%D7%95%D7%90%D7%91%D7%99%D7%96%D7%A8%D7%99%D7%9D-%D7%9C%D7%9E%D7%98%D7%91%D7%97, https://tupperware.co.il/collections/%D7%90%D7%91%D7%99%D7%96%D7%A8%D7%99-%D7%90%D7%A4%D7%99%D7%99%D7%94 and https://tupperware.co.il/collections/%D7%9E%D7%99%D7%A7%D7%A8%D7%95%D7%A4%D7%99%D7%99%D7%91%D7%A8 and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 68 found) and read each the way a search engine does.

4 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687

  • 11 small tap targets

    11 of 53 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-widget-assets.yotpo.com/ReviewsCarousel/CzeRYNxMqlpnKlWs6oH7O9XlDRIVvLX9w5kx3E…”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50

  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 151 words

    The homepage has only about 151 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed

  • 11 short forms

    11 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 36 other companies contacted

    Loading the homepage contacts 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at tupperware.co.il, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Sense Rtl · Yotpo Product Reviews · Ta Labels Badges · Appikon Back In Stock · flashyapp.com · adscale.com · goaffpro.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on tupperware.co.il, including 11 speed issues, 1 SEO issue and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25