smileperfect.us website review

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.2 s faster on a phone.

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

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

YouTube costs a phone 1.2 s of main-thread work and 2.5 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.

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Clarity and others), adding 144.3 MB and 2.8 s of main-thread time.

Shopify costs a phone 139 ms of main-thread work and 140.7 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.

About 301 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

Clarity costs a phone 548 ms of main-thread work and 29 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 357 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (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 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

Your largest element takes 60.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TEETH STRAIGHTENING MADE EASY CLEAR ALIGNERS AT AFFORDABLE …”.

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

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

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

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

Your homepage downloads 146.0 MB in 581 requests on a phone: media 124.8 MB (27), images 15.7 MB (161) and scripts 3.3 MB (115). Under 2 MB keeps phones on slow connections fast.

22 images weigh 40.6 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example image3_1.jpg at 1,002 px wide, shown at 170 px. Resized copies would save about 970 KiB.

29 images (41.8 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.

6 images further down the page (1.1 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 41.37 g of CO₂e: 4964.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

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

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

2 frames have no title, so screen-reader users cannot tell what they contain.

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

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

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

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

Your title is 78 characters, so Google will cut it off around 60: “Clear Aligners in USA | Teeth Straightening | Invisible Braces – Smile Perfect”.

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

There are 2 <h1> headlines (“Clear Aligners at Affordable Prices!” and “FROM_JS”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 79 pages on smileperfect.us and 29 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://smileperfect.us/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.

Your homepage links to https://smileperfect.us/products/pay-at-once, which answers with an error. Visitors hit a dead end and search engines drop it.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://smileperfect.us/products/day-time-both-arch, whose canonical is https://smileperfect.us/products/affordable-clear-aligners-day-time-dual-arch. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 image failed to load on a phone, for example https://smileperfect.us/.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://smileperfect.us/cdn/shop/t/2/assets/responsive.css?v=4492' because its MIME type (…”.

10 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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.

The homepage carries about 939 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 19 cookies, 1 of them by other companies (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 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.