omcaviar.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Stamped.io and rebuyengine.com and others), adding 20.8 MB and 2.1 s of main-thread time.

videowise.com costs a phone 159 ms of main-thread work and 18.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.

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

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

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

Stamped.io costs a phone 462 ms of main-thread work and 520 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.

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

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

rebuyengine.com costs a phone 356 ms of main-thread work and 700 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 320 ms. During a long task the page ignores taps.

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

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

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

28 KiB could be saved by minifying JavaScript.

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.

3 KiB could be saved by minifying CSS.

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 27.8 s. Good is under 3.8 s.

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

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

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

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

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

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

Your homepage downloads 25.0 MB in 388 requests on a phone: media 19.2 MB (3), scripts 2.1 MB (119) and images 1.5 MB (38). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

All page content should be contained by landmarks: 276 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.

Elements with visible text labels do not have matching accessible names. (1 element).

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 42 pages on omcaviar.com and 3 external pages.

The HTML your server sends has 725 of the 1,455 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://omcaviar.com/pages/art-directed and https://omcaviar.com/pages/who-we-are all use the title “About OM Caviar”. Search engines can't tell which page to show for a search, so each competes with the others.

https://omcaviar.com/policies/refund-policy has no meta description, so Google writes the search snippet from whatever text it finds.

https://omcaviar.com/pages/art-directed and https://omcaviar.com/pages/who-we-are 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://omcaviar.com/pages/art-directed, whose canonical is https://omcaviar.com/pages/who-we-are. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://omcaviar.com/pages/loyalty, https://omcaviar.com/pages/faqs and https://omcaviar.com/pages/ingredients have 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.

https://omcaviar.com/collections/shop-all took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355051575&tm=gtm002&Ver=2&mid=7ce738b0-aced-4e4f-b34c-75b7852521f4&bo=1&sid=19d63930df1a11f19e0b9d0f83f9cb78&vid=19d653a0df1a11f1b9dc57dc4d1d436f&vids=1&msclkid=N&pi=9.

10 of 37 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.”).

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'offsetTop')”.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 1,455 words of visible text.

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