goodpour.com website review

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

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

14 images could be 583 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

185 KiB could be saved by minifying JavaScript.

8 third-party services load with your homepage (calconic.com, Shopify and Klaviyo and others), adding 1.7 MB and 591 ms of main-thread time.

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

calconic.com costs a phone 390 ms of main-thread work and 1.0 MB 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.

1 long task block the main thread while loading, the longest for 435 ms. During a long task the page ignores taps.

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

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

About 38 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 100 ms faster on a phone.

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

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.

Your largest element takes 17.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

Your homepage downloads 3.8 MB in 227 requests on a phone: scripts 1.7 MB (73), images 898 KiB (34) and other files 879 KiB (98). Under 2 MB keeps phones on slow connections fast.

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

9 elements hidden from screen readers can still receive keyboard focus.

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 368 pages on goodpour.com and 22 external pages.

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.

https://goodpour.com/products/la-marca-prosecco, https://goodpour.com/collections/wine and https://goodpour.com/collections/red-wine have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://goodpour.com/pages/buy-one-help-others, whose canonical is https://goodpour.com/pages/good-pour-app. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://goodpour.com/pages/college-park, https://goodpour.com/pages/longwood, https://goodpour.com/pages/gainesville, https://goodpour.com/pages/naples, https://goodpour.com/pages/tgp-winter-park and https://goodpour.com/pages/buy-one-help-others and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://goodpour.com/pages/college-park, https://goodpour.com/pages/longwood, https://goodpour.com/pages/gainesville, https://goodpour.com/pages/naples, https://goodpour.com/pages/tgp-winter-park and https://goodpour.com/pages/buy-one-help-others and 6 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image failed to load on a phone, for example https://goodpour.com/.

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

Social proof on the homepage: 47 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 520 words of visible text.

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