wanzar.com.my website review

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

8 third-party services load with your homepage (Shopify, Facebook and TikTok and others), adding 1.4 MB and 635 ms of main-thread time.

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

About 648 KiB of JavaScript is downloaded but never used on this page.

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

Shopify costs a phone 242 ms of main-thread work and 744 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.

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

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

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

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

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

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

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

13 KiB could be saved by minifying CSS.

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.

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.

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

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

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

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

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FREE SHIPPING MY - RM200 | SG - RM600”. Most of its time is element render delay (1.5 s).

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

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

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

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

Your homepage downloads 9.4 MB in 235 requests on a phone: media 6.4 MB (1), scripts 1.5 MB (65) and other files 984 KiB (138). Under 2 MB keeps phones on slow connections fast.

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

There are 12 <h1> headlines (“Printed Luxe 2026”, “The Brides 2026” and “BRIDES”). One clear main headline is easier for people and search engines.

The homepage links to 246 pages on wanzar.com.my and 9 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://wanzar.com.my/collections/printed-luxe-2026, https://wanzar.com.my/collections/printed-luxe-2026-women, https://wanzar.com.my/collections/printed-luxe-2026-kids, https://wanzar.com.my/collections/the-brides-x, https://wanzar.com.my/collections/the-brides-x-brides and https://wanzar.com.my/collections/the-brides-x-grooms-copy and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://wanzar.com.my/collections/printed-luxe-2026, https://wanzar.com.my/collections/printed-luxe-2026-women, https://wanzar.com.my/collections/printed-luxe-2026-kids, https://wanzar.com.my/collections/the-brides-x, https://wanzar.com.my/collections/the-brides-x-brides and https://wanzar.com.my/collections/the-brides-x-grooms-copy and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://wanzar.com.my/collections/the-brides-x, https://wanzar.com.my/collections/heels-9-0, https://wanzar.com.my/collections/the-brides-x-brides-copy, https://wanzar.com.my/collections/the-brides-x-baju-melayu and https://wanzar.com.my/collections/the-brides-x-baju-melayu-copy took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://wanzar.com.my/.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 5 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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