jwine.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and commerce7.com and others), adding 3.7 MB and 2.1 s of main-thread time.

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

Google CDN costs a phone 680 ms of main-thread work and 1.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.

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

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

commerce7.com costs a phone 276 ms of main-thread work and 530 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.

redchirp.com costs a phone 31 ms of main-thread work and 312 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 190 ms. During a long task the page ignores taps.

19 KiB could be saved by minifying CSS.

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

6 KiB could be saved by minifying JavaScript.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (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.

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 first text or image appears after 9.9 s on a phone. Good is under 1.8 s.

Your largest element takes 68.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “J and the Golden State Valkyries”.

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

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

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

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

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

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

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

Your homepage downloads 22.4 MB in 175 requests on a phone: images 17.4 MB (39), scripts 3.3 MB (61) and other files 848 KiB (42). Under 2 MB keeps phones on slow connections fast.

4 images weigh 14.6 MB together. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example JVW_DEC2023_WebRefresh_Homepage_Events_2310x980.gif at 2,310 px wide, shown at 390 px. Resized copies would save about 9.5 MB.

13 images further down the page (15.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

13 images (13.8 MB) are 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 6.35 g of CO₂e: 761.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

There are 4 <h1> headlines (“October’s Pairing:”, “A Chill After Dark” and “Forty years of growth, exploration, and transform…”). One clear main headline is easier for people and search engines.

17 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 60 pages on jwine.com and 8 external pages.

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

/find-near-me, /shop, /product/j-vineyards-gift-card, /visit/legacy-tasting and /visit/signature-tasting have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /shop, whose canonical is /collection/wines. 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 42 found) and read each the way a search engine does.

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

3 errors were logged to the browser console while the page loaded, for example “fbq is not defined”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 9 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.