Website review, no card needed

bebetei.ro logo

bebetei.ro website review

Visit site (opens in a new tab)Reviewed 25 October 202639 issues · 82 checks

This review found 39 issues worth fixing on bebetei.ro, 18 of them high impact, across 82 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.6 s2.0 sMay 2Oct 172.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
142 ms109 msMay 2Oct 17138 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026115 ms
May 9, 2026114 ms
May 16, 2026113 ms
May 23, 2026113 ms
May 30, 2026113 ms
Jun 6, 2026115 ms
Jun 13, 2026118 ms
Jun 20, 2026120 ms
Jun 27, 2026120 ms
Jul 4, 2026121 ms
Jul 11, 2026120 ms
Jul 18, 2026120 ms
Jul 25, 2026120 ms
Aug 1, 2026120 ms
Aug 8, 2026123 ms
Aug 15, 2026127 ms
Aug 22, 2026132 ms
Aug 29, 2026136 ms
Sep 5, 2026136 ms
Sep 12, 2026136 ms
Sep 19, 2026137 ms
Sep 26, 2026137 ms
Oct 3, 2026137 ms
Oct 10, 2026138 ms
Oct 17, 2026138 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

Full-page screenshot of bebetei.ro (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bebetei.ro at 0.5 s0.5 s
  2. bebetei.ro at 1.1 s1.1 s
  3. bebetei.ro at 1.6 s1.6 s
  4. bebetei.ro at 2.2 s2.2 s
  5. bebetei.ro at 2.7 s2.7 s
  6. bebetei.ro at 3.3 s3.3 s
  7. bebetei.ro at 3.8 s3.8 s
  8. bebetei.ro at 4.4 s4.4 s

Speed

12 to fix24
  • Improve image delivery

    56.7 s · 19.5 MB

    108 images could be 19.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 56.7 s faster on a phone.

  • Use efficient cache lifetimes

    1.8 s · 282 KiB

    8 files are served with short cache lifetimes, so returning visitors download them again (282 KiB).

  • Reduce unused JavaScript

    1.1 s · 287 KiB

    About 287 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 24

    24/100

    Your mobile performance score is 24 (desktop: 43). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 4,038 HTML elements

    The page has 4,038 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, Facebook and TikTok and others), adding 920 KiB and 907 ms of main-thread time.

  • Render-blocking requests

    850 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

  • Font display

    550 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).

  • Reduce unused CSS

    350 ms · 52 KiB

    About 52 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 350 ms faster on a phone.

  • Google Tag Manager adds 324 ms

    324 ms

    Google Tag Manager costs a phone 324 ms of main-thread work and 365 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.

  • 8 long tasks on the main thread

    8 long tasks block the main thread while loading, the longest for 287 ms. During a long task the page ignores taps.

  • Main-thread work: 2.6 s

    A phone's processor spends 2.6 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Minify CSS

    180 ms · 9 KiB

    9 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    150 ms · 30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    6 KiB

    6 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: 270 ms

    270 ms

    Your server sent the HTML in 270 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix67
  • 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 TTFB: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 66.7 s

    66.7 s

    Your largest element takes 66.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ofertele lunii octombrie”.

  • Time to Interactive: 66.8 s

    66.8 s

    The page becomes fully interactive after 66.8 s. Good is under 3.8 s.

  • Cumulative Layout Shift: 1.21

    1.21

    The layout shifts by 1.21 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 6.7 s

    6.7 s

    Visually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 803 ms

    803 ms

    Scripts block taps and scrolling for 803 ms in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.0 s

    3.0 s

    Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 21% slower for real visitors

    +21%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 115 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.0 s

    2.0 s

    Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

  • 40 images without width and height

    40 images have no width and height attributes, so the layout jumps as each one loads.

4 checks passed
  • Real-user INP: 168 ms

    168 ms

    Real visitors wait 168 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 14% faster for real visitors

    -14%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

Images and page weight

5 to fix28
  • Page weight: 24.3 MB in 229 requests

    24.3 MB

    Your homepage downloads 24.3 MB in 229 requests on a phone: images 22.8 MB (160), scripts 1,015 KiB (24) and fonts 325 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.

  • 24 images in older formats

    24 images (5.9 MB) 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.

  • 22 images below the first screen load straight away

    22 images further down the page (5.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 8 images far larger than shown

    463 KiB

    8 images are downloaded at several times the size a phone draws them, for example v3-500-x-500-px-bulina-cadouri-6ad725cf21ef7450913731.png at 500 px wide, shown at 150 px. Resized copies would save about 463 KiB.

  • About 6.9 g of CO₂ per visit

    6.89 g

    By the Sustainable Web Design model, a visit to your homepage emits about 6.89 g of CO₂e: 826.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

1 to fixGoogle 9798
  • 22 tap targets too small

    22 tap targets are too small or too close together to hit reliably with a finger.

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 289 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10079
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (200 characters)

    Your meta description is 200 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 813 internal links, 9 external

    The homepage links to 813 pages on bebetei.ro and 9 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Bebe Tei - Magazinul familiei tale. Alege din oferta variata de dermatocosmetice, produse pentru igiena orala, produse …”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Magazinul Familiei Tale : Bebe Tei”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://comenzi.bebetei.ro/sitemaps/sitemap_categories_RO.xml.

AI search readiness

2 to fix53
  • robots.txt blocks 4 AI answer engine crawlers

    4 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://comenzi.bebetei.ro/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.

  • Opted out of AI training for 2 crawlers

    robots.txt blocks Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (2,400 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 13 pages share a meta description

    https://comenzi.bebetei.ro/despre-noi, https://comenzi.bebetei.ro/cum-comand, https://comenzi.bebetei.ro/transport-si-plata, https://comenzi.bebetei.ro/termeni-si-conditii, https://comenzi.bebetei.ro/returnare-si-garantie and https://comenzi.bebetei.ro/intrebari-frecvente and 7 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.

7 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 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9691
  • 21 small tap targets

    21 of 90 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

1 to fix83
  • 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 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 1,088 words of copy

    The homepage carries about 1,088 words of visible text.

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Lentile de Contact”, “Solutii pentru Lentile de Contact” and “Termometru non contact, TOW015194, Vicks”.

  • 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: 10 testimonial or review blocks, 10 customer or partner logos and 29 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 cookies, 2 of them by other companies (measured from a US location before any click).

  • 26 other companies contacted

    Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 bebetei.ro, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on bebetei.ro, including 23 speed issues, 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25