Website review, no card needed

1821bitters.com logo

1821bitters.com website review

Visit site (opens in a new tab)Reviewed 21 November 202633 issues · 72 checks

This review found 33 issues worth fixing on 1821bitters.com, 6 of them high impact, across 72 checks. The most urgent: render-blocking 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

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

How it loaded on a phone

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

Speed

8 to fix83
  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 83

    83/100

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

  • Improve image delivery

    977 KiB

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

  • 8 third-party services on the page

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

  • Reduce unused JavaScript

    901 KiB

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

  • Reduce unused CSS

    600 ms · 143 KiB

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

  • Squarespace adds 367 ms

    367 ms

    Squarespace costs a phone 367 ms of main-thread work and 1.3 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.

  • squarespace-cdn.com adds 0 ms

    0 ms

    squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.2 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.

  • Use efficient cache lifetimes

    193 KiB

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    105 KiB

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

  • 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.0 s

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

  • Server response: 46 ms

    46 ms

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

Core Web Vitals

5 to fix94
  • Time to Interactive: 13.7 s

    13.7 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “‍Thoughtfully Crafted. Extraordinary Cocktails.”. Most of its time is element render delay (2.4 s).

  • 1 image without width and height

    1 image 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
  • Total Blocking Time: 92 ms

    92 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix78
  • Page weight: 3.3 MB in 85 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 85 requests on a phone: scripts 1.8 MB (52), images 1.2 MB (10) and stylesheets 172 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.94 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9696
  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 8 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 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10074
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (13 characters)

    Your title is only 13 characters: “18.21 Bitters”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (318 characters)

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

  • Structured data has 3 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 3 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5300379de4b0ab61236…”.

  • 45 internal links, 1 external

    The homepage links to 45 pages on 1821bitters.com and 1 external page.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.1821bitters.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.1821bitters.com/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing name, url, logo 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.1821bitters.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.

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

Other pages

5 to fix76
  • 4 pages share 2 titles

    https://www.1821bitters.com/bitters-and-tinctures-4-oz and https://www.1821bitters.com/shop all use the title “Craft Bitters — 18.21 Bitters”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.1821bitters.com/holiday-gift-ideas, https://www.1821bitters.com/wheretofindus, https://www.1821bitters.com/non-alcoholic-ccoktails, https://www.1821bitters.com/recipesnon-alcoholic and https://www.1821bitters.com/cocktail-menu-development have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.1821bitters.com/bitters-and-tinctures-4-oz and https://www.1821bitters.com/shop use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.1821bitters.com/shop, whose canonical is https://www.1821bitters.com/bitters-and-tinctures-4-oz. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages without an H1

    https://www.1821bitters.com/bitters-and-tinctures-4-oz, https://www.1821bitters.com/mixers, https://www.1821bitters.com/holiday-gift-ideas, https://www.1821bitters.com/ourstory, https://www.1821bitters.com/wheretofindus and https://www.1821bitters.com/cocktails and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 4 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • 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.

  • Only about 139 words

    The homepage has only about 139 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

7 checks passed
  • Clear next step on the first screen

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

  • 4 calls to action

    The homepage has 4 calls to action, for example “SHOP”, “Folder: SHOP” and “Subscribe”.

  • 1 short form

    A short form (2 fields at most) is 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: 0 phone links and 2 email links.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager 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.

  • 6 cookies set on arrival

    6

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

  • 12 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Squarespace
Analytics
Google Analytics
Hosting
Squarespace

Company

Headquarters
Atlanta

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 1821bitters.com, including 13 speed issues, 4 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