osaji.net website review

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

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

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

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

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

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

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

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

Google Tag Manager costs a phone 327 ms of main-thread work and 345 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 107 ms of main-thread work and 1.2 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.

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

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

24 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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

Your homepage downloads 15.2 MB in 473 requests on a phone: fonts 8.5 MB (4), images 3.0 MB (91) and scripts 2.3 MB (94). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example nailbalm_2_1500x1500_69d469b2-9259-4bc3-bcde-c51e934864fb.jp at 1,500 px wide, shown at 115 px. Resized copies would save about 586 KiB.

Parfum_SP_Carousel_W800xH800px.jpg 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).

12 images further down the page (774 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.31 g of CO₂e: 517.2 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: 25 elements on the page fail this check, rated critical by axe-core.

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

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

Main landmark should not be contained in another landmark: 3 elements on the page fail 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.

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

ARIA role should be appropriate for the element: 9 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.

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

Your title is only 23 characters: “OSAJI〈オサジ〉| 公式オンラインショップ”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 46 characters: “健やかで美しい皮膚を保つためのスキンケアライフスタイルを提案する敏感肌ブランド"OSAJI"”. 70 to 160 characters is enough to sell the click.

Your <h1> is empty.

The homepage links to 203 pages on osaji.net and 17 external pages.

https://osaji.net/collections/all-products, https://osaji.net/collections/facialcare, https://osaji.net/collections/makeup, https://osaji.net/collections/haircare, https://osaji.net/collections/fragrance and https://osaji.net/collections/kako-%E5%AE%B6%E9%A6%99 and 4 others 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://osaji.net/collections/kako-%E5%AE%B6%E9%A6%99, whose canonical is https://osaji.net/collections/kako-%e5%ae%b6%e9%a6%99. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://osaji.net/collections/all-products, https://osaji.net/collections/facialcare, https://osaji.net/collections/bodyitem, https://osaji.net/collections/makeup, https://osaji.net/collections/makenail and https://osaji.net/collections/haircare and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://osaji.net/collections/all-products, https://osaji.net/collections/facialcare, https://osaji.net/collections/bodyitem, https://osaji.net/collections/makeup, https://osaji.net/collections/makenail and https://osaji.net/collections/haircare and 9 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 86 found) and read each the way a search engine does.

2 images failed to load on a phone, for example https://osaji.net/.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Failed to fetch”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 327 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 4 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 31 cookies, 2 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 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.