moltonbrown.co.jp website review

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

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

wovn.io costs a phone 1.4 s of main-thread work and 223 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

8 third-party services load with your homepage (wovn.io, Google Tag Manager and cloudfront.net and others), adding 20.6 MB and 3.5 s of main-thread time.

visumo.jp costs a phone 118 ms of main-thread work and 17.8 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.

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

Google Tag Manager costs a phone 887 ms of main-thread work and 1,005 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.

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

cloudfront.net costs a phone 469 ms of main-thread work and 1,000 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.

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

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

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

18 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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

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

Your homepage downloads 28.6 MB in 342 requests on a phone: media 17.0 MB (14), images 7.3 MB (81) and scripts 3.1 MB (124). Under 2 MB keeps phones on slow connections fast.

15 images are downloaded at several times the size a phone draws them, for example mbn-07.jpg at 5,906 px wide, shown at 294 px. Resized copies would save about 5.2 MB.

2 images weigh 3.5 MB together. On a phone connection a single image that size takes seconds.

19 images further down the page (5.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

7 images (749 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.

By the Sustainable Web Design model, a visit to your homepage emits about 8.12 g of CO₂e: 974.2 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 values: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

All page content should be contained by landmarks: 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.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

82 links have no real href, so search engines can't follow them.

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

There are 6 <h1> headlines (“MOLTON BROWN”, “The Festive Collection” and “カテゴリーから選ぶ”). One clear main headline is easier for people and search engines.

30 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 477 pages on moltonbrown.co.jp and 13 external pages.

A phone browser shows 4,792 words, but the HTML your server sends has only 382. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

There is no https://www.moltonbrown.co.jp/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://www.moltonbrown.co.jp/pages/rewards_club, https://www.moltonbrown.co.jp/pages/holiday2026 and https://www.moltonbrown.co.jp/pages/engraving have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.moltonbrown.co.jp/pages/rewards_club, https://www.moltonbrown.co.jp/pages/shoplist, https://www.moltonbrown.co.jp/pages/holiday2026, https://www.moltonbrown.co.jp/collections/gifts, https://www.moltonbrown.co.jp/products/mbg24017 and https://www.moltonbrown.co.jp/pages/engraving and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.moltonbrown.co.jp/pages/rewards_club, https://www.moltonbrown.co.jp/pages/shoplist, https://www.moltonbrown.co.jp/pages/holiday2026, https://www.moltonbrown.co.jp/collections/gifts, https://www.moltonbrown.co.jp/products/mbg24017 and https://www.moltonbrown.co.jp/pages/engraving and 3 others 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 171 found) and read each the way a search engine does.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

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 4,792 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 28 cookies, 2 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 56 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.