Website review, no card needed

drippingspringsdistilling.com logo

drippingspringsdistilling.com website review

Visit site (opens in a new tab)Reviewed 21 November 202637 issues · 89 checks

This review found 37 issues worth fixing on drippingspringsdistilling.com, 12 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.4 s1.9 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.1 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20261.9 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.1 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.4 s
Nov 7, 20262.3 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
90 ms67 msMay 30Nov 1487 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202686 ms
Jun 20, 202683 ms
Jun 27, 202683 ms
Jul 4, 202686 ms
Jul 11, 202682 ms
Jul 18, 202679 ms
Jul 25, 202679 ms
Aug 1, 202678 ms
Aug 8, 202678 ms
Aug 15, 202678 ms
Aug 22, 202678 ms
Aug 29, 202674 ms
Sep 5, 202671 ms
Sep 12, 202675 ms
Sep 19, 202675 ms
Sep 26, 202675 ms
Oct 3, 202671 ms
Oct 10, 202670 ms
Oct 17, 202671 ms
Oct 24, 202679 ms
Oct 31, 202684 ms
Nov 7, 202687 ms
Nov 14, 202687 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

Full-page screenshot of drippingspringsdistilling.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drippingspringsdistilling.com at 0.4 s0.4 s
  2. drippingspringsdistilling.com at 0.8 s0.8 s
  3. drippingspringsdistilling.com at 1.1 s1.1 s
  4. drippingspringsdistilling.com at 1.5 s1.5 s
  5. drippingspringsdistilling.com at 1.9 s1.9 s
  6. drippingspringsdistilling.com at 2.3 s2.3 s
  7. drippingspringsdistilling.com at 2.6 s2.6 s
  8. drippingspringsdistilling.com at 3.0 s3.0 s

Speed

9 to fix56
  • Reduce unused JavaScript

    2.6 s · 914 KiB

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

  • Render-blocking requests

    1.6 s

    59 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • Mobile performance score: 56

    56/100

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

  • Reduce unused CSS

    600 ms · 249 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Facebook and Google Tag Manager and others), adding 1.7 MB and 642 ms of main-thread time.

  • YouTube adds 318 ms

    318 ms

    YouTube costs a phone 318 ms of main-thread work and 1,016 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

    345 KiB

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

  • Facebook adds 179 ms

    179 ms

    Facebook costs a phone 179 ms of main-thread work and 372 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.

  • Main-thread work: 2.1 s

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

  • Improve image delivery

    174 KiB

    4 images could be 174 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 6 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    11 KiB

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

  • Minify CSS

    6 KiB

    6 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user CLS: 1.00

    1.00

    For real visitors the layout shifts by 1.00 (75th percentile). Good is under 0.1.

  • First Contentful Paint: 10.3 s

    10.3 s

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

  • Largest Contentful Paint: 10.3 s

    10.3 s

    Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ARE YOU AT LEAST 21 YEARS OLD?”.

  • Time to Interactive: 25.1 s

    25.1 s

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

  • Speed Index: 11.5 s

    11.5 s

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

  • Real-user LCP: 2.6 s

    2.6 s

    Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user TTFB: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 95 ms

    95 ms

    Real visitors wait 95 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 21 ms

    21 ms

    Scripts block the page for only 21 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix64
  • Page weight: 22.5 MB in 178 requests

    22.5 MB

    Your homepage downloads 22.5 MB in 178 requests on a phone: media 17.8 MB (3), scripts 1.9 MB (52) and images 1.6 MB (23). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    3-Bottle-Ship-to-Home-Image-768x833.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (45 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 6.4 g of CO₂ per visit

    6.36 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8694
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 9 text elements with low contrast

    9 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 (14 elements)

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 10 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4, 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 21 images in the HTML carry an alt attribute.

  • 48 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: 48 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9281
  • 5 H1 headlines

    There are 5 <h1> headlines (“SAVOR IT.”, “VISIT US” and “SHIP TO YOU”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (Organization and VideoObject) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://drippingspringsdistilling.com/sitemap.rss, so Google discovers your pages only by following links.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 79 internal links, 22 external

    The homepage links to 79 pages on drippingspringsdistilling.com and 22 external pages.

4 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “OUR AWARD-WINNING TEXAS VODKA INVITES YOU TO SLOW DOWN AND ENJOY WHAT MATTERS MOST IN LIFE BECAUSE WE TAKE OUR TIME SO …”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Dripping Springs Vodka - Award winning Texas Vodka”.

  • Canonical URL set

    The canonical URL is https://drippingspringsdistilling.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

3 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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,135 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://drippingspringsdistilling.com/llms.txt (75 KiB, 324 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 2 pages without a meta description

    https://drippingspringsdistilling.com/book-a-tour and https://drippingspringsdistilling.com/events have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages slow to respond

    https://drippingspringsdistilling.com/our-spirits, https://drippingspringsdistilling.com/where-to-buy, https://drippingspringsdistilling.com/visit-us, https://drippingspringsdistilling.com/book-a-tour, https://drippingspringsdistilling.com/newsroom and https://drippingspringsdistilling.com/products/dripping-springs-vodka took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 5 third-party cookies

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

  • 3 JavaScript errors while loading

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

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    6 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • 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 441 words of copy

    The homepage carries about 441 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START SIPPING”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “BUY NOW”, “BOOK A TOUR” and “BOOK YOUR EVENT”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies, 1 of them by other companies (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.

  • 18 other companies contacted

    Loading the homepage contacts 18 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 drippingspringsdistilling.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

Company

Headquarters
Dripping Springs

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on drippingspringsdistilling.com, including 17 speed issues, 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25