Website review, no card needed
vandenborre.be website review
Visit site (opens in a new tab)Reviewed 28 October 202636 issues · 90 checks
This review found 36 issues worth fixing on vandenborre.be, 17 of them high impact, across 90 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 222 ms |
| May 16, 2026 | 221 ms |
| May 23, 2026 | 221 ms |
| May 30, 2026 | 222 ms |
| Jun 6, 2026 | 225 ms |
| Jun 13, 2026 | 228 ms |
| Jun 20, 2026 | 229 ms |
| Jun 27, 2026 | 228 ms |
| Jul 4, 2026 | 229 ms |
| Jul 11, 2026 | 230 ms |
| Jul 18, 2026 | 231 ms |
| Jul 25, 2026 | 234 ms |
| Aug 1, 2026 | 234 ms |
| Aug 8, 2026 | 235 ms |
| Aug 15, 2026 | 235 ms |
| Aug 22, 2026 | 235 ms |
| Aug 29, 2026 | 234 ms |
| Sep 5, 2026 | 231 ms |
| Sep 12, 2026 | 231 ms |
| Sep 19, 2026 | 231 ms |
| Sep 26, 2026 | 230 ms |
| Oct 3, 2026 | 231 ms |
| Oct 10, 2026 | 229 ms |
| Oct 17, 2026 | 229 ms |
| Oct 24, 2026 | 229 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.8 s
1.6 s
2.4 s
3.3 s
4.1 s
4.9 s
5.7 s
6.5 s
Speed
Reduce unused JavaScript
1.5 s · 549 KiBAbout 549 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Render-blocking requests
1.5 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 55). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,817 HTML elements
The page has 3,817 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, Kameleoon and Optanon and others), adding 1.3 MB and 1.3 s of main-thread time.
Use efficient cache lifetimes
750 ms · 332 KiB28 files are served with short cache lifetimes, so returning visitors download them again (332 KiB).
Google Tag Manager adds 857 ms
857 msGoogle Tag Manager costs a phone 857 ms of main-thread work and 705 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.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 246 ms. During a long task the page ignores taps.
Reduce unused CSS
160 ms · 81 KiBAbout 81 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.
Legacy JavaScript
150 ms · 68 KiBPolyfills for old browsers add 68 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
47 KiB7 images could be 47 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
18 KiB18 KiB could be saved by minifying JavaScript.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
Duplicated JavaScript
1 KiB1 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 213 ms
213 msYour server sent the HTML in 213 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: 11.1 s
11.1 sYour largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Repair Week: bij Vanden Borre gaan we voor meer herstellen …”.
Time to Interactive: 16.7 s
16.7 sThe page becomes fully interactive after 16.7 s. Good is under 3.8 s.
Total Blocking Time: 860 ms
860 msScripts block taps and scrolling for 860 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Real-user INP: 229 ms
229 msReal visitors wait 229 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 222 ms to 229 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 617 ms
617 msReal visitors wait 617 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
Images and page weight
Page weight: 2.3 MB in 123 requests
2.3 MBYour homepage downloads 2.3 MB in 123 requests on a phone: scripts 1.5 MB (38), images 293 KiB (38) and fonts 235 KiB (5). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
20260928_Repair_mob_TopBanner_NL2.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).
About 0.7 g of CO₂ per visit
0.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 78.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
autocomplete attribute must be used correctly (1 element)
autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.
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.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (57 elements)
All page content should be contained by landmarks: 57 elements on the page fail this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
45 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: 45 passed and 7 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 (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
No XML sitemap
No XML sitemap at https://www.vandenborre.be/sitemap.xml, so Google discovers your pages only by following links.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
716 internal links, 15 external
The homepage links to 716 pages on vandenborre.be and 15 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Vanden Borre : De specialist in tv, video, hifi, elektro, multimedia en gsm in Belgi�. Gemakkelijk vergelijken, kiezen …”.
One H1 headline
Your main headline reads: “Vanden Borre, in alle vertrouwen”.
Title: 56 characters
Your title is a healthy 56 characters: “Vanden Borre | Audio, TV, Multimedia, Elektro, Telefonie”.
Canonical URL set
The canonical URL is https://www.vandenborre.be/.
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.
AI search readiness
No llms.txt
There is no https://www.vandenborre.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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,976 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without an H1
https://www.vandenborre.be/tv-audio, https://www.vandenborre.be/tv-audio/televisie, https://www.vandenborre.be/tv-audio/homecinema and https://www.vandenborre.be/tv-audio/mp3-hoofdtelefoon-oortjes have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 200 found) and read each the way a search engine does.
6 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.
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 broken images
3 images failed to load on a phone, for example https://image.vandenborre.be/WEBV3/assets/images/eprel_stickers/Pas%20d'application.svg.
24 small tap targets
24 of 73 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Missing source maps
Large scripts ship without source maps.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
A 10-field form
Your longest form asks for 10 fields (0 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 431 words of copy
The homepage carries about 431 words of visible text.
4 checks passed
Social proof on the page
Social proof on the homepage: 40 testimonial or review blocks and 1 trust badge.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Microsoft Ads and 1 more (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.
8 cookies set on arrival
8Opening the homepage sets 8 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 vandenborre.be, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Telenet
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on vandenborre.be, including 15 speed issues, 3 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.