Website review, no card needed
asilebaby.com website review
Visit site (opens in a new tab)Reviewed 11 November 202640 issues · 75 checks
This review found 40 issues worth fixing on asilebaby.com, 16 of them high impact, across 75 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
72C- #85,177 of 109,350 reviewed websitesbeats 19%
- #52,630 of 61,859 online storesbeats 12%
- #1,697 of 2,524 WooCommerce storesbeats 28%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
14.3 s · 3.5 MB50 files are served with short cache lifetimes, so returning visitors download them again (3.5 MB).
Render-blocking requests
9.3 s26 files block the first paint until they finish downloading. Deferring or inlining them could save about 9.3 s.
Reduce unused CSS
7.2 s · 1.3 MBAbout 1.3 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 7.2 s faster on a phone.
Improve image delivery
2.5 s · 1.2 MB18 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Reduce unused JavaScript
2.4 s · 482 KiBAbout 482 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Minify CSS
750 ms · 112 KiB112 KiB could be saved by minifying CSS.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Google Tag Manager and WordPress and others), adding 2.3 MB and 310 ms of main-thread time.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
WordPress adds 76 ms
76 msWordPress costs a phone 76 ms of main-thread work and 1.8 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.
Legacy JavaScript
250 ms · 39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 96 ms. During a long task the page ignores taps.
Minify JavaScript
9 KiB9 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.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 528 ms of it running JavaScript. That is comfortably low.
Server response: 109 ms
109 msYour server sent the HTML in 109 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 9.5 s
9.5 sThe first text or image appears after 9.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 23.0 s
23.0 sYour largest element takes 23.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “HASTA EL 40% RE BA JAS DESCUBRIR”.
Speed Index: 20.4 s
20.4 sVisually, the page fills in at 20.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 23.8 s
23.8 sThe page becomes fully interactive after 23.8 s. Good is under 3.8 s.
27 images without width and height
27 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.
2 checks passed
Total Blocking Time: 76 ms
76 msScripts block the page for only 76 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.026
0.026The layout barely moves while loading (CLS 0.026, good is under 0.1).
Images and page weight
Page weight: 5.6 MB in 100 requests
5.6 MBYour homepage downloads 5.6 MB in 100 requests on a phone: images 2.9 MB (37), stylesheets 1.4 MB (23) and scripts 1.1 MB (31). Under 2 MB keeps phones on slow connections fast.
15 images below the first screen load straight away
15 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images in older formats
5 images (524 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.
About 1.6 g of CO₂ per visit
1.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.59 g of CO₂e: 191.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (32 elements)
All page content should be contained by landmarks: 32 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (21 characters)
Your title is only 21 characters: “Asile. – Baby clothes”. 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.
5 H1 headlines
There are 5 <h1> headlines (“rebajas”, “RE” and “BA”). One clear main headline is easier for people and search engines.
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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
102 internal links, 11 external
The homepage links to 102 pages on asilebaby.com and 11 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://asilebaby.com/.
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://asilebaby.com/wp-sitemap.xml.
AI search readiness
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://asilebaby.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (726 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 54 found) and read each the way a search engine does.
1 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://kit-free.fontawesome.com/releases/latest/css/free.min.css?ver=5.x' from origin 'ht…”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
20 of 24 tappable elements near the top are at least 24 px.
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: 14 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 308 words of copy
The homepage carries about 308 words of visible text.
3 checks passed
7 short forms
7 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads 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.
9 cookies set on arrival
9Opening the homepage sets 9 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 asilebaby.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
- Analytics
- Google Analytics
- Hosting
- Unelink Aire Networks Del Mediterraneo Sl Unipersonal
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 asilebaby.com, including 15 speed issues, 6 SEO issues and 3 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.