tryhellosmile.com website review

8 third-party services load with your homepage (Shopify, Clarity and Klaviyo and others), adding 20.8 MB and 324 ms of main-thread time.

Shopify costs a phone 132 ms of main-thread work and 20.6 MB 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.

49 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 150 ms faster on a phone.

Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

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

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

A phone's processor spends 3.2 s on main-thread work while loading, 1.5 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 300 ms.

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

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

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

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

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

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.

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 137 ms to 137 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 2.2 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 25.9 MB in 327 requests on a phone: media 19.8 MB (1), images 4.0 MB (128) and other files 875 KiB (120). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example pakrt22_1.png at 1,080 px wide, shown at 225 px. Resized copies would save about 246 KiB.

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

1 image (169 KiB) is 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.

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

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

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

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

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

Your title is only 24 characters: “HelloSmile – Hello Smile”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 161 pages on tryhellosmile.com and 9 external pages.

https://tryhellosmile.com/pages/helloween-bundle, https://tryhellosmile.com/collections/products, https://tryhellosmile.com/pages/our-story, https://tryhellosmile.com/pages/support-center, https://tryhellosmile.com/pages/paste-bundle and https://tryhellosmile.com/collections/paste-za-zube have no meta description, so Google writes the search snippet from whatever text it finds.

https://tryhellosmile.com/products/pasta-za-zube-vanila and https://tryhellosmile.com/products/pasta-za-zube-blackberry 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://tryhellosmile.com/pages/helloween-bundle, whose canonical is https://tryhellosmile.com/pages/halloween-bundle. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://tryhellosmile.com/pages/helloween-bundle, https://tryhellosmile.com/collections/products, https://tryhellosmile.com/pages/paste-bundle and https://tryhellosmile.com/collections/paste-za-zube 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.

21 of 80 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your homepage shows a map 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.

Social proof on the homepage: 12 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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 716 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 14 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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.