Website review, no card needed

oakbeveragesinc.com logo

oakbeveragesinc.com website review

Visit site (opens in a new tab)Reviewed 19 October 202624 issues · 77 checks

This review found 24 issues worth fixing on oakbeveragesinc.com, 8 of them high impact, across 77 checks. The most urgent: render-blocking 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.5 s663 msMay 2Oct 171.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 2026971 ms
May 9, 2026850 ms
May 16, 2026754 ms
May 23, 2026824 ms
May 30, 2026931 ms
Jun 6, 20261.0 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 2026921 ms
Aug 22, 2026887 ms
Aug 29, 2026844 ms
Sep 5, 2026798 ms
Sep 12, 2026877 ms
Sep 19, 2026970 ms
Sep 26, 20261.0 s
Oct 3, 20261.4 s
Oct 10, 20261.1 s
Oct 17, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
80 ms60 msMay 9Oct 1769 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202662 ms
May 16, 202662 ms
May 23, 202663 ms
May 30, 202669 ms
Jun 6, 202671 ms
Jun 13, 202672 ms
Jun 20, 202675 ms
Jun 27, 202672 ms
Jul 4, 202675 ms
Jul 11, 202678 ms
Jul 18, 202672 ms
Jul 25, 202670 ms
Aug 1, 202670 ms
Aug 8, 202669 ms
Aug 15, 202677 ms
Aug 22, 202674 ms
Aug 29, 202673 ms
Sep 5, 202671 ms
Sep 12, 202666 ms
Sep 19, 202668 ms
Sep 26, 202666 ms
Oct 3, 202670 ms
Oct 17, 202669 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 oakbeveragesinc.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix66
  • Render-blocking requests

    1.8 s

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

  • Reduce unused JavaScript

    1.1 s · 175 KiB

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

  • Mobile performance score: 66

    66/100

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

  • Improve image delivery

    200 ms · 50 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Clarity and Google Analytics), adding 204 KiB and 228 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    10 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (10 KiB).

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

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 655 ms of it running JavaScript. That is comfortably low.

  • Server response: 25 ms

    25 ms

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

Core Web Vitals

7 to fix100
  • 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: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Oak Beverages Inc. BRIDGING BOROUGHS, POURING POSSIBILITIES…”.

  • Time to Interactive: 7.8 s

    7.8 s

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

  • Speed Index: 5.9 s

    5.9 s

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

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

    +24%

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

  • Real-user TTFB: 807 ms

    807 ms

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

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

    +12%

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

6 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 69 ms

    69 ms

    Real visitors wait 69 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.1 s

    1.1 s

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

  • Total Blocking Time: 93 ms

    93 ms

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

100
  • About 0.3 g of CO₂ per visit

    0.27 g

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

4 checks passed
  • Page weight: 991 KiB in 65 requests

    991 KiB

    Your homepage downloads 991 KiB in 65 requests on a phone: scripts 454 KiB (23), images 409 KiB (6) and fonts 55 KiB (2). That is a lean page.

  • 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

3 to fixGoogle 9296
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 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 32 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

5 to fixGoogle 8574
  • No meta description

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

  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “Oak Beverages – Bridging Boroughs, Pouring Possibilities: Your Beer, Our Passion”.

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 61 internal links, 5 external

    The homepage links to 61 pages on oakbeveragesinc.com and 5 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Oak Beverages Inc.”.

  • Canonical URL set

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

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://oakbeveragesinc.com/about-us, https://oakbeveragesinc.com/products, https://oakbeveragesinc.com/beers, https://oakbeveragesinc.com/wine-liquor, https://oakbeveragesinc.com/non-alcoholic and https://oakbeveragesinc.com/service-area and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://oakbeveragesinc.com/about-us, https://oakbeveragesinc.com/service-area, https://oakbeveragesinc.com/supplier-consideration, https://oakbeveragesinc.com/customer-portal, https://oakbeveragesinc.com/contact-us and https://oakbeveragesinc.com/engaging-with-and-uplifting-the-communities-we-serve 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 18 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • 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.

  • Thin social proof

    Social proof on the homepage: 10 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

  • No form on the homepage

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

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

  • About 411 words of copy

    The homepage carries about 411 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact Us”, “Learn more” and “Join our team”.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • 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 Analytics, Google Tag Manager and 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.

  • 4 cookies set on arrival

    4

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 oakbeveragesinc.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
Analytics
Google Analytics | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on oakbeveragesinc.com, including 10 speed issues, 5 SEO issues 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