wildmandrinking.com website review

About 3.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.5 s faster on a phone.

YouTube costs a phone 2.3 s of main-thread work and 4.7 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.

About 144 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

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

61 images could be 17.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (YouTube, Shopify and Mailchimp and others), adding 9.0 MB and 3.3 s of main-thread time.

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

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

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

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

38 KiB could be saved by minifying JavaScript.

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

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

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

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

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Your homepage downloads 27.6 MB in 371 requests on a phone: images 18.4 MB (73), scripts 5.1 MB (125) and media 1.9 MB (1). Under 2 MB keeps phones on slow connections fast.

12 images weigh 16.7 MB together. On a phone connection a single image that size takes seconds.

13 images (15.2 MB) 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 7.83 g of CO₂e: 939.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

Your title is only 25 characters: “Wild Man Drinking Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 64 pages on wildmandrinking.com and 10 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://wildmandrinking.com/products/the-krakin and https://wildmandrinking.com/products/test-product-1 all use the title “The Krak'in 2.0 - Beer Shotgun Tool with Built-in Funnel – Wild Man D…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://wildmandrinking.com/collections/original-products, https://wildmandrinking.com/collections/verified-products, https://wildmandrinking.com/collections/experimental-drinking-products, https://wildmandrinking.com/collections/merchandise-items-clothing and https://wildmandrinking.com/products/krakin-platinum have no meta description, so Google writes the search snippet from whatever text it finds.

https://wildmandrinking.com/products/the-krakin and https://wildmandrinking.com/products/test-product-1 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 https://wildmandrinking.com/products/test-product-1, whose canonical is https://wildmandrinking.com/products/the-krakin. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://wildmandrinking.com/products/cocktail-shaker, https://wildmandrinking.com/products/the-krakin, https://wildmandrinking.com/products/custom-krakin, https://wildmandrinking.com/products/riptide-the-shotgun-bottle, https://wildmandrinking.com/pages/all-products and https://wildmandrinking.com/collections/original-products and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://wildmandrinking.com/products/the-krakin, https://wildmandrinking.com/collections/original-products, https://wildmandrinking.com/collections/verified-products, https://wildmandrinking.com/collections/experimental-drinking-products, https://wildmandrinking.com/collections/merchandise-items-clothing and https://wildmandrinking.com/products/krakin-platinum and 2 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 27 found) and read each the way a search engine does.

7 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 5 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 602 words of visible text.

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