windandsea.jp website review

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

hcaptcha.com costs a phone 5.5 s of main-thread work and 4.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (hcaptcha.com, Google CDN and customerfields.com and others), adding 5.7 MB and 6.9 s of main-thread time.

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 320 ms faster on a phone.

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

Google CDN costs a phone 586 ms of main-thread work and 733 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.

customerfields.com costs a phone 361 ms of main-thread work and 209 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.

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

About 45 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 14 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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 39.4 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 20.8 s (Speed Index). Good is under 3.4 s.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 123 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 15.9 MB in 165 requests on a phone: images 9.0 MB (13), scripts 4.1 MB (77) and HTML 1.8 MB (11). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example 2_de3f09b4-6a92-422b-aa46-3d3e88217a96_1.jpg at 3,232 px wide, shown at 195 px. Resized copies would save about 8.4 MB.

6 images weigh 7.8 MB together. On a phone connection a single image that size takes seconds.

2 images (3.9 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.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

16 form fields have no label, so screen readers announce an empty box and autofill guesses.

Your title is only 25 characters: “WIND AND SEA ONLINE STORE”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 48 pages on windandsea.jp and 5 external pages.

https://windandsea.jp/collections/all, https://windandsea.jp/collections/no-coffee-x-wind-and-sea, https://windandsea.jp/collections/taion-wind-and-sea-1, https://windandsea.jp/collections/2026a-w-tech-collection and https://windandsea.jp/collections/technics-parappa-the-rapper-wind-and-sea have no meta description, so Google writes the search snippet from whatever text it finds.

https://windandsea.jp/collections/all, https://windandsea.jp/collections/originals, https://windandsea.jp/collections/no-coffee-x-wind-and-sea, https://windandsea.jp/collections/taion-wind-and-sea-1, https://windandsea.jp/collections/2026a-w-tech-collection and https://windandsea.jp/collections/technics-parappa-the-rapper-wind-and-sea have no <h1> headline, so visitors and search engines get no clear main topic.

https://windandsea.jp/collections/all, https://windandsea.jp/collections/originals, https://windandsea.jp/collections/no-coffee-x-wind-and-sea, https://windandsea.jp/collections/taion-wind-and-sea-1, https://windandsea.jp/collections/2026a-w-tech-collection and https://windandsea.jp/collections/technics-parappa-the-rapper-wind-and-sea 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 21 found) and read each the way a search engine does.

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

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.

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 64 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, Meta Pixel and X (Twitter) Ads (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 16 cookies, 3 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.