Website review, no card needed
kluswijs.nl website review
Visit site (opens in a new tab)Reviewed 23 October 202637 issues · 83 checks
This review found 37 issues worth fixing on kluswijs.nl, 17 of them high impact, across 83 checks. The most urgent: render-blocking 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.3 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 129 ms |
| May 9, 2026 | 129 ms |
| May 16, 2026 | 129 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 132 ms |
| Jun 6, 2026 | 135 ms |
| Jun 13, 2026 | 136 ms |
| Jun 20, 2026 | 136 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 139 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 136 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 138 ms |
| Aug 29, 2026 | 140 ms |
| Sep 5, 2026 | 140 ms |
| Sep 12, 2026 | 143 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 140 ms |
| Oct 3, 2026 | 141 ms |
| Oct 10, 2026 | 140 ms |
| Oct 17, 2026 | 142 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.9 s
1.8 s
2.7 s
3.5 s
4.4 s
5.3 s
6.2 s
7.1 s
Speed
Render-blocking requests
3.6 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Reduce unused JavaScript
2.1 s · 360 KiBAbout 360 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,639 HTML elements
The page has 3,639 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
1.8 MB10 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, nextchapter-ecommerce.com and Cookiebot and others), adding 3.7 MB and 707 ms of main-thread time.
nextchapter-ecommerce.com adds 216 ms
216 msnextchapter-ecommerce.com costs a phone 216 ms of main-thread work and 2.9 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.
Google Tag Manager adds 414 ms
414 msGoogle Tag Manager costs a phone 414 ms of main-thread work and 529 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 · 71 KiBAbout 71 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 170 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
36 KiB5 files are served with short cache lifetimes, so returning visitors download them again (36 KiB).
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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 680 ms of it running JavaScript. That is comfortably low.
Server response: 102 ms
102 msYour server sent the HTML in 102 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 CLS: 0.93
0.93For real visitors the layout shifts by 0.93 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 10.6 s
10.6 sYour largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Cumulative Layout Shift: 1.221
1.221The layout shifts by 1.221 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 17.0 s
17.0 sThe page becomes fully interactive after 17.0 s. Good is under 3.8 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 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.
Total Blocking Time: 308 ms
308 msScripts block taps and scrolling for 308 ms in total while the page loads. Good is under 200 ms.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 129 ms to 142 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 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: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 383 ms
383 msReal visitors wait 383 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
3 images over 500 KB
3 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
1.1 MB5 images are downloaded at several times the size a phone draws them, for example kluswijs_nl_86504_16655_3._Assortiment_uitgelicht_932x932_Is at 1,942 px wide, shown at 350 px. Resized copies would save about 1.1 MB.
Page weight: 3.7 MB in 88 requests
3.7 MBYour homepage downloads 3.7 MB in 88 requests on a phone: images 2.7 MB (49), scripts 842 KiB (14) and fonts 97 KiB (3). Under 2 MB keeps phones on slow connections fast.
6 images below the first screen load straight away
6 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (94 KiB) 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.
About 1.1 g of CO₂ per visit
1.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 126.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
66 images without alt text
66 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (188 characters)
Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.
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 set, so this is minor.
382 internal links, 4 external
The homepage links to 382 pages on kluswijs.nl and 4 external pages.
7 checks passed
One H1 headline
Your main headline reads: “KlusWijs”.
Title: 37 characters
Your title is a healthy 37 characters: “KlusWijs; maak van je huis een thuis.”.
Canonical URL set
The canonical URL is https://www.kluswijs.nl/nl/.
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://www.kluswijs.nl/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.kluswijs.nl/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: 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 (2,377 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.kluswijs.nl/nl/zoeken is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.kluswijs.nl/nl/mijn-favorieten has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.kluswijs.nl/nl/zoeken has 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 196 found) and read each the way a search engine does.
4 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.nextchapter-ecommerce.com/css/m/kluswijs_nl/a81cf409.css' from origin 'https:/…”.
2 checks passed
Tap targets are thumb-sized
46 of 47 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 787 words of copy
The homepage carries about 787 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
4 calls to action
The homepage has 4 calls to action, for example “Contact”.
12 short forms
12 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
5 cookies set on arrival
5Opening the homepage sets 5 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: 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 kluswijs.nl, 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
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 kluswijs.nl, including 19 speed issues, 2 SEO issues 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.