prodigiosovolcan.com website review

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

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

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

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

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

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

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

2 third-party services load with your homepage (Cookiebot and Google Tag Manager), adding 288 KiB and 123 ms of main-thread time.

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

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

About 25 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 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Las cookies de la web se usan para personalizar el contenid…”.

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

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

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

Visually, the page fills in at 4.7 s (Speed Index). Good is under 3.4 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' largest content (lcp) went from 2.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 64.9 MB in 54 requests on a phone: media 59.5 MB (23), images 4.5 MB (10) and scripts 479 KiB (8). Under 2 MB keeps phones on slow connections fast.

20260506_PRODIGIOS_GIFClaraWeb_800x800.gif weighs 3.1 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example 20260506_PRODIGIOS_GIFClaraWeb_800x800.gif at 800 px wide, shown at 190 px. Resized copies would save about 1.8 MB.

4 images (3.5 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.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 70 characters, so Google will cut it off around 60: “Prodigioso Volcán - Nos encantan las buenas ideas y los nuevos medios.”.

Your meta description is only 50 characters: “Nos encantan las buenas ideas y los nuevos medios.”. 70 to 160 characters is enough to sell the click.

There are 28 <h1> headlines (“¿Carpeta ciudadana o mochila ciudadana?”, “VIEJO MADRID” and “¿Qué dice de ti la IA?”). One clear main headline is easier for people and search engines.

There is no robots.txt at prodigiosovolcan.com/robots.txt, the first file search crawlers ask for.

The homepage links to 62 pages on prodigiosovolcan.com and 75 external pages.

There is no https://www.prodigiosovolcan.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.prodigiosovolcan.com/seccion/proyectos, https://www.prodigiosovolcan.com/seccion/informes, https://www.prodigiosovolcan.com/pv/marcas, https://www.prodigiosovolcan.com/pv/sostenibilidad and https://www.prodigiosovolcan.com/pv/voz-y-audio have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.prodigiosovolcan.com/pv/marcas and https://www.prodigiosovolcan.com/pv/formacion have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.prodigiosovolcan.com/pv/metodologia-sapiens 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.

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

28 of 51 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”.

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.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 45 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

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 3,022 words of visible text.

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

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