Website review, no card needed

sonic-brush.jp logo

sonic-brush.jp website review

Visit site (opens in a new tab)Reviewed 12 November 202620 issues · 73 checks

This review found 20 issues worth fixing on sonic-brush.jp, 6 of them high impact, across 73 checks. The most urgent: render-blocking requests. 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

Real-visitor load time (LCP)75th percentile, phones
2.9 s986 msMay 23Nov 71.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.6 s
May 30, 20262.1 s
Jun 6, 20261.5 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.3 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
176 ms118 msMay 23Nov 7125 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026144 ms
May 30, 2026145 ms
Jun 6, 2026149 ms
Jun 13, 2026156 ms
Jun 20, 2026162 ms
Jun 27, 2026166 ms
Jul 4, 2026166 ms
Jul 11, 2026166 ms
Jul 18, 2026160 ms
Jul 25, 2026160 ms
Aug 1, 2026158 ms
Aug 8, 2026159 ms
Aug 15, 2026161 ms
Aug 22, 2026161 ms
Aug 29, 2026167 ms
Sep 5, 2026169 ms
Sep 12, 2026161 ms
Sep 19, 2026145 ms
Sep 26, 2026136 ms
Oct 3, 2026128 ms
Oct 10, 2026127 ms
Oct 17, 2026129 ms
Oct 24, 2026128 ms
Oct 31, 2026127 ms
Nov 7, 2026125 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 sonic-brush.jp (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sonic-brush.jp at 0.4 s0.4 s
  2. sonic-brush.jp at 0.8 s0.8 s
  3. sonic-brush.jp at 1.1 s1.1 s
  4. sonic-brush.jp at 1.5 s1.5 s
  5. sonic-brush.jp at 1.9 s1.9 s
  6. sonic-brush.jp at 2.3 s2.3 s
  7. sonic-brush.jp at 2.6 s2.6 s
  8. sonic-brush.jp at 3.0 s3.0 s

Speed

2 to fix100
  • Render-blocking requests

    1.1 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Shopify adds 2 ms

    2 ms

    Shopify costs a phone 2 ms of main-thread work and 389 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

    147 KiB

    10 files are served with short cache lifetimes, so returning visitors download them again (147 KiB).

  • Improve image delivery

    130 KiB

    8 images could be 130 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    72 KiB

    About 72 KiB of CSS is downloaded but never applied on this page.

  • 5 third-party services on the page

    5 third-party services load with your homepage (JSDelivr CDN, Shopify and videowise.com and others), adding 523 KiB and 9 ms of main-thread time.

  • 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.

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.3 s

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

  • Server response: 14 ms

    14 ms

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

Core Web Vitals

1 to fix100
  • 7 images without width and height

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

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

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

  • Real-user INP: 124 ms

    124 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 670 ms

    670 ms

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

  • Tap response (INP) got 13% faster for real visitors

    -13%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 144 ms to 125 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 48% faster for real visitors

    -48%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.6 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 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.006

    0.006

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold.

  • Speed Index: 1.5 s

    1.5 s

    Visually, the page fills in at 1.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 1.2 s

    1.2 s

    The page is fully interactive after 1.2 s.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    2.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 0.3 g of CO₂ per visit

    0.35 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.35 g of CO₂e: 41.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Page weight: 1.2 MB in 56 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 56 requests on a phone: scripts 666 KiB (27), images 335 KiB (15) and stylesheets 98 KiB (10). That is a lean page.

  • 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

4 to fixGoogle 8594
  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 9 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 44 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: 44 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9289
  • Title is short (20 characters)

    Your title is only 20 characters: “Sonic Brush® | 公式サイト”. 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.

  • 73 internal links, 13 external

    The homepage links to 73 pages on sonic-brush.jp and 13 external pages.

6 checks passed
  • Meta description: 84 characters

    Your meta description is 84 characters: “Sonic Brush®で未来のオーラルケアを体験しよう。世界初の全自動歯ブラシで、わずか30秒で歯磨きが完了。私たちの革新的なソニック歯ブラシで、毎日をもっと快適に。”.

  • One H1 headline

    Your main headline reads: “Sonic Brush®”.

  • Canonical URL set

    The canonical URL is https://sonic-brush.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://sonic-brush.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://sonic-brush.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix85
  • 2 pages without a meta description

    https://sonic-brush.jp/collections/%E5%95%86%E5%93%81 and https://sonic-brush.jp/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://sonic-brush.jp/collections/%E5%95%86%E5%93%81, whose canonical is https://sonic-brush.jp/collections/%e5%95%86%e5%93%81. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages without an H1

    https://sonic-brush.jp/products/sonic-brush, https://sonic-brush.jp/products/sonic-brush-v5, https://sonic-brush.jp/products/sonic-brush%C2%AE-kids, https://sonic-brush.jp/products/nylon-mouthpiece, https://sonic-brush.jp/products/sonic-brush-head and https://sonic-brush.jp/products/foam-toothpaste and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 pages with very little text

    https://sonic-brush.jp/collections/%E5%95%86%E5%93%81, https://sonic-brush.jp/products/nylon-mouthpiece, https://sonic-brush.jp/products/sonic-brush-head, https://sonic-brush.jp/products/foam-toothpaste, https://sonic-brush.jp/products/disinfection-box-for-sonic-brush and https://sonic-brush.jp/products/3-in-1-brush-head-set 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 33 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    13 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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 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 91 words

    The homepage has only about 91 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: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 sonic-brush.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 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentik Cookie · Kaching Bundles · Microsoft Clarity · Videowise Video Commerce · Klaviyo Email Marketing Sms · Fbp Fast Bundle · Consentik Ex · Honeycomb Upsell Funnels · Countdown Timer · Section Factory · Captain Shipping Protection · elfsight.com · loox.io

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 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 20 issues on sonic-brush.jp, including 3 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

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