Website review, no card needed

goeasternair.com logo

goeasternair.com website review

Visit site (opens in a new tab)Reviewed 4 November 202627 issues · 79 checks

This review found 27 issues worth fixing on goeasternair.com, 7 of them high impact, across 79 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
3.6 s2.1 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.8 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20262.9 s
Aug 15, 20263.0 s
Aug 22, 20263.1 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.2 s
Sep 19, 20263.0 s
Sep 26, 20262.4 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
72 ms66 msMay 16Oct 3171 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202670 ms
May 23, 202669 ms
May 30, 202668 ms
Jun 6, 202667 ms
Jun 13, 202670 ms
Jun 20, 202670 ms
Jun 27, 202670 ms
Jul 4, 202669 ms
Jul 11, 202669 ms
Jul 18, 202669 ms
Jul 25, 202669 ms
Aug 1, 202671 ms
Aug 8, 202670 ms
Aug 15, 202670 ms
Aug 22, 202670 ms
Aug 29, 202669 ms
Sep 5, 202669 ms
Sep 12, 202668 ms
Sep 19, 202669 ms
Sep 26, 202670 ms
Oct 3, 202671 ms
Oct 10, 202670 ms
Oct 17, 202671 ms
Oct 24, 202671 ms
Oct 31, 202671 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 goeasternair.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix53
  • Use efficient cache lifetimes

    3.3 s · 1.6 MB

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

  • Improve image delivery

    1.1 s · 243 KiB

    3 images could be 243 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.

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and FontAwesome CDN and others), adding 428 KiB and 265 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 119 KiB

    About 119 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    200 ms · 17 KiB

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

  • Reduce unused CSS

    150 ms · 34 KiB

    About 34 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    150 ms

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

  • 4 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 361 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 6.3 s

    6.3 s

    Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WORLD-CLASS AIR TRAVEL & CARGO SERVICES Eastern Airlines se…”.

  • Cumulative Layout Shift: 0.378

    0.378

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Time to Interactive: 6.8 s

    6.8 s

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

  • Speed Index: 4.3 s

    4.3 s

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

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

  • Tap response (INP) held steady for real visitors

    +2%

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

5 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 76 ms

    76 ms

    Real visitors wait 76 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 23% faster for real visitors

    -23%

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

  • Total Blocking Time: 173 ms

    173 ms

    Scripts block the page for only 173 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 40 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 40 requests on a phone: images 1.4 MB (13), scripts 327 KiB (9) and fonts 277 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

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

  • 3 images below the first screen load straight away

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

  • About 0.6 g of CO₂ per visit

    0.59 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 70.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 are sized for phones

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

Accessibility

4 to fixGoogle 8494
  • 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.

  • Zoom is disabled

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

  • Headings should not be empty (6 elements)

    Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3, h3 → h5 and h2 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 26 automated accessibility rules passed

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

SEO

3 to fixGoogle 9288
  • Title is short (14 characters)

    Your title is only 14 characters: “Home - Eastern”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 2 links with vague text

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

  • 21 internal links, 7 external

    The homepage links to 21 pages on goeasternair.com and 7 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Eastern Airlines set the benchmark in passenger and cargo services with wide and narrow-body Boeing aircraft, deliverin…”.

  • One H1 headline

    Your main headline reads: “WORLD-CLASS AIR TRAVEL & CARGO SERVICES”.

  • Canonical URL set

    The canonical URL is https://goeasternair.com/.

  • Structured data in place

    Structured data found: Airline, Article, ImageObject, Organization and Person.

  • 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://goeasternair.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://goeasternair.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 (318 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    https://goeasternair.com/about-us and https://goeasternair.com/about all use the title “About Us - Eastern”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://goeasternair.com/about-us and https://goeasternair.com/about use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://goeasternair.com/about, whose canonical is https://goeasternair.com/about-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://goeasternair.com/fleet, https://goeasternair.com/about-us, https://goeasternair.com/contact-us, https://goeasternair.com/career, https://goeasternair.com/about and https://goeasternair.com/flights-terms-and-conditions have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://goeasternair.com/coming-soon has 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.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Looks like your website URL has changed. To ensure the proper functioning of your banner, update the re…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • 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 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 296 words of copy

    The homepage carries about 296 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: “Learn More”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Learn More” and “Learn More About Eastern”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 2 cookies set on arrival

    2

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

  • 6 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Liberty Link Holden

Company

Employees
422
Founded
2009
Headquarters
Miami-Dade County

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on goeasternair.com, including 12 speed issues, 3 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