kuwanoha.com website review

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

About 984 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

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

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

8 third-party services load with your homepage (YouTube, Bold Commerce and Google Tag Manager and others), adding 2.2 MB and 1.0 s of main-thread time.

About 216 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 740 ms faster on a phone.

1 image could be 127 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.

YouTube costs a phone 471 ms of main-thread work and 988 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.

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

Bold Commerce costs a phone 286 ms of main-thread work and 484 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.

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

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

Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need.

6 KiB could be saved by minifying CSS.

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 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “体に嬉しいこと初めてみませんか？”.

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

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

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

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

27 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' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.6 MB in 91 requests on a phone: images 3.2 MB (31), scripts 1.8 MB (26) and fonts 286 KiB (9). Under 2 MB keeps phones on slow connections fast.

image001_1024x1024.png weighs 809 KiB. On a phone connection a single image that size takes seconds.

9 images are downloaded at several times the size a phone draws them, for example AMMultEX-2.jpg at 1,920 px wide, shown at 345 px. Resized copies would save about 544 KiB.

14 images (2.0 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.

13 images further down the page (1.9 MB) 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 1.59 g of CO₂e: 190.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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 22 characters: “桑茶セレクト ～ こだわりの桑の葉茶・桑青汁”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 86 pages on kuwanoha.com and 0 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

/products/kobashitaste.html, /products/ryokuchataste.html and /products/maroyakataste.html have no <title>, so Google invents the link text in results.

/products/kobashitaste.html, /products/ryokuchataste.html, /products/maroyakataste.html, /blogs/column.html, /blogs/recipe.html and /blogs/review.html and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/products/kobashitaste.html, /products/ryokuchataste.html and /products/maroyakataste.html have no <h1> headline, so visitors and search engines get no clear main topic.

/products/kobashitaste-large.html, /pages/muberry-leaf-powder.html, /products/matchataste.html, /products/kuwanohasoap.html, /products/amm-ult-ex.html and /pages/guide.html and 6 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.

/products/ryokuchataste.html, /products/maroyakataste.html, /pages/concept.html, /blogs/column.html, /blogs/recipe.html and /blogs/review.html took over 3 s to send their HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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 ()”.

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