Website review, no card needed

toothbrushtoys.com logo

toothbrushtoys.com website review

Visit site (opens in a new tab)Reviewed 10 November 202647 issues · 91 checks

This review found 47 issues worth fixing on toothbrushtoys.com, 15 of them high impact, across 91 checks. The most urgent: improve image delivery. 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

Full-page screenshot of toothbrushtoys.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. toothbrushtoys.com at 1.6 s1.6 s
  2. toothbrushtoys.com at 3.2 s3.2 s
  3. toothbrushtoys.com at 4.7 s4.7 s
  4. toothbrushtoys.com at 6.3 s6.3 s
  5. toothbrushtoys.com at 7.9 s7.9 s
  6. toothbrushtoys.com at 9.5 s9.5 s
  7. toothbrushtoys.com at 11.1 s11.1 s
  8. toothbrushtoys.com at 12.6 s12.6 s

Speed

15 to fix33
  • Improve image delivery

    3.7 s · 1.5 MB

    17 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.7 s faster on a phone.

  • Render-blocking requests

    2.4 s

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

  • Main-thread work: 18.2 s

    A phone's processor spends 18.2 s on main-thread work while loading, 10.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hotjar and Google CDN and others), adding 16.0 MB and 3.6 s of main-thread time.

  • Reduce unused JavaScript

    750 ms · 2.2 MB

    About 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Use efficient cache lifetimes

    1.1 MB

    36 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 892 ms. During a long task the page ignores taps.

  • Google Tag Manager adds 553 ms

    553 ms

    Google Tag Manager costs a phone 553 ms of main-thread work and 441 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.

  • Google CDN adds 518 ms

    518 ms

    Google CDN costs a phone 518 ms of main-thread work and 740 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.

  • Hotjar adds 534 ms

    534 ms

    Hotjar costs a phone 534 ms of main-thread work and 65 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.

  • espn.com adds 489 ms

    489 ms

    espn.com costs a phone 489 ms of main-thread work and 404 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.

  • heatmap.com adds 419 ms

    419 ms

    heatmap.com costs a phone 419 ms of main-thread work and 94 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.

  • Minify JavaScript

    300 ms · 81 KiB

    81 KiB could be saved by minifying JavaScript.

  • 1,833 HTML elements

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

  • Reduce unused CSS

    150 ms · 238 KiB

    About 238 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.

  • Legacy JavaScript

    19 KiB

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

1 checks passed
  • Server response: 16 ms

    16 ms

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

Core Web Vitals

6 to fix34
  • Largest Contentful Paint: 11.6 s

    11.6 s

    Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 20.6 s

    20.6 s

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

  • Time to Interactive: 50.7 s

    50.7 s

    The page becomes fully interactive after 50.7 s. Good is under 3.8 s.

  • Total Blocking Time: 3.0 s

    3.0 s

    Scripts block taps and scrolling for 3.0 s in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.3 s

    2.3 s

    The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

  • 2 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.046

    0.046

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

Images and page weight

3 to fix43
  • Page weight: 22.7 MB in 679 requests

    22.7 MB

    Your homepage downloads 22.7 MB in 679 requests on a phone: media 11.9 MB (1), scripts 4.4 MB (205) and images 2.7 MB (43). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    1.0 MB

    7 images are downloaded at several times the size a phone draws them, for example Website_stuff_5.png at 2,000 px wide, shown at 230 px. Resized copies would save about 1.0 MB.

  • 5 images below the first screen load straight away

    5 images further down the page (744 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.4 g of CO₂ per visit

    6.42 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8891
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

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

  • 2 images without alt text

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

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • 12 form fields without a label

    12 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 7787
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Shop Toothbrush Toys”). One clear main headline is easier for people and search engines.

  • Structured data has 2 problems

    Structured data found (Organization, ToyStore and WebSite) but with 2 problems, for example “ToyStore: sameAs is an empty list”.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 60 internal links, 9 external

    The homepage links to 60 pages on toothbrushtoys.com and 9 external pages.

6 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Toothbrush Toys are the first ever kid’s character toothbrushes that double as fun, interactive toys! Explore our wide …”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Fun Kids Toothbrush Toys | Make Brushing an Exciting Adventure!”.

  • Canonical URL set

    The canonical URL is https://www.toothbrushtoys.com/.

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

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    32%

    The HTML your server sends has 861 of the 2,730 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

3 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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • llms.txt published

    The site publishes https://www.toothbrushtoys.com/llms.txt (67 KiB, 44 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.toothbrushtoys.com/collections/shop-all and https://www.toothbrushtoys.com/collections/kids-character-toothbrushes all use the title “Kids Character Toothbrushes for Fun Brushing Time | Toothbrush Toys”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.toothbrushtoys.com/collections/shop-all and https://www.toothbrushtoys.com/collections/kids-character-toothbrushes 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://www.toothbrushtoys.com/collections/shop-all, whose canonical is https://www.toothbrushtoys.com/collections/kids-character-toothbrushes. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 2 pages that loaded have a meta description.

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

Best practices

4 to fixGoogle 5474
  • 7 broken images

    7 images failed to load on a phone, for example https://m.media-amazon.com/images/I/71ha-h4b+zL._SY1000.jpg.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • A 10-field form

    Your longest form asks for 10 fields (5 required). Every extra field lowers completion.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 2,730 words of copy

    The homepage carries about 2,730 words of visible text.

6 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop”, “Shop Now” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 7 customer or partner logos and a star rating.

  • Analytics in place

    Analytics detected: Google Analytics, Microsoft Clarity and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 24 cookies set on arrival

    24

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

  • 59 other companies contacted

    Loading the homepage contacts 59 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 toothbrushtoys.com, 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 17 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Tapita Seo Speed · Hulk Form Builder · Sami B2b Lock · Judge Me Reviews · Seal Subscriptions · Klaviyo Email Marketing Sms · Triplewhale · Inbox · Sami Wholesale · Assortion · Store Locator · Wholesale Lock Hide Price · Forms · Bestpush · nfcube.com · shareasale.com · goaudience.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 | Hotjar | Microsoft Clarity
Hosting
Cloudflare

Company

Headquarters
Westlake Village

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on toothbrushtoys.com, including 21 speed issues, 4 SEO issues and 3 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