marquesderiscal.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Cookie-Script.com and others), adding 22.0 MB and 810 ms of main-thread time.

Instagram costs a phone 0 ms of main-thread work and 20.9 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.

17 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

About 40 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.

9 long tasks block the main thread while loading, the longest for 200 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).

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 51.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Le informamos de que este sitio web, cuyo responsable y tit…”.

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

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

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

Real visitors wait 218 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 195 ms to 225 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 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 44.4 MB in 84 requests on a phone: media 27.7 MB (7), images 15.4 MB (45) and scripts 987 KiB (12). Under 2 MB keeps phones on slow connections fast.

2 images weigh 6.0 MB together. On a phone connection a single image that size takes seconds.

21 images (7.9 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.

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

Images must have alternative text: 12 elements on the page fail this check, rated critical by axe-core.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 85 characters, so Google will cut it off around 60: “Herederos del Marqués de Riscal - Vinos con carácter de Rioja, Rueda, Castilla y León”.

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

There are 3 <h1> headlines (“Visita el mejor viñedo del mundo”, “Éxito de Sublimme by Riscal, el primer vino espum…” and “Marqués de Riscal prolonga la vida de sus viñedos”). One clear main headline is easier for people and search engines.

Your hreflang tags are invalid, so Google may show the wrong language version.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 89 pages on marquesderiscal.com and 30 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.

There is no https://www.marquesderiscal.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.marquesderiscal.com/nuestra-historia, https://www.marquesderiscal.com/la-botelleria, https://www.marquesderiscal.com/100-organic, https://www.marquesderiscal.com/denominaciones-marques-de-riscal, https://www.marquesderiscal.com/do-ca-rioja and https://www.marquesderiscal.com/do-rueda and 7 others use the same meta description. A description written for each page earns more clicks.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 2 cookies (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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.