mipequeno.com website review

169 files are served with short cache lifetimes, so returning visitors download them again (5.4 MB).

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

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

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

About 772 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.6 s faster on a phone.

361 KiB could be saved by minifying JavaScript.

164 KiB could be saved by minifying CSS.

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

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

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

3 third-party services load with your homepage (Bootstrap CDN, Google Fonts and wikimedia.org), adding 119 KiB and 4 ms of main-thread time.

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

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

Your largest element takes 29.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Iniciar sesión Mi cuenta Política de uso de datos Llámenos …”.

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

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

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

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.

Your homepage downloads 5.7 MB in 178 requests on a phone: images 2.7 MB (74), scripts 1.7 MB (43) and stylesheets 956 KiB (53). Under 2 MB keeps phones on slow connections fast.

logo-1774472091.jpg weighs 926 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example logo-1774472091.jpg at 4,000 px wide, shown at 312 px. Resized copies would save about 875 KiB.

7 images (1.2 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.

19 images further down the page (571 KiB) 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.62 g of CO₂e: 194.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

24 buttons have no accessible name, so screen readers announce just “button”.

Some list items are not inside a list.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

No XML sitemap at https://www.mipequeno.com/sitemap.xml, so Google discovers your pages only by following links.

5 links have no real href, so search engines can't follow them.

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

The homepage links to 172 pages on mipequeno.com and 3 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.mipequeno.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.

https://www.mipequeno.com/carrito and https://www.mipequeno.com/pedido are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.mipequeno.com/carrito and https://www.mipequeno.com/pedido all use the title “Carrito”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mipequeno.com/carrito and https://www.mipequeno.com/pedido have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mipequeno.com/306-sillas-coche-grupo-01, https://www.mipequeno.com/307-sillas-coche-grupo-23 and https://www.mipequeno.com/342-sillas-coche-grupo-123 took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 images are served at too low a resolution for sharp phone screens.

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.

Social proof on the homepage: 25 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 342 words of visible text.

Opening the homepage sets 2 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.