Website review, no card needed
shoyoroll.jp website review
Visit site (opens in a new tab)Reviewed 5 November 202619 issues · 62 checks
This review found 19 issues worth fixing on shoyoroll.jp, 5 of them high impact, across 62 checks. The most urgent: no social proof. 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
87B- #8,286 of 119,930 reviewed websitesbeats 90%
- #4,798 of 67,979 online storesbeats 89%
- #4,651 of 61,955 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 725 ms |
| May 23, 2026 | 794 ms |
| May 30, 2026 | 750 ms |
| Jun 6, 2026 | 750 ms |
| Jun 13, 2026 | 757 ms |
| Jun 20, 2026 | 744 ms |
| Jun 27, 2026 | 760 ms |
| Jul 4, 2026 | 797 ms |
| Jul 11, 2026 | 788 ms |
| Jul 18, 2026 | 833 ms |
| Jul 25, 2026 | 813 ms |
| Aug 8, 2026 | 728 ms |
| Aug 15, 2026 | 748 ms |
| Aug 22, 2026 | 729 ms |
| Aug 29, 2026 | 765 ms |
| Sep 5, 2026 | 752 ms |
| Sep 12, 2026 | 750 ms |
| Sep 19, 2026 | 802 ms |
| Sep 26, 2026 | 817 ms |
| Oct 3, 2026 | 855 ms |
| Oct 10, 2026 | 865 ms |
| Oct 17, 2026 | 892 ms |
| Oct 24, 2026 | 884 ms |
| Oct 31, 2026 | 871 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 62 ms |
| May 23, 2026 | 62 ms |
| May 30, 2026 | 62 ms |
| Jun 6, 2026 | 62 ms |
| Jun 20, 2026 | 62 ms |
| Jun 27, 2026 | 63 ms |
| Jul 4, 2026 | 64 ms |
| Jul 11, 2026 | 64 ms |
| Jul 18, 2026 | 63 ms |
| Jul 25, 2026 | 62 ms |
| Aug 8, 2026 | 61 ms |
| Aug 15, 2026 | 62 ms |
| Aug 22, 2026 | 60 ms |
| Aug 29, 2026 | 60 ms |
| Sep 5, 2026 | 61 ms |
| Sep 12, 2026 | 60 ms |
| Sep 19, 2026 | 63 ms |
| Sep 26, 2026 | 62 ms |
| Oct 3, 2026 | 59 ms |
| Oct 10, 2026 | 59 ms |
| Oct 17, 2026 | 60 ms |
| Oct 24, 2026 | 62 ms |
| Oct 31, 2026 | 62 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
Speed
Render-blocking requests
450 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Reduce unused CSS
150 ms · 17 KiBAbout 17 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
90 KiBAbout 90 KiB of JavaScript is downloaded but never used on this page.
7 third-party services on the page
7 third-party services load with your homepage (Amazon Web Services, Google CDN and Mailchimp and others), adding 256 KiB and 47 ms of main-thread time.
Use efficient cache lifetimes
29 KiB15 files are served with short cache lifetimes, so returning visitors download them again (29 KiB).
Improve image delivery
12 KiB1 image could be 12 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
3 checks passed
Mobile performance score: 94
94/100Your mobile performance score is 94. That is in Google's “good” band (90 and up).
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 199 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
1 image without width and height
1 image 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 62 ms to 62 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.9 s 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 62 ms
62 msReal visitors wait 62 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.
Time to Interactive: 3.0 s
3.0 sThe page is fully interactive after 3.0 s.
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.
Speed Index: 2.0 s
2.0 sVisually, the page fills in at 2.0 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.4 g of CO₂ per visit
0.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.38 g of CO₂e: 45.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.3 MB in 115 requests
1.3 MBYour homepage downloads 1.3 MB in 115 requests on a phone: other files 689 KiB (73), scripts 348 KiB (32) and images 248 KiB (4). That is a lean page.
Accessibility
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Form elements do not have associated labels
Form elements do not have associated labels (1 element).
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 link without text
1 link has no text or label, so screen readers cannot say where it goes.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
One H1 headline
Your <h1> is empty.
12 internal links, 2 external
The homepage links to 12 pages on shoyoroll.jp and 2 external pages.
5 checks passed
Title: 33 characters
Your title is a healthy 33 characters: “SHOYOROLL JAPAN – Shoyoroll Japan”.
Canonical URL set
The canonical URL is https://shoyoroll.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://shoyoroll.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://shoyoroll.jp/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://shoyoroll.jp/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://shoyoroll.jp/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://shoyoroll.jp/collections/all has 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 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
1 page of 4 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 1 page that loaded have a <title>.
Best practices
3 console errors
3 errors were logged to the browser console during Google's test (“[object XMLHttpRequest]”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 29 words
The homepage has only about 29 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
2 calls to action
The homepage has 2 calls to action, for example “Shop”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
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 shoyoroll.jp, 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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
chimpstatic.com
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
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on shoyoroll.jp, including 3 speed issues, 4 SEO 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.