Website review, no card needed

highlandbrewing.com logo

highlandbrewing.com website review

Visit site (opens in a new tab)Reviewed 19 October 202637 issues · 83 checks

This review found 37 issues worth fixing on highlandbrewing.com, 13 of them high impact, across 83 checks. The most urgent: improve image delivery. 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.3 s2.0 sApr 25Oct 103.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.2 s
May 2, 20262.3 s
May 9, 20262.3 s
May 16, 20262.4 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.6 s
Jun 20, 20262.7 s
Jun 27, 20262.8 s
Jul 4, 20262.9 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.9 s
Oct 3, 20263.0 s
Oct 10, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
108 ms84 msApr 25Oct 10105 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202687 ms
May 2, 202687 ms
May 9, 202687 ms
May 16, 202687 ms
May 23, 202688 ms
May 30, 202693 ms
Jun 6, 202695 ms
Jun 13, 202696 ms
Jun 20, 202696 ms
Jun 27, 202695 ms
Jul 4, 202696 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 202697 ms
Aug 1, 202696 ms
Aug 8, 202698 ms
Aug 15, 2026100 ms
Aug 22, 202699 ms
Aug 29, 202699 ms
Sep 5, 202697 ms
Sep 12, 202696 ms
Sep 19, 202698 ms
Sep 26, 2026102 ms
Oct 3, 2026103 ms
Oct 10, 2026105 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 highlandbrewing.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. highlandbrewing.com at 1.3 s1.3 s
  2. highlandbrewing.com at 2.6 s2.6 s
  3. highlandbrewing.com at 3.9 s3.9 s
  4. highlandbrewing.com at 5.2 s5.2 s
  5. highlandbrewing.com at 6.5 s6.5 s
  6. highlandbrewing.com at 7.8 s7.8 s
  7. highlandbrewing.com at 9.1 s9.1 s
  8. highlandbrewing.com at 10.4 s10.4 s

Speed

9 to fix20
  • Improve image delivery

    2.8 s · 611 KiB

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

  • Render-blocking requests

    3.4 s

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

  • Mobile performance score: 20

    20/100

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

  • Reduce unused JavaScript

    900 ms · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • 8 third-party services on the page

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

  • Use efficient cache lifetimes

    1.0 MB

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

  • Google Tag Manager adds 781 ms

    781 ms

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

  • Reduce unused CSS

    600 ms · 133 KiB

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

  • Main-thread work: 3.0 s

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

  • 18 long tasks on the main thread

    18 long tasks block the main thread while loading, the longest for 244 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).

  • Legacy JavaScript

    50 KiB

    Polyfills for old browsers add 50 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.

  • Forced reflow

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

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

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

  • Largest Contentful Paint: 22.4 s

    22.4 s

    Your largest element takes 22.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Video Player Media error: Format(s) not supported or source…”. Most of its time is resource load delay (10.1 s).

  • Speed Index: 17.4 s

    17.4 s

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

  • Time to Interactive: 26.1 s

    26.1 s

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

  • Cumulative Layout Shift: 0.818

    0.818

    The layout shifts by 0.818 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user CLS: 0.13

    0.13

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

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

    +20%

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

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

    +38%

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

  • Total Blocking Time: 591 ms

    591 ms

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 108 ms

    108 ms

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

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

  • Real-user TTFB: 569 ms

    569 ms

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

Images and page weight

2 to fix60
  • Page weight: 11.1 MB in 161 requests

    11.1 MB

    Your homepage downloads 11.1 MB in 161 requests on a phone: images 5.1 MB (17), media 3.6 MB (3) and scripts 2.1 MB (83). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    55 KiB

    1 image is downloaded at several times the size a phone draws it, for example HBC-simplified.png at 1,500 px wide, shown at 310 px. Resized copies would save about 55 KiB.

  • 1 image in older formats

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

    3.16 g

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

1 checks passed
  • Images load when needed

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

Accessibility

4 to fixGoogle 9195
  • All page content should be contained by landmarks (6 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 2 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 4 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 9285
  • No meta description

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“The Haze” and “That Hits”). One clear main headline is easier for people and search engines.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 35 internal links, 7 external

    The homepage links to 35 pages on highlandbrewing.com and 7 external pages.

5 checks passed
  • Title: 53 characters

    Your title is a healthy 53 characters: “Highland Brewing - Asheville's Original Craft Brewery”.

  • Canonical URL set

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

  • Structured data in place

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://highlandbrewing.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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://highlandbrewing.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

1 to fix95
  • 3 pages without a meta description

    https://highlandbrewing.com/beers, https://highlandbrewing.com/beer-finder and https://highlandbrewing.com/about-2 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://highlandbrewing.com/beer-finder has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 3 pages slow to respond

    https://highlandbrewing.com/beers, https://highlandbrewing.com/beer-finder and https://highlandbrewing.com/about-2 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

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

  • 4 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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.

  • Only about 110 words

    The homepage has only about 110 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us”, “Shop” and “Sign Up Now”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 21 cookies set on arrival

    21

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 highlandbrewing.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 37 issues on highlandbrewing.com, including 20 speed issues, 2 SEO issues and 4 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