Website review, no card needed

blacksheepbrewery.com logo

blacksheepbrewery.com website review

Visit site (opens in a new tab)Reviewed 25 October 202626 issues · 78 checks

This review found 26 issues worth fixing on blacksheepbrewery.com, 4 of them high impact, across 78 checks. The most urgent: form elements must have labels (2 elements). 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.2 s860 msMay 2Oct 17953 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026922 ms
May 9, 2026950 ms
May 16, 2026947 ms
May 23, 2026902 ms
May 30, 2026895 ms
Jun 6, 2026915 ms
Jun 13, 2026938 ms
Jun 20, 2026978 ms
Jun 27, 2026996 ms
Jul 4, 2026957 ms
Jul 11, 2026967 ms
Jul 18, 20261.0 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 2026998 ms
Oct 17, 2026953 ms
Real-visitor tap response (INP)75th percentile, phones
143 ms93 msMay 2Oct 17129 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202699 ms
May 9, 2026104 ms
May 16, 2026105 ms
May 23, 2026110 ms
May 30, 2026110 ms
Jun 6, 2026110 ms
Jun 13, 2026110 ms
Jun 20, 2026108 ms
Jun 27, 2026111 ms
Jul 4, 2026113 ms
Jul 11, 2026120 ms
Jul 18, 2026125 ms
Jul 25, 2026126 ms
Aug 1, 2026126 ms
Aug 8, 2026126 ms
Aug 15, 2026129 ms
Aug 22, 2026129 ms
Aug 29, 2026135 ms
Sep 5, 2026137 ms
Sep 12, 2026135 ms
Sep 19, 2026136 ms
Sep 26, 2026136 ms
Oct 3, 2026132 ms
Oct 10, 2026133 ms
Oct 17, 2026129 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 blacksheepbrewery.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix70
  • Mobile performance score: 70

    70/100

    Your mobile performance score is 70 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    650 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 1.4 MB and 492 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 475 KiB

    About 475 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    400 ms · 135 KiB

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

  • Improve image delivery

    400 ms · 67 KiB

    3 images could be 67 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Main-thread work: 3.1 s

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

  • Shopify adds 98 ms

    98 ms

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

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    100 ms · 33 KiB

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

  • Duplicated JavaScript

    100 ms · 17 KiB

    17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.

  • Minify JavaScript

    35 KiB

    35 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    16 KiB

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

1 checks passed
  • Server response: 66 ms

    66 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 14.7 s

    14.7 s

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

  • Largest Contentful Paint: 5.4 s

    5.4 s

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

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

    +29%

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 4.7 s

    4.7 s

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

8 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 LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 138 ms

    138 ms

    Real visitors wait 138 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.

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 373 ms

    373 ms

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

  • Total Blocking Time: 166 ms

    166 ms

    Scripts block the page for only 166 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

1 to fix85
  • Page weight: 3.4 MB in 440 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 440 requests on a phone: scripts 1.4 MB (167), other files 1.1 MB (201) and images 382 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.97 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 8995
  • Form elements must have labels (2 elements)

    Form elements must have labels: 2 elements on the page fail this check, rated critical by axe-core.

  • 57 text elements with low contrast

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

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • One H1 headline

    Your <h1> is empty.

  • 95 internal links, 1 external

    The homepage links to 95 pages on blacksheepbrewery.com and 1 external page.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Black Sheep Brewery – proudly independent since 1992 in Masham, North Yorkshire. Award-winning ales, brewery tours, bar…”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Black Sheep Brewery | Award-Winning Yorkshire Beer Since 1992”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, Product, ProductGroup 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.blacksheepbrewery.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.blacksheepbrewery.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.blacksheepbrewery.com/pages/sheepy-shop has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.blacksheepbrewery.com/pages/bar-kitchen and https://www.blacksheepbrewery.com/pages/sheepy-shop 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 45 found) and read each the way a search engine does.

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

  • 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 9289
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

2 checks passed
  • Tap targets are thumb-sized

    23 of 23 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
  • Thin social proof

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

  • No direct contact details

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

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

    The homepage carries about 608 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 9 calls to action

    The homepage has 9 calls to action, for example “SHOP”, “Sheepy Shop” and “CONTACT US”.

  • 7 short forms

    7 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Hotjar.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 15 cookies set on arrival

    15

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

  • 33 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Shopify
Analytics
Google Analytics | Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on blacksheepbrewery.com, including 13 speed issues, 1 SEO issue 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