Website review, no card needed

airasia.com logo

airasia.com website review

Visit site (opens in a new tab)Reviewed 18 October 202639 issues · 83 checks

This review found 39 issues worth fixing on airasia.com, 14 of them high impact, across 83 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

Real-visitor load time (LCP)75th percentile, phones
5.1 s3.2 sApr 25Oct 103.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20264.9 s
May 2, 20264.9 s
May 9, 20264.7 s
May 16, 20264.5 s
May 23, 20264.4 s
May 30, 20264.3 s
Jun 6, 20264.3 s
Jun 13, 20264.2 s
Jun 20, 20264.2 s
Jun 27, 20264.1 s
Jul 4, 20264.0 s
Jul 11, 20264.0 s
Jul 18, 20264.1 s
Jul 25, 20264.2 s
Aug 1, 20264.2 s
Aug 8, 20264.1 s
Aug 15, 20264.0 s
Aug 22, 20263.8 s
Aug 29, 20263.7 s
Sep 5, 20263.6 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.6 s
Oct 10, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
1.1 s608 msApr 25Oct 10663 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 20261.0 s
May 2, 20261.0 s
May 9, 2026999 ms
May 16, 2026991 ms
May 23, 20261.0 s
May 30, 2026995 ms
Jun 6, 2026968 ms
Jun 13, 2026950 ms
Jun 20, 2026888 ms
Jun 27, 2026961 ms
Jul 4, 2026963 ms
Jul 11, 2026937 ms
Jul 18, 2026923 ms
Jul 25, 2026836 ms
Aug 1, 2026792 ms
Aug 8, 2026773 ms
Aug 15, 2026753 ms
Aug 22, 2026762 ms
Aug 29, 2026743 ms
Sep 5, 2026728 ms
Sep 12, 2026715 ms
Sep 19, 2026695 ms
Sep 26, 2026742 ms
Oct 3, 2026719 ms
Oct 10, 2026663 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 airasia.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. airasia.com at 0.4 s0.4 s
  2. airasia.com at 0.8 s0.8 s
  3. airasia.com at 1.1 s1.1 s
  4. airasia.com at 1.5 s1.5 s
  5. airasia.com at 1.9 s1.9 s
  6. airasia.com at 2.3 s2.3 s
  7. airasia.com at 2.6 s2.6 s
  8. airasia.com at 3.0 s3.0 s

Speed

8 to fix27
  • Reduce unused JavaScript

    2.1 s · 2.1 MB

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

  • Google Tag Manager adds 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 929 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 27

    27/100

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

  • Main-thread work: 8.7 s

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

  • Use efficient cache lifetimes

    950 ms · 1.2 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.6 MB and 1.8 s of main-thread time.

  • Improve image delivery

    800 ms · 338 KiB

    19 images could be 338 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    104 KiB

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

  • Legacy JavaScript

    61 KiB

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

  • Minify JavaScript

    20 KiB

    20 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 57 but mobile only 27. 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: 4 ms

    4 ms

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

Core Web Vitals

11 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 INP: 547 ms

    547 ms

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

  • Time to Interactive: 28.0 s

    28.0 s

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

  • Largest Contentful Paint: 9.2 s

    9.2 s

    Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Total Blocking Time: 3.5 s

    3.5 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Real-user LCP: 3.4 s

    3.4 s

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

  • Real-user CLS: 0.15

    0.15

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

  • Real-user TTFB: 849 ms

    849 ms

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

  • Cumulative Layout Shift: 0.212

    0.212

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

3 checks passed
  • Real-user FCP: 1.3 s

    1.3 s

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

  • Tap response (INP) got 31% faster for real visitors

    -31%

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

  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

Images and page weight

2 to fix75
  • Page weight: 3.9 MB in 160 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 160 requests on a phone: scripts 3.0 MB (46), images 546 KiB (34) and other files 152 KiB (70). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    94 KiB

    1 image is downloaded at several times the size a phone draws it, for example deals.png at 400 px wide, shown at 48 px. Resized copies would save about 94 KiB.

  • 1 image in older formats

    1 image (108 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.

  • About 1.1 g of CO₂ per visit

    1.10 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 8791
  • Images must have alternative text (4 elements)

    Images must have alternative text: 4 elements on the page fail this check, rated critical by axe-core.

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

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

  • No main landmark

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

  • Page should contain a level-one heading (1 element)

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

  • 6 links without text

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

1 checks passed
  • 27 automated accessibility rules passed

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

SEO

2 to fixGoogle 9286
  • No H1 headline

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

  • No structured data

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

  • 22 internal links, 28 external

    The homepage links to 22 pages on airasia.com and 28 external pages.

6 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Download AirAsia MOVE today and get only the best deals on flights, hotels, ride and more! Completing your travel, all …”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “AirAsia MOVE | Discover deals on flights, hotels, rides & more”.

  • Canonical URL set

    The canonical URL is https://www.airasia.com/en/gb/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.airasia.com/google-sitemap/sitemap.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.airasia.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.

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 (340 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix67
  • 3 pages without a title

    https://www.airasia.com/unlimited/en/gb, https://www.airasia.com/rewards/en/gb and https://www.airasia.com/promotions have no <title>, so Google invents the link text in results.

  • 4 pages share a title

    https://www.airasia.com/en/gb, https://www.airasia.com/flight/en/gb, https://www.airasia.com/snap/en/gb and https://www.airasia.com/hotels/en/gb all use the title “AirAsia MOVE | Discover deals on flights, hotels, rides & more”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.airasia.com/flightstatus/en/GB, https://www.airasia.com/unlimited/en/gb and https://www.airasia.com/promotions have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.airasia.com/flight/en/gb, https://www.airasia.com/snap/en/gb and https://www.airasia.com/hotels/en/gb use the same meta description. A description written for each page earns more clicks.

  • 8 pages without an H1

    https://www.airasia.com/flightstatus/en/GB, https://www.airasia.com/aa/inflight-comforts, https://www.airasia.com/flight/en/gb, https://www.airasia.com/snap/en/gb, https://www.airasia.com/hotels/en/gb and https://www.airasia.com/ride and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.airasia.com/aa/about-us/en/gb/fees-and-charges.html and https://www.airasia.com/rewards/en/gb have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 3 pages slow to respond

    https://www.airasia.com/flight/en/gb, https://www.airasia.com/rewards/en/gb and https://www.airasia.com/promotions took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 5494
  • Deprecated browser APIs

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

  • 1 third-party cookie

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

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 direct contact details

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

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

  • About 273 words of copy

    The homepage carries about 273 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Pre-book duty-free”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Pre-book duty-free” and “Register as trade partner”.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 2 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js

Company

Headquarters
Phnom Penh

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on airasia.com, including 19 speed issues, 2 SEO issues and 2 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