mellerio.jp website review

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

7 images could be 605 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

6 third-party services load with your homepage (Adobe TypeKit, Shopify and booxi.com and others), adding 3.3 MB and 61 ms of main-thread time.

Adobe TypeKit costs a phone 32 ms of main-thread work and 3.2 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.

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

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

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

9 KiB could be saved by minifying JavaScript.

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.

4 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cabinet de Curiosités”.

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

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

Your homepage downloads 5.6 MB in 222 requests on a phone: other files 3.9 MB (115), images 1.2 MB (25) and scripts 376 KiB (48). Under 2 MB keeps phones on slow connections fast.

4 images (290 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.

1 image further down the page (57 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

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

There are 3 <h1> headlines (“”, “Cabinet de Curiosités” and “LES MUSES”). One clear main headline is easier for people and search engines.

The homepage links to 174 pages on mellerio.jp and 3 external pages.

There is no https://mellerio.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://mellerio.jp/collections/all and https://mellerio.jp/collections/stella have no meta description, so Google writes the search snippet from whatever text it finds.

https://mellerio.jp/collections/muse, https://mellerio.jp/collections/pinta, https://mellerio.jp/collections/maria and https://mellerio.jp/collections/mini-giardino use the same meta description. A description written for each page earns more clicks.

https://mellerio.jp/collections/fine-jewelry-necklaces, https://mellerio.jp/collections/fine-jewelry-bracelets, https://mellerio.jp/collections/fine-jewelry-earrings, https://mellerio.jp/collections/stella, https://mellerio.jp/collections/riviera and https://mellerio.jp/collections/pinta and 2 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 68 found) and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.booxi.com/api/style_v2.css?ver=1-32-0' from origin 'https://mellerio.jp' has b…”.

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

Social proof on the homepage: 2 trust badges. 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.

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

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, 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 10 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.