svakom.jp website review

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

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

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

Shopify costs a phone 231 ms of main-thread work and 465 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.

4 third-party services load with your homepage (Shopify, shop.app and FontAwesome CDN and others), adding 548 KiB and 231 ms of main-thread time.

About 73 KiB of JavaScript is downloaded but never used on this page.

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

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

4 files are served with short cache lifetimes, so returning visitors download them again (6 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.

Your largest element takes 4.2 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 6.6 s. Good is under 3.8 s.

2 images have no width and height attributes, so the layout jumps as each one loads.

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 2.0 MB in 180 requests on a phone: other files 648 KiB (69), images 592 KiB (16) and scripts 377 KiB (62). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example GROUP_PHOTO-HIGH-001_2.webp at 1,200 px wide, shown at 350 px. Resized copies would save about 52 KiB.

6 images (435 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 0.58 g of CO₂e: 69.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

There are 3 <h1> headlines (“”, “ハイライト” and “世界有名のメディアに掲載された”). One clear main headline is easier for people and search engines.

The homepage links to 33 pages on svakom.jp and 14 external pages.

https://svakom.jp/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://svakom.jp/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://svakom.jp/collections/all, https://svakom.jp/customer_authentication/redirect, https://svakom.jp/collections/all-products, https://svakom.jp/collections/new-product, https://svakom.jp/collections/%E4%BA%BA%E6%B0%97%E5%95%86%E5%93%81 and https://svakom.jp/collections/anal 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://svakom.jp/collections/%E4%BA%BA%E6%B0%97%E5%95%86%E5%93%81, whose canonical is https://svakom.jp/collections/%e4%ba%ba%e6%b0%97%e5%95%86%e5%93%81. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://svakom.jp/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://svakom.jp/collections/pos, https://svakom.jp/collections/anal, https://svakom.jp/collections/wand-vibrator, https://svakom.jp/pages/contact, https://svakom.jp/pages/delivery-date and https://svakom.jp/pages/legal-notice and 1 other 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 14 pages linked from your homepage and read each the way a search engine does.

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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.