maidesite.es website review

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

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

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

8 third-party services load with your homepage (xcottons.com, Clarity and Shopify and others), adding 868 KiB and 510 ms of main-thread time.

3 images could be 547 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

The page has 1,707 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

xcottons.com costs a phone 132 ms of main-thread work and 357 KiB 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.

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

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

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

About 11 KiB of CSS is downloaded but never applied on this page.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.

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

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

2 images are downloaded at several times the size a phone draws them, for example 2_-_0731_-_2.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 510 KiB.

Your homepage downloads 3.8 MB in 200 requests on a phone: images 1.9 MB (24), other files 869 KiB (86) and scripts 836 KiB (54). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

5 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 (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

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

Your title is 71 characters, so Google will cut it off around 60: “El mejor escritorio elevable & silla | Ergonomica Muebles – MaidesiteES”.

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

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 86 pages on maidesite.es and 6 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.

Your homepage links to https://maidesite.es/pages/black-friday-2025, which answers with an error. Visitors hit a dead end and search engines drop it.

https://maidesite.es/collections/all, https://maidesite.es/collections/serie-inicial, https://maidesite.es/collections/serie-pro, https://maidesite.es/collections/serie-premium and https://maidesite.es/pages/bulk-order have no meta description, so Google writes the search snippet from whatever text it finds.

https://maidesite.es/collections/all, https://maidesite.es/collections/marco-de-escritorio-elevable, https://maidesite.es/collections/serie-inicial, https://maidesite.es/collections/serie-pro, https://maidesite.es/collections/serie-premium and https://maidesite.es/pages/bulk-order and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://maidesite.es/collections/marco-de-escritorio-elevable, https://maidesite.es/collections/serie-inicial, https://maidesite.es/collections/serie-pro, https://maidesite.es/collections/serie-premium, https://maidesite.es/products/maidesite-t1-basic-marco-de-escritorio-elevable-en-altura and https://maidesite.es/products/maidesite-th2-pro-plus-marco-de-escritorio-electrico-elevable-en-altura-doble-motor and 3 others took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

Before a visitor clicks anything, the page loads Google Tag Manager and Microsoft Clarity (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 9 cookies, 1 of them by other companies (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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.