sunseeker.jp website review

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

3 third-party services load with your homepage (Shopify, Clarity and shop.app), adding 1.2 MB and 940 ms of main-thread time.

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

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

Shopify costs a phone 734 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.

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

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

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

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

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

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

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.

3 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 41.6 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 30.4 s (Speed Index). Good is under 3.4 s.

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

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

Your homepage downloads 23.7 MB in 470 requests on a phone: media 12.9 MB (5), fonts 6.0 MB (4) and images 2.0 MB (26). Under 2 MB keeps phones on slow connections fast.

9f3b29bd7bf740a3802458279a21d0bf.thumbnail.0000000000_2500x. weighs 848 KiB. On a phone connection a single image that size takes seconds.

3 images (1.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.

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

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

13 images have no alt text, which hurts accessibility and image search.

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

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

Headings skip levels (h2 → h5, h3 → h5 and h3 → h6), which makes the page harder to scan with a screen reader.

There are 6 <h1> headlines (“SUNSEEKERについて”, “200万台以上” and “Top 3”). One clear main headline is easier for people and search engines.

The homepage links to 94 pages on sunseeker.jp and 4 external pages.

Your Organization JSON-LD is missing 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://sunseeker.jp/pages/x7, https://sunseeker.jp/pages/x5, https://sunseeker.jp/pages/x3, https://sunseeker.jp/collections/spare-blade, https://sunseeker.jp/collections/4g-gps-module and https://sunseeker.jp/collections/%E3%82%AC%E3%83%AC%E3%83%BC%E3%82%B8 and 8 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://sunseeker.jp/collections/%E3%82%AC%E3%83%AC%E3%83%BC%E3%82%B8, whose canonical is https://sunseeker.jp/collections/%e3%82%ac%e3%83%ac%e3%83%bc%e3%82%b8. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://sunseeker.jp/pages/x7, https://sunseeker.jp/collections/spare-blade, https://sunseeker.jp/collections/4g-gps-module, https://sunseeker.jp/collections/%E3%82%AC%E3%83%AC%E3%83%BC%E3%82%B8, https://sunseeker.jp/collections/charging-station and https://sunseeker.jp/collections/battery-pack and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sunseeker.jp/pages/x7, https://sunseeker.jp/pages/x5, https://sunseeker.jp/pages/x3, https://sunseeker.jp/collections/spare-blade, https://sunseeker.jp/collections/4g-gps-module and https://sunseeker.jp/collections/%E3%82%AC%E3%83%AC%E3%83%BC%E3%82%B8 and 8 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 44 found) and read each the way a search engine does.

4 of 20 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: net::ERR_FAILED”.

2 images are displayed at the wrong aspect ratio, so they look 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.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 200 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, Microsoft Ads and Microsoft Clarity (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 14 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.