Website review, no card needed
dryfarmwines.com website review
Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 83 checks
This review found 36 issues worth fixing on dryfarmwines.com, 12 of them high impact, across 83 checks. The most urgent: page weight: 18.4 MB in 517 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78C- #62,179 of 124,078 reviewed websitesbeats 44%
- #40,565 of 69,765 online storesbeats 36%
- #38,732 of 63,454 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 136 ms |
| May 23, 2026 | 137 ms |
| May 30, 2026 | 132 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 129 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 129 ms |
| Aug 8, 2026 | 130 ms |
| Aug 15, 2026 | 136 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 140 ms |
| Sep 5, 2026 | 144 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 146 ms |
| Sep 26, 2026 | 153 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 173 ms |
| Oct 24, 2026 | 172 ms |
| Oct 31, 2026 | 171 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.3 s
2.6 s
3.9 s
5.2 s
6.5 s
7.8 s
9.1 s
10.4 s
Speed
Main-thread work: 8.0 s
A phone's processor spends 8.0 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Klaviyo and others), adding 3.0 MB and 1.8 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
999 KiBAbout 999 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
900 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Google Tag Manager adds 781 ms
781 msGoogle Tag Manager costs a phone 781 ms of main-thread work and 846 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.
Use efficient cache lifetimes
420 KiB28 files are served with short cache lifetimes, so returning visitors download them again (420 KiB).
ZenDesk adds 361 ms
361 msZenDesk costs a phone 361 ms of main-thread work and 479 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.
Klaviyo adds 211 ms
211 msKlaviyo costs a phone 211 ms of main-thread work and 317 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.
2,050 HTML elements
The page has 2,050 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 68 ms
68 msShopify costs a phone 68 ms of main-thread work and 812 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 226 ms. During a long task the page ignores taps.
Legacy JavaScript
58 KiBPolyfills for old browsers add 58 KiB JavaScript that modern phones do not need.
Reduce unused CSS
22 KiBAbout 22 KiB of CSS is downloaded but never applied on this page.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 28.9 s
28.9 sThe page becomes fully interactive after 28.9 s. Good is under 3.8 s.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A long table draped with a cream tablecloth, styled with ca…”.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 842 ms
842 msScripts block taps and scrolling for 842 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 136 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 567 ms
567 msReal visitors wait 567 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 18.4 MB in 517 requests
18.4 MBYour homepage downloads 18.4 MB in 517 requests on a phone: media 13.0 MB (2), scripts 2.7 MB (135) and other files 1.5 MB (280). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (45 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 5.2 g of CO₂ per visit
5.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.22 g of CO₂e: 626.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Sugar-Free, Low Alcohol, Low Sulfite Artisan Wine | Dry Farm Wines”.
2 H1 headlines
There are 2 <h1> headlines (“” and “What Our Members Say...”). One clear main headline is easier for people and search engines.
Meta description is long (208 characters)
Your meta description is 208 characters; Google truncates after about 160, so the end of your pitch is cut.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
93 internal links, 5 external
The homepage links to 93 pages on dryfarmwines.com and 5 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.dryfarmwines.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.dryfarmwines.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,105 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.dryfarmwines.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.dryfarmwines.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.dryfarmwines.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://www.dryfarmwines.com/collections/exclusive-artisan-wine-collections, https://www.dryfarmwines.com/customer_authentication/redirect, https://www.dryfarmwines.com/pages/by-the-bottle-holiday and https://www.dryfarmwines.com/collections/holiday-gift-collection-2026 have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.dryfarmwines.com/collections/shop-all, whose canonical is https://www.dryfarmwines.com/collections/all. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages without an H1
https://www.dryfarmwines.com/customer_authentication/redirect, https://www.dryfarmwines.com/products/complete-thanksgiving-collection, https://www.dryfarmwines.com/pages/by-the-bottle-holiday, https://www.dryfarmwines.com/products/cervo and https://www.dryfarmwines.com/collections/holiday-gift-collection-2026 have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.dryfarmwines.com/collections/shop-all took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5712893&tm=gtm002&Ver=2&mid=d559cc94-9015-4682-b4bb-9228c3ae5f03&bo=1&sid=fb16ec80dabc11f1b7996bbcc90b6621&vid=fb170230dabc11f1bed265f0d5bf3bd5&vids=1&msclkid=N&pi=918.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
15 of 15 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,449 words of copy
The homepage carries about 1,449 words of visible text.
3 checks passed
13 calls to action
The homepage has 13 calls to action, for example “Shop All”, “First time? Start Here →” and “Bottle Shop”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 5 mores (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.
30 cookies set on arrival
30Opening the homepage sets 30 cookies, 3 of them by other companies (measured from a US location before any click).
54 other companies contacted
Loading the homepage contacts 54 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at dryfarmwines.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Elevar Conversion Tracking · Yotpo Product Reviews · Okendo · Hulk Form Builder · Klaviyo Email Marketing Sms · Gift Box Builder · rise-ai.com · amazonaws.com · rechargecdn.com · getsitecontrol.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Napa
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on dryfarmwines.com, including 17 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.