envoyerfinewines.com website review

6 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.7 s faster on a phone.

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

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

About 166 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

8 third-party services load with your homepage (Google CDN, Shopify and onltr.app and others), adding 2.0 MB and 304 ms of main-thread time.

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

onltr.app costs a phone 51 ms of main-thread work and 1.6 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.

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

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

About 38 KiB of CSS is downloaded but never applied on this page.

10 KiB could be saved by minifying JavaScript.

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

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 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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.

XRFNx8u5kg.jpg weighs 1.1 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example XRFNx8u5kg.jpg at 2,880 px wide, shown at 175 px. Resized copies would save about 1.1 MB.

Your homepage downloads 3.5 MB in 176 requests on a phone: images 1.8 MB (20), scripts 806 KiB (50) and other files 760 KiB (94). Under 2 MB keeps phones on slow connections fast.

1 image (1.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 0.98 g of CO₂e: 117.6 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.

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

<html> element must have a lang attribute: 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: 6 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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), which makes the page harder to scan with a screen reader.

Your meta description is only 44 characters: “Fine Wines, Delivered Directly to Your Door.”. 70 to 160 characters is enough to sell the click.

Structured data found (Corporation and Organization) but with 4 problems, for example “Corporation: logo is not an absolute URL ("//www.envoyerfinewines.com/cdn/shopifycloud/storefront/a…”.

Your <h1> is empty.

The homepage links to 57 pages on envoyerfinewines.com and 0 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.envoyerfinewines.com/products/2022-louis-jadot-corton-pougets-domaine-des-heritiers-louis-jadot-eta-w-o-7-21-2025 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.

/ and https://www.envoyerfinewines.com/products/2022-louis-jadot-corton-pougets-domaine-des-heritiers-louis-jadot-eta-w-o-7-21-2025 all use the title “Envoyer Fine Wines – Envoyer Imports”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.envoyerfinewines.com/collections/all, https://www.envoyerfinewines.com/pages/about-us, https://www.envoyerfinewines.com/collections/new-arrivals, https://www.envoyerfinewines.com/collections/trying-to-fill-your-case-check-out-our-30-and-under-items, https://www.envoyerfinewines.com/collections/premier-cru-1 and https://www.envoyerfinewines.com/collections/last-chance and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.envoyerfinewines.com/collections and https://www.envoyerfinewines.com/products/2022-louis-jadot-corton-pougets-domaine-des-heritiers-louis-jadot-eta-w-o-7-21-2025 use the same meta description. A description written for each page earns more clicks.

https://www.envoyerfinewines.com/pages/ordering-contact, https://www.envoyerfinewines.com/collections/all, https://www.envoyerfinewines.com/collections, https://www.envoyerfinewines.com/pages/about-us, https://www.envoyerfinewines.com/collections/new-arrivals and https://www.envoyerfinewines.com/collections/trying-to-fill-your-case-check-out-our-30-and-under-items and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 15 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.

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 555 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 Analytics and Google Tag Manager (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 9 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.