Website review, no card needed
crisp.nl website review
Visit site (opens in a new tab)Reviewed 3 November 202618 issues · 72 checks
This review found 18 issues worth fixing on crisp.nl, 4 of them high impact, across 72 checks. The most urgent: positive tabindex. 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
93AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 113 ms |
| May 23, 2026 | 113 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 114 ms |
| Jun 27, 2026 | 117 ms |
| Jul 4, 2026 | 119 ms |
| Jul 11, 2026 | 119 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 115 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 111 ms |
| Aug 29, 2026 | 111 ms |
| Sep 5, 2026 | 112 ms |
| Sep 12, 2026 | 117 ms |
| Sep 19, 2026 | 118 ms |
| Sep 26, 2026 | 117 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 129 ms |
| Oct 24, 2026 | 133 ms |
| Oct 31, 2026 | 128 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
Mobile performance score: 89
89/100Your mobile performance score is 89. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
274 KiB9 images could be 274 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1 third-party service on the page
1 third-party service load with your homepage (Google Tag Manager), adding 176 KiB and 188 ms of main-thread time.
Reduce unused JavaScript
188 KiBAbout 188 KiB of JavaScript is downloaded but never used on this page.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 163 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 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.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 329 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
Time to Interactive: 8.1 s
8.1 sThe page becomes fully interactive after 8.1 s. Good is under 3.8 s.
Largest Contentful Paint: 3.6 s
3.6 sYour largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “De boodschappen-app met de beste smaak Vandaag besteld, mor…”.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 113 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 455 ms
455 msReal visitors wait 455 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 125 ms
125 msScripts block the page for only 125 ms while loading. Good is under 200 ms.
Speed Index: 2.5 s
2.5 sVisually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.013
0.013The layout barely moves while loading (CLS 0.013, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Images and page weight
1 image far larger than shown
32 KiB1 image is downloaded at several times the size a phone draws it, for example x8WlqMpFp4kr8LO0 at 1,500 px wide, shown at 390 px. Resized copies would save about 32 KiB.
7 images below the first screen load straight away
7 images further down the page (255 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.42 g of CO₂e: 49.9 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.5 MB in 36 requests
1.5 MBYour homepage downloads 1.5 MB in 36 requests on a phone: images 641 KiB (28), fonts 506 KiB (4) and scripts 337 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Positive tabindex
6 elements have a tabindex above 0, which scrambles the keyboard order.
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.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
1 checks passed
25 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 27 WCAG 2.2 A/AA and best-practice rules on the phone render: 25 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
22 internal links, 13 external
The homepage links to 22 pages on crisp.nl and 13 external pages.
6 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “De boodschappen-app met de beste smaak. Vandaag besteld, morgen gratis thuisbezorgd in heel Nederland. Kom je kiezen wa…”.
One H1 headline
Your main headline reads: “De boodschappen-app met de beste smaak”.
Title: 53 characters
Your title is a healthy 53 characters: “Crisp online supermarkt | Beter eten, lekker geregeld”.
Canonical URL set
The canonical URL is https://crisp.nl/.
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://crisp.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://crisp.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 (1,204 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://crisp.nl/wa-contact is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a meta description
https://crisp.nl/onze-producten and https://crisp.nl/team use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://crisp.nl/cookiebeleid, https://crisp.nl/privacy, https://crisp.nl/wa-contact, https://crisp.nl/voorwaarden and https://crisp.nl/toegankelijkheid have no <h1> headline, so visitors and search engines get no clear main topic.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 12 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 12 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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.
About 468 words of copy
The homepage carries about 468 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Download nu de app”.
5 calls to action
The homepage has 5 calls to action, for example “Contact” and “Download nu de app”.
Social proof on the page
Social proof on the homepage: 32 testimonial or review blocks, 1 customer or partner logo and 2 trust badges.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
1 other company contacted
Loading the homepage contacts 1 host 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 crisp.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Google Cloud
Hiring
- Hiring
- 40 open roles
- Teams
- Internships - HQ (13), Warehouse (6), Bezorger (4), Vers Bereid (4)
- Job board
- ashby
- Careers page
- jobs.ashbyhq.com/crisp (opens in a new tab)
Company
- Founded
- 2018
- Headquarters
- Amsterdam
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on crisp.nl, including 5 speed issues, 1 SEO issue 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.