Website review, no card needed
kloffie.nl website review
Visit site (opens in a new tab)Reviewed 20 November 202642 issues · 89 checks
This review found 42 issues worth fixing on kloffie.nl, 13 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 736 ms |
| Jun 6, 2026 | 753 ms |
| Jun 13, 2026 | 732 ms |
| Jun 20, 2026 | 747 ms |
| Jun 27, 2026 | 827 ms |
| Jul 4, 2026 | 812 ms |
| Jul 11, 2026 | 779 ms |
| Jul 18, 2026 | 766 ms |
| Jul 25, 2026 | 855 ms |
| Aug 1, 2026 | 870 ms |
| Aug 8, 2026 | 994 ms |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 814 ms |
| Aug 29, 2026 | 814 ms |
| Sep 5, 2026 | 747 ms |
| Sep 12, 2026 | 759 ms |
| Sep 19, 2026 | 803 ms |
| Sep 26, 2026 | 789 ms |
| Oct 3, 2026 | 903 ms |
| Oct 10, 2026 | 802 ms |
| Oct 17, 2026 | 802 ms |
| Oct 24, 2026 | 799 ms |
| Oct 31, 2026 | 828 ms |
| Nov 7, 2026 | 818 ms |
| Nov 14, 2026 | 770 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 79 ms |
| Jul 11, 2026 | 57 ms |
| Jul 18, 2026 | 56 ms |
| Jul 25, 2026 | 54 ms |
| Aug 1, 2026 | 55 ms |
| Aug 15, 2026 | 70 ms |
| Aug 22, 2026 | 72 ms |
| Sep 5, 2026 | 70 ms |
| Nov 7, 2026 | 72 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
Use efficient cache lifetimes
2.2 s · 701 KiB64 files are served with short cache lifetimes, so returning visitors download them again (701 KiB).
Render-blocking requests
2.3 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Reduce unused JavaScript
1.8 s · 290 KiBAbout 290 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Reduce unused CSS
1.1 s · 224 KiBAbout 224 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
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.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, swretail.nl and Google/Doubleclick Ads and others), adding 1.0 MB and 459 ms of main-thread time.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
Improve image delivery
300 ms · 97 KiB5 images could be 97 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 341 ms
341 msGoogle Tag Manager costs a phone 341 ms of main-thread work and 397 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 263 ms. During a long task the page ignores taps.
swretail.nl adds 116 ms
116 msswretail.nl costs a phone 116 ms of main-thread work and 570 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.
Minify CSS
150 ms · 7 KiB7 KiB could be saved by minifying CSS.
Minify JavaScript
150 ms · 5 KiB5 KiB could be saved by minifying JavaScript.
Legacy JavaScript
6 KiBPolyfills for old browsers add 6 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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 423 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 1.402
1.402The layout shifts by 1.402 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 11.0 s
11.0 sYour largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “new_collection_kids_clothing_2024”.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
50 images without width and height
50 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 79 ms to 72 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-11-14, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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: 0.8 s
0.8 sReal visitors wait 0.8 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: 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: 581 ms
581 msReal visitors wait 581 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 118 ms
118 msScripts block the page for only 118 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
24 KiB1 image is downloaded at several times the size a phone draws it, for example 1-kloffies_winter_width_1280_height_375_alt_kinderkleding.jp at 1,280 px wide, shown at 360 px. Resized copies would save about 24 KiB.
2 images in older formats
2 images (166 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 0.4 g of CO₂ per visit
0.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.45 g of CO₂e: 53.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.6 MB in 78 requests
1.6 MBYour homepage downloads 1.6 MB in 78 requests on a phone: scripts 611 KiB (8), images 546 KiB (55) and stylesheets 248 KiB (6). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
31 tap targets too small
31 tap targets are too small or too close together to hit reliably with a finger.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
32 images without alt text
32 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (105 elements)
All page content should be contained by landmarks: 105 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
39 links without text
39 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 11 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 short (28 characters)
Your meta description is only 28 characters: “Kloffie's & Zo kinderkleding”. 70 to 160 characters is enough to sell the click.
10 H1 headlines
There are 10 <h1> headlines (“MELD U AAN VOOR ONZE NIEUWSBRIEF”, “Categorieën” and “”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
165 internal links, 4 external
The homepage links to 165 pages on kloffie.nl and 4 external pages.
4 checks passed
Title: 35 characters
Your title is a healthy 35 characters: “Online kinderkleding kloffie's & Zo”.
Structured data in place
Structured data found: BreadcrumbList.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://kloffie.nl/sitemap.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://kloffie.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.
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 (330 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages share 2 titles
/, https://kloffie.nl/customerLogOut and https://kloffie.nl/bsuede all use the title “Online kinderkleding kloffie's & Zo”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://kloffie.nl/kids-meisjes, https://kloffie.nl/kids-meisjes/accesoires, https://kloffie.nl/kids-jongens/accesoires, https://kloffie.nl/kids-jongens/badkleding-sokken and https://kloffie.nl/kids-jongens/bottoms have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://kloffie.nl/customerLogOut and https://kloffie.nl/bsuede use the same meta description. A description written for each page earns more clicks.
6 pages slow to respond
https://kloffie.nl/customerLogOut, https://kloffie.nl/kids-meisjes, https://kloffie.nl/kids-meisjes/accesoires, https://kloffie.nl/kids-jongens/accesoires, https://kloffie.nl/kids-jongens/badkleding-sokken and https://kloffie.nl/kids-jongens/bottoms took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 89 found) and read each the way a search engine does.
5 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
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 9 pages that loaded have a <title>.
Best practices
20 small tap targets
20 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 181 words
The homepage has only about 181 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
1 call to action
The homepage has 1 call to action, for example “Contact”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
4 cookies set on arrival
4Opening the homepage sets 4 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.
8 other companies contacted
Loading the homepage contacts 8 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 kloffie.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2020.
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Leaseweb
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on kloffie.nl, including 17 speed issues, 4 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.