lafinka.pe website review

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

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

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

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

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

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

5 third-party services load with your homepage (YouTube, Facebook and Other Google APIs/SDKs and others), adding 1.2 MB and 653 ms of main-thread time.

YouTube costs a phone 574 ms of main-thread work and 1,015 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.

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

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

16 KiB could be saved by minifying JavaScript.

10 KiB could be saved by minifying CSS.

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

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

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.

Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “en medio de la naturaleza”. Most of its time is element render delay (6.8 s).

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.2 MB in 134 requests on a phone: images 2.8 MB (19), scripts 1.6 MB (59) and fonts 445 KiB (11). Under 2 MB keeps phones on slow connections fast.

1 image (121 KiB) is 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.

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

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

3 images have no alt text, which hurts accessibility and image search.

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.

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 22 characters: “LA FINKA – Apart Hotel”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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 66 pages on lafinka.pe and 9 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.lafinka.pe/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.lafinka.pe/carrito and https://www.lafinka.pe/finalizar-compra are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.lafinka.pe/carrito and https://www.lafinka.pe/finalizar-compra all use the title “Carrito – LA FINKA”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.lafinka.pe/nosotros, https://www.lafinka.pe/espacios, https://www.lafinka.pe/atractivos, https://www.lafinka.pe/habitaciones, https://www.lafinka.pe/galeria and https://www.lafinka.pe/contacto and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lafinka.pe/404page has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.lafinka.pe/nosotros, https://www.lafinka.pe/espacios, https://www.lafinka.pe/atractivos, https://www.lafinka.pe/habitaciones, https://www.lafinka.pe/galeria and https://www.lafinka.pe/contacto and 7 others took over 3 s to send their HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 189 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Before a visitor clicks anything, the page loads Google Ads 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, 1 of them by other companies (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.