pethroom.jp website review

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

8 third-party services load with your homepage (channel.io, Shopify and Clarity and others), adding 1.2 MB and 813 ms of main-thread time.

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

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

channel.io costs a phone 334 ms of main-thread work and 347 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.

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

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

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

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

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

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

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

11 KiB could be saved by minifying JavaScript.

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

3 KiB JavaScript is shipped twice across bundles.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.2 MB in 298 requests on a phone: fonts 8.9 MB (9), scripts 1.2 MB (95) and images 1.1 MB (37). Under 2 MB keeps phones on slow connections fast.

TOP_MO_01_d7bce93d-3a82-433a-8718-9566d7781a7e.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example pethroom-awards-mo-260909.jpg at 1,290 px wide, shown at 390 px. Resized copies would save about 17 KiB.

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

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is only 27 characters: “PETHROOM（ペスルーム）日本公式オンラインストア”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 179 pages on pethroom.jp and 6 external pages.

https://pethroom.jp/collections/%E8%87%AA%E7%A4%BE%E9%96%8B%E7%99%BA, https://pethroom.jp/collections/%E3%83%94%E3%83%B3%E3%82%AF%E3%83%A9%E3%82%A4%E3%83%B3, https://pethroom.jp/collections/all, https://pethroom.jp/collections/best, https://pethroom.jp/collections/for-dogs and https://pethroom.jp/collections/for-cats and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://pethroom.jp/collections/%E8%87%AA%E7%A4%BE%E9%96%8B%E7%99%BA, whose canonical is https://pethroom.jp/collections/%e8%87%aa%e7%a4%be%e9%96%8b%e7%99%ba. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://pethroom.jp/collections/%E8%87%AA%E7%A4%BE%E9%96%8B%E7%99%BA, https://pethroom.jp/collections/%E3%83%94%E3%83%B3%E3%82%AF%E3%83%A9%E3%82%A4%E3%83%B3, https://pethroom.jp/collections/all, https://pethroom.jp/collections/best, https://pethroom.jp/collections/for-dogs and https://pethroom.jp/collections/for-cats and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://pethroom.jp/collections/all, https://pethroom.jp/collections/for-dogs, https://pethroom.jp/collections/for-cats, https://pethroom.jp/collections/%E3%81%8A%E6%89%8B%E5%85%A5%E3%82%8C and https://pethroom.jp/pages/customer-support took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: e is not a function”.

1 image is served at too low a resolution for sharp phone screens.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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 143 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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