Website review, no card needed

fourwallswhiskey.com logo

fourwallswhiskey.com website review

Visit site (opens in a new tab)Reviewed 8 November 202629 issues · 76 checks

This review found 29 issues worth fixing on fourwallswhiskey.com, 7 of them high impact, across 76 checks. The most urgent: page weight: 8.7 MB in 211 requests. 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
1.3 s883 msMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.1 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.1 s
Sep 26, 20261.0 s
Oct 3, 2026945 ms
Oct 10, 2026936 ms
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
141 ms117 msMay 16Oct 31136 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026129 ms
May 23, 2026128 ms
May 30, 2026129 ms
Jun 6, 2026130 ms
Jun 13, 2026124 ms
Jun 20, 2026128 ms
Jun 27, 2026123 ms
Jul 4, 2026120 ms
Jul 11, 2026126 ms
Jul 18, 2026128 ms
Jul 25, 2026128 ms
Aug 1, 2026129 ms
Aug 8, 2026132 ms
Aug 15, 2026137 ms
Aug 22, 2026137 ms
Aug 29, 2026138 ms
Sep 5, 2026134 ms
Sep 12, 2026125 ms
Sep 19, 2026126 ms
Sep 26, 2026127 ms
Oct 3, 2026128 ms
Oct 10, 2026129 ms
Oct 17, 2026129 ms
Oct 24, 2026129 ms
Oct 31, 2026136 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 fourwallswhiskey.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fourwallswhiskey.com at 0.5 s0.5 s
  2. fourwallswhiskey.com at 0.9 s0.9 s
  3. fourwallswhiskey.com at 1.4 s1.4 s
  4. fourwallswhiskey.com at 1.8 s1.8 s
  5. fourwallswhiskey.com at 2.3 s2.3 s
  6. fourwallswhiskey.com at 2.8 s2.8 s
  7. fourwallswhiskey.com at 3.2 s3.2 s
  8. fourwallswhiskey.com at 3.7 s3.7 s

Speed

6 to fix84
  • Improve image delivery

    5.4 MB

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

  • Mobile performance score: 84

    84/100

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

  • Render-blocking requests

    350 ms

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

  • Reduce unused JavaScript

    266 KiB

    About 266 KiB of JavaScript is downloaded but never used on this page.

  • 2,479 HTML elements

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

  • Klaviyo adds 123 ms

    123 ms

    Klaviyo costs a phone 123 ms of main-thread work and 345 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Accessibe Accessibility Overlay and Shopify and others), adding 833 KiB and 249 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 27 KiB

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

  • 4 long tasks on the main thread

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

  • Use efficient cache lifetimes

    71 KiB

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

  • Reduce unused CSS

    29 KiB

    About 29 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.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 796 ms of it running JavaScript. That is comfortably low.

  • Server response: 10 ms

    10 ms

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

Core Web Vitals

3 to fix100
  • Speed Index: 17.5 s

    17.5 s

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

  • Time to Interactive: 31.0 s

    31.0 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

6 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 CLS: 0.02

    0.02

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Largest Contentful Paint: 2.5 s

    2.5 s

    Your largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “GOOD TIMES CALL FOR THE BETTER BROWN”.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 44 ms

    44 ms

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

Images and page weight

5 to fix28
  • Page weight: 8.7 MB in 211 requests

    8.7 MB

    Your homepage downloads 8.7 MB in 211 requests on a phone: images 6.4 MB (50), scripts 880 KiB (67) and fonts 707 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    smaller.gif weighs 2.6 MB. On a phone connection a single image that size takes seconds.

  • 10 images in older formats

    10 images (3.7 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.

  • 5 images far larger than shown

    250 KiB

    5 images are downloaded at several times the size a phone draws them, for example d2abedae-2a05-4079-8bb8-e6d88595ab09.png at 2,100 px wide, shown at 250 px. Resized copies would save about 250 KiB.

  • 8 images below the first screen load straight away

    8 images further down the page (479 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.5 g of CO₂ per visit

    2.46 g

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

Accessibility

6 to fixGoogle 9292
  • Positive tabindex

    3 elements have a tabindex above 0, which scrambles the keyboard order.

  • 3 images without alt text

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

  • All page content should be contained by landmarks (8 elements)

    All page content should be contained by landmarks: 8 elements on the page fail 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.

  • 5 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10084
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Four Walls Whiskey | Come on in! – Four Walls Irish American Whiskey”.

  • Meta description is long (178 characters)

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

  • Structured data has 2 problems

    Structured data found (Organization) but with 2 problems, for example “Organization: missing name”.

  • 47 internal links, 9 external

    The homepage links to 47 pages on fourwallswhiskey.com and 9 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Good TimesCall For The Better Brown”.

  • Canonical URL set

    The canonical URL is https://www.fourwallswhiskey.com/.

  • 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.fourwallswhiskey.com/sitemap.xml.

AI search readiness

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

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

  • No llms.txt

    There is no https://www.fourwallswhiskey.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 3 pages without a meta description

    https://www.fourwallswhiskey.com/pages/our-story, https://www.fourwallswhiskey.com/blogs/break-the-fourth-wall and https://www.fourwallswhiskey.com/collections/whiskey have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    5 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 5 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.fourwallswhiskey.com/cdn/shop/t/43/assets/fonts.static.css?v=16120' because it…”.

2 checks passed
  • Tap targets are thumb-sized

    13 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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.

  • About 1,186 words of copy

    The homepage carries about 1,186 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP LOCALLY”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop”, “SHOP ALL” and “Shop locally”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 21 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on fourwallswhiskey.com, including 9 speed issues, 3 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