Website review, no card needed
bebevista.com website review
Visit site (opens in a new tab)Reviewed 22 November 202640 issues · 74 checks
This review found 40 issues worth fixing on bebevista.com, 14 of them high impact, across 74 checks. The most urgent: use efficient cache lifetimes. 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
62D- #119,918 of 125,055 reviewed websitesbeats 3%
- #68,925 of 70,102 online storesbeats 1%
- #60 of 64 OpenCart storesbeats 5%
Closest competitors among OpenCart stores
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
9.3 s · 2.6 MB29 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Improve image delivery
6.0 s · 1.5 MB15 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.0 s faster on a phone.
Reduce unused JavaScript
1.9 s · 414 KiBAbout 414 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.5 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Font display
650 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).
Google Tag Manager adds 240 ms
240 msGoogle Tag Manager costs a phone 240 ms of main-thread work and 458 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.
Facebook adds 201 ms
201 msFacebook costs a phone 201 ms of main-thread work and 319 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.
1,749 HTML elements
The page has 1,749 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Facebook and Roxr Software and others), adding 891 KiB and 454 ms of main-thread time.
Reduce unused CSS
150 ms · 79 KiBAbout 79 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 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: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 607 ms of it running JavaScript. That is comfortably low.
Server response: 132 ms
132 msYour server sent the HTML in 132 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.5 s
16.5 sYour largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Cumulative Layout Shift: 1.091
1.091The layout shifts by 1.091 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 14.7 s
14.7 sVisually, the page fills in at 14.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 18.3 s
18.3 sThe page becomes fully interactive after 18.3 s. Good is under 3.8 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Total Blocking Time: 98 ms
98 msScripts block the page for only 98 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.3 MB in 58 requests
3.3 MBYour homepage downloads 3.3 MB in 58 requests on a phone: images 1.9 MB (21), scripts 919 KiB (12) and fonts 283 KiB (5). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (686 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
1 image far larger than shown
196 KiB1 image is downloaded at several times the size a phone draws it, for example Header-1920x909w.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 196 KiB.
2 images below the first screen load straight away
2 images further down the page (128 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.93 g of CO₂e: 111.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
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.
All page content should be contained by landmarks (88 elements)
All page content should be contained by landmarks: 88 elements on the page fail this check, rated moderate by axe-core.
20 form fields without a label
20 form fields have no label, so screen readers announce an empty box and autofill guesses.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 49 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 3 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.
85 links crawlers can't follow
85 links have no real href, so search engines can't follow them.
Title is short (9 characters)
Your title is only 9 characters: “Bebevista”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (52 characters)
Your meta description is only 52 characters: “Онлайн магазин за бебешки и детски дрехи и аксесоари”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.
125 internal links, 2 external
The homepage links to 125 pages on bebevista.com and 2 external pages.
3 checks passed
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.
XML sitemap found
Your XML sitemap is reachable at https://bebevista.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, 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.
No llms.txt
There is no https://bebevista.com/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.
1 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.
Other pages
4 pages share 2 titles
https://bebevista.com/bebe-momiche/bebe-momiche-aksesoari and https://bebevista.com/bebe-momche/bebe-momche-aksesoari all use the title “Аксесоари”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://bebevista.com/bebe-momiche/bebe-momiche-aksesoari, https://bebevista.com/bebe-momiche/bebe-momiche-obuvki and https://bebevista.com/bebe-momche/bebe-momche-aksesoari have no meta description, so Google writes the search snippet from whatever text it finds.
13 links to non-canonical URLs
Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://bebevista.com/bebe-momiche/bebe-momiche-aksesoari, whose canonical is https://bebevista.com/bebe-momiche-aksesoari. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
11 pages with very little text
https://bebevista.com/bebe-momiche/bebe-momiche-bluzi-i-rizi-s-dylyg-rykav, https://bebevista.com/bebe-momiche/bebe-momiche-bluzi-i-rizi-s-kys-rykav, https://bebevista.com/bebe-momiche/bebe-momiche-bodita-i-gashterizoni, https://bebevista.com/bebe-momiche/bebe-momiche-bolera-zhiletki-suitcheri, https://bebevista.com/bebe-momiche/bebe-momiche-komplekti and https://bebevista.com/bebe-momiche/bebe-momiche-kysi-pantaloni-i-bermudi and 5 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.
2 pages slow to respond
https://bebevista.com/bebe-momiche/bebe-momiche-yaketa-palta-i-greiki and https://bebevista.com/bebe-momche/bebe-momche-aksesoari took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
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
34 small tap targets
34 of 71 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 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 80 words
The homepage has only about 80 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
12 other companies contacted
Loading the homepage contacts 12 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 bebevista.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2019.
Stack
- Analytics
- Google Analytics
- Hosting
- SuperHosting.BG Ltd.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on bebevista.com, including 15 speed issues, 6 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.