supermouth.com website review

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

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

Shopify costs a phone 1.3 s of main-thread work and 4.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Tag Manager costs a phone 1.3 s of main-thread work and 930 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Wistia and others), adding 6.7 MB and 4.6 s of main-thread time.

About 925 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

Wistia costs a phone 850 ms of main-thread work and 395 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.

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

Facebook costs a phone 529 ms of main-thread work and 318 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.

ZenDesk costs a phone 368 ms of main-thread work and 431 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.

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

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

12 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

3 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

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

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

17 images weigh 49.0 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 46.3 MB in 228 requests on a phone: images 43.6 MB (79), scripts 2.5 MB (92) and fonts 125 KiB (11). Under 2 MB keeps phones on slow connections fast.

22 images are downloaded at several times the size a phone draws them, for example testimonial_Akoya_Pediatric_Dentistry.jpg at 7,952 px wide, shown at 96 px. Resized copies would save about 38.1 MB.

30 images (52.7 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

29 images further down the page (43.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

Elements with visible text labels do not have matching accessible names. (3 elements).

Your title is only 10 characters: “SuperMouth”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 2 <h1> headlines (“Your family doesn't need a better toothpaste. The…” and “Your family doesn't need a better toothpaste. The…”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 177 pages on supermouth.com and 9 external pages.

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.

There is no https://supermouth.com/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.

https://supermouth.com/systems/teens-and-adults and https://supermouth.com/systems/orthodontics all use the title “SuperMouth | Systems”. Search engines can't tell which page to show for a search, so each competes with the others.

https://supermouth.com/collections/ages-13-and-up, https://supermouth.com/collections/ortho, https://supermouth.com/collections/pregnancy and https://supermouth.com/products/supermouth-hydroxamin-with-fluoride-mouthfloss have no meta description, so Google writes the search snippet from whatever text it finds.

https://supermouth.com/shop-all and https://supermouth.com/shop-all-kids use the same meta description. A description written for each page earns more clicks.

https://supermouth.com/shop-all, https://supermouth.com/assessment, https://supermouth.com/systems-overview, https://supermouth.com/shop-all-kids, https://supermouth.com/collections/ages-13-and-up and https://supermouth.com/collections/ortho and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Loading the image 'https://www.googletagmanager.com/a?id=GTM-TPNWGV2&v=3&t=t&pid=151639977&gtm=45He6b41h1v9116094387za2…”.

Chrome logged issues while loading the page (“Content security policy”).

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The page uses urgency cues (a countdown or limited-time wording).

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

Opening the homepage sets 12 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.