voramar.net website review

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

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

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

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

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

6 images could be 269 KiB 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.

8 third-party services load with your homepage (Google Tag Manager, hijiffy.com and Google Maps and others), adding 1.4 MB and 562 ms of main-thread time.

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

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

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

hijiffy.com costs a phone 167 ms of main-thread work and 513 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.

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

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

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

Desktop scores 89 but mobile only 59. 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 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Para ofrecer las mejores experiencias, utilizamos tecnologí…”.

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

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

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

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

The first text or image appears after 2.9 s on a phone. 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-10, real Chrome visitors' tap response (inp) went from 132 ms to 142 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.6 MB in 174 requests on a phone: media 6.6 MB (2), scripts 1.4 MB (67) and images 1.0 MB (24). Under 2 MB keeps phones on slow connections fast.

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

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

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

17 tap targets are too small or too close together to hit reliably with a finger.

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

[role="img"] and [role="image"] elements must have alternative text: 4 elements on the page fail this check, rated serious by axe-core.

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

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.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“Hotel Voramar Benicàssim — En primera línea del M…” and “Hotel Voramar Benicàssim — En primera línea del M…”). One clear main headline is easier for people and search engines.

Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://voramar.net/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 84 pages on voramar.net and 51 external pages.

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.

/reserva-habitacion-hotel-benicasim-playa-castellon and /habitaciones all use the title “Reservar Hotel en Benicàssim | Hotel Voramar ★★★★ — Primera línea de …”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/nosotros, /promos, /blog and /contacto have no meta description, so Google writes the search snippet from whatever text it finds.

/reserva-habitacion-hotel-benicasim-playa-castellon and /habitaciones use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /habitaciones, whose canonical is /reserva-habitacion-hotel-benicasim-playa-castellon. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/nosotros, /eventos, /promos, /galeria and /contacto have no <h1> headline, so visitors and search engines get no clear main topic.

/habitaciones, /gastronomia and /experiencias took over 3 s to send their HTML from our server.

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

7 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

4 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://voramar.net/' was loaded over HTTPS, but requested an insecure font 'http://voramar…”.

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

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.

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.

2 links go through two or more redirects, for example https://voramar.net/carta_terraza.

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.

voramar.net 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.

voramar.net'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.

Your longest form asks for 17 fields (5 required). Every extra field lowers completion.

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

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

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