Website review, no card needed

blackhorsebrews.com logo

blackhorsebrews.com website review

Visit site (opens in a new tab)Reviewed 19 October 202640 issues · 82 checks

This review found 40 issues worth fixing on blackhorsebrews.com, 19 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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
3.8 s3.2 sApr 25Oct 103.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.3 s
May 2, 20263.3 s
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.4 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.6 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.6 s
Aug 15, 20263.6 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
72 ms62 msApr 25Oct 1066 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202670 ms
May 2, 202667 ms
May 9, 202665 ms
May 16, 202665 ms
May 23, 202666 ms
May 30, 202668 ms
Jun 6, 202669 ms
Jun 13, 202670 ms
Jun 20, 202670 ms
Jun 27, 202670 ms
Jul 4, 202670 ms
Jul 11, 202669 ms
Jul 18, 202670 ms
Jul 25, 202670 ms
Aug 1, 202670 ms
Aug 8, 202671 ms
Aug 15, 202671 ms
Aug 22, 202670 ms
Aug 29, 202670 ms
Sep 5, 202669 ms
Sep 12, 202667 ms
Sep 19, 202666 ms
Sep 26, 202663 ms
Oct 3, 202664 ms
Oct 10, 202666 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 blackhorsebrews.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. blackhorsebrews.com at 0.6 s0.6 s
  2. blackhorsebrews.com at 1.1 s1.1 s
  3. blackhorsebrews.com at 1.7 s1.7 s
  4. blackhorsebrews.com at 2.3 s2.3 s
  5. blackhorsebrews.com at 2.8 s2.8 s
  6. blackhorsebrews.com at 3.4 s3.4 s
  7. blackhorsebrews.com at 4.0 s4.0 s
  8. blackhorsebrews.com at 4.5 s4.5 s

Speed

10 to fix42
  • Use efficient cache lifetimes

    14.1 s · 36.6 MB

    117 files are served with short cache lifetimes, so returning visitors download them again (36.6 MB).

  • Improve image delivery

    10.3 s · 32.2 MB

    25 images could be 32.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.3 s faster on a phone.

  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 42

    42/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Mailchimp and others), adding 1.5 MB and 1.2 s of main-thread time.

  • Reduce unused JavaScript

    678 KiB

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

  • Google CDN adds 534 ms

    534 ms

    Google CDN costs a phone 534 ms of main-thread work and 730 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.

  • Google Tag Manager adds 472 ms

    472 ms

    Google Tag Manager costs a phone 472 ms of main-thread work and 455 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.

  • Reduce unused CSS

    300 ms · 102 KiB

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

  • Main-thread work: 4.0 s

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

  • 14 long tasks on the main thread

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

  • 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: 48 ms

    48 ms

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

Core Web Vitals

9 to fix67
  • 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 TTFB: 2.5 s

    2.5 s

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

  • Largest Contentful Paint: 32.7 s

    32.7 s

    Your largest element takes 32.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Hero-Section”.

  • Time to Interactive: 34.3 s

    34.3 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Total Blocking Time: 815 ms

    815 ms

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 3.9 s

    3.9 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Tap response (INP) held steady for real visitors

    -5%

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

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

    +10%

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

3 checks passed
  • Real-user INP: 78 ms

    78 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

5 to fix18
  • Page weight: 38.3 MB in 148 requests

    38.3 MB

    Your homepage downloads 38.3 MB in 148 requests on a phone: images 36.0 MB (39), scripts 1.6 MB (56) and other files 354 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 7 images over 500 KB

    7 images weigh 25.5 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    21.3 MB

    4 images are downloaded at several times the size a phone draws them, for example Blackhorse-IPA-Mockup.png at 3,000 px wide, shown at 335 px. Resized copies would save about 21.3 MB.

  • 19 images in older formats

    19 images (28.5 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.

  • 18 images below the first screen load straight away

    18 images further down the page (28.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 10.8 g of CO₂ per visit

    10.85 g

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

Accessibility

7 to fixGoogle 8691
  • 21 text elements with low contrast

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

  • 2 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 1 form field without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

2 to fixGoogle 8583
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (21 characters)

    Your title is only 21 characters: “Homepage - Blackhorse”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 119 internal links, 12 external

    The homepage links to 119 pages on blackhorsebrews.com and 12 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “adventure with Blackhorse”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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.blackhorsebrews.com/sitemap_index.xml.

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.

  • No llms.txt

    There is no https://www.blackhorsebrews.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 (553 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.blackhorsebrews.com/our-beers, https://www.blackhorsebrews.com/events, https://www.blackhorsebrews.com/blog, https://www.blackhorsebrews.com/about-us, https://www.blackhorsebrews.com/shop and https://www.blackhorsebrews.com/distributors and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages slow to respond

    https://www.blackhorsebrews.com/our-beers, https://www.blackhorsebrews.com/events, https://www.blackhorsebrews.com/blog, https://www.blackhorsebrews.com/about-us, https://www.blackhorsebrews.com/shop and https://www.blackhorsebrews.com/distributors and 9 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

1 to fixGoogle 9693
  • 40 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • 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 opening hours

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

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

    The homepage carries about 394 words of visible text.

5 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop”, “SHOP Blackhorse Gear & Gifts” and “Learn More About Us”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 11 other companies contacted

    Loading the homepage contacts 11 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 blackhorsebrews.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
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on blackhorsebrews.com, including 19 speed issues, 2 SEO issues and 3 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