parcesa.es website review

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

YouTube costs a phone 3.5 s of main-thread work and 9.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

The page goes through 2 redirects before it starts loading, costing about 1.3 s. Link and advertise the final URL directly.

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

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

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

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

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

1 image could be 552 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

Polyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

11 KiB could be saved by minifying CSS.

25 KiB could be saved by minifying JavaScript.

Desktop scores 64 but mobile only 26. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

Your largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “PARCESA Servicios Funerarios Integrales | Funeraria Madrid”.

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

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

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

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

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

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

4 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-17, real Chrome visitors' tap response (inp) went from 140 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 13.9 MB in 334 requests on a phone: scripts 10.7 MB (121), stylesheets 903 KiB (54) and HTML 702 KiB (29). Under 2 MB keeps phones on slow connections fast.

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

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

[aria-*] attributes do not have valid values (1 element).

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

Elements with role="none" or role="presentation" have conflicts (1 element).

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.

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

The homepage links to 304 pages on parcesa.es and 5 external pages.

Your Organization JSON-LD is missing url, 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://parcesa.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://parcesa.es/espacio-de-cuidadores is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

Chrome logged issues while loading the page (“Cookie”).

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.

The homepage has only about 16 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.

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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.