Website review, no card needed
beerwulf.com website review
Visit site (opens in a new tab)Reviewed 21 October 202629 issues · 78 checks
This review found 29 issues worth fixing on beerwulf.com, 9 of them high impact, across 78 checks. The most urgent: page weight: 6.5 MB in 247 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
84B- #21,596 of 120,386 reviewed websitesbeats 77%
- #14,000 of 68,150 online storesbeats 73%
- #13,583 of 62,105 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.0 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 106 ms |
| May 9, 2026 | 106 ms |
| May 16, 2026 | 109 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 116 ms |
| Jun 13, 2026 | 118 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 122 ms |
| Jul 25, 2026 | 125 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 131 ms |
| Aug 15, 2026 | 133 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 136 ms |
| Oct 10, 2026 | 136 ms |
| Oct 17, 2026 | 137 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
Speed
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Optanon and Klaviyo and others), adding 1.3 MB and 1.1 s of main-thread time.
Mobile performance score: 58
58/100Your mobile performance score is 58 (desktop: 83). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 776 ms
776 msGoogle Tag Manager costs a phone 776 ms of main-thread work and 687 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.
Reduce unused JavaScript
150 ms · 426 KiBAbout 426 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 362 ms. During a long task the page ignores taps.
2,147 HTML elements
The page has 2,147 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
150 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Improve image delivery
116 KiB4 images could be 116 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
99 KiB17 files are served with short cache lifetimes, so returning visitors download them again (99 KiB).
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need.
Reduce unused CSS
17 KiBAbout 17 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 83 but mobile only 58. 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 17.8 s
17.8 sThe page becomes fully interactive after 17.8 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Speed Index: 6.1 s
6.1 sVisually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A BLADE beer machine on a kitchen counter with people in th…”.
Total Blocking Time: 607 ms
607 msScripts block taps and scrolling for 607 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 106 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 129 ms
129 msReal visitors wait 129 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 410 ms
410 msReal visitors wait 410 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.093
0.093The layout barely moves while loading (CLS 0.093, good is under 0.1).
Images and page weight
Page weight: 6.5 MB in 247 requests
6.5 MBYour homepage downloads 6.5 MB in 247 requests on a phone: media 3.6 MB (3), scripts 1.4 MB (103) and other files 769 KiB (102). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
295 KiB6 images are downloaded at several times the size a phone draws them, for example BLADE-8l-keg-bundle-heineken-2-new.png at 1,080 px wide, shown at 256 px. Resized copies would save about 295 KiB.
1 image below the first screen load straight away
1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.84 g of CO₂e: 220.9 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
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
182 internal links, 7 external
The homepage links to 182 pages on beerwulf.com and 7 external pages.
6 checks passed
Meta description: 128 characters
Your meta description is 128 characters: “Discover the BLADE & BeerTender home draught beer machines and shop a range of beer kegs & home bar accessories at Beer…”.
One H1 headline
Your main headline reads: “Beer Taps, Beer Kegs & Accessories”.
Title: 56 characters
Your title is a healthy 56 characters: “Beer Taps, Beer Kegs & Accessories – Beerwulf - UK store”.
Canonical URL set
The canonical URL is https://beerwulf.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://beerwulf.com/sitemap.xml.
AI search readiness
Organization data is thin (0 of 6 facts)
Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,350 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://beerwulf.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://beerwulf.com/pages/beer-accessories and https://beerwulf.com/collections/all-accessories all use the title “Beer Accessories – Beerwulf - UK store”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://beerwulf.com/pages/bundle/blade-starter-pack and https://beerwulf.com/pages/bundle/beertender-starter-pack have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 72 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.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=5565348&tm=gtm002&Ver=2&mid=2f622ea8-3f71-4954-a099-82bcd32b03c6&bo=3&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Beer%20Taps,%20Beer%20Kegs%20%26%20Accessories.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
52 of 61 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 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 1,048 words of copy
The homepage carries about 1,048 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: “Buy 6 BLADE kegs get 5% off*” and “Shop kegs”.
11 calls to action
The homepage has 11 calls to action, for example “Buy 6 BLADE kegs get 5% off*”, “Shop kegs” and “Shop accessories”.
19 short forms
19 short forms (1 field at most) are right on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Microsoft Ads (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 beerwulf.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on beerwulf.com, including 13 speed issues, 3 SEO issues 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.