mabelle.com website review

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

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

About 896 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.7 s faster on a phone.

About 770 KiB 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.

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

67 images could be 8.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 third-party services load with your homepage (Google Tag Manager, Google Analytics and retchat.com and others), adding 5.5 MB and 725 ms of main-thread time.

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

Google Tag Manager costs a phone 677 ms of main-thread work and 774 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 HTML itself could arrive about 600 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

Reduce initial server response time. Google estimates savings of 576 ms on a phone.

fanshare.hk costs a phone 0 ms of main-thread work and 4.7 MB 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 2.9 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Your server takes 676 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

16 KiB could be saved by minifying CSS.

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

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.

5 KiB could be saved by minifying JavaScript.

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.

For real visitors the layout shifts by 0.35 (75th percentile). Good is under 0.1.

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

Your largest element takes 42.9 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

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

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

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

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

Your homepage downloads 20.0 MB in 227 requests on a phone: images 15.4 MB (137), fonts 2.0 MB (45) and scripts 1.3 MB (14). Under 2 MB keeps phones on slow connections fast.

23 images are downloaded at several times the size a phone draws them, for example 20250513101711713_mobile.jpg at 1,240 px wide, shown at 390 px. Resized copies would save about 3.1 MB.

3 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.

40 images (10.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.

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

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 31 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 viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 15 characters: “MaBelle 天然鑽飾專門店”. Between 30 and 65 characters leaves room to say what you do and for whom.

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.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 261 pages on mabelle.com and 63 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://www.mabelle.com/hk/chi/new100, https://www.mabelle.com/hk/chi/jewellery/earrings, https://www.mabelle.com/hk/chi/jewellery/cute-earrings, https://www.mabelle.com/hk/chi/jewellery/necklace-pendant, https://www.mabelle.com/hk/chi/online-shopping/info and https://www.mabelle.com/hk/chi/information/store-location and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mabelle.com/hk/chi/jewellery/necklace-pendant, https://www.mabelle.com/hk/chi/online-shopping/info and https://www.mabelle.com/hk/chi/jewellery/ring took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fanshare.hk/CC_upload/banner/20230809/Video-Banner.css' from origin 'https://www.m…”.

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

Large scripts ship without source maps.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage has only about 113 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

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

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