Website review, no card needed
zipsterbaby.fr website review
Visit site (opens in a new tab)Reviewed 20 November 202641 issues · 93 checks
This review found 41 issues worth fixing on zipsterbaby.fr, 14 of them high impact, across 93 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- #48,261 of 123,845 reviewed websitesbeats 55%
- #31,905 of 69,689 online storesbeats 48%
- #30,661 of 63,398 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.9 s |
| Nov 14, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 160 ms |
| Jun 13, 2026 | 165 ms |
| Jun 20, 2026 | 163 ms |
| Jun 27, 2026 | 166 ms |
| Jul 4, 2026 | 169 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 162 ms |
| Aug 1, 2026 | 169 ms |
| Aug 8, 2026 | 173 ms |
| Aug 15, 2026 | 176 ms |
| Aug 22, 2026 | 177 ms |
| Aug 29, 2026 | 170 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 177 ms |
| Sep 26, 2026 | 181 ms |
| Oct 3, 2026 | 183 ms |
| Oct 10, 2026 | 185 ms |
| Oct 17, 2026 | 184 ms |
| Oct 24, 2026 | 185 ms |
| Oct 31, 2026 | 185 ms |
| Nov 7, 2026 | 188 ms |
| Nov 14, 2026 | 193 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
1.1 s
2.2 s
3.4 s
4.5 s
5.6 s
6.7 s
7.9 s
9.0 s
Speed
Improve image delivery
2.5 s · 1.2 MB28 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Main-thread work: 16.5 s
A phone's processor spends 16.5 s on main-thread work while loading, 6.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
4,184 HTML elements
The page has 4,184 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Shopify and commslayer.com and others), adding 5.0 MB and 1.4 s of main-thread time.
Reduce unused JavaScript
450 ms · 1,015 KiBAbout 1,015 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Shopify adds 427 ms
427 msShopify costs a phone 427 ms of main-thread work and 2.7 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.
Clarity adds 473 ms
473 msClarity costs a phone 473 ms of main-thread work and 29 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 · 153 KiBAbout 153 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.
Use efficient cache lifetimes
406 KiB16 files are served with short cache lifetimes, so returning visitors download them again (406 KiB).
Legacy JavaScript
300 ms · 59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
commslayer.com adds 143 ms
143 mscommslayer.com costs a phone 143 ms of main-thread work and 1.6 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 158 ms. During a long task the page ignores taps.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 23 ms
23 msYour server sent the HTML in 23 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 25.4 s
25.4 sYour largest element takes 25.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Animal Kingdom Collection”.
Speed Index: 27.2 s
27.2 sVisually, the page fills in at 27.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 45.3 s
45.3 sThe page becomes fully interactive after 45.3 s. Good is under 3.8 s.
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 355 ms
355 msScripts block taps and scrolling for 355 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.108
0.108The layout shifts by 0.108 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 161 ms to 193 ms 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: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 196 ms
196 msReal visitors wait 196 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 570 ms
570 msReal visitors wait 570 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 12.0 MB in 545 requests
12.0 MBYour homepage downloads 12.0 MB in 545 requests on a phone: images 4.8 MB (117), other files 3.5 MB (309) and scripts 2.9 MB (90). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
banner_evergreen.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images below the first screen load straight away
2 images further down the page (114 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.4 g of CO₂ per visit
3.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.40 g of CO₂e: 407.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Scrollable region must have keyboard access (7 elements)
Scrollable region must have keyboard access: 7 elements on the page fail this check, rated serious by axe-core.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
22 links without text
22 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 (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 11 failed. 2 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.
261 internal links, 12 external
The homepage links to 261 pages on zipsterbaby.fr and 12 external pages.
7 checks passed
Meta description: 105 characters
Your meta description is 105 characters: “Shop beautifully soft, sustainable bamboo clothes for babies, children and adults. Designed in Amsterdam.”.
Title: 61 characters
Your title is a healthy 61 characters: “Zipster Official Site | Soft Bamboo wear for the whole family”.
Canonical URL set
The canonical URL is https://zipsterbaby.com/en-us.
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://zipsterbaby.com/sitemap.xml.
AI search readiness
4 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 (1,669 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://zipsterbaby.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://zipsterbaby.com/en-us/collections/christmas-2026 and https://zipsterbaby.com/en-us/collections/pure-collection use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://zipsterbaby.com/en-us/collections/zipster%E2%84%A2-ribbed, whose canonical is https://zipsterbaby.com/en-us/collections/zipster%e2%84%a2-ribbed. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://zipsterbaby.com/en-us/collections/christmas-2026, https://zipsterbaby.com/en-us/collections/pure-collection and https://zipsterbaby.com/en-us/collections/playwear have 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 95 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
9 small tap targets
9 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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 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.
About 435 words of copy
The homepage carries about 435 words of visible text.
6 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Shop All Mum”, “Shop Animal Kingdom” and “Shop Now”.
63 short forms
63 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo, a star rating and 5 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity and Hotjar.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Hotjar, Klaviyo and Microsoft Clarity (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.
16 cookies set on arrival
16Opening the homepage sets 16 cookies, 4 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.
35 other companies contacted
Loading the homepage contacts 35 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 zipsterbaby.fr, 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
Triplewhale · Microsoft Clarity · Klaviyo Email Marketing Sms · Langshop · Wrapped · Hidepay · Upez · Airwallex Fraud Protection · Reviews Co Uk Product And Merchant Review Collection · Postco 360 Staging · herokuapp.com · rise-ai.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 41 issues on zipsterbaby.fr, including 20 speed issues, 1 SEO issue and 1 conversion gap. 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.