evisu.com.hk website review

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

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

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

40 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

8 third-party services load with your homepage (Google CDN, Shopify and Google Tag Manager and others), adding 1.4 MB and 962 ms of main-thread time.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 7.1 MB in 288 requests on a phone: images 4.0 MB (65), scripts 1.4 MB (72) and other files 1.1 MB (97). Under 2 MB keeps phones on slow connections fast.

0209_Evisu_Kizzu_Tiger_Homepage_bottom_banner_Moblie_750x108 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

8 images (743 KiB) 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.

6 images are downloaded at several times the size a phone draws them, for example 2EAKZK6JE4006RXDN-INDM_w2_443df43f-d118-4622-87d3-60bf4ee15a at 533 px wide, shown at 132 px. Resized copies would save about 150 KiB.

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

1 dropdown has no label.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

14 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.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your <h1> is empty.

The homepage links to 282 pages on evisu.com.hk and 5 external pages.

There is no https://evisu.com.hk/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.

https://evisu.com.hk/collections/all, https://evisu.com.hk/pages/double-11-carnival, https://evisu.com.hk/collections/2024-spring-collection and https://evisu.com.hk/collections/men have no meta description, so Google writes the search snippet from whatever text it finds.

https://evisu.com.hk/collections/all, https://evisu.com.hk/pages/double-11-carnival, https://evisu.com.hk/collections/2024-spring-collection and https://evisu.com.hk/collections/men have no <h1> headline, so visitors and search engines get no clear main topic.

https://evisu.com.hk/collections/all and https://evisu.com.hk/collections/men 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 104 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to fetch”.

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

Before a visitor clicks anything, the page loads Criteo, 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 19 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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.