passmorecaviar.com website review

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

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

7 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 third-party services load with your homepage (Bold Commerce, Facebook and monkcommerce.app and others), adding 2.2 MB and 716 ms of main-thread time.

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

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

Bold Commerce costs a phone 177 ms of main-thread work and 485 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.

monkcommerce.app costs a phone 129 ms of main-thread work and 542 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.

Vimeo costs a phone 109 ms of main-thread work and 527 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.

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

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

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

11 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 27.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 7.5 MB in 246 requests on a phone: images 3.9 MB (22), scripts 2.4 MB (98) and other files 773 KiB (108). Under 2 MB keeps phones on slow connections fast.

Caviar_Bumps-high_2_540x.gif weighs 3.1 MB. On a phone connection a single image that size takes seconds.

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

1 element hidden from screen readers can still receive keyboard focus.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 8 characters: “PASSMORE”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 57 pages on passmorecaviar.com and 6 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.

Your homepage links to https://passmorecaviar.com/pages/circle41 and https://passmorecaviar.com/products/smoked-white-sturgeon, which answer with an error. Visitors hit a dead end and search engines drop them.

/ and https://passmorecaviar.com/apps/loyalty all use the title “PASSMORE”. Search engines can't tell which page to show for a search, so each competes with the others.

https://passmorecaviar.com/collections/passmore-ranch-caviar, https://passmorecaviar.com/collections/curated-caviar, https://passmorecaviar.com/collections/frontpage, https://passmorecaviar.com/pages/new-passmore-professional-program and https://passmorecaviar.com/apps/loyalty have no meta description, so Google writes the search snippet from whatever text it finds.

https://passmorecaviar.com/pages/subscribe-save-benefits-details, https://passmorecaviar.com/pages/new-passmore-professional-program and https://passmorecaviar.com/apps/loyalty have no <h1> headline, so visitors and search engines get no clear main topic.

https://passmorecaviar.com/collections/passmore-ranch-caviar, https://passmorecaviar.com/collections/frontpage, https://passmorecaviar.com/collections/accompaniments and https://passmorecaviar.com/apps/loyalty 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.

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

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

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

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

2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

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.

Social proof on the homepage: 24 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

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

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

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

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