tupperware.co.kr website review

95 images could be 27.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 51.5 s faster on a phone.

212 files are served with short cache lifetimes, so returning visitors download them again (9.9 MB).

About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

Vimeo costs a phone 1.3 s of main-thread work and 27.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.5 s).

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

Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Vimeo, Facebook and TikTok and others), adding 28.4 MB and 1.8 s of main-thread time.

164 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

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

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

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

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

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

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

Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

The first text or image appears after 2.9 s on a phone. Good is under 1.8 s.

37 images have no width and height attributes, so the layout jumps as each one loads.

The layout shifts by 0.127 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 82.7 MB in 368 requests on a phone: images 49.2 MB (182), other files 24.8 MB (117) and fonts 4.4 MB (7). Under 2 MB keeps phones on slow connections fast.

25 images weigh 34.8 MB together. On a phone connection a single image that size takes seconds.

29 images are downloaded at several times the size a phone draws them, for example f642237807ac1562b2354abc7ae7ffb1.gif at 1,200 px wide, shown at 390 px. Resized copies would save about 15.6 MB.

40 images (40.0 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

13 images further down the page (11.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

2 buttons have no accessible name, so screen readers announce just “button”.

34 tap targets are too small or too close together to hit reliably with a finger.

22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

6 frames have no title, so screen-reader users cannot tell what they contain.

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

7 visible links have no text or label, so screen readers cannot say where they go.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

Your title is only 29 characters: “타파웨어 공식 온라인 스토어 | 라이프스타일 키친웨어”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your canonical URL points to tupperwarekr.cafe24.com, not tupperware.co.kr, so Google may credit that host instead.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://tupperware.co.kr/sitemap.xml, so Google discovers your pages only by following links.

Your <h1> is empty.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 225 pages on tupperware.co.kr and 7 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://tupperware.co.kr/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to https://tupperware.co.kr/%7B and https://tupperware.co.kr/product/detail.html, which answer with an error. Visitors hit a dead end and search engines drop them.

/, https://tupperware.co.kr/shopinfo/brand.html, https://tupperware.co.kr/product/recent_view_product.html, https://tupperware.co.kr/member/agreement.html and https://tupperware.co.kr/member/privacy.html all use the title “타파웨어 공식 온라인 스토어 | 라이프스타일 키친웨어”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://tupperware.co.kr/shopinfo/brand.html, https://tupperware.co.kr/product/recent_view_product.html, https://tupperware.co.kr/member/agreement.html and https://tupperware.co.kr/member/privacy.html use the same meta description. A description written for each page earns more clicks.

https://tupperware.co.kr/product/list.html, https://tupperware.co.kr/board/notice/1, https://tupperware.co.kr/product/recent_view_product.html and https://tupperware.co.kr/board/free/list.html 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.

https://tupperware.co.kr/shopinfo/brand.html, https://tupperware.co.kr/board/notice/1, https://tupperware.co.kr/board/reviews/4, https://tupperware.co.kr/board/%EC%9E%90%EC%A3%BC-%EB%AC%BB%EB%8A%94-%EC%A7%88%EB%AC%B8/3, https://tupperware.co.kr/board/qa/6 and https://tupperware.co.kr/product/recent_view_product.html and 1 other took over 3 s to send their HTML from our server.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_UNKNOWN_URL_SCHEME”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

The homepage carries about 270 words of visible text.

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

Before a visitor clicks anything, the page loads Meta Pixel and TikTok Pixel (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.

Opening the homepage sets 24 cookies, 3 of them by other companies (measured from a US location before any click).

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.

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