Website review, no card needed

glazersbeer.com logo

glazersbeer.com website review

Visit site (opens in a new tab)Reviewed 29 October 202623 issues · 71 checks

This review found 23 issues worth fixing on glazersbeer.com, 5 of them high impact, across 71 checks. The most urgent: page weight: 6.3 MB in 184 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

Real-visitor load time (LCP)75th percentile, phones
1.1 s926 msMay 9Oct 24977 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026982 ms
May 16, 20261.0 s
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.0 s
Jun 27, 20261.1 s
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 2026995 ms
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 2026968 ms
Sep 5, 2026948 ms
Sep 12, 2026955 ms
Sep 19, 2026984 ms
Sep 26, 2026988 ms
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 2026970 ms
Oct 24, 2026977 ms
Real-visitor tap response (INP)75th percentile, phones
66 ms53 msMay 9Oct 2454 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202661 ms
May 16, 202657 ms
May 23, 202659 ms
May 30, 202658 ms
Jun 6, 202658 ms
Jun 13, 202660 ms
Jun 20, 202657 ms
Jun 27, 202657 ms
Jul 4, 202657 ms
Jul 11, 202655 ms
Jul 18, 202656 ms
Jul 25, 202661 ms
Aug 1, 202661 ms
Aug 8, 202664 ms
Aug 15, 202664 ms
Aug 22, 202661 ms
Aug 29, 202661 ms
Sep 5, 202659 ms
Sep 12, 202660 ms
Sep 19, 202662 ms
Sep 26, 202661 ms
Oct 3, 202660 ms
Oct 10, 202654 ms
Oct 17, 202654 ms
Oct 24, 202654 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 glazersbeer.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix80
  • 4 third-party services on the page

    4 third-party services load with your homepage (Wix, Clarity and Sentry and others), adding 5.6 MB and 695 ms of main-thread time.

  • Wix adds 569 ms

    569 ms

    Wix costs a phone 569 ms of main-thread work and 5.6 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.

  • Mobile performance score: 80

    80/100

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

  • Main-thread work: 2.4 s

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

  • Improve image delivery

    150 ms · 22 KiB

    1 image could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused JavaScript

    131 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 68 ms. During a long task the page ignores taps.

  • Duplicated JavaScript

    30 KiB

    30 KiB JavaScript is shipped twice across bundles.

  • Use efficient cache lifetimes

    21 KiB

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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 JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 24 ms

    24 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FullSizeRender (1).JPG”.

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Time to Interactive: 4.4 s

    4.4 s

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

  • Speed Index: 3.8 s

    3.8 s

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

  • Tap response (INP) held steady for real visitors

    -8%

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

  • Largest content (LCP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.0 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.3 s

    1.3 s

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

  • Real-user INP: 54 ms

    54 ms

    Real visitors wait 54 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 472 ms

    472 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 18 ms

    18 ms

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

Images and page weight

1 to fix70
  • Page weight: 6.3 MB in 184 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 184 requests on a phone: media 4.5 MB (1), scripts 975 KiB (94) and other files 480 KiB (70). Under 2 MB keeps phones on slow connections fast.

  • About 1.8 g of CO₂ per visit

    1.79 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.79 g of CO₂e: 215.0 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

1 to fixGoogle 9799
  • 1 link without text

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

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

4 to fixGoogle 10076
  • No H1 headline

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

  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “Glazer's Beer and Beverage | Glazersbeer.com | Arkansas, Louisiana, Texas”.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 28 internal links, 5 external

    The homepage links to 28 pages on glazersbeer.com and 5 external pages.

4 checks passed
  • Meta description: 93 characters

    Your meta description is 93 characters: “Glazers Beer & Beverage is the top beverage distributor across Arkansas, Louisiana and Texas.”.

  • Canonical URL set

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

  • 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.glazersbeer.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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://www.glazersbeer.com/llms.txt (3 KiB, 3 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.glazersbeer.com/about, https://www.glazersbeer.com/supplier, https://www.glazersbeer.com/banquets-4-the-brave, https://www.glazersbeer.com/locations, https://www.glazersbeer.com/el-paso and https://www.glazersbeer.com/general-office-go and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://www.glazersbeer.com/about, https://www.glazersbeer.com/el-paso, https://www.glazersbeer.com/general-office-go, https://www.glazersbeer.com/midland-odessa, https://www.glazersbeer.com/mountain-home and https://www.glazersbeer.com/north-little-rock and 6 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 26 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

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “globalThis.defineStrictProperty is not a function”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 134 words

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

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

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Online Ordering Sign Up” and “CONTACT”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Microsoft Clarity (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.

  • 9 cookies set on arrival

    9

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 glazersbeer.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
Wix
Framework
React
Analytics
Microsoft Clarity
Hosting
Wix

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on glazersbeer.com, including 8 speed issues, 4 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