sayweee.com website review

About 917 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.

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

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

8 third-party services load with your homepage (weeecdn.com, Google CDN and Google Tag Manager and others), adding 2.9 MB and 1.6 s of main-thread time.

17 images could be 524 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

weeecdn.com costs a phone 935 ms of main-thread work and 992 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.

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

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

Google CDN costs a phone 334 ms of main-thread work and 734 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.

weeecdn.net costs a phone 6 ms of main-thread work and 721 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.

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

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

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

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

Your largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “weee carousel banner component 0 image”.

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

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

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

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

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

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

Your homepage downloads 3.6 MB in 162 requests on a phone: scripts 2.0 MB (65), images 860 KiB (28) and other files 389 KiB (52). Under 2 MB keeps phones on slow connections fast.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

ARIA commands must have an accessible name: 18 elements on the page fail this check, rated serious by axe-core.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (6 elements).

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

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

The homepage links to 101 pages on sayweee.com and 14 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.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.weee.com/en, https://www.weee.com/en/promotion/top-x/chart, https://www.weee.com/about/privacy-policy, https://www.weee.com/about/terms-of-service and https://www.weee.com/promotion/collection/IDwkaaft all use the title “Weee! | America’s largest online Asian supermarket”, 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://www.weee.com/en/cms/page/activity/tzXe5h0v has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.weee.com/en/category/sale and https://www.weee.com/category/sale use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.weee.com/about/privacy-policy, whose canonical is https://www.weee.com/en/about/privacy-policy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.weee.com/en/promotion/top-x/chart, https://www.weee.com/mgp/download-app, https://www.weee.com/company/ads, https://www.weee.com/company/home, https://www.weee.com/about/privacy-policy and https://www.weee.com/about/terms-of-service and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.weee.com/en/category/sale, https://www.weee.com/en/promotion/top-x/chart, https://www.weee.com/category/sale, https://www.weee.com/en/social and https://www.weee.com/company/press-and-media 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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17540290&Ver=2&mid=c2437657-9668-4e93-8fbe-92d19cf31ca0&bo=1&sid=8587c7f0d52511f19d923b79a188a1bd&vid=8587f4c0d52511f1b65cc57666b2ae3f&vids=1&msclkid=N&pi=918639831&lg.

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://www.weee.com' has been blocked…”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 437 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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 48 cookies (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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.