beds.es website review

About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Optanon and others), adding 2.7 MB and 1.6 s of main-thread time.

11 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

Google CDN costs a phone 732 ms of main-thread work and 1.1 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.

Google Tag Manager costs a phone 575 ms of main-thread work and 535 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.

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

site.com costs a phone 21 ms of main-thread work and 682 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.

2 images could be 70 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

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

Polyfills for old browsers add 9 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.

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

Your largest element takes 18.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “VER OFERTAS”.

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

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

Scripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 5.7 MB in 149 requests on a phone: scripts 2.9 MB (61), other files 1.2 MB (34) and fonts 759 KiB (14). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must be contained by particular parents: 9 elements on the page fail this check, rated critical by axe-core.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

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

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

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

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

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

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

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

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 67 characters, so Google will cut it off around 60: “Bed's: tu tienda online de colchones y productos de descanso | Beds”.

There are 4 <h1> headlines (“Bed’s, las tiendas de colchones mejor valoradas d…”, “+140.000 valoraciones” and “Nuestras Bed's se tiñen de rosa”). One clear main headline is easier for people and search engines.

Structured data found (ItemList, Organization and WebSite) but with 2 problems, for example “Organization: missing name”.

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

The homepage links to 348 pages on beds.es and 10 external pages.

Your Organization JSON-LD is missing name, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

Your homepage links to /blog and /blog/como-elegir-tu-colchon, which answer with an error. Visitors hit a dead end and search engines drop them.

/colchones/firmeza/duales has no meta description, so Google writes the search snippet from whatever text it finds.

/en has no <h1> headline, so visitors and search engines get no clear main topic.

/tiendas took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=8326f6b8-2adf-4487-96c2-ac61a3e22e84&referrer=&landingpage=https%3A%2F%2Fwww.beds.es%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%2017_5%.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://espadesa.my.site.com/ESWWebChat1758778597081/assets/styles/bootstrap.min.css' from…”.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

2 links from your homepage to your own site are broken, for example https://www.beds.es/blog (503).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

beds.es has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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 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 1,425 words of visible text.

beds.es has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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