Website review, no card needed
fukuromono-studio.com website review
Visit site (opens in a new tab)Reviewed 9 November 202635 issues · 86 checks
This review found 35 issues worth fixing on fukuromono-studio.com, 11 of them high impact, across 86 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,085 of 126,357 reviewed websitesbeats 61%
- #27,654 of 70,445 online storesbeats 54%
- #26,622 of 63,945 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 145 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 147 ms |
| Jun 13, 2026 | 147 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 149 ms |
| Jul 4, 2026 | 150 ms |
| Jul 11, 2026 | 152 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 156 ms |
| Aug 1, 2026 | 159 ms |
| Aug 8, 2026 | 163 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 166 ms |
| Aug 29, 2026 | 167 ms |
| Sep 5, 2026 | 169 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 176 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 178 ms |
| Oct 17, 2026 | 180 ms |
| Oct 24, 2026 | 179 ms |
| Oct 31, 2026 | 178 ms |
| Nov 7, 2026 | 173 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.5 s
2.2 s
2.9 s
3.7 s
4.4 s
5.2 s
5.9 s
Speed
Render-blocking requests
1.3 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,248 HTML elements
The page has 6,248 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
150 ms · 2.2 MB19 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
450 ms · 195 KiBAbout 195 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.
Reduce unused CSS
300 ms · 67 KiBAbout 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Klaviyo adds 143 ms
143 msKlaviyo costs a phone 143 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.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Clarity and Shopify and others), adding 694 KiB and 439 ms of main-thread time.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 122 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
19 KiB6 files are served with short cache lifetimes, so returning visitors download them again (19 KiB).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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 JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 26 ms
26 msYour server sent the HTML in 26 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.3 s
7.3 sYour largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Cumulative Layout Shift: 0.705
0.705The layout shifts by 0.705 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 11.5 s
11.5 sThe page becomes fully interactive after 11.5 s. Good is under 3.8 s.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 145 ms to 173 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 244 ms
244 msScripts block taps and scrolling for 244 ms in total while the page loads. Good is under 200 ms.
7 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 173 ms
173 msReal visitors wait 173 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: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 358 ms
358 msReal visitors wait 358 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 6.5 MB in 262 requests
6.5 MBYour homepage downloads 6.5 MB in 262 requests on a phone: images 4.6 MB (65), other files 807 KiB (100) and scripts 775 KiB (69). Under 2 MB keeps phones on slow connections fast.
15 images far larger than shown
2.0 MB15 images are downloaded at several times the size a phone draws them, for example fs.jpg at 1,600 px wide, shown at 228 px. Resized copies would save about 2.0 MB.
An image on the first screen is lazy-loaded
fj_1247.jpg 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).
About 1.8 g of CO₂ per visit
1.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.85 g of CO₂e: 221.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 456 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
427 internal links, 1 external
The homepage links to 427 pages on fukuromono-studio.com and 1 external page.
8 checks passed
Meta description: 104 characters
Your meta description is 104 characters: “財布、バッグ、革小物などのオリジナルアイテムを取り扱うFUKUROMONO STUDIO ONLINE SHOP。レザーやコットン、麻といった天然素材の持つ風合いを活かした、長く愛せるアイテムをお届けします。”.
One H1 headline
Your main headline reads: “FUKUROMONO STUDIO ONLINE SHOP”.
Title: 45 characters
Your title is a healthy 45 characters: “財布、バッグ、革小物などを扱う FUKUROMONO STUDIO ONLINE SHOP”.
Canonical URL set
The canonical URL is https://fukuromono-studio.com/.
Structured data in place
Structured data found: BreadcrumbList, Corporation, Organization, SiteNavigationElement 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://fukuromono-studio.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (701 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://fukuromono-studio.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://fukuromono-studio.com/pages/member-benefits has no meta description, so Google writes the search snippet from whatever text it finds.
14 links to non-canonical URLs
Your homepage links to 14 pages by a URL that isn't their canonical one, for example https://fukuromono-studio.com/collections/%E3%82%A6%E3%82%A3%E3%83%A1%E3%83%B3%E3%82%BA, whose canonical is https://fukuromono-studio.com/collections/%e3%82%a6%e3%82%a3%e3%83%a1%e3%83%b3%e3%82%ba. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://fukuromono-studio.com/pages/member-benefits, https://fukuromono-studio.com/collections/%E3%82%A6%E3%82%A3%E3%83%A1%E3%83%B3%E3%82%BA, https://fukuromono-studio.com/collections/%E3%83%A1%E3%83%B3%E3%82%BA, https://fukuromono-studio.com/collections/%E3%83%90%E3%83%83%E3%82%B0, https://fukuromono-studio.com/collections/%E3%83%8F%E3%83%B3%E3%83%89%E3%83%90%E3%83%83%E3%82%B0 and https://fukuromono-studio.com/collections/%E3%83%88%E3%83%BC%E3%83%88%E3%83%90%E3%83%83%E3%82%B0 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://fukuromono-studio.com/pages/member-benefits, https://fukuromono-studio.com/collections/%E3%83%88%E3%83%A9%E3%83%99%E3%83%AB%E3%83%90%E3%83%83%E3%82%B0, https://fukuromono-studio.com/collections/%E3%83%90%E3%83%83%E3%82%B0%E3%81%9D%E3%81%AE%E4%BB%96 and https://fukuromono-studio.com/collections/%EF%BC%93way%E3%83%90%E3%83%83%E3%82%B0 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://fukuromono-studio.com/collections/2way%E3%83%90%E3%83%83%E3%82%B0, https://fukuromono-studio.com/collections/%EF%BC%93way%E3%83%90%E3%83%83%E3%82%B0, https://fukuromono-studio.com/collections/%E8%B2%A1%E5%B8%83 and https://fukuromono-studio.com/collections/%E9%95%B7%E8%B2%A1%E5%B8%83 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 153 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 15 pages that loaded have a <title>.
Best practices
41 small tap targets
41 of 86 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 2 trust badges. 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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
About 289 words of copy
The homepage carries about 289 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “FUKUROMONO STUDIO ONLINE SHOP”.
1 call to action
The homepage has 1 call to action, for example “FUKUROMONO STUDIO ONLINE SHOP”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
32 other companies contacted
Loading the homepage contacts 32 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 fukuromono-studio.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Klaviyo Email Marketing Sms · Judge Me Reviews · Boost Ai Search Filter · Super Gift Options · Helium Customer Fields · Version · Swym Wishlist Plus
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- 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 35 issues on fukuromono-studio.com, including 15 speed issues and 4 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.