Website review, no card needed
vanhonsebrouck.be website review
Visit site (opens in a new tab)Reviewed 24 October 202637 issues · 84 checks
This review found 37 issues worth fixing on vanhonsebrouck.be, 15 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
82B- #34,686 of 124,235 reviewed websitesbeats 67%
- #22,948 of 69,818 online storesbeats 61%
- #440 of 2,907 WooCommerce storesbeats 81%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 145 ms |
| May 9, 2026 | 146 ms |
| May 16, 2026 | 145 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 147 ms |
| Jun 27, 2026 | 153 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 153 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 149 ms |
| Aug 1, 2026 | 147 ms |
| Aug 8, 2026 | 153 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 166 ms |
| Sep 5, 2026 | 165 ms |
| Sep 12, 2026 | 169 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 167 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.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.6 s
Speed
Reduce unused JavaScript
2.9 s · 895 KiBAbout 895 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Render-blocking requests
3.6 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 84). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,259 HTML elements
The page has 3,259 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cookiebot and Google CDN and others), adding 1.8 MB and 1.6 s of main-thread time.
Google Tag Manager adds 708 ms
708 msGoogle Tag Manager costs a phone 708 ms of main-thread work and 702 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.
Use efficient cache lifetimes
400 ms · 84 KiB10 files are served with short cache lifetimes, so returning visitors download them again (84 KiB).
Cookiebot adds 440 ms
440 msCookiebot costs a phone 440 ms of main-thread work and 231 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.
Google CDN adds 285 ms
285 msGoogle CDN costs a phone 285 ms of main-thread work and 734 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.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 242 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 84 but mobile only 42. 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
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.
Largest Contentful Paint: 14.0 s
14.0 sYour largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We gebruiken cookies om content en advertenties te personal…”.
Time to Interactive: 18.0 s
18.0 sThe page becomes fully interactive after 18.0 s. Good is under 3.8 s.
First Contentful Paint: 5.2 s
5.2 sThe first text or image appears after 5.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 753 ms
753 msScripts block taps and scrolling for 753 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 813 ms
813 msReal visitors wait 813 ms for your server to start answering (75th percentile). Good is under 800 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 145 ms to 167 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 153 ms
153 msReal visitors wait 153 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.
Cumulative Layout Shift: 0.043
0.043The layout barely moves while loading (CLS 0.043, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 178 requests
3.7 MBYour homepage downloads 3.7 MB in 178 requests on a phone: scripts 2.9 MB (128), other files 353 KiB (12) and images 253 KiB (29). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Kasteel-Donker-Header-1600x0-c-default.jpg 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).
2 images far larger than shown
105 KiB2 images are downloaded at several times the size a phone draws them, for example Kasteel-Donker-Header-1600x0-c-default.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 105 KiB.
About 1.0 g of CO₂ per visit
1.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 125.0 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
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
167 tap targets too small
167 tap targets are too small or too close together to hit reliably with a finger.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 87 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
201 internal links, 3 external
The homepage links to 201 pages on vanhonsebrouck.be and 3 external pages.
7 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Kasteel Brouwerij Vanhonsebrouck brouwt sinds 1811 unieke speciaalbieren. Ontdek o.a. Kasteel, Filou & Bacchus in het B…”.
One H1 headline
Your main headline reads: “Kasteel Donker”.
Title: 65 characters
Your title is a healthy 65 characters: “Kasteel Brouwerij Vanhonsebrouck | Kasteel, Filou, Bacchus & meer”.
Canonical URL set
The canonical URL is https://www.vanhonsebrouck.be/.
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://www.vanhonsebrouck.be/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://www.vanhonsebrouck.be/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 (749 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.vanhonsebrouck.be/es declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.vanhonsebrouck.be/es all use the title “Kasteel Brouwerij Vanhonsebrouck | Kasteel, Filou, Bacchus & meer”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://www.vanhonsebrouck.be/onze-bieren, https://www.vanhonsebrouck.be/events, https://www.vanhonsebrouck.be/ontdekken, https://www.vanhonsebrouck.be/over, https://www.vanhonsebrouck.be/over/jobs and https://www.vanhonsebrouck.be/shop and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.vanhonsebrouck.be/bier/kasteel/kasteel-rouge has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.vanhonsebrouck.be/ontdekken, https://www.vanhonsebrouck.be/over/jobs and https://www.vanhonsebrouck.be/shop took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 86 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
15 of 16 tappable elements near the top are at least 24 px.
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 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 401 words of copy
The homepage carries about 401 words of visible text.
4 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Shop” and “Contact”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and TikTok Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (measured from a US location before any click).
15 other companies contacted
Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 vanhonsebrouck.be, 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
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
Company
- Headquarters
- Emelgem
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on vanhonsebrouck.be, including 19 speed issues, 1 SEO issue 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.