Website review, no card needed
kidobebe.com website review
Visit site (opens in a new tab)Reviewed 17 November 202627 issues · 88 checks
This review found 27 issues worth fixing on kidobebe.com, 7 of them high impact, across 88 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
88B- #5,585 of 116,895 reviewed websitesbeats 93%
- #3,103 of 66,850 online storesbeats 93%
- #3,008 of 60,976 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 984 ms |
| Oct 10, 2026 | 739 ms |
| Oct 17, 2026 | 702 ms |
| Oct 24, 2026 | 691 ms |
| Oct 31, 2026 | 693 ms |
| Nov 7, 2026 | 690 ms |
| Nov 14, 2026 | 686 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 153 ms |
| Jun 27, 2026 | 155 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 159 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 147 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 143 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 149 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 150 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 138 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 150 ms |
| Oct 17, 2026 | 176 ms |
| Oct 24, 2026 | 216 ms |
| Oct 31, 2026 | 227 ms |
| Nov 7, 2026 | 192 ms |
| Nov 14, 2026 | 162 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
Render-blocking requests
1.6 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
4,116 HTML elements
The page has 4,116 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 1 ms
1 msShopify costs a phone 1 ms of main-thread work and 322 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
122 KiB6 images could be 122 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
71 KiBAbout 71 KiB of CSS is downloaded but never applied on this page.
7 third-party services on the page
7 third-party services load with your homepage (Shopify, Google CDN and shop.app and others), adding 428 KiB and 1 ms of main-thread time.
Use efficient cache lifetimes
28 KiB6 files are served with short cache lifetimes, so returning visitors download them again (28 KiB).
Minify CSS
16 KiB16 KiB could be saved by minifying CSS.
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.
3 checks passed
Mobile performance score: 92
92/100Your mobile performance score is 92. That is in Google's “good” band (90 and up).
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 51 ms of it running JavaScript. That is comfortably low.
Server response: 18 ms
18 msYour server sent the HTML in 18 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.
Real-user INP: 234 ms
234 msReal visitors wait 234 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “🔄”. Most of its time is element render delay (1.5 s).
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index). Good is under 3.4 s.
8 images without width and height
8 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-11-14, real Chrome visitors' tap response (inp) went from 154 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
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: 412 ms
412 msReal visitors wait 412 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 60% faster for real visitors
-60%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 2.6 s
2.6 sThe page is fully interactive after 2.6 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
An image on the first screen is lazy-loaded
2_0f380eae-9da2-42b1-89b4-b9eadd9ad91c.jpg 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).
About 0.5 g of CO₂ per visit
0.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.50 g of CO₂e: 60.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.8 MB in 146 requests
1.8 MBYour homepage downloads 1.8 MB in 146 requests on a phone: images 692 KiB (77), scripts 586 KiB (34) and fonts 211 KiB (5). That is a lean page.
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
Form elements should have a visible label (61 elements)
Form elements should have a visible label: 61 elements on the page fail this check, rated serious by axe-core.
22 text elements with low contrast
22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 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 (h2 → h5, h2 → h5 and h2 → h5), 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. (19 elements).
1 checks passed
45 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: 45 passed and 8 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.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
593 internal links, 11 external
The homepage links to 593 pages on kidobebe.com and 11 external pages.
7 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Shop your baby's essentials at Kido Bebe, a Montreal baby store offering a variety of baby products, furniture, strolle…”.
Title: 42 characters
Your title is a healthy 42 characters: “Montreal's Favorite Baby Store | Kido Bebe”.
Canonical URL set
The canonical URL is https://kidobebe.com/.
Structured data in place
Structured data found: BreadcrumbList, LocalBusiness, Organization, Store 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://kidobebe.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, description and contact details; logo and sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,567 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://kidobebe.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
10 pages without a meta description
https://kidobebe.com/pages/baby-registry, https://kidobebe.com/collections/gift-cards, https://kidobebe.com/collections/limited-time-sale, https://kidobebe.com/collections/bundle, https://kidobebe.com/collections/clearance and https://kidobebe.com/collections/sales and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://kidobebe.com/pages/baby-registry, https://kidobebe.com/collections/gift-cards, https://kidobebe.com/collections/sale, https://kidobebe.com/collections/limited-time-sale, https://kidobebe.com/collections/bundle and https://kidobebe.com/collections/clearance and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages with very little text
https://kidobebe.com/collections/sale, https://kidobebe.com/collections/limited-time-sale, https://kidobebe.com/collections/bundle, https://kidobebe.com/collections/clearance, https://kidobebe.com/collections/new-arrivals and https://kidobebe.com/collections/new-arrivals-gear and 2 others have 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.
1 page slow to respond
https://kidobebe.com/collections/sale took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 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.
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 14 pages that loaded have a <title>.
Best practices
28 small tap targets
28 of 82 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 543 words of copy
The homepage carries about 543 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start your baby registry”.
34 calls to action
The homepage has 34 calls to action, for example “Shop All Sales”, “Shop New products” and “Shop Now”.
33 short forms
33 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 80 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
7 other companies contacted
Loading the homepage contacts 7 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 kidobebe.com, 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
Blockify Fraud Filter · Wishlist Hero · Microsoft Clarity · Gift Reggie Gift Registry · Judge Me Reviews · Klaviyo Email Marketing Sms · Rapid Search Bar Filter · Region Restrictions · Affirm · Freegifts · cloudfront.net · bogos.io
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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | 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 27 issues on kidobebe.com, including 9 speed issues, 2 SEO issues 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.