Website review, no card needed
nabreweries.com website review
Visit site (opens in a new tab)Reviewed 25 October 202619 issues · 67 checks
This review found 19 issues worth fixing on nabreweries.com, 6 of them high impact, across 67 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.9 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Reduce unused JavaScript
900 ms · 131 KiBAbout 131 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
150 ms · 128 KiB4 images could be 128 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.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 240 KiB and 149 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 117 ms. During a long task the page ignores taps.
Reduce unused CSS
37 KiBAbout 37 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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 541 ms of it running JavaScript. That is comfortably low.
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Labatt USA”.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.3 s
6.3 sThe page becomes fully interactive after 6.3 s. Good is under 3.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 96 ms
96 msScripts block the page for only 96 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
An image on the first screen is lazy-loaded
header-genesee.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.3 g of CO₂ per visit
0.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.31 g of CO₂e: 36.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.1 MB in 35 requests
1.1 MBYour homepage downloads 1.1 MB in 35 requests on a phone: images 542 KiB (9), scripts 394 KiB (9) and fonts 73 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
2 checks passed
Every image has alt text
All 60 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image (also missing: og:title), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
50 internal links, 3 external
The homepage links to 50 pages on nabreweries.com and 3 external pages.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “We have extensive experience in alcoholic contract manufacturing. Find out about our liquid production, packaging, vari…”.
One H1 headline
Your main headline reads: “Welcome to North American Breweries”.
Title: 34 characters
Your title is a healthy 34 characters: “Welcome | North American Breweries”.
Canonical URL set
The canonical URL is https://www.nabreweries.com/.
Structured data in place
Structured data found: Corporation.
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.nabreweries.com/sitemap-index.xml.
AI search readiness
No llms.txt
There is no https://www.nabreweries.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.
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (583 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages point its canonical at the homepage
https://www.nabreweries.com/news, https://www.nabreweries.com/community-investment, https://www.nabreweries.com/community-investment/support-application, https://www.nabreweries.com/news/2026/9/14/lhit-celebrates-inaugural-season and https://www.nabreweries.com/news/2026/9/3/saothair-captial-partners-acquires-fifco-usa declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
4 pages share a meta description
https://www.nabreweries.com/contract-manufacturing, https://www.nabreweries.com/contact-us, https://www.nabreweries.com/community-investment/support-application and https://www.nabreweries.com/news/2026/9/14/lhit-celebrates-inaugural-season use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.nabreweries.com/news/2026/9/14/lhit-celebrates-inaugural-season and https://www.nabreweries.com/news/2026/9/3/saothair-captial-partners-acquires-fifco-usa have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://www.nabreweries.com/contact-us, https://www.nabreweries.com/news, https://www.nabreweries.com/brands/lipton-hard-iced-tea and https://www.nabreweries.com/brands/bubly-wine-refresher have 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
12 small tap targets
12 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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: 3 trust badges. 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 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 357 words of copy
The homepage carries about 357 words of visible text.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us” and “CCPA Request”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
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.
3 other companies contacted
Loading the homepage contacts 3 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 nabreweries.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Netlify
Company
- Founded
- 2009
- Headquarters
- Rochester
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on nabreweries.com, including 7 speed issues, 1 SEO issue and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.