sunsmarche.jp website review

102 files are served with short cache lifetimes, so returning visitors download them again (22.7 MB).

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

9 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.

About 452 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.3 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, TikTok and cloudfront.net and others), adding 15.9 MB and 1.0 s of main-thread time.

cloudfront.net costs a phone 142 ms of main-thread work and 14.6 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.

82 KiB could be saved by minifying CSS.

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

102 KiB could be saved by minifying JavaScript.

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

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

Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

tag-plus.com costs a phone 9 ms of main-thread work and 417 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.

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.

Real visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

The layout shifts by 0.275 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.

Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

34 images 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 144 ms to 166 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 3.4 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 24.8 MB in 214 requests on a phone: images 21.5 MB (84), scripts 1.8 MB (23) and fonts 878 KiB (47). Under 2 MB keeps phones on slow connections fast.

27 images (3.1 MB) 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.

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

27 images are downloaded at several times the size a phone draws them, for example open-uri20261104-3221-1ymplt7 at 1,040 px wide, shown at 328 px. Resized copies would save about 428 KiB.

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

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

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

Some list items are not inside a list.

3 elements hidden from screen readers can still receive keyboard focus.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your <h1> is empty.

The homepage links to 143 pages on sunsmarche.jp and 4 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.

There is no https://sunsmarche.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://sunsmarche.jp/shop, https://sunsmarche.jp/shop/contact/draft, https://sunsmarche.jp/shop/products, https://sunsmarche.jp/shop/product_categories/sale and https://sunsmarche.jp/shop/product_categories/price-categories and 5 others all use the title “SUNSMARCHE/サン・スマイル公式オンラインショップ | 化粧品・コスメの通販 | サンスマルシェ”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sunsmarche.jp/shop, https://sunsmarche.jp/shop/pages/shopping-guide, https://sunsmarche.jp/shop/pages/subscription, https://sunsmarche.jp/shop/pages/tracking, https://sunsmarche.jp/shop/contact/draft and https://sunsmarche.jp/shop/products and 7 others use the same meta description. A description written for each page earns more clicks.

https://sunsmarche.jp/shop/pages/shopping-guide, https://sunsmarche.jp/shop/information_categories/news, https://sunsmarche.jp/shop/pages/subscription, https://sunsmarche.jp/shop/pages/tracking, https://sunsmarche.jp/shop/contact/draft and https://sunsmarche.jp/shop/product_categories/3000-3999-items and 1 other 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.

https://sunsmarche.jp/shop/pages/subscription, https://sunsmarche.jp/shop/contact/draft, https://sunsmarche.jp/shop/products, https://sunsmarche.jp/shop/product_categories/sale, https://sunsmarche.jp/shop/product_categories/price-categories and https://sunsmarche.jp/shop/product_categories/1000yen-miman and 3 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 89 found) and read each the way a search engine does.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 (Forbidden)”.

Large scripts ship without source maps.

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