Website review, no card needed
thebeercafe.com website review
Visit site (opens in a new tab)Reviewed 26 October 202631 issues · 72 checks
This review found 31 issues worth fixing on thebeercafe.com, 13 of them high impact, across 72 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.2 s |
| May 16, 2026 | 6.0 s |
| May 23, 2026 | 6.1 s |
| May 30, 2026 | 6.1 s |
| Jun 6, 2026 | 6.1 s |
| Jun 13, 2026 | 6.4 s |
| Jun 20, 2026 | 6.5 s |
| Jun 27, 2026 | 6.7 s |
| Jul 4, 2026 | 6.8 s |
| Jul 11, 2026 | 6.8 s |
| Jul 18, 2026 | 6.8 s |
| Jul 25, 2026 | 6.8 s |
| Aug 1, 2026 | 7.4 s |
| Aug 8, 2026 | 7.4 s |
| Aug 15, 2026 | 7.4 s |
| Aug 22, 2026 | 6.9 s |
| Aug 29, 2026 | 6.6 s |
| Sep 5, 2026 | 6.3 s |
| Sep 12, 2026 | 6.1 s |
| Sep 19, 2026 | 6.1 s |
| Sep 26, 2026 | 6.0 s |
| Oct 3, 2026 | 6.1 s |
| Oct 10, 2026 | 6.1 s |
| Oct 17, 2026 | 6.2 s |
| Oct 24, 2026 | 6.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 94 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 102 ms |
| Jun 13, 2026 | 102 ms |
| Jun 20, 2026 | 100 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 101 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 102 ms |
| Jul 25, 2026 | 101 ms |
| Aug 8, 2026 | 99 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 99 ms |
| Aug 29, 2026 | 97 ms |
| Sep 5, 2026 | 98 ms |
| Sep 19, 2026 | 106 ms |
| Sep 26, 2026 | 107 ms |
| Oct 3, 2026 | 100 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
1.6 s
3.2 s
4.8 s
6.4 s
8.1 s
9.7 s
11.3 s
12.9 s
Speed
Render-blocking requests
3.9 s47 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.9 s.
Improve image delivery
300 ms · 1,022 KiB4 images could be 1,022 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
900 ms · 180 KiBAbout 180 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61 (desktop: 78). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
173 KiBAbout 173 KiB of JavaScript is downloaded but never used on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
Minify JavaScript
12 KiB12 KiB could be saved by minifying JavaScript.
2 third-party services on the page
2 third-party services load with your homepage (YouTube and Google Fonts), adding 51 KiB and 5 ms of main-thread time.
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 CSS
5 KiB5 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 622 ms of it running JavaScript. That is comfortably low.
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 7.4 s
7.4 sReal visitors wait 7.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.0 s
6.0 sReal visitors see the first content after 6.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.1 s
4.1 sReal visitors wait 4.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 17.6 s
17.6 sVisually, the page fills in at 17.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At the forefront of India’s beer scene stands THE BEER CAFÉ…”. Most of its time is element render delay (10.1 s).
Time to Interactive: 5.6 s
5.6 sThe page becomes fully interactive after 5.6 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 94 ms to 100 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 6.2 s to 6.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.1 MB in 91 requests
3.1 MBYour homepage downloads 3.1 MB in 91 requests on a phone: images 2.1 MB (9), scripts 490 KiB (29) and stylesheets 279 KiB (44). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 104.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
2 checks passed
Every image has alt text
All 9 images in the HTML carry an alt attribute.
14 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 16 WCAG 2.2 A/AA and best-practice rules on the phone render: 14 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
6 H1 headlines
There are 6 <h1> headlines (“Our Story”, “Make a reservation” and “Our story”). One clear main headline is easier for people and search engines.
No XML sitemap
No XML sitemap at https://www.thebeercafe.com/wp-sitemap.xml, so Google discovers your pages only by following links.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
Open Graph partly set
Open Graph is missing og:title, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
21 internal links, 6 external
The homepage links to 21 pages on thebeercafe.com and 6 external pages.
3 checks passed
Title: 32 characters
Your title is a healthy 32 characters: “The Beer Cafe – Sports Pub & Bar”.
Canonical URL set
The canonical URL is https://www.thebeercafe.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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://www.thebeercafe.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.
1 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.
Other pages
1 linked page is broken
Your homepage links to https://www.thebeercafe.com/enquiry-form, which answers with an error. Visitors hit a dead end and search engines drop it.
9 pages without a meta description
https://www.thebeercafe.com/food-menu, https://www.thebeercafe.com/beverage-menu, https://www.thebeercafe.com/brewmiles, https://www.thebeercafe.com/franchise-with-us, https://www.thebeercafe.com/alliance-with-us and https://www.thebeercafe.com/join-our-team and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page with very little text
https://www.thebeercafe.com/investors-column 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.
5 pages slow to respond
https://www.thebeercafe.com/food-menu, https://www.thebeercafe.com/beverage-menu, https://www.thebeercafe.com/brewmiles, https://www.thebeercafe.com/franchise-with-us and https://www.thebeercafe.com/alliance-with-us took over 3 s to send their HTML from our server.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
5 checks passed
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 9 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 ()”.
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.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 38 words
The homepage has only about 38 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
3 calls to action
The homepage has 3 calls to action, for example “Join Our Team” and “Start search”.
1 short form
A short form (1 field at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 thebeercafe.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
- Liquidnetltd1
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on thebeercafe.com, including 12 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.