Website review, no card needed
wardrobe-sangetsu.jp website review
Visit site (opens in a new tab)Reviewed 11 November 202638 issues · 87 checks
This review found 38 issues worth fixing on wardrobe-sangetsu.jp, 15 of them high impact, across 87 checks. The most urgent: render-blocking 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,073 of 126,317 reviewed websitesbeats 61%
- #27,649 of 70,430 online storesbeats 54%
- #26,619 of 63,936 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 208 ms |
| May 30, 2026 | 197 ms |
| Jun 6, 2026 | 201 ms |
| Jun 13, 2026 | 213 ms |
| Jun 20, 2026 | 249 ms |
| Jun 27, 2026 | 274 ms |
| Jul 4, 2026 | 286 ms |
| Jul 11, 2026 | 283 ms |
| Jul 18, 2026 | 281 ms |
| Jul 25, 2026 | 285 ms |
| Aug 1, 2026 | 285 ms |
| Aug 8, 2026 | 292 ms |
| Aug 15, 2026 | 269 ms |
| Aug 22, 2026 | 255 ms |
| Aug 29, 2026 | 242 ms |
| Sep 5, 2026 | 232 ms |
| Sep 12, 2026 | 241 ms |
| Sep 19, 2026 | 232 ms |
| Sep 26, 2026 | 232 ms |
| Oct 3, 2026 | 224 ms |
| Oct 10, 2026 | 225 ms |
| Oct 17, 2026 | 230 ms |
| Oct 24, 2026 | 229 ms |
| Oct 31, 2026 | 202 ms |
| Nov 7, 2026 | 179 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
1.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.5 s
7.6 s
8.7 s
Speed
Render-blocking requests
1.2 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Main-thread work: 9.6 s
A phone's processor spends 9.6 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,192 HTML elements
The page has 4,192 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (channel.io, revico.jp and visumo.jp and others), adding 2.3 MB and 1.7 s of main-thread time.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
810 KiB33 images could be 810 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
741 KiBAbout 741 KiB of JavaScript is downloaded but never used on this page.
channel.io adds 560 ms
560 mschannel.io costs a phone 560 ms of main-thread work and 337 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.
Use efficient cache lifetimes
539 KiB25 files are served with short cache lifetimes, so returning visitors download them again (539 KiB).
revico.jp adds 397 ms
397 msrevico.jp costs a phone 397 ms of main-thread work and 173 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 314 ms. During a long task the page ignores taps.
visumo.jp adds 259 ms
259 msvisumo.jp costs a phone 259 ms of main-thread work and 250 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 adds 34 ms
34 msShopify costs a phone 34 ms of main-thread work and 1.3 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.
Reduce unused CSS
90 KiBAbout 90 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
21 KiB21 KiB could be saved by minifying JavaScript.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 19.5 s
19.5 sThe page becomes fully interactive after 19.5 s. Good is under 3.8 s.
Speed Index: 11.1 s
11.1 sVisually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 803 ms
803 msScripts block taps and scrolling for 803 ms in total while the page loads. Good is under 200 ms.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 208 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 433 ms
433 msReal visitors wait 433 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Largest Contentful Paint: 1.1 s
1.1 sYour largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “このたびの令和8年熊本地震により被災された方々に謹んでお見舞いを申しあげます。 一日も早い復旧・復興を心よりお祈りいた…”.
Images and page weight
Page weight: 5.5 MB in 266 requests
5.5 MBYour homepage downloads 5.5 MB in 266 requests on a phone: images 2.7 MB (109), scripts 1.2 MB (48) and fonts 942 KiB (42). Under 2 MB keeps phones on slow connections fast.
4 images below the first screen load straight away
4 images further down the page (242 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 187.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
91 tap targets too small
91 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
24 elements hidden from screen readers can still receive keyboard focus.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
24 images without alt text
24 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
29 links without text
29 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 (22 elements)
Alternative text of images should not be repeated as text: 22 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“WARDROBE sangetsu” and “WARDROBE sangetsu”). One clear main headline is easier for people and search engines.
396 internal links, 4 external
The homepage links to 396 pages on wardrobe-sangetsu.jp and 4 external pages.
6 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “創業70年以上の実績を持つサンゲツが運営するオーダーカーテン・インテリアの公式オンライン通販サイトです。WEB限定の高品質で多彩なデザインのカーテンを取り揃え、リネンやコットンなどの天然繊維の上質なカーテンや、遮光、遮熱などの機能付きカー…”.
Title: 60 characters
Your title is a healthy 60 characters: “【サンゲツ公式通販】オーダーカーテン・インテリア専門店 | ワードローブサンゲツ – WARDROBE sangetsu”.
Canonical URL set
The canonical URL is https://wardrobe-sangetsu.jp/.
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://wardrobe-sangetsu.jp/sitemap.xml.
AI search readiness
No Organization structured data
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.
2 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.
llms.txt published
The site publishes https://wardrobe-sangetsu.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
12 pages with very little text
https://wardrobe-sangetsu.jp/collections/curtain-set, https://wardrobe-sangetsu.jp/collections/tassel, https://wardrobe-sangetsu.jp/collections/outlet, https://wardrobe-sangetsu.jp/collections/clearance-sale, https://wardrobe-sangetsu.jp/collections/cushion and https://wardrobe-sangetsu.jp/collections/multi-cover 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.
4 pages slow to respond
https://wardrobe-sangetsu.jp/collections/linen-curtain, https://wardrobe-sangetsu.jp/collections/curtain-set, https://wardrobe-sangetsu.jp/collections/tassel and https://wardrobe-sangetsu.jp/collections/outlet took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 84 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://wardrobe-sangetsu.jp/.
47 small tap targets
47 of 94 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://b6.im-apps.net/topics' from origin 'null' has been blocked by CORS policy: No 'Access-Contr…”.
1 checks passed
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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 137 words
The homepage has only about 137 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.
2 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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, 2 of them by other companies (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.
41 other companies contacted
Loading the homepage contacts 41 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 wardrobe-sangetsu.jp, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on wardrobe-sangetsu.jp, including 17 speed issues, 2 SEO issues and 5 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.