decameron.com website review

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

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

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

Google Tag Manager costs a phone 370 ms of main-thread work and 380 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 3.3 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

6 third-party services load with your homepage (Google Tag Manager, Cookie-Script.com and thehotelsnetwork.com and others), adding 584 KiB and 467 ms of main-thread time.

1 file is served with short cache lifetimes, so returning visitors download them again (52 KiB).

8 images could be 180 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

Real visitors wait 4.9 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 2.7 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

The layout shifts by 0.236 while loading, so content jumps under the reader's thumb. Good is under 0.1.

The first text or image appears after 2.1 s on a phone. Good is under 1.8 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 5.4 s to 5.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.7 MB in 68 requests on a phone: scripts 1.4 MB (19), images 1.1 MB (30) and fonts 134 KiB (4). Under 2 MB keeps phones on slow connections fast.

17 images further down the page (792 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example ticuna.webp at 1,200 px wide, shown at 350 px. Resized copies would save about 40 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 dropdown has no label.

20 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: 12 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.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Elements with visible text labels do not have matching accessible names. (1 element).

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 178 pages on decameron.com and 16 external pages.

/es/promociones, /es/destinos-decameron, /es/destinos-en-colombia, /es/hoteles/cartagena/apartahotel-boutique-san-pedro, /es/hoteles/baru/decameron-baru and /es/hoteles/cartagena/decameron-cartagena and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/es/hoteles/baru/decameron-baru and /es/hoteles/cartagena/decameron-cartagena took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

Large scripts ship without source maps.

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

Opening https://decameron.com goes through 2 redirects before the homepage loads.

1 link go through two or more redirects, for example https://instagram.com/decameronhotels.

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.

decameron.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

decameron.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.

decameron.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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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