moderncellars.com website review

Google CDN costs a phone 1.2 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Your mobile performance score is 43. 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 Clarity and others), adding 2.2 MB and 3.4 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page.

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

12 images could be 776 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.

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

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

Clarity costs a phone 286 ms of main-thread work and 29 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.

tfaforms.com costs a phone 259 ms of main-thread work and 205 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.

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

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

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

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

11 KiB could be saved by minifying JavaScript.

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.

4 KiB could be saved by minifying CSS.

2 KiB JavaScript is shipped twice across bundles.

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

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

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

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

Your largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our signature gold finish is expanding. With the introducti…”.

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 106 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.6 MB in 246 requests on a phone: images 2.8 MB (26), scripts 2.4 MB (90) and other files 1.0 MB (88). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example The_Tasting_10_Walnut_Gold.png at 2,048 px wide, shown at 322 px. Resized copies would save about 1.1 MB.

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

5 images (422 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.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is 71 characters, so Google will cut it off around 60: “Custom Wine Cellars, Wine Storage & Displays – Millesime Modern Cellars”.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 115 pages on moderncellars.com and 4 external pages.

There is no https://moderncellars.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.

We fetched 15 pages linked from your homepage (of 58 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=187144134&tm=gtm002&Ver=2&mid=fed983f7-3512-4479-a5a6-ef74a69672ae&bo=1&sid=b207c880dae611f1a0d0ebb8cbf756f3&vid=b2080390dae611f18700176f08c0c45b&vids=1&msclkid=N&gtm_.

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.tfaforms.com/dist/form-builder/5.0.0/wforms-layout.css?v=52130' from origin 'h…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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