vitalsleep.com website review

audioeye.com costs a phone 2.9 s of main-thread work and 301 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.

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

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

8 third-party services load with your homepage (audioeye.com, Google Tag Manager and Klaviyo and others), adding 11.0 MB and 4.4 s of main-thread time.

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

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

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

Shopify costs a phone 40 ms of main-thread work and 9.3 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 793 KiB of JavaScript is downloaded but never used on this page.

Klaviyo costs a phone 312 ms of main-thread work and 533 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.

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

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

12 images could be 171 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need.

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.

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

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

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

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

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

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

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

Your homepage downloads 20.1 MB in 306 requests on a phone: media 16.2 MB (3), scripts 2.0 MB (104) and other files 834 KiB (128). Under 2 MB keeps phones on slow connections fast.

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

1 image (191 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 5.69 g of CO₂e: 682.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

button, link, and menuitem elements do not have accessible names. (1 element).

There are 2 <h1> headlines (“Your Snoring Keeps Two People Awake. VitalSleep H…” and “Quieter Nights for You Both. Try It for 60 Nights”). One clear main headline is easier for people and search engines.

The homepage links to 56 pages on vitalsleep.com and 9 external pages.

https://www.vitalsleep.com/discount/sleepwell10 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://www.vitalsleep.com/pages/fit-quiz and https://www.vitalsleep.com/pages/how-vitalsleep-works are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://www.vitalsleep.com/discount/sleepwell10 all use the title “Quieter Nights Start Here | VitalSleep® Anti-Snoring Device”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.vitalsleep.com/pages/how-a-snoring-mouthpiece-works and https://www.vitalsleep.com/pages/how-it-works use the same meta description. A description written for each page earns more clicks.

https://www.vitalsleep.com/pages/find-my-snoring-solution has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.vitalsleep.com/pages/find-my-snoring-solution has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

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

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

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

The homepage carries about 1,952 words of visible text.

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