corazoncabo.com website review

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

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

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

8 third-party services load with your homepage (asksuite.com, Pixlee and Cookiebot and others), adding 532 KiB and 227 ms of main-thread time.

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

About 187 KiB of CSS is downloaded but never applied on this page.

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

Polyfills for old browsers add 9 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.

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 9.9 s. Good is under 3.8 s.

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Your homepage downloads 2.4 MB in 103 requests on a phone: scripts 765 KiB (13), other files 744 KiB (62) and images 433 KiB (8). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example f3f40239-dc79-4cc1-af55-00dfe7c52b00.png at 338 px wide, shown at 44 px. Resized copies would save about 103 KiB.

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

ARIA dialog and alertdialog nodes should have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

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

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (12 elements).

Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “ld+json block 2 is not valid JSON (Unexpected token '/', ..."abo", // "https"... is not va)”.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 173 pages on corazoncabo.com and 57 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.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.asksuite.com/infochat.css?v=1792176364883' from origin 'https://www.corazoncab…”.

Large scripts ship without source maps.

1 link to other sites is dead, for example https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.websitealive10.com%2F418%2Foperator%2Fguest%2FgDefault_v2.asp%3Fcframe%3Dlogin%26chattype%3Dnormal%26groupid%3D418%26websiteid%3D106%26departmentid%3D1544%26sessionid_%3D5053%26iniframe%3D%26ppc_id%3D%26autostart%3D%26text2chat_info%3D%26loginname%3D%26loginnamelast%3D%26loginemail%3D%26loginphone%3D%26infocapture_ids%3D%26infocapture_values%3D%26dl%3Dhttp%3A%252F%252Fwww.cabovillasbeachresort.com%252F%2523seccion%26loginquestion%3D&data=02%7C01%7C%7Cb2dcc9e01bdc412d1ffd08d83e3371c1%7Cb3f4f7c272ce4192aba4d6c7719b5766%7C0%7C0%7C637327738031535909&sdata=LQLhm7CXHDaIYJcSw%2BzPpixQXo9eOIjqIAnIzqzZdj4%3D&reserved=0 (500).

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.

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.

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

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

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 1,291 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, Google Tag Manager and Pinterest Tag (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 13 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.