otty.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and cnnx.link and others), adding 591 KiB and 199 ms of main-thread time.

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

1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.

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.

Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Black Friday SaleNow Live! Save up to 20% on all our mattre…”.

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

Real visitors wait 201 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

The layout shifts by 0.207 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 2.3 MB in 132 requests on a phone: images 1.0 MB (69), scripts 835 KiB (37) and fonts 290 KiB (3). Under 2 MB keeps phones on slow connections fast.

TP-Star.svg 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.64 g of CO₂e: 76.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

Your title is 80 characters, so Google will cut it off around 60: “Hybrid Mattresses In A Box | 100 Night Trial & Fast Delivery | OTTY – OTTY Sleep”.

There are 2 <h1> headlines (“” and “Black Friday SaleNow Live!”). One clear main headline is easier for people and search engines.

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

The homepage links to 163 pages on otty.com and 21 external pages.

https://otty.com/products/otty-pure-hybrid-charcoal-bamboo-mattress and https://otty.com/products/otty-pure-3000-hybrid-bamboo-charcoal-mattress all use the title “Hybrid Bamboo Memory Foam Mattress With Charcoal – OTTY Sleep”. Search engines can't tell which page to show for a search, so each competes with the others.

https://otty.com/collections/bed-frames has no meta description, so Google writes the search snippet from whatever text it finds.

https://otty.com/products/otty-pure-hybrid-charcoal-bamboo-mattress and https://otty.com/products/otty-pure-3000-hybrid-bamboo-charcoal-mattress 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://otty.com/collections/single-hybrid-mattress-comparison, whose canonical is https://otty.com/collections/single-hybrid-mattresses. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://otty.com/collections has no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

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

The homepage carries about 903 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, 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.