yuehwa.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Privy and others), adding 1.3 MB and 1.3 s of main-thread time.

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

Google Tag Manager costs a phone 422 ms of main-thread work and 438 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.

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

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

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

About 58 KiB of CSS is downloaded but never applied on this page.

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

10 KiB could be saved by minifying JavaScript.

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 27.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

The layout shifts by 0.15 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 6.5 MB in 381 requests on a phone: images 3.6 MB (82), scripts 1.6 MB (106) and other files 926 KiB (170). Under 2 MB keeps phones on slow connections fast.

18 images are downloaded at several times the size a phone draws them, for example YueHwa_202402_Web_5___Banner_c46f9125-386d-4e53-9481-63e9c95 at 1,280 px wide, shown at 370 px. Resized copies would save about 534 KiB.

1 image (121 KiB) is 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.

2 images further down the page (198 KiB) 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 1.83 g of CO₂e: 220.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

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

Some list items are not inside a list.

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

<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

14 images have no alt text, which hurts accessibility and image search.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

The page declares lang=“{{ shop.loc…”, which is not a usable language code, so screen readers and translation tools guess.

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

Your title is 82 characters, so Google will cut it off around 60: “Hong Kong Souvenir Shop | Buy Premium Gifts Online - Yue Hwa | Yue Hwa Online Shop”.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

1 link has no real href, so search engines can't follow it.

The homepage links to 370 pages on yuehwa.com and 17 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.

https://yuehwa.com/collections/ladies_ladies-wear, https://yuehwa.com/collections/ladies_ladies-wear/Traditional-Silk-Wear, https://yuehwa.com/collections/ladies_ladies-wear/Ladies'-Scarves-&-Shawls, https://yuehwa.com/collections/ladies_ladies-wear/Qi-Pao and https://yuehwa.com/collections/ladies_ladies-wear/Ladies'-Chinese-Clothing all use the title “Ladies' Wear | Yue Hwa Online Shop”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://yuehwa.com/collections/whats-new, https://yuehwa.com/pages/online-exclusive and https://yuehwa.com/collections/cypherhood have no meta description, so Google writes the search snippet from whatever text it finds.

https://yuehwa.com/collections/ladies_ladies-wear, https://yuehwa.com/collections/ladies_ladies-wear/Traditional-Silk-Wear, https://yuehwa.com/collections/ladies_ladies-wear/Ladies'-Scarves-&-Shawls, https://yuehwa.com/collections/ladies_ladies-wear/Qi-Pao, https://yuehwa.com/collections/ladies_ladies-wear/Ladies'-Chinese-Clothing and https://yuehwa.com/collections/ladies_ladies-underwear-pyjamas and 4 others use the same meta description. A description written for each page earns more clicks.

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

43 of 82 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.

2 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

12 images are served at too low a resolution for sharp phone screens.

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

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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