postresreina.com website review

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

About 126 KiB 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.

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

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, cloudflare.com and Unpkg and others), adding 233 KiB and 94 ms of main-thread time.

1 long task block the main thread while loading, the longest for 56 ms. During a long task the page ignores taps.

7 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 5.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Utilizamos cookies propias y de terceros para mejorar la ex…”. Most of its time is element render delay (5.0 s).

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

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

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

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

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

Your homepage downloads 12.4 MB in 86 requests on a phone: media 9.7 MB (7), images 1.8 MB (8) and scripts 521 KiB (48). Under 2 MB keeps phones on slow connections fast.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

The homepage links to 33 pages on postresreina.com and 16 external pages.

Your Organization JSON-LD is missing 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 /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.

/aviso-legal, /politicas-de-cookies and /politicas-de-privacidad are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/tienda, /empleo, /grupo-reina-participa-en-la-feria-sial-de-paris-2026, /presentacion-concierto-heroes-beethoven-en-la-basilica, /jose-manuel-lag-galardonado-en-la-gala-enae-alumni and /reina-proteinas-y-maria-paredes-renuevan-su-acuerdo-de-patrocinio and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/kefir, /tienda, /en and /aviso-legal have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is served at too low a resolution for sharp phone screens.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://www.etcanaldenuncias.com/canal.aspx?proyecto=REINA&idioma=Spanish.

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.

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

postresreina.com 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.

postresreina.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

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

DMARC is set to p=none, so mail pretending to be postresreina.com is still delivered. Reports are on, so moving to quarantine is the next step.

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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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