hexclad.co.jp website review

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

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

A phone's processor spends 11.1 s on main-thread work while loading, 5.9 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.

8 third-party services load with your homepage (Google Tag Manager, channel.io and alia-prod.com and others), adding 2.1 MB and 3.2 s of main-thread time.

About 899 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

alia-prod.com costs a phone 521 ms of main-thread work and 419 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.

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

Osano CMP costs a phone 337 ms of main-thread work and 87 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.

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

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

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

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

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.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

The first text or image appears after 2.6 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 119 ms to 142 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 2.3 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 34.4 MB in 371 requests on a phone: fonts 13.8 MB (21), media 12.4 MB (1) and images 4.4 MB (51). Under 2 MB keeps phones on slow connections fast.

4 images (180 KiB) 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.

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

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate 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: 7 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is only 43 characters: “HexClad は最高品質の素材で作られており、生涯使用できるように設計されています。”. 70 to 160 characters is enough to sell the click.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 157 pages on hexclad.co.jp and 5 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.

https://hexclad.co.jp/pages/egg_pan_collection declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://hexclad.co.jp/products/orusuta4dian-setutogai-fu-ki and https://hexclad.co.jp/products/hitorimu-rasi2dian-setutogai-fu-ki-totobatugu-purezento-copy all use the title “HEXCLAD 人気フライパン2点セット(蓋付き) + トートバッグ（Onyx) | HexClad 公式”. Search engines can't tell which page to show for a search, so each competes with the others.

https://hexclad.co.jp/pages/egg_pan_collection, https://hexclad.co.jp/pages/about-us, https://hexclad.co.jp/blogs/recipes, https://hexclad.co.jp/collections/npd, https://hexclad.co.jp/collections/best-sellers and https://hexclad.co.jp/collections/sets have no meta description, so Google writes the search snippet from whatever text it finds.

https://hexclad.co.jp/pages/egg_pan_collection, https://hexclad.co.jp/pages/stores, https://hexclad.co.jp/products/7pc-hexclad-set-w-lids-wok, https://hexclad.co.jp/products/6pc-hexclad-pot-set, https://hexclad.co.jp/products/hybrid-roasting-pan-with-flat-rack and https://hexclad.co.jp/products/hybrid-oval-roasting-pan and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin”.

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.

Social proof on the homepage: 47 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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 123 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 Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 11 cookies, 2 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.