Website review, no card needed

juneyaoair.com logo

juneyaoair.com website review

Visit site (opens in a new tab)Reviewed 17 November 202653 issues · 76 checks

This review found 53 issues worth fixing on juneyaoair.com, 24 of them high impact, across 76 checks. The most urgent: avoid multiple page redirects. 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
7.0 s5.4 sMay 30Nov 146.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.8 s
Jun 6, 20265.7 s
Jun 13, 20265.7 s
Jun 20, 20265.6 s
Jun 27, 20265.7 s
Jul 4, 20266.1 s
Jul 11, 20266.6 s
Jul 18, 20266.8 s
Jul 25, 20266.7 s
Aug 1, 20266.7 s
Aug 8, 20266.4 s
Aug 15, 20266.5 s
Aug 22, 20266.5 s
Aug 29, 20266.4 s
Sep 5, 20266.6 s
Sep 12, 20266.6 s
Sep 19, 20266.5 s
Sep 26, 20266.5 s
Oct 3, 20266.5 s
Oct 10, 20266.5 s
Oct 17, 20266.6 s
Oct 24, 20266.6 s
Oct 31, 20266.6 s
Nov 7, 20266.5 s
Nov 14, 20266.4 s
Real-visitor tap response (INP)75th percentile, phones
332 ms123 msMay 30Nov 14197 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026161 ms
Jun 6, 2026161 ms
Jun 13, 2026180 ms
Jun 20, 2026193 ms
Jun 27, 2026242 ms
Jul 4, 2026195 ms
Jul 11, 2026190 ms
Jul 18, 2026162 ms
Jul 25, 2026230 ms
Aug 1, 2026252 ms
Aug 8, 2026242 ms
Aug 15, 2026252 ms
Aug 22, 2026172 ms
Aug 29, 2026187 ms
Sep 5, 2026170 ms
Sep 12, 2026175 ms
Sep 19, 2026185 ms
Sep 26, 2026285 ms
Oct 3, 2026308 ms
Oct 10, 2026305 ms
Oct 17, 2026290 ms
Oct 24, 2026147 ms
Oct 31, 2026174 ms
Nov 7, 2026195 ms
Nov 14, 2026197 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 juneyaoair.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. juneyaoair.com at 1.0 s1.0 s
  2. juneyaoair.com at 2.0 s2.0 s
  3. juneyaoair.com at 3.0 s3.0 s
  4. juneyaoair.com at 4.0 s4.0 s
  5. juneyaoair.com at 5.0 s5.0 s
  6. juneyaoair.com at 6.0 s6.0 s
  7. juneyaoair.com at 7.0 s7.0 s
  8. juneyaoair.com at 8.0 s8.0 s

Speed

12 to fix47
  • Avoid multiple page redirects

    176.3 s

    The page goes through 1 redirect before it starts loading, costing about 176.3 s. Link and advertise the final URL directly.

  • Use efficient cache lifetimes

    24.1 s · 5.9 MB

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

  • Render-blocking requests

    24.9 s

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

  • Reduce unused CSS

    19.1 s · 3.8 MB

    About 3.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 19.1 s faster on a phone.

  • Reduce unused JavaScript

    7.1 s · 1.2 MB

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

  • Minify CSS

    1.5 s · 320 KiB

    320 KiB could be saved by minifying CSS.

  • Mobile performance score: 47

    47/100

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

  • Main-thread work: 5.2 s

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (tongdun.net), adding 177 KiB and 779 ms of main-thread time.

  • tongdun.net adds 779 ms

    779 ms

    tongdun.net costs a phone 779 ms of main-thread work and 177 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.

  • 15 long tasks on the main thread

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

  • 2,018 HTML elements

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

  • Legacy JavaScript

    150 ms · 30 KiB

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

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

    1 ms

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

Core Web Vitals

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

  • First Contentful Paint: 37.9 s

    37.9 s

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

  • Largest Contentful Paint: 37.9 s

    37.9 s

    Your largest element takes 37.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “尊敬的旅客,欢迎您使用吉祥航空App。请您在使用我们的App前仔细阅读我们的《吉祥航空隐私政策》,我们将在隐私通知内向…”.

  • Speed Index: 58.8 s

    58.8 s

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

  • Time to Interactive: 185.5 s

    185.5 s

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

  • Real-user INP: 209 ms

    209 ms

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

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

    +22%

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 350 ms

    350 ms

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

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

    +13%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 55.3 MB in 186 requests

    55.3 MB

    Your homepage downloads 55.3 MB in 186 requests on a phone: images 32.4 MB (63), other files 16.7 MB (67) and stylesheets 3.8 MB (18). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 5.7 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    1.1 MB

    2 images are downloaded at several times the size a phone draws them, for example 6215eb18-33f6-42ef-bc24-0b38a68d1666.jpg at 2,572 px wide, shown at 282 px. Resized copies would save about 1.1 MB.

  • 20 images in older formats

    20 images (8.4 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.

  • 14 images below the first screen load straight away

    14 images further down the page (5.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 15.7 g of CO₂ per visit

    15.68 g

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

Accessibility

10 to fixGoogle 6782
  • Hidden but focusable

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

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

  • 13 images without alt text

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

  • Zoom is disabled

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

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

    All page content should be contained by landmarks: 46 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.

  • 8 form fields without a label

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

  • 4 text elements with low contrast

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

  • ARIA role should be appropriate for the element (2 elements)

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

1 checks passed
  • 28 automated accessibility rules passed

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

SEO

7 to fixGoogle 9166
  • No H1 headline

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

  • Title is short (4 characters)

    Your title is only 4 characters: “吉祥航空”. 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://www.juneyaoair.com/sitemap.xml, so Google discovers your pages only by following links.

  • 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 X (Twitter) card tag

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

2 checks passed
  • Meta description: 97 characters

    Your meta description is 97 characters: “上海吉祥航空有限公司是著名民营企业均瑶集团的全资子公司。吉祥航空以全新飞机、精确定位、标准服务享誉业界。吉祥航空官方购票网站为旅客提供国内机票预订、电子客票销售、特价机票销售等多种优惠促销活动。”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

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

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

Best practices

3 to fixGoogle 8173
  • 2 broken images

    2 images failed to load on a phone, for example https://oss-shanghai.sangforcloud.com:12000/jxhk_mhsh/mall/prod/media/store/10002/20250425/f9078eeb3d0c473a97b1fff93f8bc72c.png.

  • 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 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_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

6 to fix33
  • 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.

  • Thin social proof

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

  • 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 48 words

    The homepage has only about 48 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

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

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 juneyaoair.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
China Telecom Group

Company

Founded
2005
Headquarters
Shanghai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on juneyaoair.com, including 21 speed issues, 7 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