miruto.shop website review

Google Tag Manager costs a phone 1.2 s of main-thread work and 915 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.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, zeals.ai and firebaseapp.com and others), adding 9.6 MB and 1.9 s of main-thread time.

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

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

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

zeals.ai costs a phone 478 ms of main-thread work and 13 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 26 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 190 ms faster on a phone.

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

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

Polyfills for old browsers add 19 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.

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

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

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

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

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

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

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

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

Your homepage downloads 17.8 MB in 276 requests on a phone: images 7.1 MB (111), fonts 5.7 MB (5) and other files 3.0 MB (108). Under 2 MB keeps phones on slow connections fast.

30 images are downloaded at several times the size a phone draws them, for example animation_cat_toilet.png at 1,030 px wide, shown at 109 px. Resized copies would save about 4.1 MB.

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

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

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

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.

1 visible link has no text or label, so screen readers cannot say where it goes.

ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 16 characters: “miruto（ミルト）公式サイト”. 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.

Your <h1> is empty.

The homepage links to 196 pages on miruto.shop and 23 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.miruto.shop/products/water-dispenser-filter and https://www.miruto.shop/products/filter all use the title “専用フィルター(8個入り) 購入ページ | miruto（ミルト）公式サイト 購入ページ | miruto公式”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.miruto.shop/products/toilet-lala has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.miruto.shop/products/water-dispenser-filter and https://www.miruto.shop/products/filter use the same meta description. A description written for each page earns more clicks.

https://www.miruto.shop/pages/about, https://www.miruto.shop/pages/products, https://www.miruto.shop/pages/products-toilet, https://www.miruto.shop/products/toilet-coco, https://www.miruto.shop/products/water-dispenser-filter and https://www.miruto.shop/pages/products-water-dispenser and 6 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 35 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://api.ad-platform.jmty.jp/v1/ev/1?loc=https%3A%2F%2Fwww.miruto.shop%2F&os=iOS&osver=17.5&model=iPhone&browser=Mobile+Safari&tv=1.0.14&evType=pv&aId=tQ1CenHvX5ihvdQzW3HTgdxqPpN9iZ-HuSryQSG7lXk&cl.

4 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

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 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 114 words of visible text; thin pages give Google and first-time buyers little to go on.

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, Google Tag Manager, Meta Pixel and TikTok Pixel and 1 more (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 22 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.