mysweetsmile.com website review

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

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

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

About 60 KiB of JavaScript is downloaded but never used on this page.

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

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

1 image could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 KiB could be saved by minifying CSS.

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

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.

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

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

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

Early_Black_Friday_Sale_2026_Mobile_Banners_360x.png 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).

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

There are 6 <h1> headlines (“MySweetSmile®”, “Early Black Friday Is Here: Up To 58% Off! ⏰” and “Clinically Proven & Dentist-Approved 🇩🇪”). One clear main headline is easier for people and search engines.

Your meta description is 225 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 87 pages on mysweetsmile.com and 4 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.

https://mysweetsmile.com/en-us/products/teeth-whitening-powder and https://mysweetsmile.com/en-us/collections/products/products/teeth-whitening-powder all use the title “Teeth Whitening Powder | MySweetSmile®”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mysweetsmile.com/en-us/products/teeth-whitening-powder and https://mysweetsmile.com/en-us/collections/products/products/teeth-whitening-powder use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mysweetsmile.com/en-us/collections/products/products/teeth-whitening-powder, whose canonical is https://mysweetsmile.com/en-us/products/teeth-whitening-powder. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mysweetsmile.com/en-us/pages/buy-2-get-1-free and https://mysweetsmile.com/en-us/pages/buy-3-get-2-free have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'themeVersion')”.

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 local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 492 words of visible text.

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.

Opening the homepage sets 6 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.