Website review, no card needed
centralcitybrewing.com website review
Visit site (opens in a new tab)Reviewed 25 October 202626 issues · 76 checks
This review found 26 issues worth fixing on centralcitybrewing.com, 7 of them high impact, across 76 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 sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Sep 5, 2026 | 777 ms |
| Sep 12, 2026 | 799 ms |
| Sep 19, 2026 | 776 ms |
| Sep 26, 2026 | 706 ms |
| Oct 3, 2026 | 671 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
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
2.6 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Improve image delivery
1.0 s · 220 KiB6 images could be 220 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.
Mobile performance score: 69
69/100Your mobile performance score is 69 (desktop: 96). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
570 ms · 156 KiBAbout 156 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 570 ms faster on a phone.
Google Tag Manager adds 209 ms
209 msGoogle Tag Manager costs a phone 209 ms of main-thread work and 310 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and JSDelivr CDN and others), adding 483 KiB and 246 ms of main-thread time.
Minify JavaScript
150 ms · 15 KiB15 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 144 ms. During a long task the page ignores taps.
Reduce unused CSS
23 KiBAbout 23 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 96 but mobile only 69. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 193 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 7.4 s
7.4 sThe page becomes fully interactive after 7.4 s. Good is under 3.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Speed Index: 3.6 s
3.6 sVisually, the page fills in at 3.6 s (Speed Index). Good is under 3.4 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
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.
3 checks passed
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 113 ms
113 msScripts block the page for only 113 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 4.2 MB in 51 requests
4.2 MBYour homepage downloads 4.2 MB in 51 requests on a phone: images 3.7 MB (14), scripts 418 KiB (20) and fonts 57 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
BeerLeague_473mL_CA_Lager-ENG-DRY-RGB-scaled.png weighs 1.3 MB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
1.1 MB2 images are downloaded at several times the size a phone draws them, for example BeerLeague_473mL_CA_Lager-ENG-DRY-RGB-scaled.png at 2,560 px wide, shown at 400 px. Resized copies would save about 1.1 MB.
2 images below the first screen load straight away
2 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.20 g of CO₂e: 143.4 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
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (96 characters)
Your title is 96 characters, so Google will cut it off around 60: “Homefield Brewery - Proudly Brewing & Distilling Award-Winning Craft Beers & Spirits Sinc…”.
Meta description is long (252 characters)
Your meta description is 252 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, 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.
31 internal links, 1 external
The homepage links to 31 pages on centralcitybrewing.com and 1 external page.
5 checks passed
One H1 headline
Your main headline reads: “Are you of legal drinking age?”.
Canonical URL set
The canonical URL is https://homefieldbrewing.ca/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
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://homefieldbrewing.ca/sitemap_index.xml.
AI search readiness
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://homefieldbrewing.ca/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 (390 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://homefieldbrewing.ca/products has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages share a meta description
https://homefieldbrewing.ca/brewery, https://homefieldbrewing.ca/retail, https://homefieldbrewing.ca/contact, https://homefieldbrewing.ca/brewery/red-racer, https://homefieldbrewing.ca/brewery/beer-league and https://homefieldbrewing.ca/brewery/street-legal and 1 other use the same meta description. A description written for each page earns more clicks.
1 page with very little text
https://homefieldbrewing.ca/privacy-policy 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.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 10 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.
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 10 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
21 of 26 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 1 trust badge. 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 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 452 words of copy
The homepage carries about 452 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT”.
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “Learn More” and “Contact Us”.
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Ketch
A consent management tool (Ketch) loads with the page.
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 centralcitybrewing.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 Tag Manager
Company
- Founded
- 2003
- Headquarters
- Surrey
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on centralcitybrewing.com, including 10 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.