Website review, no card needed
breww.co.uk website review
Visit site (opens in a new tab)Reviewed 7 November 202615 issues · 92 checks
This review found 15 issues worth fixing on breww.co.uk, 2 of them high impact, across 92 checks. The most urgent: fails Core Web Vitals for real visitors. 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
94AClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Sep 5, 2026 | 1.5 s |
| Oct 31, 2026 | 1.4 s |
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
breww.co.uk does not allow embedding, so this is Google's rendering of the page.
Speed
Render-blocking requests
950 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Use efficient cache lifetimes
303 KiB13 files are served with short cache lifetimes, so returning visitors download them again (303 KiB).
Improve image delivery
133 KiB1 image could be 133 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
6 third-party services on the page
6 third-party services load with your homepage (Hubspot, apollo.io and Google Fonts and others), adding 406 KiB and 71 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 84 ms. During a long task the page ignores taps.
Reduce unused CSS
45 KiBAbout 45 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.
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100. That is in Google's “good” band (90 and up).
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 319 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
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 TTFB: 832 ms
832 msReal visitors wait 832 ms for your server to start answering (75th percentile). Good is under 800 ms.
11 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 78 ms
78 msReal visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 3.8 s
3.8 sThe page is fully interactive after 3.8 s.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Largest Contentful Paint: 1.5 s
1.5 sYour largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Production, stock, sales, distribution and reporting. Every…”.
Speed Index: 1.7 s
1.7 sVisually, the page fills in at 1.7 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 20 ms
20 msScripts block the page for only 20 ms while loading. Good is under 200 ms.
Images and page weight
About 0.1 g of CO₂ per visit
0.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.14 g of CO₂e: 16.8 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: 507 KiB in 33 requests
507 KiBYour homepage downloads 507 KiB in 33 requests on a phone: images 229 KiB (9), scripts 116 KiB (6) and fonts 80 KiB (6). 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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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
148 internal links, 7 external
The homepage links to 148 pages on breww.co.uk and 7 external pages.
8 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “Breww is modern brewery management software designed specifically for craft breweries. Manage production, sales, delive…”.
One H1 headline
Your main headline reads: “Brewery management, sorted.”.
Title: 42 characters
Your title is a healthy 42 characters: “Breww | Modern Brewery Management Software”.
Canonical URL set
The canonical URL is https://breww.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://breww.com/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (731 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (20 KiB, 114 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 64 found) and read each the way a search engine does.
7 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.
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.
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 15 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 13 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 “Failed to load resource: the server responded with a status of 400 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Security and trust
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
7 checks passed
Served over HTTPS
The homepage is served over HTTPS (breww.com).
Valid certificate (84 days left)
The certificate from Google Trust Services · WE1 verifies for breww.co.uk and is valid for another 84 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://breww.co.uk redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 47 links work
All 47 links checked from your homepage (40 internal, 7 external) answered without errors.
Domain and trust
No CAA record
breww.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
3 checks passed
Domain is 22 years old
22 yearsbreww.com was registered in May 2004 through Cloudflare, Inc.. An established domain carries more trust with email providers and search engines.
DNSSEC is on
breww.com's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.
Registered until May 2027
breww.com is registered until May 2027.
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 28 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
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.
About 600 words of copy
The homepage carries about 600 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a demo →” and “Get started”.
19 calls to action
The homepage has 19 calls to action, for example “Taproom/shop managers”, “Pricing” and “Contact”.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Email authentication
Email authentication score: 95/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
3 checks passed
DMARC policy: reject
DMARC tells receivers to reject mail that fails authentication, and sends you reports.
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com ~all”.
DKIM signing found
A DKIM key is published (selector “google”, “s1” and “s2”), so receivers can verify mail really came from you.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads HubSpot (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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 6 of them by other companies (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.
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 15 issues on breww.co.uk, including 4 speed issues and 5 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.