vsattui.com website review

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

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

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

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

Your mobile performance score is 31 (desktop: 40). 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 CDN, Google Tag Manager and ecellar-rw.com and others), adding 2.1 MB and 1.6 s of main-thread time.

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

Google Tag Manager costs a phone 458 ms of main-thread work and 512 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 346 ms. During a long task the page ignores taps.

ecellar-rw.com costs a phone 300 ms of main-thread work and 220 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.

userway.org costs a phone 104 ms of main-thread work and 303 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 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 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).

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

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.

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.

Your largest element takes 32.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use essential cookies to make our site work. With your c…”.

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

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

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

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

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your homepage downloads 10.8 MB in 199 requests on a phone: images 7.3 MB (35), scripts 2.1 MB (65) and other files 601 KiB (36). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (241 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 3.06 g of CO₂e: 367.3 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.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

There are 10 <h1> headlines (“A Napa Valley Tradition”, “Celebrating 50 Years of Purpose and Connection in…” and “Wines of Quality, Character and Diversity”). One clear main headline is easier for people and search engines.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 151 pages on vsattui.com and 12 external pages.

There is no https://www.vsattui.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.vsattui.com/category/products/all_red_wines, https://www.vsattui.com/category/products/all_white_wines, https://www.vsattui.com/category/products/rose_wine, https://www.vsattui.com/category/products/sparkling_wine, https://www.vsattui.com/category/products/dessert_wine and https://www.vsattui.com/category/products/reserve_wine and 4 others all use the title “Shop Category | V. Sattui Winery”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.vsattui.com/category/products/all_red_wines, https://www.vsattui.com/category/products/all_white_wines, https://www.vsattui.com/category/products/rose_wine, https://www.vsattui.com/category/products/sparkling_wine, https://www.vsattui.com/category/products/dessert_wine and https://www.vsattui.com/category/products/reserve_wine and 4 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 10 pages by a URL that isn't their canonical one, for example https://www.vsattui.com/category/products/all_red_wines, whose canonical is https://www.vsattui.com/category. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.vsattui.com/shop, https://www.vsattui.com/category/products/all_red_wines, https://www.vsattui.com/category/products/all_white_wines, https://www.vsattui.com/category/products/rose_wine, https://www.vsattui.com/category/products/sparkling_wine and https://www.vsattui.com/category/products/dessert_wine and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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

Opening the homepage sets 5 cookies (measured from a US location before any click).

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