Website review, no card needed
wondr.care website review
Visit site (opens in a new tab)Reviewed 8 November 202637 issues · 91 checks
This review found 37 issues worth fixing on wondr.care, 14 of them high impact, across 91 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
81B- #41,381 of 123,879 reviewed websitesbeats 61%
- #27,425 of 69,702 online storesbeats 54%
- #26,427 of 63,406 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 186 ms |
| May 23, 2026 | 190 ms |
| May 30, 2026 | 194 ms |
| Jun 6, 2026 | 201 ms |
| Jun 13, 2026 | 207 ms |
| Jun 20, 2026 | 212 ms |
| Jun 27, 2026 | 216 ms |
| Jul 4, 2026 | 218 ms |
| Jul 11, 2026 | 223 ms |
| Jul 18, 2026 | 236 ms |
| Jul 25, 2026 | 245 ms |
| Aug 1, 2026 | 260 ms |
| Aug 8, 2026 | 268 ms |
| Aug 15, 2026 | 268 ms |
| Aug 22, 2026 | 268 ms |
| Aug 29, 2026 | 268 ms |
| Sep 5, 2026 | 268 ms |
| Sep 12, 2026 | 261 ms |
| Sep 19, 2026 | 256 ms |
| Sep 26, 2026 | 249 ms |
| Oct 3, 2026 | 245 ms |
| Oct 10, 2026 | 245 ms |
| Oct 17, 2026 | 245 ms |
| Oct 24, 2026 | 248 ms |
| Oct 31, 2026 | 246 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.5 s
1.1 s
1.6 s
2.1 s
2.7 s
3.2 s
3.7 s
4.3 s
Speed
Render-blocking requests
2.3 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Main-thread work: 5.7 s
A phone's processor spends 5.7 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,079 HTML elements
The page has 3,079 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
600 ms · 767 KiBAbout 767 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, runconverge.com and getdalton.com and others), adding 1.8 MB and 935 ms of main-thread time.
Use efficient cache lifetimes
650 ms · 435 KiB27 files are served with short cache lifetimes, so returning visitors download them again (435 KiB).
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 149 KiBAbout 149 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Minify CSS
300 ms · 43 KiB43 KiB could be saved by minifying CSS.
Google Tag Manager adds 261 ms
261 msGoogle Tag Manager costs a phone 261 ms of main-thread work and 552 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.
Shopify adds 70 ms
70 msShopify costs a phone 70 ms of main-thread work and 417 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.
Improve image delivery
150 ms · 57 KiB7 images could be 57 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 153 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
40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need.
Minify JavaScript
11 KiB11 KiB could be saved by minifying JavaScript.
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: 80 ms
80 msYour server sent the HTML in 80 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.
Time to Interactive: 27.1 s
27.1 sThe page becomes fully interactive after 27.1 s. Good is under 3.8 s.
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “GIVE A WONDR MOMENT”.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Real-user INP: 278 ms
278 msReal visitors wait 278 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 186 ms to 246 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 243 ms
243 msScripts block taps and scrolling for 243 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
6 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 CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 371 ms
371 msReal visitors wait 371 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 31% faster for real visitors
-31%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 5.1 MB in 416 requests
5.1 MBYour homepage downloads 5.1 MB in 416 requests on a phone: scripts 2.2 MB (150), fonts 1.1 MB (33) and other files 796 KiB (141). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.44 g of CO₂e: 172.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 7 failed. 5 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.
316 internal links, 14 external
The homepage links to 316 pages on wondr.care and 14 external pages.
7 checks passed
Meta description: 129 characters
Your meta description is 129 characters: “Ontdek WONDR: heerlijk geurende, vegan verzorgingsproducten. Van shampoo bars tot skincare. Goed voor jouw lichaam én d…”.
Title: 37 characters
Your title is a healthy 37 characters: “WONDR | Vegan Haar-, Body- & Skincare”.
Canonical URL set
The canonical URL is https://wondr.planetb.care/.
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://planetb.care/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,698 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://wondr.planetb.care/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
10 pages share a meta description
https://wondr.planetb.care/pages/general-membership, https://wondr.planetb.care/collections/wondr-hair, https://wondr.planetb.care/collections/wondr-body, https://wondr.planetb.care/collections/all-products-accesoires, https://wondr.planetb.care/collections/wondr-gifts and https://wondr.planetb.care/collections/pick-mix-planet-b and 4 others use the same meta description. A description written for each page earns more clicks.
10 pages without an H1
https://wondr.planetb.care/en, https://wondr.planetb.care/fr, https://wondr.planetb.care/collections/wondr-hair, https://wondr.planetb.care/collections/wondr-body, https://wondr.planetb.care/collections/wondr-skincare and https://wondr.planetb.care/collections/all-products-accesoires and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://wondr.planetb.care/collections/wondr-gifts has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
4 pages slow to respond
https://wondr.planetb.care/collections/wondr-liquids, https://wondr.planetb.care/pages/think-pink-deelactie, https://wondr.planetb.care/blogs/wondr-blogs and https://wondr.planetb.care/collections/shampoo-bars took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 120 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
3 broken images
3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343271704&Ver=2&mid=295e938a-a520-4459-ae5c-0012aa9f7f0e&bo=1&sid=d9992410db7911f1b5358b69f745c0bb&vid=d9993f50db7911f1a63c9d8e2b81e075&vids=1&msclkid=N&pi=918639831&l.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://gro-pixel-resolver-prod.vercel.app/api/resolve/gro_px_517ea6ca86c44b5a960a53d2a66cffd8?host…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
52 of 56 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 950 words of copy
The homepage carries about 950 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “START MET KERSTSHOPPEN”.
9 calls to action
The homepage has 9 calls to action, for example “Shop all”, “START MET KERSTSHOPPEN” and “Wondr Shop All →”.
7 short forms
7 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: 57 testimonial or review blocks, a star rating and 3 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity, Hotjar and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 6 mores (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.
39 cookies set on arrival
39Opening the homepage sets 39 cookies, 2 of them by other companies (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.
50 other companies contacted
Loading the homepage contacts 50 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 wondr.care, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Simprosys Google Shopping Feed · Microsoft Clarity · Multifeeds · Gsc Countdown Timer · Gdpr Cookie Consent · Auto Gifter · stamped.io · socialsnowball.io · 9gtb.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Hotjar | Microsoft Clarity
- Hosting
- Cloudflare
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 wondr.care, including 20 speed issues and 1 SEO issue. 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.