sootang.jp website review

27 images could be 874 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

About 142 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Shopify, Google CDN and aiqua.io and others), adding 1.9 MB and 371 ms of main-thread time.

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

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

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

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

Google Fonts costs a phone 4 ms of main-thread work and 963 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.

15 KiB could be saved by minifying CSS.

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

6 long tasks block the main thread while loading, the longest for 89 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 30 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.

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.

For real visitors the layout shifts by 0.53 (75th percentile). Good is under 0.1.

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

The layout shifts by 0.561 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

39 images 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 95 ms to 94 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.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.0 MB in 270 requests on a phone: images 2.0 MB (65), scripts 1,006 KiB (52) and fonts 878 KiB (42). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

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

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

Your title is only 23 characters: “【SOOTANG HOBBY】ホビー通販サイト”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 64 characters: “フィギュア、プラモデルを中心に、国内・海外の多種多様なホビー商品を扱う総合通販サイト。最新商品も随時更新中！是非ご利用ください！”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 289 pages on sootang.jp and 6 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.

There is no https://www.sootang.jp/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.sootang.jp/collections/%E6%96%B0%E8%A6%8F%E5%85%A5%E8%8D%B7%E5%95%86%E5%93%81, https://www.sootang.jp/collections/%E6%96%B0%E8%A6%8F%E4%BA%88%E7%B4%84%E5%95%86%E5%93%81, https://www.sootang.jp/pages/ranking-list, https://www.sootang.jp/collections/gunpla, https://www.sootang.jp/collections/%E3%82%AD%E3%83%A3%E3%83%A9%E3%82%AF%E3%82%BF%E3%83%BC%E3%83%97%E3%83%A9%E3%83%A2%E3%83%87%E3%83%AB and https://www.sootang.jp/collections/%E3%81%9D%E3%81%AE%E4%BB%96%E3%83%97%E3%83%A9%E3%83%A2%E3%83%87%E3%83%AB have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.sootang.jp/collections/%E6%96%B0%E8%A6%8F%E5%85%A5%E8%8D%B7%E5%95%86%E5%93%81, whose canonical is https://www.sootang.jp/collections/%e6%96%b0%e8%a6%8f%e5%85%a5%e8%8d%b7%e5%95%86%e5%93%81. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.sootang.jp/collections/%E6%96%B0%E8%A6%8F%E5%85%A5%E8%8D%B7%E5%95%86%E5%93%81, https://www.sootang.jp/collections/%E6%96%B0%E8%A6%8F%E4%BA%88%E7%B4%84%E5%95%86%E5%93%81, https://www.sootang.jp/collections/%E3%83%97%E3%83%A9%E3%83%A2%E3%83%87%E3%83%AB, https://www.sootang.jp/collections/gunpla, https://www.sootang.jp/collections/%E3%82%AD%E3%83%A3%E3%83%A9%E3%82%AF%E3%82%BF%E3%83%BC%E3%83%97%E3%83%A9%E3%83%A2%E3%83%87%E3%83%AB and https://www.sootang.jp/collections/%E3%81%9D%E3%81%AE%E4%BB%96%E3%83%97%E3%83%A9%E3%83%A2%E3%83%87%E3%83%AB have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sootang.jp/collections/%E6%96%B0%E8%A6%8F%E5%85%A5%E8%8D%B7%E5%95%86%E5%93%81, https://www.sootang.jp/collections/%E6%96%B0%E8%A6%8F%E4%BA%88%E7%B4%84%E5%95%86%E5%93%81, https://www.sootang.jp/pages/ranking-list, https://www.sootang.jp/collections/%E3%83%97%E3%83%A9%E3%83%A2%E3%83%87%E3%83%AB, https://www.sootang.jp/collections/gunpla and https://www.sootang.jp/collections/%E3%82%AD%E3%83%A3%E3%83%A9%E3%82%AF%E3%82%BF%E3%83%BC%E3%83%97%E3%83%A9%E3%83%A2%E3%83%87%E3%83%AB 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 15 pages linked from your homepage (of 134 found) and read each the way a search engine does.

63 of 166 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 ()”.

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 278 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 23 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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.