Website review, no card needed
kabegamiyahonpo.com website review
Visit site (opens in a new tab)Reviewed 4 November 202642 issues · 89 checks
This review found 42 issues worth fixing on kabegamiyahonpo.com, 13 of them high impact, across 89 checks. The most urgent: page weight: 23.6 MB in 340 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81B- #42,113 of 126,442 reviewed websitesbeats 61%
- #27,667 of 70,471 online storesbeats 54%
- #26,638 of 63,972 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 160 ms |
| May 23, 2026 | 168 ms |
| May 30, 2026 | 175 ms |
| Jun 6, 2026 | 179 ms |
| Jun 13, 2026 | 182 ms |
| Jun 20, 2026 | 185 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 189 ms |
| Jul 11, 2026 | 189 ms |
| Jul 18, 2026 | 188 ms |
| Jul 25, 2026 | 188 ms |
| Aug 1, 2026 | 185 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 175 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 172 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 167 ms |
| Oct 3, 2026 | 164 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 164 ms |
| Oct 31, 2026 | 164 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.3 s
2.0 s
2.7 s
3.3 s
4.0 s
4.7 s
5.3 s
Speed
Render-blocking requests
1.0 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
3,654 HTML elements
The page has 3,654 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
450 ms · 595 KiBAbout 595 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (visumo.jp, Shopify and Google CDN and others), adding 1.8 MB and 845 ms of main-thread time.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
374 KiB15 images could be 374 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
335 KiB19 files are served with short cache lifetimes, so returning visitors download them again (335 KiB).
Shopify adds 178 ms
178 msShopify costs a phone 178 ms of main-thread work and 974 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.
Klaviyo adds 113 ms
113 msKlaviyo costs a phone 113 ms of main-thread work and 305 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 114 ms. During a long task the page ignores taps.
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 14.7 s
14.7 sThe page becomes fully interactive after 14.7 s. Good is under 3.8 s.
Largest Contentful Paint: 6.1 s
6.1 sYour largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 8.8 s
8.8 sVisually, the page fills in at 8.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 160 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 149 ms
149 msReal visitors wait 149 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 473 ms
473 msReal visitors wait 473 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 147 ms
147 msScripts block the page for only 147 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 23.6 MB in 340 requests
23.6 MBYour homepage downloads 23.6 MB in 340 requests on a phone: media 18.1 MB (6), images 3.2 MB (107) and scripts 1.2 MB (95). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
repeat-wed-spbn.gif 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).
5 images far larger than shown
81 KiB5 images are downloaded at several times the size a phone draws them, for example minrifo_toppc3sp.gif at 1,100 px wide, shown at 344 px. Resized copies would save about 81 KiB.
3 images in older formats
3 images (483 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.
1 image below the first screen load straight away
1 image further down the page (256 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 6.7 g of CO₂ per visit
6.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.68 g of CO₂e: 801.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
179 images without alt text
179 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
30 links without text
30 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (10 elements)
ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
25 links crawlers can't follow
25 links have no real href, so search engines can't follow them.
Meta description is long (192 characters)
Your meta description is 192 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
367 internal links, 30 external
The homepage links to 367 pages on kabegamiyahonpo.com and 30 external pages.
6 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “壁紙屋本舗【公式サイト】壁紙やインテリアをもっと楽しもう、 セルフリフォームの総合サイト壁紙屋本舗 | 壁紙屋本舗 公式”.
Canonical URL set
The canonical URL is https://kabegamiyahonpo.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://kabegamiyahonpo.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://kabegamiyahonpo.com/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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (329 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://kabegamiyahonpo.com/pages/swym-wishlist has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://kabegamiyahonpo.com/pages/swym-wishlist has no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://kabegamiyahonpo.com/pages/swym-wishlist, https://kabegamiyahonpo.com/collections/3506, https://kabegamiyahonpo.com/collections/3363, https://kabegamiyahonpo.com/collections/3169, https://kabegamiyahonpo.com/collections/3834s and https://kabegamiyahonpo.com/collections/1122 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 193 found) and read each the way a search engine does.
5 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
17 distorted images
17 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
28 of 32 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 124 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 49-field form
Your longest form asks for 49 fields (0 required). Every extra field lowers completion.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 187 words
The homepage has only about 187 words of visible text; thin pages give Google and first-time buyers little to go on.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
1 checks passed
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies (measured from a US location before any click).
No consent tool detected
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.
36 other companies contacted
Loading the homepage contacts 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at kabegamiyahonpo.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on kabegamiyahonpo.com, including 15 speed issues, 3 SEO issues and 6 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.