Website review, no card needed
exellent.be website review
Visit site (opens in a new tab)Reviewed 17 November 202647 issues · 89 checks
This review found 47 issues worth fixing on exellent.be, 18 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.5 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 164 ms |
| Jun 6, 2026 | 165 ms |
| Jun 13, 2026 | 168 ms |
| Jun 20, 2026 | 166 ms |
| Jun 27, 2026 | 167 ms |
| Jul 4, 2026 | 169 ms |
| Jul 11, 2026 | 169 ms |
| Jul 18, 2026 | 173 ms |
| Jul 25, 2026 | 176 ms |
| Aug 1, 2026 | 177 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 185 ms |
| Aug 22, 2026 | 189 ms |
| Aug 29, 2026 | 193 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 186 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 195 ms |
| Oct 10, 2026 | 203 ms |
| Oct 17, 2026 | 211 ms |
| Oct 24, 2026 | 215 ms |
| Oct 31, 2026 | 215 ms |
| Nov 7, 2026 | 212 ms |
| Nov 14, 2026 | 208 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.4 s
0.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.0 s
3.5 s
Speed
Use efficient cache lifetimes
5.7 s · 1.4 MB82 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Improve image delivery
2.6 s · 1.7 MB14 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Reduce unused JavaScript
3.1 s · 555 KiBAbout 555 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Render-blocking requests
1.5 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Font display
1.3 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.3 s).
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, zoovu.com and Bazaarvoice and others), adding 3.7 MB and 958 ms of main-thread time.
Google Tag Manager adds 591 ms
591 msGoogle Tag Manager costs a phone 591 ms of main-thread work and 537 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 CSS
300 ms · 32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,392 HTML elements
The page has 2,392 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
img-exellent.be adds 0 ms
0 msimg-exellent.be costs a phone 0 ms of main-thread work and 2.3 MB 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.
zoovu.com adds 118 ms
118 mszoovu.com costs a phone 118 ms of main-thread work and 458 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
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: 3 ms
3 msYour server sent the HTML in 3 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: 25.3 s
25.3 sYour largest element takes 25.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Deze website gebruikt cookies (en daarmee vergelijkbare tec…”.
Time to Interactive: 26.4 s
26.4 sThe page becomes fully interactive after 26.4 s. Good is under 3.8 s.
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.425
0.425The layout shifts by 0.425 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.15
0.15For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.
Tap response (INP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 164 ms to 208 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 507 ms
507 msReal visitors wait 507 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 197 ms
197 msScripts block the page for only 197 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.8 MB in 109 requests
4.8 MBYour homepage downloads 4.8 MB in 109 requests on a phone: images 2.4 MB (46), scripts 1.4 MB (39) and fonts 792 KiB (6). Under 2 MB keeps phones on slow connections fast.
19 images in older formats
19 images (2.3 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
14 images below the first screen load straight away
14 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
59 KiB2 images are downloaded at several times the size a phone draws them, for example black-deals.png at 1,130 px wide, shown at 370 px. Resized copies would save about 59 KiB.
About 1.4 g of CO₂ per visit
1.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.36 g of CO₂e: 163.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 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.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (39 elements)
All page content should be contained by landmarks: 39 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
44 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: 44 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at exellent.be/robots.txt, the first file search crawlers ask for.
10 links crawlers can't follow
10 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 incomplete here.
537 internal links, 6 external
The homepage links to 537 pages on exellent.be and 6 external pages.
5 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “De beste elektro van je vakman in tv, audio, IT, telefonie, foto, video, smart devices, huishouden, keuken, verzorging …”.
Title: 54 characters
Your title is a healthy 54 characters: “Exellent | Je vakman steeds dichtbij | 24/24 bestellen”.
Canonical URL set
The canonical URL is https://www.exellent.be/nl.
Structured data in place
Structured data found: ItemList and Organization.
XML sitemap found
Your XML sitemap is reachable at https://www.exellent.be/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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.
No llms.txt
There is no https://www.exellent.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,315 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.exellent.be/nl and / all use the title “Exellent | Je vakman steeds dichtbij | 24/24 bestellen”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.exellent.be/nl/p/contact, https://www.exellent.be/nl/p/advies, https://www.exellent.be/nl/p/services and https://www.exellent.be/nl/p/winkels have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.exellent.be/nl. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.exellent.be/fr and / 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 199 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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
30 of 33 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.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 535 words of copy
The homepage carries about 535 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
8 short forms
8 short forms (4 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 32 testimonial or review blocks and 1 trust badge.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (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.
19 other companies contacted
Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 exellent.be, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- Combell
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on exellent.be, including 22 speed issues, 4 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.