Website review, no card needed

azwbeer.com logo

azwbeer.com website review

Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 73 checks

This review found 44 issues worth fixing on azwbeer.com, 28 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. 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
5.1 s4.0 sMay 2Oct 174.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.5 s
May 9, 20264.5 s
May 16, 20264.6 s
May 23, 20264.4 s
May 30, 20264.2 s
Jun 6, 20264.2 s
Jun 13, 20264.2 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20264.2 s
Jul 11, 20264.2 s
Jul 18, 20264.2 s
Jul 25, 20264.1 s
Aug 1, 20264.1 s
Aug 8, 20264.1 s
Aug 15, 20264.2 s
Aug 22, 20264.3 s
Aug 29, 20264.3 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.4 s
Sep 26, 20264.5 s
Oct 3, 20264.7 s
Oct 10, 20264.9 s
Oct 17, 20264.9 s
Real-visitor tap response (INP)75th percentile, phones
176 ms132 msMay 2Oct 17171 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026138 ms
May 9, 2026138 ms
May 16, 2026137 ms
May 23, 2026138 ms
May 30, 2026138 ms
Jun 6, 2026142 ms
Jun 13, 2026149 ms
Jun 20, 2026146 ms
Jun 27, 2026146 ms
Jul 4, 2026145 ms
Jul 11, 2026145 ms
Jul 18, 2026145 ms
Jul 25, 2026145 ms
Aug 1, 2026146 ms
Aug 8, 2026146 ms
Aug 15, 2026148 ms
Aug 22, 2026149 ms
Aug 29, 2026148 ms
Sep 5, 2026153 ms
Sep 12, 2026149 ms
Sep 19, 2026154 ms
Sep 26, 2026162 ms
Oct 3, 2026169 ms
Oct 10, 2026169 ms
Oct 17, 2026171 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 azwbeer.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. azwbeer.com at 1.0 s1.0 s
  2. azwbeer.com at 2.0 s2.0 s
  3. azwbeer.com at 3.0 s3.0 s
  4. azwbeer.com at 4.0 s4.0 s
  5. azwbeer.com at 5.0 s5.0 s
  6. azwbeer.com at 5.9 s5.9 s
  7. azwbeer.com at 6.9 s6.9 s
  8. azwbeer.com at 7.9 s7.9 s

Speed

12 to fix12
  • Reduce unused JavaScript

    3.4 s · 838 KiB

    About 838 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.

  • Reduce unused CSS

    1.7 s · 413 KiB

    About 413 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.7 s faster on a phone.

  • Render-blocking requests

    2.0 s

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

  • dashtrack.com adds 1.3 s

    1.3 s

    dashtrack.com costs a phone 1.3 s of main-thread work and 1.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Sentry adds 1.2 s

    1.2 s

    Sentry costs a phone 1.2 s of main-thread work and 73 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 12

    12/100

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

  • Main-thread work: 7.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (dashtrack.com, Sentry and Google Tag Manager and others), adding 2.5 MB and 2.9 s of main-thread time.

  • Improve image delivery

    1.4 MB

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

  • Font display

    700 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 218 ms

    218 ms

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

  • Use efficient cache lifetimes

    200 ms · 41 KiB

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

  • Legacy JavaScript

    30 KiB

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

1 checks passed
  • Server response: 138 ms

    138 ms

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

Core Web Vitals

12 to fix33
  • 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 LCP: 5.5 s

    5.5 s

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

  • Real-user CLS: 0.48

    0.48

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

  • Real-user FCP: 3.5 s

    3.5 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Largest Contentful Paint: 31.7 s

    31.7 s

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

  • Speed Index: 19.2 s

    19.2 s

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

  • Time to Interactive: 31.9 s

    31.9 s

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

  • First Contentful Paint: 5.8 s

    5.8 s

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

  • Total Blocking Time: 2.7 s

    2.7 s

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

  • Cumulative Layout Shift: 0.29

    0.29

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

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

    +23%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

1 checks passed
  • Real-user INP: 166 ms

    166 ms

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

Images and page weight

4 to fix28
  • Page weight: 11.3 MB in 65 requests

    11.3 MB

    Your homepage downloads 11.3 MB in 65 requests on a phone: images 8.2 MB (27), scripts 2.1 MB (10) and HTML 447 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.

  • 11 images far larger than shown

    2.6 MB

    11 images are downloaded at several times the size a phone draws them, for example pride-guide-trusted-partner-2026-desert-badge.png at 1,000 px wide, shown at 200 px. Resized copies would save about 2.6 MB.

  • 9 images below the first screen load straight away

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

  • About 3.2 g of CO₂ per visit

    3.20 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 8592
  • 3 text elements with low contrast

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • No H1 headline

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 15 links crawlers can't follow

    15 links have no real href, so search engines can't follow them.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Discover bold, sustainable beers brewed with local ingredients. Join AZ Wilderness Brewing Co. in savoring the spirit o…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Explore Arizona's Wild Flavors | AZ Wilderness Brewing Co.”.

  • Canonical URL set

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

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 151 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

  • llms.txt published

    The site publishes https://azwbeer.com/llms.txt (14 KiB, 78 links), a plain-text guide to the site for AI tools.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://unpkg.com/@material-tailwind/[email protected]/styles.min.css' (redirected from 'h…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    7 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 direct contact details

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

  • Only about 151 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

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.

  • 3 cookies set on arrival

    3

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 azwbeer.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
Tailwind CSS
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on azwbeer.com, including 24 speed issues, 4 SEO issues and 5 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