king-makura.com website review

About 485 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, firebaseapp.com and Shopify and others), adding 2.6 MB and 538 ms of main-thread time.

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

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

Google Tag Manager costs a phone 331 ms of main-thread work and 615 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.

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

Google Fonts costs a phone 2 ms of main-thread work and 1,003 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.

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

15 KiB could be saved by minifying JavaScript.

12 KiB could be saved by minifying CSS.

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

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

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

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

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

The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 262 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 94 ms to 109 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 1.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.6 MB in 255 requests on a phone: scripts 1.1 MB (54), fonts 913 KiB (50) and other files 730 KiB (78). Under 2 MB keeps phones on slow connections fast.

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Your title is only 28 characters: “【公式】王様の夢枕と王様の抱き枕の専門店キング枕.com”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 87 pages on king-makura.com and 6 external pages.

https://www.king-makura.com/collections/all, https://www.king-makura.com/policies/shipping-policy, https://www.king-makura.com/collections/%E7%8E%8B%E6%A7%98%E3%81%AE%E5%A4%A2%E6%9E%95%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA, https://www.king-makura.com/collections/%E7%8E%8B%E6%A7%98%E3%81%AE%E6%8A%B1%E3%81%8D%E6%9E%95%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA, https://www.king-makura.com/collections/%E7%8E%8B%E6%A7%98%E3%81%AE%E8%85%B0%E6%8E%9B%E3%81%91%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA and https://www.king-makura.com/collections/%E7%8E%8B%E6%A7%98%E3%81%AE%E3%82%B5%E3%83%9D%E3%83%BC%E3%83%88%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://www.king-makura.com/collections/%E7%8E%8B%E6%A7%98%E3%81%AE%E5%A4%A2%E6%9E%95%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA, whose canonical is https://www.king-makura.com/collections/%e7%8e%8b%e6%a7%98%e3%81%ae%e5%a4%a2%e6%9e%95%e3%82%b7%e3%83%aa%e3%83%bc%e3%82%ba. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.king-makura.com/policies/shipping-policy, https://www.king-makura.com/collections/%E7%8E%8B%E6%A7%98%E3%81%AE%E5%A4%A2%E6%9E%95%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA, https://www.king-makura.com/collections/%E7%8E%8B%E6%A7%98%E3%81%AE%E6%8A%B1%E3%81%8D%E6%9E%95%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA, https://www.king-makura.com/collections/%E7%8E%8B%E6%A7%98%E3%81%AE%E8%85%B0%E6%8E%9B%E3%81%91%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA, https://www.king-makura.com/collections/%E7%8E%8B%E6%A7%98%E3%81%AE%E3%82%B5%E3%83%9D%E3%83%BC%E3%83%88%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA and https://www.king-makura.com/collections/%E3%82%AF%E3%83%BC%E3%83%AB%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA and 6 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 43 found) 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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 35 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, Meta Pixel and Pinterest Tag (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 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.