Website review, no card needed

aena.es logo

aena.es website review

Visit site (opens in a new tab)Reviewed 18 October 202646 issues · 97 checks

This review found 46 issues worth fixing on aena.es, 18 of them high impact, across 97 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.6 s1.3 sApr 25Oct 101.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.3 s
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
192 ms149 msApr 25Oct 10182 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026154 ms
May 2, 2026155 ms
May 9, 2026156 ms
May 16, 2026159 ms
May 23, 2026160 ms
May 30, 2026162 ms
Jun 6, 2026163 ms
Jun 13, 2026162 ms
Jun 20, 2026163 ms
Jun 27, 2026163 ms
Jul 4, 2026164 ms
Jul 11, 2026166 ms
Jul 18, 2026168 ms
Jul 25, 2026172 ms
Aug 1, 2026177 ms
Aug 8, 2026182 ms
Aug 15, 2026186 ms
Aug 22, 2026187 ms
Aug 29, 2026187 ms
Sep 5, 2026186 ms
Sep 12, 2026184 ms
Sep 19, 2026184 ms
Sep 26, 2026182 ms
Oct 3, 2026182 ms
Oct 10, 2026182 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of aena.es (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aena.es at 0.8 s0.8 s
  2. aena.es at 1.7 s1.7 s
  3. aena.es at 2.5 s2.5 s
  4. aena.es at 3.4 s3.4 s
  5. aena.es at 4.2 s4.2 s
  6. aena.es at 5.1 s5.1 s
  7. aena.es at 5.9 s5.9 s
  8. aena.es at 6.7 s6.7 s

Speed

14 to fix33
  • Use efficient cache lifetimes

    5.0 s · 2.2 MB

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

  • Reduce unused JavaScript

    3.6 s · 812 KiB

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

  • Improve image delivery

    1.1 s · 2.7 MB

    11 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Render-blocking requests

    3.8 s

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

  • Reduce unused CSS

    1.1 s · 172 KiB

    About 172 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33 (desktop: 59). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (elixregtech.com, Facebook and airport.ai and others), adding 1.5 MB and 1.3 s of main-thread time.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.

  • elixregtech.com adds 874 ms

    874 ms

    elixregtech.com costs a phone 874 ms of main-thread work and 291 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.

  • Legacy JavaScript

    500 ms · 61 KiB

    Polyfills for old browsers add 61 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.

  • Main-thread work: 2.6 s

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

  • 1,607 HTML elements

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

  • airport.ai adds 87 ms

    87 ms

    airport.ai costs a phone 87 ms of main-thread work and 321 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 CDN adds 65 ms

    65 ms

    Google CDN costs a phone 65 ms of main-thread work and 352 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.

  • Minify JavaScript

    150 ms · 27 KiB

    27 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 16 KiB

    16 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 59 but mobile only 33. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 28 ms

    28 ms

    Your server sent the HTML in 28 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 16.7 s

    16.7 s

    Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Aniversario T4 Madrid”.

  • First Contentful Paint: 6.8 s

    6.8 s

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

  • Time to Interactive: 18.5 s

    18.5 s

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

  • Speed Index: 9.6 s

    9.6 s

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

  • Total Blocking Time: 587 ms

    587 ms

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

  • Cumulative Layout Shift: 0.184

    0.184

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

  • 20 images without width and height

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

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

  • Largest content (LCP) got 12% slower for real visitors

    +12%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 152 ms

    152 ms

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

  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 326 ms

    326 ms

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

Images and page weight

4 to fix38
  • Page weight: 6.0 MB in 105 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 105 requests on a phone: images 3.8 MB (26), scripts 1.6 MB (33) and fonts 307 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Satellite weighs 1.7 MB. On a phone connection a single image that size takes seconds.

  • 12 images in older formats

    12 images (3.5 MB) 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.

  • 5 images below the first screen load straight away

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

  • About 1.7 g of CO₂ per visit

    1.70 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

11 to fixGoogle 9189
  • Hidden but focusable

    9 elements hidden from screen readers can still receive keyboard focus.

  • Interactive controls must not be nested (6 elements)

    Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.

  • ARIA commands must have an accessible name (1 element)

    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)

    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.

  • Banner landmark should not be contained in another landmark (2 elements)

    Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (2 elements)

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

  • Main landmark should not be contained in another landmark (1 element)

    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)

    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 main landmark (1 element)

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

  • 3 form fields without a label

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

  • 2 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h5 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.

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8391
  • No structured data

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

  • No social preview image

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

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 268 internal links, 27 external

    The homepage links to 268 pages on aena.es and 27 external pages.

6 checks passed
  • Meta description: 115 characters

    Your meta description is 115 characters: “Infórmate sobre todo lo que necesitas saber como pasajero de Aena. ¡Descubre toda la información en la web de Aena!”.

  • One H1 headline

    Your main headline reads: “Te damos la bienvenida a Aena”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Información para nuestros pasajeros | Aena”.

  • Canonical URL set

    The canonical URL is https://www.aena.es/es/pasajeros/pasajeros.html.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.aena.es/sites/sitemaps/sitemap_index.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.aena.es/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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,498 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.aena.es/es/infovuelos.html has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7797
  • Deprecated browser APIs

    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…”).

  • Browser-reported issues

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    124 of 134 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 838 words of copy

    The homepage carries about 838 words of visible text.

3 checks passed
  • 5 short forms

    5 short forms (4 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 13 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at aena.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Company

Employees
8,771
Founded
2017
Headquarters
Madrid

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on aena.es, including 21 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25