zyppah.com website review

About 597 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.

184 KiB could be saved by minifying JavaScript.

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

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

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

13 images could be 392 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

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

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

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

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

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

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

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

4 KiB could be saved by minifying CSS.

Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “anti snoring device”.

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

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

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

12 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 126 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 22.9 MB in 300 requests on a phone: media 19.6 MB (6), scripts 1.5 MB (117) and other files 844 KiB (104). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example nascar_wht.png at 6,472 px wide, shown at 94 px. Resized copies would save about 250 KiB.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

There are 2 <h1> headlines (“” and “Stop Snoring FAST”). One clear main headline is easier for people and search engines.

The homepage links to 53 pages on zyppah.com and 1 external page.

https://zyppah.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://zyppah.com/products/original-zyppah-anti-snoring-mouthpiece 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://zyppah.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://zyppah.com/products/original-zyppah-anti-snoring-mouthpiece all use the title “Zyppah Anti Snoring Mouthguard”. Search engines can't tell which page to show for a search, so each competes with the others.

https://zyppah.com/collections/all, https://zyppah.com/customer_authentication/redirect, https://zyppah.com/policies/shipping-policy, https://zyppah.com/collections/snoring-solutions, https://zyppah.com/pages/shop-hsa-fsa and https://zyppah.com/pages/the-science and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://zyppah.com/products/mouth-tape-3-month-supply and https://zyppah.com/products/mouth-tape-180-day-supply use the same meta description. A description written for each page earns more clicks.

https://zyppah.com/customer_authentication/redirect, https://zyppah.com/pages/the-science and https://zyppah.com/pages/reviews have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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