cwspirits.com website review

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

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

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

The page has 3,227 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

8 third-party services load with your homepage (rebuyengine.com, Google Tag Manager and blackcrow.ai and others), adding 1.4 MB and 954 ms of main-thread time.

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

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

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

rebuyengine.com costs a phone 217 ms of main-thread work and 329 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 237 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.

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

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

29 KiB could be saved by minifying CSS.

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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Online Liquor Store — Buy Alcohol Online with Nationwi…”.

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

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

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

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

11 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-31, real Chrome visitors' tap response (inp) went from 117 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.2 MB in 279 requests on a phone: scripts 1.4 MB (90), images 1.2 MB (65) and other files 780 KiB (91). Under 2 MB keeps phones on slow connections fast.

soda-jerk-2025.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

6 images (672 KiB) 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.

5 images are downloaded at several times the size a phone draws them, for example soda-jerk-2025.webp at 1,191 px wide, shown at 390 px. Resized copies would save about 22 KiB.

8 images further down the page (239 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 1.20 g of CO₂e: 144.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is 72 characters, so Google will cut it off around 60: “Online Liquor Store | Buy Wine & Spirits Online – Country Wine & Spirits”.

There is no robots.txt at cwspirits.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 380 pages on cwspirits.com and 7 external pages.

/pages/product-finder, /pages/media-kit-new and /pages/order-tracking use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /pages/media-kit-new, whose canonical is /pages/media-kit. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/price-match, /collections/sale and /pages/order-tracking have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/sale and /collections/tequila took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=148009561&Ver=2&mid=e8477ca4-c244-46ee-a5d2-bb27563da09f&bo=1&sid=b849e8f0d88811f18c3d47dec6173ceb&vid=b849faf0d88811f199deab0e897b0843&vids=1&msclkid=N&pi=918639831&l.

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

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'replace')”.

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.

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

The homepage carries about 2,261 words of visible text.

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