petruscocaviar.com website review

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

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

8 third-party services load with your homepage (rebuyengine.com, Judge.me and userway.org and others), adding 1.7 MB and 448 ms of main-thread time.

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

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

rebuyengine.com costs a phone 127 ms of main-thread work and 703 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 1,703 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

18 KiB could be saved by minifying JavaScript.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 32.7 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 34.5 s. Good is under 3.8 s.

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

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

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

Your homepage downloads 6.5 MB in 328 requests on a phone: fonts 3.1 MB (5), scripts 1.4 MB (96) and other files 1.2 MB (183). Under 2 MB keeps phones on slow connections fast.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

5 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 120 pages on petruscocaviar.com and 5 external pages.

https://petruscocaviar.com/collections/japanese-a5-wagyu has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://petruscocaviar.com/collections/cheese/products/epoisses-aoc-burned-box-cheese, whose canonical is https://petruscocaviar.com/products/epoisses-aoc-burned-box-cheese. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 15 pages linked from your homepage (of 48 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: the server responded with a status of 400 ()”.

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

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

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