hitowan.jp website review

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

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

8 third-party services load with your homepage (channel.io, Shopify and socialplus.jp and others), adding 1.2 MB and 489 ms of main-thread time.

17 images could be 548 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

channel.io costs a phone 351 ms of main-thread work and 378 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.

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

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

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

leeep.jp costs a phone 18 ms of main-thread work and 447 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.

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

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

Polyfills for old browsers add 8 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 26.7 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 27.2 s. Good is under 3.8 s.

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

The first text or image appears after 2.1 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 96 ms to 116 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.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.7 MB in 221 requests on a phone: fonts 3.0 MB (2), other files 925 KiB (129) and images 900 KiB (26). Under 2 MB keeps phones on slow connections fast.

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

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

Elements with visible text labels do not have matching accessible names. (1 element).

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

12 links have no real href, so search engines can't follow them.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 149 pages on hitowan.jp and 12 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), 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.

https://hitowan.jp/pages/instagram is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://hitowan.jp/pages/brands, https://hitowan.jp/pages/shoplist, https://hitowan.jp/blogs/info, https://hitowan.jp/blogs/media, https://hitowan.jp/pages/first-meal-guide and https://hitowan.jp/pages/%E3%81%8A%E5%BE%97%E3%81%AA%E5%AE%9A%E6%9C%9F%E4%BE%BF and 2 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://hitowan.jp/pages/%E3%81%8A%E5%BE%97%E3%81%AA%E5%AE%9A%E6%9C%9F%E4%BE%BF, whose canonical is https://hitowan.jp/pages/%e3%81%8a%e5%be%97%e3%81%aa%e5%ae%9a%e6%9c%9f%e4%be%bf. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://hitowan.jp/pages/brands, https://hitowan.jp/collections/all-products, https://hitowan.jp/pages/faq, https://hitowan.jp/pages/first-meal-guide and https://hitowan.jp/pages/instagram have no <h1> headline, so visitors and search engines get no clear main topic.

https://hitowan.jp/pages/brands, https://hitowan.jp/pages/shoplist, https://hitowan.jp/blogs/info, https://hitowan.jp/blogs/media, https://hitowan.jp/pages/feeding-calculator and https://hitowan.jp/pages/faq 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.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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