Website review, no card needed
ebebek.co.uk website review
Visit site (opens in a new tab)Reviewed 6 November 202637 issues · 85 checks
This review found 37 issues worth fixing on ebebek.co.uk, 12 of them high impact, across 85 checks. The most urgent: mobile performance score: 48. 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,508 of 124,378 reviewed websitesbeats 61%
- #27,483 of 69,874 online storesbeats 54%
- #26,476 of 63,538 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 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 | 138 ms |
| May 23, 2026 | 139 ms |
| May 30, 2026 | 143 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 157 ms |
| Jul 4, 2026 | 160 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 164 ms |
| Aug 1, 2026 | 171 ms |
| Aug 8, 2026 | 175 ms |
| Aug 15, 2026 | 177 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 167 ms |
| Sep 5, 2026 | 161 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 167 ms |
| Oct 10, 2026 | 169 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 178 ms |
| Oct 31, 2026 | 177 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: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,206 HTML elements
The page has 3,206 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 (Google Tag Manager, Shopify and growave.io and others), adding 2.6 MB and 1.7 s of main-thread time.
Reduce unused JavaScript
945 KiBAbout 945 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
250 ms · 395 KiB21 images could be 395 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Google Tag Manager adds 496 ms
496 msGoogle Tag Manager costs a phone 496 ms of main-thread work and 524 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 426 ms
426 msShopify costs a phone 426 ms of main-thread work and 935 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 291 ms. During a long task the page ignores taps.
Google CDN adds 179 ms
179 msGoogle CDN costs a phone 179 ms of main-thread work and 298 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
180 ms · 127 KiBAbout 127 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 180 ms faster on a phone.
Render-blocking requests
200 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
Use efficient cache lifetimes
142 KiB13 files are served with short cache lifetimes, so returning visitors download them again (142 KiB).
Legacy JavaScript
39 KiBPolyfills for old browsers add 39 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.
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.
1 checks passed
Server response: 83 ms
83 msYour server sent the HTML in 83 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.0 s
9.0 sYour largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 20.5 s
20.5 sThe page becomes fully interactive after 20.5 s. Good is under 3.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 791 ms
791 msScripts block taps and scrolling for 791 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 138 ms to 177 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
9 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 170 ms
170 msReal visitors wait 170 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 555 ms
555 msReal visitors wait 555 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.029
0.029The layout barely moves while loading (CLS 0.029, good is under 0.1).
Images and page weight
Page weight: 5.7 MB in 490 requests
5.7 MBYour homepage downloads 5.7 MB in 490 requests on a phone: scripts 2.5 MB (182), images 1.7 MB (73) and other files 1.2 MB (204). Under 2 MB keeps phones on slow connections fast.
About 1.6 g of CO₂ per visit
1.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.63 g of CO₂e: 195.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Documents must have <title> element to aid in navigation (1 element)
Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.
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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 234 images in the HTML carry an alt attribute.
6 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 10 WCAG 2.2 A/AA and best-practice rules on the phone render: 6 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
349 internal links, 0 external
The homepage links to 349 pages on ebebek.co.uk and 0 external pages.
7 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Buy now at the best price on ebebek.co.uk! Enjoy high quality, safety, and convenience. Fast delivery & great deals awa…”.
Title: 65 characters
Your title is a healthy 65 characters: “ebebek | Award Winning Best Products for Babies, Kids & Parenting”.
Canonical URL set
The canonical URL is https://ebebek.co.uk/.
Structured data in place
Structured data found: Organization, Store, WebPage 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://ebebek.co.uk/sitemap.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
2 checks passed
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
llms.txt published
The site publishes https://ebebek.co.uk/llms.txt (39 KiB, 258 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://ebebek.co.uk/pages/wishlist and https://ebebek.co.uk/collections/pushchairs-car-seats, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page without a title
https://ebebek.co.uk/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://ebebek.co.uk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://ebebek.co.uk/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
12 pages share a meta description
https://ebebek.co.uk/collections/baby-friday, https://ebebek.co.uk/collections/pushchairs-prams, https://ebebek.co.uk/collections/travel-systems, https://ebebek.co.uk/collections/twin-prams-pushchairs, https://ebebek.co.uk/collections/car-seats and https://ebebek.co.uk/collections/highchairs and 6 others use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://ebebek.co.uk/collections/baby-friday and https://ebebek.co.uk/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://ebebek.co.uk/collections/bouncers-walkers-swings, https://ebebek.co.uk/collections/travel-cots and https://ebebek.co.uk/collections/baby-bedside-cribs took over 3 s to send their 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.
2 checks passed
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.
Best practices
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Boost > [ERROR] Cart icon selector not found in matched config”.
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.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 12 words
The homepage has only about 12 words of visible text; thin pages give Google and first-time buyers little to go on.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
7 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Shop Now Pay Later with Klarna”, “Start shopping” and “Contact Us”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 2 trust badges and “over 200 brands”.
Analytics in place
Analytics detected: Google Tag Manager.
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.
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
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
21 cookies set on arrival
21Opening the homepage sets 21 cookies (measured from a US location before any click).
40 other companies contacted
Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 ebebek.co.uk, 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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Onetrust Consent Management · Google Youtube · Selly Promotion Pricing · Swatch King · Blocky Fraud Blocker · Boost Ai Search Filter · Returngo Returns Exchanges · Multi Location Inv · Flair · Inbox · Seowill Redirects · Klaviyo Email Marketing Sms · Forms · Cowlendar · Growave Loyalty Wishlist
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
- Google Tag Manager
- Hosting
- Shopify
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 ebebek.co.uk, including 16 speed issues, 2 SEO issues and 4 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.