themedicube.jp website review

20 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

8 third-party services load with your homepage (Shopify, searchserverapi.com and Stamped.io and others), adding 4.3 MB and 332 ms of main-thread time.

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

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

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

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

About 56 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.

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

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

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

Polyfills for old browsers add 10 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 59.8 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 23.0 s (Speed Index). Good is under 3.4 s.

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

33 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 95 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.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 21.2 MB in 288 requests on a phone: fonts 16.5 MB (18), images 2.7 MB (66) and scripts 1.0 MB (65). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example 00_c066466e-63ab-4522-8c19-fc69d01cb135.jpg at 2,000 px wide, shown at 103 px. Resized copies would save about 618 KiB.

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

1 image (32 KiB) is 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 6.01 g of CO₂e: 721.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 dropdowns have no label.

Certain ARIA roles must contain particular children: 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”.

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

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

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

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

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your meta description is only 22 characters: “肌を研究するメディカルコスメ、メディキューブ”. 70 to 160 characters is enough to sell the click.

No XML sitemap at https://themedicube.jp/sitemap.xml, so Google discovers your pages only by following links.

Your <h1> is empty.

The homepage links to 146 pages on themedicube.jp and 19 external pages.

There is no https://themedicube.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://themedicube.jp/collections/all-product, https://themedicube.jp/collections/top10, https://themedicube.jp/pages/ager_guide, https://themedicube.jp/pages/devices_spec and https://themedicube.jp/collections/%E6%AF%9B%E7%A9%B4%E5%8F%8E%E7%B8%AE-zero-line have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://themedicube.jp/collections/%E6%AF%9B%E7%A9%B4%E5%8F%8E%E7%B8%AE-zero-line, whose canonical is https://themedicube.jp/collections/%e6%af%9b%e7%a9%b4%e5%8f%8e%e7%b8%ae-zero-line. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://themedicube.jp/pages/ager_guide and https://themedicube.jp/pages/devices_spec have no <h1> headline, so visitors and search engines get no clear main topic.

https://themedicube.jp/pages/ager_guide and https://themedicube.jp/pages/devices_spec 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 45 found) and read each the way a search engine does.

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

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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