vacatia.com website review

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

8 third-party services load with your homepage (Facebook, Google Tag Manager and sift.com and others), adding 727 KiB and 684 ms of main-thread time.

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

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

About 437 KiB of JavaScript is downloaded but never used on this page.

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

Facebook costs a phone 323 ms of main-thread work and 389 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.

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

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

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

2 images could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

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

8 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 123 ms to 150 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “First hero image”.

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

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

2 images (130 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.

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

110 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: 74 elements on the page fail this check, rated moderate by axe-core.

13 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 66 characters, so Google will cut it off around 60: “Resort Residences: Space of a Home + Services of a Hotel | Vacatia”.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 59 pages on vacatia.com and 7 external pages.

There is no https://vacatia.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://vacatia.com/ownerplus has no meta description, so Google writes the search snippet from whatever text it finds.

https://vacatia.com/ownerplus has no <h1> headline, so visitors and search engines get no clear main topic.

https://vacatia.com/ownerplus 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 50 found) and read each the way a search engine does.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage carries about 495 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 8 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.