Website review, no card needed
goodclean.wine website review
Visit site (opens in a new tab)Reviewed 8 November 202633 issues · 78 checks
This review found 33 issues worth fixing on goodclean.wine, 6 of them high impact, across 78 checks. The most urgent: render-blocking 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
85B- #16,261 of 120,375 reviewed websitesbeats 82%
- #10,304 of 68,150 online storesbeats 79%
- #10,009 of 62,105 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 82
82/100Your mobile performance score is 82. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 424 KiB12 images could be 424 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused JavaScript
300 ms · 223 KiBAbout 223 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Klaviyo adds 168 ms
168 msKlaviyo costs a phone 168 ms of main-thread work and 609 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.
6 third-party services on the page
6 third-party services load with your homepage (Klaviyo, jQuery CDN and Shopify and others), adding 827 KiB and 204 ms of main-thread time.
Reduce unused CSS
150 ms · 71 KiBAbout 71 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.
Minify JavaScript
150 ms · 40 KiB40 KiB could be saved by minifying JavaScript.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 64 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
18 KiB4 files are served with short cache lifetimes, so returning visitors download them again (18 KiB).
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 678 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 10.6 s
10.6 sThe page becomes fully interactive after 10.6 s. Good is under 3.8 s.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.017
0.017The layout barely moves while loading (CLS 0.017, good is under 0.1).
Total Blocking Time: 7 ms
7 msScripts block the page for only 7 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.0 MB in 222 requests
3.0 MBYour homepage downloads 3.0 MB in 222 requests on a phone: images 1.1 MB (41), scripts 881 KiB (75) and other files 756 KiB (89). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
348 KiB2 images are downloaded at several times the size a phone draws them, for example best-natural-wine.webp at 1,200 px wide, shown at 70 px. Resized copies would save about 348 KiB.
1 image in older formats
1 image (328 KiB) is 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.
About 0.9 g of CO₂ per visit
0.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.86 g of CO₂e: 103.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
Elements must only use permitted ARIA attributes (13 elements)
Elements must only use permitted ARIA attributes: 13 elements on the page fail this check, rated serious by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements marked as presentational should be consistently ignored (4 elements)
Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 32 images in the HTML carry an alt attribute.
45 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: 45 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (257 characters)
Your meta description is 257 characters; Google truncates after about 160, so the end of your pitch is cut.
36 internal links, 5 external
The homepage links to 36 pages on goodclean.wine and 5 external pages.
6 checks passed
One H1 headline
Your main headline reads: “wine that's easy to love.”.
Title: 62 characters
Your title is a healthy 62 characters: “Good Clean Wine - The Truth About 'Clean Wine' & Italian Wines”.
Canonical URL set
The canonical URL is https://goodclean.wine/.
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://goodclean.wine/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
Some text only appears after JavaScript runs
54%The HTML your server sends has 420 of the 781 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
2 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.
llms.txt published
The site publishes https://goodclean.wine/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://goodclean.wine/collections/frontpage/products/rose-bundle and https://goodclean.wine/collections/frontpage/products/synchronized-swimming all use the title “Synchronized Swimming: The Best Clean Rosé – Good Clean Wine”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages share a meta description
https://goodclean.wine/blogs/news, https://goodclean.wine/policies/privacy-policy, https://goodclean.wine/policies/terms-of-service and https://goodclean.wine/policies/shipping-policy use the same meta description. A description written for each page earns more clicks.
7 links to non-canonical URLs
Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://goodclean.wine/collections/frontpage/products/good-clean-cabernet, whose canonical is https://goodclean.wine/products/good-clean-cabernet. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://goodclean.wine/pages/about has no <h1> headline, so visitors and search engines get no clear main topic.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 14 pages we checked loaded without an error.
Every page has a meta description
All 14 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'split')”.
2 checks passed
Tap targets are thumb-sized
102 of 104 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 781 words of copy
The homepage carries about 781 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SUBSCRIBE” and “shop best sellers”.
4 calls to action
The homepage has 4 calls to action, for example “Shop”, “Contact” and “shop best sellers”.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
No consent tool detected
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.
15 other companies contacted
Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 goodclean.wine, 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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Okendo · Klaviyo Email Marketing Sms
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
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Springfield
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on goodclean.wine, including 10 speed issues, 2 SEO issues and 2 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.