halcones.co website review

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

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

About 838 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Facebook and clientify.net and others), adding 2.5 MB and 926 ms of main-thread time.

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

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

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

Facebook costs a phone 264 ms of main-thread work and 335 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.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

clientify.net costs a phone 156 ms of main-thread work and 918 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 2,011 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google Fonts costs a phone 0 ms of main-thread work and 566 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.

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

1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

Your largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Con más de 59 años formando pilotos y tripulantes de cabina…”.

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

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

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

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

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

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

7 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' largest content (lcp) went from 3.5 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 19.5 MB in 104 requests on a phone: media 16.3 MB (6), scripts 2.2 MB (48) and fonts 559 KiB (28). Under 2 MB keeps phones on slow connections fast.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

Structured data found (EducationalOrganization, FAQPage, LocalBusiness and SiteNavigationElement) but with 3 problems, for example “FAQPage: no questions in mainEntity”.

The homepage links to 89 pages on halcones.co and 40 external pages.

/estudiar-aviacion-medellin and /programas all use the title “Estudiar Aviación en Medellín | Programas aeronáuticos | Halcones”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/estudiar-aviacion-medellin and /programas use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example /programa-piloto-comercial-de-avion, whose canonical is /piloto-comercial-de-avion. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/seguridad-operacional, /admision, /egresados, /blog-aviacion-halcones, /escuela-de-aviacion-en-medellin and /simuladores-de-vuelo-en-medellin have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link to other sites is dead, for example https://www.linkedin.com/company/escuela-de-aviacion-los-halcones/ (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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.

1 link go through two or more redirects, for example https://halcones.co/programa-piloto-comercial-de-avion.

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.

halcones.co 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.

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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

halcones.co has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 ip4:38.113.1.0/24 ip4:38.113.20.0/24 ip4:65.254.224.0/19 include:websitewelcome.com ?all”.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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