Website review, no card needed

legobebe.com logo

legobebe.com website review

Visit site (opens in a new tab)Reviewed 20 November 202625 issues · 70 checks

This review found 25 issues worth fixing on legobebe.com, 8 of them high impact, across 70 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of legobebe.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. legobebe.com at 0.4 s0.4 s
  2. legobebe.com at 0.8 s0.8 s
  3. legobebe.com at 1.1 s1.1 s
  4. legobebe.com at 1.5 s1.5 s
  5. legobebe.com at 1.9 s1.9 s
  6. legobebe.com at 2.3 s2.3 s
  7. legobebe.com at 2.6 s2.6 s
  8. legobebe.com at 3.0 s3.0 s

Speed

3 to fix81
  • Render-blocking requests

    2.1 s

    24 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.

  • Mobile performance score: 81

    81/100

    Your mobile performance score is 81. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    590 ms · 124 KiB

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

  • Use efficient cache lifetimes

    150 ms · 207 KiB

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

  • Improve image delivery

    150 ms · 108 KiB

    4 images could be 108 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 54 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    37 KiB

    Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need.

  • Reduce unused JavaScript

    32 KiB

    About 32 KiB of JavaScript is downloaded but never used on this page.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Cloudflare, Google Fonts and Qode Interactive), adding 148 KiB and 16 ms of main-thread time.

  • 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: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 215 ms of it running JavaScript. That is comfortably low.

  • Server response: 101 ms

    101 ms

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

Core Web Vitals

4 to fix80
  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LEGO BEBE İhtiyacınıza yönelik; bebek & genç odası mobilyal…”.

  • First Contentful Paint: 2.3 s

    2.3 s

    The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 4.4 s

    4.4 s

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

  • Speed Index: 3.6 s

    3.6 s

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

  • 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.

2 checks passed
  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

  • Total Blocking Time: 2 ms

    2 ms

    Scripts block the page for only 2 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    main-img-2-600x768.jpg.webp 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.3 g of CO₂ per visit

    0.28 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.28 g of CO₂e: 33.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,003 KiB in 80 requests

    1,003 KiB

    Your homepage downloads 1,003 KiB in 80 requests on a phone: images 420 KiB (12), scripts 270 KiB (34) and stylesheets 175 KiB (27). 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

4 to fixGoogle 9194
  • 24 text elements with low contrast

    24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 8 tap targets too small

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

  • 12 links without text

    12 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 22 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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9282
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 44 internal links, 2 external

    The homepage links to 44 pages on legobebe.com and 2 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Lego Bebe”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Legobebe.com | Bebek & Genç Odası Mobilyaları”.

  • Canonical URL set

    The canonical URL is https://www.legobebe.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.legobebe.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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://www.legobebe.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

2 to fix90
  • 14 pages without a meta description

    https://www.legobebe.com/hakkimizda, https://www.legobebe.com/urunler, https://www.legobebe.com/iletisim, https://www.legobebe.com/blog, https://www.legobebe.com/online-imalat and https://www.legobebe.com/urun/sedef-bebek-odasi-takimi and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.legobebe.com/hakkimizda, https://www.legobebe.com/urunler, https://www.legobebe.com/iletisim, https://www.legobebe.com/blog and https://www.legobebe.com/online-imalat have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages with very little text

    https://www.legobebe.com/iletisim, https://www.legobebe.com/blog, https://www.legobebe.com/urun/sedef-bebek-odasi-takimi, https://www.legobebe.com/urun/karizma-bebek-odasi-takimi, https://www.legobebe.com/urun/derzli-bebek-odasi-takimi and https://www.legobebe.com/urun/panjurlu-bebek-odasi-takimi 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.

  • 3 pages slow to respond

    https://www.legobebe.com/urun/kale-bebek-odasi-takimi, https://www.legobebe.com/urun/akvaryum-bebek-odasi-takimi and https://www.legobebe.com/urun/panjurlu-xl-bebek-odasi-takimi took over 3 s to send their HTML from our server.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • 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

2 to fixGoogle 9687
  • 3 small tap targets

    3 of 11 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 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 101 words

    The homepage has only about 101 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 (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

  • 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.

  • 4 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 legobebe.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on legobebe.com, including 7 speed issues, 4 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

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