Website review, no card needed

aeromexico.com logo

aeromexico.com website review

Visit site (opens in a new tab)Reviewed 18 October 202657 issues · 77 checks

This review found 57 issues worth fixing on aeromexico.com, 25 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. 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

Full-page screenshot of aeromexico.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aeromexico.com at 3.7 s3.7 s
  2. aeromexico.com at 7.3 s7.3 s
  3. aeromexico.com at 11.0 s11.0 s
  4. aeromexico.com at 14.7 s14.7 s
  5. aeromexico.com at 18.3 s18.3 s
  6. aeromexico.com at 22.0 s22.0 s
  7. aeromexico.com at 25.7 s25.7 s
  8. aeromexico.com at 29.3 s29.3 s

Speed

14 to fix27
  • Reduce unused JavaScript

    18.1 s · 3.1 MB

    About 3.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 18.1 s faster on a phone.

  • Use efficient cache lifetimes

    6.3 s · 1.3 MB

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

  • Improve image delivery

    1.1 s · 894 KiB

    16 images could be 894 KiB 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.

  • Avoid multiple page redirects

    1.5 s

    The page goes through 2 redirects before it starts loading, costing about 1.5 s. Link and advertise the final URL directly.

  • Main-thread work: 10.3 s

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

  • Mobile performance score: 27

    27/100

    Your mobile performance score is 27. 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 (Google Tag Manager, securitytrfx.com and sprinklr.com and others), adding 2.3 MB and 1.4 s of main-thread time.

  • Render-blocking requests

    900 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 900 ms.

  • Google Tag Manager adds 549 ms

    549 ms

    Google Tag Manager costs a phone 549 ms of main-thread work and 1.0 MB 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

    450 ms · 38 KiB

    38 KiB could be saved by minifying JavaScript.

  • 20 long tasks on the main thread

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

  • securitytrfx.com adds 322 ms

    322 ms

    securitytrfx.com costs a phone 322 ms of main-thread work and 16 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.

  • sprinklr.com adds 132 ms

    132 ms

    sprinklr.com costs a phone 132 ms of main-thread work and 397 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 95 ms

    95 ms

    Google CDN costs a phone 95 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.

  • Document request latency

    250 ms

    The HTML itself could arrive about 250 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    50 ms

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

  • 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: 4 ms

    4 ms

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

Core Web Vitals

12 to fix0
  • Fails Core Web Vitals for real visitors

    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-user LCP: 6.5 s

    6.5 s

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

  • Real-user INP: 814 ms

    814 ms

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

  • Real-user FCP: 5.0 s

    5.0 s

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

  • First Contentful Paint: 17.4 s

    17.4 s

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

  • Largest Contentful Paint: 51.2 s

    51.2 s

    Your largest element takes 51.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cancún México”.

  • Speed Index: 33.5 s

    33.5 s

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

  • Time to Interactive: 54.2 s

    54.2 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Real-user CLS: 0.16

    0.16

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

  • Cumulative Layout Shift: 0.101

    0.101

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

  • 3 images without width and height

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

1 checks passed
  • Real-user TTFB: 559 ms

    559 ms

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

Images and page weight

1 to fix33
  • Page weight: 8.7 MB in 268 requests

    8.7 MB

    Your homepage downloads 8.7 MB in 268 requests on a phone: scripts 5.9 MB (110), images 1.9 MB (51) and other files 661 KiB (94). Under 2 MB keeps phones on slow connections fast.

  • About 2.5 g of CO₂ per visit

    2.47 g

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

Accessibility

10 to fixGoogle 7061
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (2 elements).

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 18 text elements with low contrast

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

  • 6 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 8 automated accessibility rules passed

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

SEO

9 to fixGoogle 9260
  • No meta description

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

  • Title is short (16 characters)

    Your title is only 16 characters: “Site Maintenance”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

  • No XML sitemap

    No XML sitemap at https://aeromexico.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at aeromexico.com/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

1 checks passed
  • One H1 headline

    Your main headline reads: “Oops! Something went wrong”.

AI search readiness

1 to fix69
  • 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://aeromexico.com/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.

Best practices

4 to fixGoogle 6563
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • No character set

    No character set is declared, so some characters can render as gibberish.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • No console errors

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

Content and conversion

6 to fix25
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • Only about 8 words

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

  • No form on the homepage

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

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

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 aeromexico.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 57 issues on aeromexico.com, including 26 speed issues, 9 SEO issues and 6 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