Website review, no card needed

airspace-intelligence.com logo

airspace-intelligence.com website review

Visit site (opens in a new tab)Reviewed 18 October 202615 issues · 75 checks

This review found 15 issues worth fixing on airspace-intelligence.com, 6 of them high impact, across 75 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
1.4 s638 msApr 25Oct 10792 ms
Show as table
DateReal-visitor load time (LCP)
Apr 25, 2026940 ms
May 2, 2026763 ms
May 9, 2026720 ms
May 16, 2026886 ms
May 23, 2026888 ms
May 30, 20261.2 s
Jun 6, 20261.3 s
Jun 13, 20261.1 s
Jun 20, 2026908 ms
Jun 27, 2026852 ms
Jul 4, 2026841 ms
Jul 11, 2026818 ms
Jul 18, 2026886 ms
Jul 25, 2026964 ms
Aug 1, 2026919 ms
Aug 8, 2026919 ms
Aug 15, 2026839 ms
Aug 22, 2026811 ms
Aug 29, 2026770 ms
Sep 5, 2026722 ms
Sep 12, 2026728 ms
Sep 19, 2026732 ms
Sep 26, 2026746 ms
Oct 3, 2026784 ms
Oct 10, 2026792 ms
Real-visitor tap response (INP)75th percentile, phones
81 ms66 msApr 25Oct 1072 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202679 ms
May 2, 202670 ms
May 9, 202669 ms
May 16, 202669 ms
May 23, 202669 ms
May 30, 202677 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202674 ms
Jun 27, 202670 ms
Jul 4, 202669 ms
Jul 11, 202668 ms
Jul 18, 202668 ms
Jul 25, 202671 ms
Aug 1, 202673 ms
Aug 8, 202676 ms
Aug 15, 202672 ms
Aug 22, 202672 ms
Aug 29, 202670 ms
Sep 5, 202670 ms
Sep 12, 202670 ms
Sep 19, 202671 ms
Sep 26, 202672 ms
Oct 3, 202673 ms
Oct 10, 202672 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 airspace-intelligence.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. airspace-intelligence.com at 0.6 s0.6 s
  2. airspace-intelligence.com at 1.2 s1.2 s
  3. airspace-intelligence.com at 1.8 s1.8 s
  4. airspace-intelligence.com at 2.3 s2.3 s
  5. airspace-intelligence.com at 2.9 s2.9 s
  6. airspace-intelligence.com at 3.5 s3.5 s
  7. airspace-intelligence.com at 4.1 s4.1 s
  8. airspace-intelligence.com at 4.7 s4.7 s

Speed

5 to fix65
  • Reduce unused JavaScript

    1.7 s · 312 KiB

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

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 98). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    750 ms

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

  • Improve image delivery

    400 ms · 236 KiB

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

  • sanity.io adds 0 ms

    0 ms

    sanity.io costs a phone 0 ms of main-thread work and 354 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, b-cdn.net and sanity.io and others), adding 511 KiB and 142 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 36 KiB

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

  • 3 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 98 but mobile only 65. 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.

  • Use efficient cache lifetimes

    2 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (2 KiB).

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 7.6 s

    7.6 s

    Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Delta Air Lines U.S. Army Federal Aviation Administration S…”.

  • Time to Interactive: 7.7 s

    7.7 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 87 ms

    87 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 469 ms

    469 ms

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

  • Total Blocking Time: 111 ms

    111 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.30 g

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

4 checks passed
  • Page weight: 1.1 MB in 27 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 27 requests on a phone: scripts 500 KiB (8), images 373 KiB (7) and fonts 151 KiB (7). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

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

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 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

1 to fixGoogle 10093
  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “Frontier AI to orchestrate critical infrastructure and national security”.

  • 19 internal links, 4 external

    The homepage links to 19 pages on airspace-intelligence.com and 4 external pages.

7 checks passed
  • Meta description: 73 characters

    Your meta description is 73 characters: “Frontier AI to orchestrate critical infrastructure and national security.”.

  • One H1 headline

    Your main headline reads: “America’sEngine”.

  • Canonical URL set

    The canonical URL is https://www.airspace-intelligence.com/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • 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.airspace-intelligence.com/sitemap-index.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.airspace-intelligence.com/llms.txt (3 KiB, 18 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 3 pages with very little text

    https://www.airspace-intelligence.com/news/fox-business-smart, https://www.airspace-intelligence.com/media and https://www.airspace-intelligence.com/contact 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.

  • 2 pages slow to respond

    https://www.airspace-intelligence.com/media and https://www.airspace-intelligence.com/contact took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

Google 100100
  • 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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.

  • Thin social proof

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

  • 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 502 words of copy

    The homepage carries about 502 words of visible text.

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 airspace-intelligence.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
Astro
Analytics
Google Analytics
Hosting
Vercel

Hiring

Hiring
7 open roles
Teams
HVAC Sales (1), HVAC Service (1), Plumbing Service (1)
Job board
greenhouse

Company

Headquarters
Boston

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 15 issues on airspace-intelligence.com, including 9 speed issues, 1 SEO issue and 3 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