Website review, no card needed

rapsodo.co.jp logo

rapsodo.co.jp website review

Visit site (opens in a new tab)Reviewed 9 November 202626 issues · 66 checks

This review found 26 issues worth fixing on rapsodo.co.jp, 6 of them high impact, across 66 checks. The most urgent: 6 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
1.6 s1.1 sMay 23Nov 71.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.3 s
Aug 8, 20261.4 s
Aug 15, 20261.5 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Oct 31, 20261.4 s
Nov 7, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
109 ms91 msMay 23Nov 799 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202695 ms
May 30, 202696 ms
Jun 6, 202693 ms
Jun 13, 202693 ms
Jun 20, 202695 ms
Jun 27, 202694 ms
Jul 4, 202695 ms
Jul 11, 202695 ms
Jul 18, 202694 ms
Jul 25, 202693 ms
Aug 1, 202695 ms
Aug 8, 202696 ms
Aug 15, 2026102 ms
Aug 22, 2026107 ms
Aug 29, 2026106 ms
Sep 5, 2026105 ms
Sep 12, 202699 ms
Sep 19, 202699 ms
Sep 26, 202696 ms
Oct 3, 202696 ms
Oct 10, 2026102 ms
Oct 17, 2026103 ms
Oct 24, 202696 ms
Oct 31, 202697 ms
Nov 7, 202699 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

Full-page screenshot of rapsodo.co.jp (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rapsodo.co.jp at 0.5 s0.5 s
  2. rapsodo.co.jp at 1.1 s1.1 s
  3. rapsodo.co.jp at 1.6 s1.6 s
  4. rapsodo.co.jp at 2.2 s2.2 s
  5. rapsodo.co.jp at 2.7 s2.7 s
  6. rapsodo.co.jp at 3.3 s3.3 s
  7. rapsodo.co.jp at 3.8 s3.8 s
  8. rapsodo.co.jp at 4.4 s4.4 s

Speed

2 to fix
  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, YouTube and Google Fonts and others), adding 1.1 MB and 21 ms of main-thread time.

  • Shopify adds 17 ms

    17 ms

    Shopify costs a phone 17 ms of main-thread work and 1,009 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 273 ms of it running JavaScript. That is comfortably low.

  • Server response: 11 ms

    11 ms

    Your server sent the HTML in 11 ms, well inside Google's 600 ms guideline.

Core Web Vitals

2 to fix100
  • Speed Index: 5.6 s

    5.6 s

    Visually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.

  • 33 images without width and height

    33 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 95 ms to 99 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-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 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 s

    Real visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 91 ms

    91 ms

    Real visitors wait 91 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.09

    0.09

    For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

    Real visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 462 ms

    462 ms

    Real visitors wait 462 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix75
  • Page weight: 2.0 MB in 146 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 146 requests on a phone: images 949 KiB (31), other files 662 KiB (69) and scripts 295 KiB (36). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    104 KiB

    2 images are downloaded at several times the size a phone draws them, for example Frame_23.jpg at 2,880 px wide, shown at 390 px. Resized copies would save about 104 KiB.

  • About 0.6 g of CO₂ per visit

    0.57 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.8 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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8894
  • 6 text elements with low contrast

    6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9279
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (29 characters)

    Your title is only 29 characters: “Rapsodo Japan (ラプソード) - 公式サイト”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 63 internal links, 30 external

    The homepage links to 63 pages on rapsodo.co.jp and 30 external pages.

5 checks passed
  • Meta description: 78 characters

    Your meta description is 78 characters: “Rapsodo Japan公式サイトです。ラプソードは、野球・ソフトボール・ゴルフの投球・打球をカメラとレーダーで計測・分析するデータトラッキング機器です。”.

  • Canonical URL set

    The canonical URL is https://rapsodo.co.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://rapsodo.co.jp/sitemap.xml.

AI search readiness

1 to fix83
  • 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://rapsodo.co.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix83
  • 2 pages without a meta description

    https://rapsodo.co.jp/collections/all and https://rapsodo.co.jp/pages/mlm2xpro-more-ways-to-play-more-ways-to-improve have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://rapsodo.co.jp/pages/learn-more-about-pro-2, https://rapsodo.co.jp/products/rapsodo-pro-2 and https://rapsodo.co.jp/pages/softball-pro-2 use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://rapsodo.co.jp/pages/range, whose canonical is https://rapsodo.co.jp/pages/transform-your-range-with-rapsodo-range. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://rapsodo.co.jp/pages/softball, https://rapsodo.co.jp/pages/range, https://rapsodo.co.jp/collections/all, https://rapsodo.co.jp/pages/softball-pro-2, https://rapsodo.co.jp/pages/mlm2pro-golf-simulator and https://rapsodo.co.jp/pages/golf-mlm have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://rapsodo.co.jp/pages/softball, https://rapsodo.co.jp/collections/all, https://rapsodo.co.jp/pages/learn-more-about-pro-2, https://rapsodo.co.jp/pages/softball-pro-2, https://rapsodo.co.jp/pages/mlm2xpro-more-ways-to-play-more-ways-to-improve and https://rapsodo.co.jp/pages/mlm2pro-golf-simulator 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 34 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

1 to fixGoogle 8897
  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    20 of 21 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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.

  • 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 64 words

    The homepage has only about 64 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
  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and X (Twitter) Ads (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

    16

    Opening the homepage sets 16 cookies, 3 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 rapsodo.co.jp, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

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
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on rapsodo.co.jp, including 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25