innisfree.jp website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, visumo.io and loox.io and others), adding 2.7 MB and 3.0 s of main-thread time.

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

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

visumo.io costs a phone 616 ms of main-thread work and 1,008 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.

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

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

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

Facebook costs a phone 310 ms of main-thread work and 298 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.

loox.io costs a phone 335 ms of main-thread work and 27 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.

TikTok costs a phone 283 ms of main-thread work and 167 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 73 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

33 KiB JavaScript is shipped twice across bundles.

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 60.7 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 34.0 s (Speed Index). Good is under 3.4 s.

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

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

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

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

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

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

Your homepage downloads 14.8 MB in 335 requests on a phone: fonts 9.4 MB (8), scripts 3.1 MB (103) and images 1.4 MB (58). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (112 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 21 characters: “イニスフリー 日本公式 オンラインショップ”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 302 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 269 pages on innisfree.jp and 3 external pages.

https://www.innisfree.jp/collections/recommended-products and https://www.innisfree.jp/collections/part-care 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://www.innisfree.jp/blogs/notice/%E3%83%AA%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%A2%E3%83%AB%E3%81%AB%E4%BC%B4%E3%81%86%E4%BC%9A%E5%93%A1%E6%83%85%E5%A0%B1%E7%A7%BB%E8%A1%8C%E3%81%AB%E9%96%A2%E3%81%99%E3%82%8B%E5%A4%A7%E5%88%87%E3%81%AA%E3%81%8A%E7%9F%A5%E3%82%89%E3%81%9B, whose canonical is https://www.innisfree.jp/blogs/notice/%e3%83%aa%e3%83%8b%e3%83%a5%e3%83%bc%e3%82%a2%e3%83%ab%e3%81%ab%e4%bc%b4%e3%81%86%e4%bc%9a%e5%93%a1%e6%83%85%e5%a0%b1%e7%a7%bb%e8%a1%8c%e3%81%ab%e9%96%a2%e3%81%99%e3%82%8b%e5%a4%a7%e5%88%87%e3%81%aa%e3%81%8a%e7%9f%a5%e3%82%89%e3%81%9b. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.innisfree.jp/blogs/notice/%E3%83%AA%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%A2%E3%83%AB%E3%81%AB%E4%BC%B4%E3%81%86%E4%BC%9A%E5%93%A1%E6%83%85%E5%A0%B1%E7%A7%BB%E8%A1%8C%E3%81%AB%E9%96%A2%E3%81%99%E3%82%8B%E5%A4%A7%E5%88%87%E3%81%AA%E3%81%8A%E7%9F%A5%E3%82%89%E3%81%9B has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.innisfree.jp/blogs/notice/%E3%83%AA%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%A2%E3%83%AB%E3%81%AB%E4%BC%B4%E3%81%86%E4%BC%9A%E5%93%A1%E6%83%85%E5%A0%B1%E7%A7%BB%E8%A1%8C%E3%81%AB%E9%96%A2%E3%81%99%E3%82%8B%E5%A4%A7%E5%88%87%E3%81%AA%E3%81%8A%E7%9F%A5%E3%82%89%E3%81%9B 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 103 found) and read each the way a search engine does.

4 errors were logged to the browser console while the page loaded, for example “Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.”.

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.

The homepage has only about 110 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 Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 mores (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 33 cookies, 3 of them by other companies (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 52 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.