Website review, no card needed

xiamenair.com logo

xiamenair.com website review

Visit site (opens in a new tab)Reviewed 27 October 202657 issues · 92 checks

This review found 57 issues worth fixing on xiamenair.com, 23 of them high impact, across 92 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
4.0 s2.7 sMay 9Oct 243.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.8 s
May 16, 20263.9 s
May 23, 20263.9 s
May 30, 20263.8 s
Jun 6, 20263.9 s
Jun 13, 20263.9 s
Jun 20, 20263.9 s
Jun 27, 20263.9 s
Jul 4, 20263.8 s
Jul 11, 20263.8 s
Jul 18, 20263.9 s
Jul 25, 20263.8 s
Aug 1, 20263.6 s
Aug 8, 20263.4 s
Aug 15, 20263.2 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20263.0 s
Oct 10, 20263.0 s
Oct 17, 20263.1 s
Oct 24, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
175 ms142 msMay 9Oct 24148 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026150 ms
May 16, 2026155 ms
May 23, 2026156 ms
May 30, 2026155 ms
Jun 6, 2026159 ms
Jun 13, 2026162 ms
Jun 20, 2026168 ms
Jun 27, 2026171 ms
Jul 4, 2026170 ms
Jul 11, 2026167 ms
Jul 18, 2026163 ms
Jul 25, 2026162 ms
Aug 1, 2026161 ms
Aug 8, 2026162 ms
Aug 15, 2026161 ms
Aug 22, 2026161 ms
Aug 29, 2026161 ms
Sep 5, 2026156 ms
Sep 12, 2026153 ms
Sep 19, 2026148 ms
Sep 26, 2026146 ms
Oct 3, 2026150 ms
Oct 10, 2026151 ms
Oct 17, 2026151 ms
Oct 24, 2026148 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 xiamenair.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. xiamenair.com at 1.7 s1.7 s
  2. xiamenair.com at 3.4 s3.4 s
  3. xiamenair.com at 5.1 s5.1 s
  4. xiamenair.com at 6.9 s6.9 s
  5. xiamenair.com at 8.6 s8.6 s
  6. xiamenair.com at 10.3 s10.3 s
  7. xiamenair.com at 12.0 s12.0 s
  8. xiamenair.com at 13.7 s13.7 s

Speed

13 to fix43
  • Use efficient cache lifetimes

    3.0 s · 11.0 MB

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

  • Reduce unused JavaScript

    2.1 s · 2.2 MB

    About 2.2 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.

  • Improve image delivery

    3.0 s · 1.2 MB

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

  • Font display

    1.8 s

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

  • Mobile performance score: 43

    43/100

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

  • Reduce unused CSS

    2.7 MB

    About 2.7 MB of CSS is downloaded but never applied on this page.

  • 7 third-party services on the page

    7 third-party services load with your homepage (xiamenair.cn, Google Tag Manager and Bing Ads and others), adding 2.9 MB and 693 ms of main-thread time.

  • xiamenair.cn adds 406 ms

    406 ms

    xiamenair.cn costs a phone 406 ms of main-thread work and 2.4 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.

  • Main-thread work: 3.6 s

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

  • Render-blocking requests

    300 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • 9 long tasks on the main thread

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

  • 2,132 HTML elements

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

  • Google Tag Manager adds 163 ms

    163 ms

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

    17 KiB

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 104 ms

    104 ms

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

Core Web Vitals

10 to fix67
  • 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 FCP: 3.0 s

    3.0 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 16.6 s

    16.6 s

    Your largest element takes 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mazu's blessings,safe journey with Xiamen Airlines”.

  • Speed Index: 27.1 s

    27.1 s

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

  • Time to Interactive: 89.6 s

    89.6 s

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

  • Total Blocking Time: 731 ms

    731 ms

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

4 checks passed
  • Real-user INP: 137 ms

    137 ms

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

  • Real-user CLS: 0.01

    0.01

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

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

    -21%

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

  • Cumulative Layout Shift: 0.007

    0.007

    The layout barely moves while loading (CLS 0.007, good is under 0.1).

Images and page weight

3 to fix45
  • Page weight: 17.9 MB in 145 requests

    17.9 MB

    Your homepage downloads 17.9 MB in 145 requests on a phone: images 7.1 MB (57), scripts 6.3 MB (34) and stylesheets 2.6 MB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    616237561baef59.jpg weighs 519 KiB. On a phone connection a single image that size takes seconds.

  • 9 images in older formats

    9 images (2.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.

  • 1 image below the first screen load straight away

    1 image further down the page (265 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 5.1 g of CO₂ per visit

    5.06 g

    By the Sustainable Web Design model, a visit to your homepage emits about 5.06 g of CO₂e: 607.4 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

10 to fixGoogle 7285
  • ARIA attributes must conform to valid values (3 elements)

    ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical by axe-core.

  • Required ARIA attributes must be provided (1 element)

    Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

  • 3 text elements with low contrast

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

  • ARIA commands must have an accessible name (2 elements)

    ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (2 elements)

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

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

  • Frames without titles

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

  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

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

  • 9 form fields without a label

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

1 checks passed
  • 50 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: 50 passed and 10 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

11 to fixGoogle 6756
  • No H1 headline

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

  • Title is short (15 characters)

    Your title is only 15 characters: “Xiamen Airlines”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 45 links with vague text

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

  • No structured data

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

  • Meta description is short (12 characters)

    Your meta description is only 12 characters: “国际官网2.0 nuxt”. 70 to 160 characters is enough to sell the click.

  • 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://www.xiamenair.com/sitemap.xml, so Google discovers your pages only by following links.

  • 19 links crawlers can't follow

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

  • No robots.txt

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

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

  • 230 internal links, 3 external

    The homepage links to 230 pages on xiamenair.com and 3 external pages.

AI search readiness

1 to fix81
  • 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.

1 checks passed
  • Text is in the HTML

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

Other pages

4 to fix81
  • 11 pages share 2 titles

    https://www.xiamenair.com/en-us, https://www.xiamenair.com/tw-hk, https://www.xiamenair.com/en-hk, https://www.xiamenair.com/tw-mo, https://www.xiamenair.com/en-mo and https://www.xiamenair.com/tw-tw and 3 others all use the title “Xiamen Airlines”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.xiamenair.com/zh-cn and https://www.xiamenair.com/en-cn have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages share a meta description

    https://www.xiamenair.com/tw-hk, https://www.xiamenair.com/en-hk, https://www.xiamenair.com/tw-mo, https://www.xiamenair.com/en-mo, https://www.xiamenair.com/tw-tw and https://www.xiamenair.com/en-tw and 2 others use the same meta description. A description written for each page earns more clicks.

  • 10 pages without an H1

    https://www.xiamenair.com/zh-cn, https://www.xiamenair.com/en-cn, https://www.xiamenair.com/tw-hk, https://www.xiamenair.com/en-hk, https://www.xiamenair.com/tw-mo and https://www.xiamenair.com/en-mo and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.xiamenair.com/tw-hk, https://www.xiamenair.com/en-hk, https://www.xiamenair.com/tw-tw, https://www.xiamenair.com/en-tw, https://www.xiamenair.com/zh-au and https://www.xiamenair.com/en-au took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

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

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 57 small tap targets

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

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

  • 3 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

    Social proof on the homepage: 8 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

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

  • About 815 words of copy

    The homepage carries about 815 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Sign up” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 2 cookies set on arrival

    2

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

  • 8 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Ml 1432

Company

Founded
1984
Headquarters
Xiamen

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 57 issues on xiamenair.com, including 23 speed issues, 11 SEO issues and 1 conversion gap. 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