mibaby.es website review

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

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

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

12 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

176 KiB could be saved by minifying JavaScript.

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

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

2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 182 KiB and 242 ms of main-thread time.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Utilizamos cookies, píxeles de seguimiento y tecnologías si…”.

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

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

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

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

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

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

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

11 images are downloaded at several times the size a phone draws them, for example icon_pig.png at 632 px wide, shown at 80 px. Resized copies would save about 1.1 MB.

Your homepage downloads 3.8 MB in 61 requests on a phone: images 3.0 MB (29), scripts 608 KiB (8) and stylesheets 133 KiB (14). Under 2 MB keeps phones on slow connections fast.

22 images (2.6 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.

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

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

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

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

4 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

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

Structured data found (Product) but with 1 problem, for example “Product: no offers (price) block”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing og:title, so shared links fall back to guesses.

The homepage links to 26 pages on mibaby.es and 5 external pages.

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.

There is no https://www.mibaby.es/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.

https://www.mibaby.es/lista-nacimiento-de-amazon, https://www.mibaby.es/panales-populares, https://www.mibaby.es/imprescindible-con-el-bebe, https://www.mibaby.es/ProfilEinstellungen, https://www.mibaby.es/condiciones-generales and https://www.mibaby.es/politica-de-privacidad and 1 other are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.mibaby.es/imprescindible-con-el-bebe, https://www.mibaby.es/politica-de-privacidad and https://www.mibaby.es/aviso-legal have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mibaby.es/ProfilEinstellungen and https://www.mibaby.es/condiciones-generales use the same meta description. A description written for each page earns more clicks.

https://www.mibaby.es/ProfilEinstellungen, https://www.mibaby.es/condiciones-generales, https://www.mibaby.es/politica-de-privacidad and https://www.mibaby.es/aviso-legal have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mibaby.es/raffles-bebe and https://www.mibaby.es/el-quipo 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.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 365 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

Opening the homepage sets 6 cookies (measured from a US location before any click).

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.

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