lacasa.es website review

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

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

6 images could be 312 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

Your mobile performance score is 62 (desktop: 79). Pages that score under 90 lose visitors before the first paint.

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

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

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

2 third-party services load with your homepage (Cloudflare and Google Fonts), adding 138 KiB and 11 ms of main-thread time.

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

4 KiB could be saved by minifying CSS.

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 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (4.1 s).

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

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

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

1 image 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' largest content (lcp) went from 2.5 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.3 MB in 88 requests on a phone: images 2.2 MB (13), fonts 602 KiB (10) and scripts 389 KiB (41). Under 2 MB keeps phones on slow connections fast.

creatividad-con-fondo-1-768x341.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

6 images (496 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.

1 image is downloaded at several times the size a phone draws it, for example image-12.png at 620 px wide, shown at 98 px. Resized copies would save about 39 KiB.

1 image further down the page (51 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

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

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.

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

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

Headings skip levels (h2 → h5), 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.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

The homepage links to 37 pages on lacasa.es and 8 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. 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 https://www.lacasa.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.lacasa.es/2022/10 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/, https://www.lacasa.es/en and https://www.lacasa.es/2022/10 all use the title “⁩ CHOCOLATES LACASA® · Alegrando tu día a día y el de los tuyos”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.lacasa.es/author/lacasitos and https://www.lacasa.es/category/sin-categoria have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lacasa.es/en and https://www.lacasa.es/2022/10 use the same meta description. A description written for each page earns more clicks.

https://www.lacasa.es/productos, https://www.lacasa.es/alegrate-con-lacasa, https://www.lacasa.es/en, https://www.lacasa.es/author/lacasitos, https://www.lacasa.es/2022/10 and https://www.lacasa.es/category/sin-categoria have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.lacasa.es/productos has 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.

https://www.lacasa.es/2022/10 took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://lacasa.imascono.com/wp-content/uploads/2022/10/svgviewer-output-66.svg.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'setAttribute')”.

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

The homepage has only about 108 words of visible text; thin pages give Google and first-time buyers little to go on.

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

The page uses urgency cues (a countdown or limited-time wording).

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.