Website review, no card needed

canillulubaby.com logo

canillulubaby.com website review

Visit site (opens in a new tab)Reviewed 11 November 202635 issues · 65 checks

This review found 35 issues worth fixing on canillulubaby.com, 12 of them high impact, across 65 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 canillulubaby.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix71
  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 71

    71/100

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google CDN, eb4us.com and builderall.com), adding 3.2 MB and 27 ms of main-thread time.

  • builderall.com adds 0 ms

    0 ms

    builderall.com costs a phone 0 ms of main-thread work and 3.2 MB 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 JavaScript

    180 ms · 69 KiB

    About 69 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 180 ms faster on a phone.

  • 1 long task on the main thread

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

  • Improve image delivery

    14 KiB

    1 image could be 14 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    6 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (6 KiB).

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.3 s

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

  • Server response: 30 ms

    30 ms

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

Core Web Vitals

3 to fix66
  • Largest Contentful Paint: 18.4 s

    18.4 s

    Your largest element takes 18.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 18.4 s

    18.4 s

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

  • Speed Index: 4.2 s

    4.2 s

    Visually, the page fills in at 4.2 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.

3 checks passed
  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Cumulative Layout Shift: 0.054

    0.054

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

  • Total Blocking Time: 87 ms

    87 ms

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

Images and page weight

5 to fix43
  • 3 images over 500 KB

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

  • Page weight: 3.4 MB in 10 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 10 requests on a phone: images 3.2 MB (3), scripts 142 KiB (4) and HTML 28 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (1.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.

  • 5 images below the first screen load straight away

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

  • 3 images far larger than shown

    191 KiB

    3 images are downloaded at several times the size a phone draws them, for example 9258846.jpg at 1,080 px wide, shown at 340 px. Resized copies would save about 191 KiB.

  • About 0.9 g of CO₂ per visit

    0.95 g

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

Accessibility

8 to fixGoogle 9185
  • Images must have alternative text (3 elements)

    Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • All page content should be contained by landmarks (37 elements)

    All page content should be contained by landmarks: 37 elements on the page fail this check, rated moderate by axe-core.

  • Heading levels should only increase by one (2 elements)

    Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 4 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 checks passed
  • 26 automated accessibility rules passed

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

SEO

5 to fixGoogle 10072
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (22 characters)

    Your title is only 22 characters: “Canil Lulu Baby | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is long (161 characters)

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

4 checks passed
  • Canonical URL set

    The canonical URL is https://canillulubaby.com/.

  • 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://canillulubaby.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    4%

    A phone browser shows 223 words, but the HTML your server sends has only 9. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://canillulubaby.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.

Best practices

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://builderall.com//franquias/2/73748/editor-html/3484811.png.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'register')”.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

    6 of 6 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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.

  • 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 223 words

    The homepage has only about 223 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies, 1 of them by other companies (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.

  • 21 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Oracle Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on canillulubaby.com, including 7 speed issues, 5 SEO issues and 5 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