Website review, no card needed
coravin.jp website review
Visit site (opens in a new tab)Reviewed 11 November 202625 issues · 82 checks
This review found 25 issues worth fixing on coravin.jp, 6 of them high impact, across 82 checks. The most urgent: page weight: 8.7 MB in 354 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
84B- #19,850 of 109,350 reviewed websitesbeats 77%
- #12,897 of 61,859 online storesbeats 73%
- #12,521 of 56,401 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 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.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 124 ms |
| May 30, 2026 | 125 ms |
| Jun 6, 2026 | 127 ms |
| Jun 13, 2026 | 128 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 134 ms |
| Jul 11, 2026 | 131 ms |
| Jul 18, 2026 | 132 ms |
| Jul 25, 2026 | 131 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 150 ms |
| Aug 15, 2026 | 136 ms |
| Aug 22, 2026 | 138 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 118 ms |
| Sep 19, 2026 | 125 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 151 ms |
| Oct 10, 2026 | 149 ms |
| Oct 17, 2026 | 149 ms |
| Oct 24, 2026 | 164 ms |
| Oct 31, 2026 | 138 ms |
| Nov 7, 2026 | 141 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
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and Klaviyo and others), adding 1.6 MB and 938 ms of main-thread time.
Mobile performance score: 88
88/100Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Google Tag Manager adds 600 ms
600 msGoogle Tag Manager costs a phone 600 ms of main-thread work and 1.0 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 JavaScript
595 KiBAbout 595 KiB of JavaScript is downloaded but never used on this page.
1,677 HTML elements
The page has 1,677 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
239 KiB9 images could be 239 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
230 KiB31 files are served with short cache lifetimes, so returning visitors download them again (230 KiB).
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 200 ms. During a long task the page ignores taps.
Reduce unused CSS
70 KiBAbout 70 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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 CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 26.0 s
26.0 sThe page becomes fully interactive after 26.0 s. Good is under 3.8 s.
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 334 ms
334 msScripts block taps and scrolling for 334 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 124 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 142 ms
142 msReal visitors wait 142 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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 700 ms
700 msReal visitors wait 700 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Largest Contentful Paint: 1.3 s
1.3 sYour largest element renders in 1.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Six+ Ocean Blue グラスワインシステムが20%OFF”.
Images and page weight
Page weight: 8.7 MB in 354 requests
8.7 MBYour homepage downloads 8.7 MB in 354 requests on a phone: media 3.9 MB (1), scripts 1.9 MB (112) and images 1.4 MB (58). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (113 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.47 g of CO₂e: 296.2 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
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://www.coravin.com.au)”.
101 internal links, 34 external
The homepage links to 101 pages on coravin.jp and 34 external pages.
7 checks passed
Meta description: 74 characters
Your meta description is 74 characters: “Coravinのワイン・バイ・ザ・グラス システムを体験。どんなワインも、いつでも一杯ずつ。最初の一杯の美味しさを保ったまま、何年先でも楽しめます。”.
One H1 headline
Your main headline reads: “Six+ Ocean Blue グラスワインシステムが20%OFF”.
Title: 56 characters
Your title is a healthy 56 characters: “Coravin ワイン・バイ・ザ・グラス システムで広がる、自由なワイン体験|日本 – Coravin APAC”.
Canonical URL set
The canonical URL is https://www.coravin.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://www.coravin.jp/sitemap.xml.
AI search readiness
4 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 (340 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.coravin.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages share a meta description
https://www.coravin.jp/collections/all, https://www.coravin.jp/collections/coravin-systems, https://www.coravin.jp/collections/coravin-pure-capsules, https://www.coravin.jp/collections/coravin-needles, https://www.coravin.jp/collections/accessories and https://www.coravin.jp/pages/trade-create-account use the same meta description. A description written for each page earns more clicks.
8 pages with very little text
https://www.coravin.jp/pages/support-accessibility, https://www.coravin.jp/collections/coravin-pure-capsules, https://www.coravin.jp/pages/how-it-works, https://www.coravin.jp/pages/technology, https://www.coravin.jp/pages/industry-professionals and https://www.coravin.jp/pages/training and 2 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://www.coravin.jp/collections/all, https://www.coravin.jp/collections/coravin-systems, https://www.coravin.jp/collections/coravin-pure-capsules and https://www.coravin.jp/collections/accessories took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 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
9 small tap targets
9 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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: 4 testimonial or review blocks. 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 243 words
The homepage has only about 243 words of visible text; thin pages give Google and first-time buyers little to go on.
3 checks passed
18 short forms
18 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 2 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.
27 cookies set on arrival
27Opening the homepage sets 27 cookies, 1 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.
49 other companies contacted
Loading the homepage contacts 49 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 coravin.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Selecty · Triplewhale · Microsoft Clarity · Tolstoy · Stack Discounts Pro · Aspire App · digitaloceanspaces.com · cloudfront.net
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
- Google Tag Manager | 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 25 issues on coravin.jp, including 10 speed issues, 1 SEO issue 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.