pso-rite.co.jp website review

8 third-party services load with your homepage (Google Tag Manager, Hubspot and Shopify and others), adding 9.3 MB and 337 ms of main-thread time.

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

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

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

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

Google Tag Manager costs a phone 201 ms of main-thread work and 484 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 2,214 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 29 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 121 ms. During a long task the page ignores taps.

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

Polyfills for old browsers add 34 KiB JavaScript that modern phones do not need.

1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

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

Your largest element takes 5.2 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 3.8 s (Speed Index). Good is under 3.4 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 10.4 MB in 181 requests on a phone: media 8.3 MB (2), scripts 957 KiB (50) and other files 823 KiB (96). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 2.94 g of CO₂e: 352.4 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.

1 button has no accessible name, so screen readers announce just “button”.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is 66 characters, so Google will cut it off around 60: “PSO-RITE | PSOミニ | PSO-スパイン | PSOAS |戻る |マッサージツール – Pso-Rite Japan”.

There are 4 <h1> headlines (“Pso-Rite Japan”, “あらゆるライフスタイルに最適なセルフコンディショニング&リカバリーツール” and “小さなお子様向けの、かわいいセルフケアツール”). One clear main headline is easier for people and search engines.

Structured data found (Organization and Product) but with 1 problem, for example “Organization: url points at a different host (https://pso-rite.com)”.

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

The homepage links to 52 pages on pso-rite.co.jp and 18 external pages.

Your homepage links to https://www.pso-rite.co.jp/pages/how-to-videos-1, which answers with an error. Visitors hit a dead end and search engines drop it.

/ and https://www.pso-rite.co.jp/collections/all all use the title “PSO-RITE | PSOミニ | PSO-スパイン | PSOAS |戻る |マッサージツール – Pso-Rite Japan”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.pso-rite.co.jp/pages/about-us-pso and https://www.pso-rite.co.jp/blogs/dev-test-blog have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pso-rite.co.jp/pages/%E3%83%8F%E3%82%A6%E3%83%84%E3%83%BC%E3%83%93%E3%83%87%E3%82%AA and https://www.pso-rite.co.jp/pages/copia-de-pso-rite-%E3%83%8F%E3%82%A6%E3%83%84%E3%83%BC%E3%83%93%E3%83%87%E3%82%AA use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.pso-rite.co.jp/pages/%E3%83%8F%E3%82%A6%E3%83%84%E3%83%BC%E3%83%93%E3%83%87%E3%82%AA, whose canonical is https://www.pso-rite.co.jp/pages/%e3%83%8f%e3%82%a6%e3%83%84%e3%83%bc%e3%83%93%e3%83%87%e3%82%aa. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.pso-rite.co.jp/pages/about-us-pso, https://www.pso-rite.co.jp/pages/%E3%83%8F%E3%82%A6%E3%83%84%E3%83%BC%E3%83%93%E3%83%87%E3%82%AA, https://www.pso-rite.co.jp/pages/copia-de-pso-rite-%E3%83%8F%E3%82%A6%E3%83%84%E3%83%BC%E3%83%93%E3%83%87%E3%82%AA and https://www.pso-rite.co.jp/pages/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.pso-rite.co.jp/collections/all, https://www.pso-rite.co.jp/pages/about-us-pso, https://www.pso-rite.co.jp/pages/%E3%83%8F%E3%82%A6%E3%83%84%E3%83%BC%E3%83%93%E3%83%87%E3%82%AA, https://www.pso-rite.co.jp/pages/frequently-asked-questions, https://www.pso-rite.co.jp/products/pso-rite and https://www.pso-rite.co.jp/products/pso-spine and 7 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 22 found) and read each the way a search engine does.

3 images failed to load on a phone, for example https://www.pso-rite.co.jp/.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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