Website review, no card needed

sonic-brush.net logo

sonic-brush.net website review

Visit site (opens in a new tab)Reviewed 7 November 202619 issues · 75 checks

This review found 19 issues worth fixing on sonic-brush.net, 5 of them high impact, across 75 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
3.2 s758 msMay 16Oct 311.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.3 s
May 30, 20261.7 s
Jun 6, 20261.3 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
167 ms125 msMay 16Oct 31154 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026135 ms
May 23, 2026132 ms
May 30, 2026130 ms
Jun 6, 2026137 ms
Jun 13, 2026137 ms
Jun 20, 2026138 ms
Jun 27, 2026144 ms
Jul 4, 2026145 ms
Jul 11, 2026145 ms
Jul 18, 2026146 ms
Jul 25, 2026146 ms
Aug 1, 2026152 ms
Aug 8, 2026154 ms
Aug 15, 2026154 ms
Aug 22, 2026156 ms
Aug 29, 2026159 ms
Sep 5, 2026162 ms
Sep 12, 2026161 ms
Sep 19, 2026159 ms
Sep 26, 2026158 ms
Oct 3, 2026155 ms
Oct 10, 2026154 ms
Oct 17, 2026153 ms
Oct 24, 2026154 ms
Oct 31, 2026154 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.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix100
  • Render-blocking requests

    1.4 s

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

  • 2,424 HTML elements

    The page has 2,424 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Shopify adds 5 ms

    5 ms

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

    153 KiB

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

  • Improve image delivery

    121 KiB

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

  • 8 third-party services on the page

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

  • Reduce unused CSS

    86 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 56 ms. During a long task the page ignores taps.

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

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

  • Server response: 17 ms

    17 ms

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

Core Web Vitals

4 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user INP: 202 ms

    202 ms

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

  • Real-user TTFB: 902 ms

    902 ms

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

  • 7 images without width and height

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

  • Tap response (INP) got 15% slower for real visitors

    +15%

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

10 checks passed
  • Real-user LCP: 1.3 s

    1.3 s

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

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

    1.3 s

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

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

    -60%

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Speed Index: 2.0 s

    2.0 s

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

  • Cumulative Layout Shift: 0.003

    0.003

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

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 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.4 s

    1.4 s

    The page is fully interactive after 1.4 s.

Images and page weight

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

    50874051_2186405958288006_881074362810105856_n_2048x2048_b1b 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.4 g of CO₂ per visit

    0.43 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.8 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.5 MB in 71 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 71 requests on a phone: scripts 941 KiB (34), images 317 KiB (15) and stylesheets 132 KiB (18). 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.

  • 8 images without alt text

    8 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

1 to fixGoogle 9296
  • No structured data

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

  • 163 internal links, 15 external

    The homepage links to 163 pages on sonic-brush.net and 15 external pages.

7 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Experience the future of oral care with Sonic Brush® – the world’s first automatic sonic toothbrush 💙 Brush smarter an…”.

  • One H1 headline

    Your main headline reads: “Sonic Brush®”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Sonic Brush® | The World’s First Automatic Sonic Toothbrush”.

  • Canonical URL set

    The canonical URL is https://sonic-brush.net/.

  • 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.net/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://sonic-brush.net/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,584 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://sonic-brush.net/products/sonic-brush%C2%AE-kids, whose canonical is https://sonic-brush.net/products/sonic-brush%c2%ae-kids. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://sonic-brush.net/products/sonic-brush-v6-pro, https://sonic-brush.net/products/sonic-brush and https://sonic-brush.net/products/nylon-mouthpiece have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 5 pages that loaded have a meta description.

  • 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 5 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Refused to apply style from 'https://sonic-brush.net/cdn/shop/t/43/assets/country-flags.css' because its MIME type ('te…”.

2 checks passed
  • Tap targets are thumb-sized

    14 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 832 words of copy

    The homepage carries about 832 words of visible text.

4 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Shop”, “Contact Us” and “Order Tracking”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 441 testimonial or review blocks, 40 customer or partner logos, a star rating, 1 trust badge and “100K+ Happy Users”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and 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.

  • 7 cookies set on arrival

    7

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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.net, 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 20 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Fbp Fast Bundle · Consentik Cookie · Microsoft Clarity · Powerful Form Builder · Triplewhale · Videowise Video Commerce · Kaching Bundles · Klaviyo Email Marketing Sms · Wetracked Io Connect · Consentik Ex · Honeycomb Upsell Funnels · Countdown Timer · Fokkio Gift With Purchase · Captain Shipping Protection · loox.io · elfsight.com · salessquad.co.uk · weglot.com · cloudfront.net · goaffpro.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
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 19 issues on sonic-brush.net, including 7 speed issues, 1 SEO issue and 1 conversion gap. 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