unimmee.com website review

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

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

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

5 third-party services load with your homepage (Google Tag Manager, Shopify and Google/Doubleclick Ads and others), adding 808 KiB and 866 ms of main-thread time.

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

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

Google Tag Manager costs a phone 337 ms of main-thread work and 164 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.

Shopify costs a phone 262 ms of main-thread work and 350 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 283 KiB of JavaScript is downloaded but never used on this page.

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

About 23 KiB of CSS is downloaded but never applied on this page.

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

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.

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

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

Your largest element takes 4.6 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 4.4 s (Speed Index). Good is under 3.4 s.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 96 ms to 109 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.7 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.3 MB in 210 requests on a phone: other files 883 KiB (95), scripts 713 KiB (47) and images 504 KiB (30). Under 2 MB keeps phones on slow connections fast.

1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

Your title is 75 characters, so Google will cut it off around 60: “商店風 お名前入り商店風グッズ 商店風の最新コレクション 商店風オリジナルグッズ オリジナル フィギュア 作成 似顔絵 フィギュア – Unimmee”.

Your <h1> is empty.

The homepage links to 241 pages on unimmee.com and 3 external pages.

There is no https://unimmee.com/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://unimmee.com/collections/my-figure has 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 52 found) and read each the way a search engine does.

2 images failed to load on a phone, for example https://unimmee.com/.

5 of 18 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 “Failed to load resource: the server responded with a status of 404 ()”.

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.

Social proof on the homepage: 16 testimonial or review blocks. 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 70 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, Meta Pixel and TikTok 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 16 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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.