Website review, no card needed

moiselle-hk.com logo

moiselle-hk.com website review

Visit site (opens in a new tab)Reviewed 21 October 202629 issues · 64 checks

This review found 29 issues worth fixing on moiselle-hk.com, 7 of them high impact, across 64 checks. The most urgent: page weight: 53.1 MB in 458 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.8 s1.2 sMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.8 s
May 16, 20261.9 s
May 23, 20262.1 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.6 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20261.9 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.9 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.8 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
143 ms76 msMay 2Oct 17111 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026104 ms
May 9, 2026106 ms
May 16, 2026113 ms
May 23, 2026117 ms
May 30, 2026117 ms
Jun 6, 2026120 ms
Jun 13, 2026135 ms
Jun 20, 2026114 ms
Jun 27, 2026111 ms
Jul 4, 2026106 ms
Jul 18, 202689 ms
Jul 25, 202684 ms
Aug 1, 202687 ms
Aug 8, 2026102 ms
Aug 15, 2026105 ms
Aug 22, 2026103 ms
Aug 29, 2026102 ms
Sep 12, 2026117 ms
Oct 17, 2026111 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of moiselle-hk.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. moiselle-hk.com at 1.2 s1.2 s
  2. moiselle-hk.com at 2.5 s2.5 s
  3. moiselle-hk.com at 3.7 s3.7 s
  4. moiselle-hk.com at 5.0 s5.0 s
  5. moiselle-hk.com at 6.2 s6.2 s
  6. moiselle-hk.com at 7.5 s7.5 s
  7. moiselle-hk.com at 8.7 s8.7 s
  8. moiselle-hk.com at 10.0 s10.0 s

Speed

8 to fix65
  • Main-thread work: 7.9 s

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

  • 3,498 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Azure Web Services and others), adding 29.3 MB and 1.1 s of main-thread time.

  • Shopify adds 414 ms

    414 ms

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

  • Improve image delivery

    2.7 MB

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

  • Mobile performance score: 65

    65/100

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

  • Reduce unused JavaScript

    948 KiB

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

  • Render-blocking requests

    850 ms

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

  • 18 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 44 KiB

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

  • Font display

    150 ms

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

  • Use efficient cache lifetimes

    101 KiB

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

  • Legacy JavaScript

    13 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 15 ms

    15 ms

    Your server sent the HTML in 15 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Speed Index: 31.1 s

    31.1 s

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

  • Time to Interactive: 78.5 s

    78.5 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 3.6 s

    3.6 s

    Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By using this website, you agree to our Cookies Policy. We …”.

  • Total Blocking Time: 398 ms

    398 ms

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

  • Tap response (INP) held steady for real visitors

    +9%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 111 ms

    111 ms

    Real visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 516 ms

    516 ms

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

  • Largest content (LCP) got 18% faster for real visitors

    -18%

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

  • Cumulative Layout Shift: 0.07

    0.07

    The layout barely moves while loading (CLS 0.07, good is under 0.1).

Images and page weight

1 to fix0
  • Page weight: 53.1 MB in 458 requests

    53.1 MB

    Your homepage downloads 53.1 MB in 458 requests on a phone: media 26.7 MB (5), images 23.1 MB (158) and scripts 1.9 MB (95). Under 2 MB keeps phones on slow connections fast.

  • About 15.0 g of CO₂ per visit

    15.05 g

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

Accessibility

6 to fix76
  • 39 images without alt text

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

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 7 links without text

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

SEO

6 to fixGoogle 8577
  • 21 H1 headlines

    There are 21 <h1> headlines (“SIGNATURE TWEED JACKETS”, “CLASSIC DRESSES” and “Lancaster Paris”). One clear main headline is easier for people and search engines.

  • Meta description is long (202 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//moiselle-hk.com/cdn/shop/files/social.png?v=164921899…”.

  • No XML sitemap

    No XML sitemap at https://moiselle-hk.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at moiselle-hk.com/robots.txt, the first file search crawlers ask for.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 108 internal links, 19 external

    The homepage links to 108 pages on moiselle-hk.com and 19 external pages.

3 checks passed
  • Title: 50 characters

    Your title is a healthy 50 characters: “MOISELLE E-Flagship | Asian's Women Designer Label”.

  • Canonical URL set

    The canonical URL is https://moiselle-hk.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

100
1 checks passed
  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

2 to fixGoogle 7388
  • 2 third-party cookies

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

  • 12 console errors

    12 errors were logged to the browser console during Google's test (“Failed to load resource: net::ERR_BLOCKED_BY_CLIENT”).

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88
  • Thin social proof

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No risk reducer

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

  • About 1,063 words of copy

    The homepage carries about 1,063 words of visible text.

3 checks passed
  • 15 calls to action

    The homepage has 15 calls to action, for example “SHOP”, “SHOP NOW” and “Join”.

  • 30 short forms

    30 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at moiselle-hk.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on moiselle-hk.com, including 13 speed issues, 6 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25