Website review, no card needed

flytradewind.com logo

flytradewind.com website review

Visit site (opens in a new tab)Reviewed 3 November 202631 issues · 84 checks

This review found 31 issues worth fixing on flytradewind.com, 7 of them high impact, across 84 checks. The most urgent: page weight: 14.4 MB in 133 requests. 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.5 s1.8 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.0 s
May 23, 20265.1 s
May 30, 20264.9 s
Jun 6, 20264.7 s
Jun 13, 20264.2 s
Jun 20, 20263.4 s
Jun 27, 20262.7 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.5 s
Sep 12, 20262.7 s
Sep 19, 20262.8 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.8 s
Oct 17, 20262.7 s
Oct 24, 20262.6 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
188 ms112 msMay 16Oct 31169 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026128 ms
May 23, 2026122 ms
May 30, 2026121 ms
Jun 6, 2026129 ms
Jun 13, 2026130 ms
Jun 20, 2026129 ms
Jun 27, 2026134 ms
Jul 4, 2026135 ms
Jul 11, 2026133 ms
Jul 18, 2026134 ms
Jul 25, 2026137 ms
Aug 1, 2026142 ms
Aug 8, 2026145 ms
Aug 15, 2026146 ms
Aug 22, 2026148 ms
Aug 29, 2026154 ms
Sep 5, 2026156 ms
Sep 12, 2026161 ms
Sep 19, 2026170 ms
Sep 26, 2026175 ms
Oct 3, 2026177 ms
Oct 10, 2026179 ms
Oct 17, 2026179 ms
Oct 24, 2026171 ms
Oct 31, 2026169 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 flytradewind.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. flytradewind.com at 0.9 s0.9 s
  2. flytradewind.com at 1.7 s1.7 s
  3. flytradewind.com at 2.6 s2.6 s
  4. flytradewind.com at 3.4 s3.4 s
  5. flytradewind.com at 4.3 s4.3 s
  6. flytradewind.com at 5.2 s5.2 s
  7. flytradewind.com at 6.0 s6.0 s
  8. flytradewind.com at 6.9 s6.9 s

Speed

10 to fix65
  • 4,235 HTML elements

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

  • 8 third-party services on the page

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

  • Mobile performance score: 65

    65/100

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

  • Google Tag Manager adds 865 ms

    865 ms

    Google Tag Manager costs a phone 865 ms of main-thread work and 1,000 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.

  • Reduce unused JavaScript

    705 KiB

    About 705 KiB of JavaScript is downloaded but never used on this page.

  • Reduce initial server response time

    501 ms

    Reduce initial server response time. Google estimates savings of 501 ms on a phone.

  • Document request latency

    500 ms

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

  • Main-thread work: 3.2 s

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

  • Use efficient cache lifetimes

    268 KiB

    13 files are served with short cache lifetimes, so returning visitors download them again (268 KiB).

  • Server response: 601 ms

    601 ms

    Your server takes 601 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 15 long tasks on the main thread

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

  • Reduce unused CSS

    59 KiB

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

  • Improve image delivery

    25 KiB

    1 image could be 25 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    20 KiB

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

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

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

Core Web Vitals

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

  • Time to Interactive: 21.1 s

    21.1 s

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

  • Speed Index: 12.2 s

    12.2 s

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

  • Total Blocking Time: 995 ms

    995 ms

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

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

    +36%

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

  • Real-user TTFB: 842 ms

    842 ms

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Three Tradewind PC-12s flying in formation against a clear …”. Most of its time is resource load delay (3.0 s).

7 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 177 ms

    177 ms

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 1.2 s

    1.2 s

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

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

    -49%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.032

    0.032

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

Images and page weight

1 to fix70
  • Page weight: 14.4 MB in 133 requests

    14.4 MB

    Your homepage downloads 14.4 MB in 133 requests on a phone: media 10.4 MB (3), scripts 1.7 MB (39) and other files 1.6 MB (44). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (115 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 4.1 g of CO₂ per visit

    4.09 g

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

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 10098
  • 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 52 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 1 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 9295
  • No social preview image

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

  • 12 links with vague text

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

  • 101 internal links, 13 external

    The homepage links to 101 pages on flytradewind.com and 13 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Fly private charter and semi-private scheduled service with Tradewind to the Northeast, Caribbean, and Bahamas. Explore…”.

  • One H1 headline

    Your main headline reads: “Fly Personal Across North America and the Caribbean”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Scheduled and Private Charter Flights | Tradewind Aviation”.

  • Canonical URL set

    The canonical URL is https://www.flytradewind.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • 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.flytradewind.com/sitemap_index.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.

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

  • llms.txt published

    The site publishes https://www.flytradewind.com/llms.txt (8 KiB, 33 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 10 pages slow to respond

    https://www.flytradewind.com/ticket-books, https://www.flytradewind.com/travel-info, https://www.flytradewind.com/northeast-kbyg, https://www.flytradewind.com/caribbean-kbyg, https://www.flytradewind.com/southeast-bahamas-kbyg and https://www.flytradewind.com/flight-status and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

5 to fixGoogle 5469
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=56369803&Ver=2&mid=699ba18c-27ca-45ab-8587-d20dc4a4f5cd&bo=1&sid=fe67db80d77011f181981bab1af74a9e&vid=fe680bc0d77011f1bb30d748b58b4ba3&vids=1&msclkid=N&pi=918639831&lg.

  • 5 small tap targets

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

  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • 6 JavaScript errors while loading

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

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No analytics detected

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

  • A 8-field form

    Your longest form asks for 8 fields (4 required). Every extra field lowers completion.

  • 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 1,238 words of copy

    The homepage carries about 1,238 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.” and “BOOK”.

  • 30 calls to action

    The homepage has 30 calls to action, for example “Learn more.”, “Book a flight” and “Book”.

  • Social proof on the page

    Social proof on the homepage: 29 testimonial or review blocks and 3 trust badges.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 12 cookies set on arrival

    12

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

  • 43 other companies contacted

    Loading the homepage contacts 43 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 flytradewind.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
Hosting
AWS

Hiring

Hiring
22 open roles
Teams
Maintenance (7), Flight Operations (3), Caribbean Office (2), Scheduling (1)
Job board
paylocity

Company

Founded
2001
Headquarters
Oxford

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on flytradewind.com, including 17 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