Website review, no card needed
leurs.nl website review
Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 78 checks
This review found 32 issues worth fixing on leurs.nl, 14 of them high impact, across 78 checks. The most urgent: improve image delivery. 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
80B- #47,157 of 120,317 reviewed websitesbeats 55%
- #31,329 of 68,134 online storesbeats 48%
- #115 of 714 Magento storesbeats 81%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.1 s |
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.3 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.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 120 ms |
| May 9, 2026 | 123 ms |
| May 16, 2026 | 121 ms |
| May 23, 2026 | 121 ms |
| May 30, 2026 | 124 ms |
| Jun 6, 2026 | 126 ms |
| Jun 13, 2026 | 135 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 152 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 134 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 143 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 144 ms |
| Sep 12, 2026 | 145 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 149 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 135 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
Improve image delivery
3.1 s · 705 KiB8 images could be 705 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.
3,733 HTML elements
The page has 3,733 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 61
61/100Your mobile performance score is 61 (desktop: 62). Pages that score under 90 lose visitors before the first paint.
Klaviyo adds 110 ms
110 msKlaviyo costs a phone 110 ms of main-thread work and 324 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
150 ms · 35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Klaviyo, Cloudflare and Trust Pilot and others), adding 393 KiB and 126 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 13 KiB5 files are served with short cache lifetimes, so returning visitors download them again (13 KiB).
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.
Reduce unused JavaScript
55 KiBAbout 55 KiB of JavaScript is downloaded but never used on this page.
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.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 607 ms of it running JavaScript. That is comfortably low.
Server response: 175 ms
175 msYour server sent the HTML in 175 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: 32.3 s
32.3 sYour largest element takes 32.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 36.4 s
36.4 sThe page becomes fully interactive after 36.4 s. Good is under 3.8 s.
Speed Index: 11.1 s
11.1 sVisually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 120 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 164 ms
164 msReal visitors wait 164 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.081
0.081The layout barely moves while loading (CLS 0.081, good is under 0.1).
Total Blocking Time: 137 ms
137 msScripts block the page for only 137 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 10.8 MB in 128 requests
10.8 MBYour homepage downloads 10.8 MB in 128 requests on a phone: images 10.1 MB (73), scripts 349 KiB (36) and fonts 117 KiB (6). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 5.2 MB together. On a phone connection a single image that size takes seconds.
11 images in older formats
11 images (6.6 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.
1 image below the first screen load straight away
1 image further down the page (275 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.1 g of CO₂ per visit
3.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.05 g of CO₂e: 366.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
32 tap targets too small
32 tap targets are too small or too close together to hit reliably with a finger.
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.
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.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
49 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: 49 passed and 4 failed. 1 more 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.
96 links crawlers can't follow
96 links have no real href, so search engines can't follow them.
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 XML sitemap
No XML sitemap at https://www.leurs.nl/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at leurs.nl/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
416 internal links, 6 external
The homepage links to 416 pages on leurs.nl and 6 external pages.
4 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Beleef Tuincentrum Leurs in Venlo: hét familie-uitje vol geluksmomentjes. Alles voor huis & tuin, met meubels, BBQ’s, p…”.
Title: 60 characters
Your title is a healthy 60 characters: “Tuincentrum Leurs Venlo – Jouw huis & tuin inspiratiecentrum”.
Canonical URL set
The canonical URL is https://www.leurs.nl/.
Structured data in place
Structured data found: Organization.
AI search readiness
No llms.txt
There is no https://www.leurs.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
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,486 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 192 found) and read each the way a search engine does.
1 checks passed
Linked pages load
1 page of 15 loaded without an error (the rest turned automated requests away).
Best practices
21 small tap targets
21 of 85 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 “Access to fetch at 'https://graph.instagram.com/me/media?fields=id,caption,media_type,media_url,permalink&access_token=…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
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.
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 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 648 words of copy
The homepage carries about 648 words of visible text.
6 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Contact” and “Shop nu”.
55 short forms
55 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
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.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
10 other companies contacted
Loading the homepage contacts 10 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 leurs.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Magento
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on leurs.nl, including 14 speed issues, 5 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.