Website review, no card needed

airlinq.com logo

airlinq.com website review

Visit site (opens in a new tab)Reviewed 3 November 202629 issues · 74 checks

This review found 29 issues worth fixing on airlinq.com, 8 of them high impact, across 74 checks. The most urgent: render-blocking 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
6.0 s4.5 sMay 16Sep 125.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.8 s
May 23, 20265.7 s
May 30, 20265.6 s
Jun 6, 20265.7 s
Jun 13, 20265.4 s
Jun 20, 20265.2 s
Jun 27, 20265.3 s
Jul 4, 20265.1 s
Jul 11, 20264.9 s
Jul 18, 20264.9 s
Jul 25, 20264.7 s
Aug 1, 20264.9 s
Aug 8, 20264.9 s
Aug 15, 20264.9 s
Aug 22, 20265.0 s
Aug 29, 20265.1 s
Sep 5, 20265.3 s
Sep 12, 20265.4 s
Real-visitor tap response (INP)75th percentile, phones
146 ms91 msMay 16Sep 5122 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026130 ms
May 23, 2026128 ms
May 30, 2026121 ms
Jun 6, 2026120 ms
Jun 13, 2026115 ms
Jun 20, 2026119 ms
Jun 27, 2026117 ms
Jul 4, 2026115 ms
Jul 11, 2026114 ms
Jul 18, 202697 ms
Jul 25, 2026103 ms
Aug 1, 2026106 ms
Aug 8, 2026121 ms
Aug 15, 2026138 ms
Aug 22, 2026140 ms
Aug 29, 2026135 ms
Sep 5, 2026122 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 airlinq.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. airlinq.com at 0.5 s0.5 s
  2. airlinq.com at 0.9 s0.9 s
  3. airlinq.com at 1.4 s1.4 s
  4. airlinq.com at 1.9 s1.9 s
  5. airlinq.com at 2.4 s2.4 s
  6. airlinq.com at 2.8 s2.8 s
  7. airlinq.com at 3.3 s3.3 s
  8. airlinq.com at 3.8 s3.8 s

Speed

4 to fix68
  • Render-blocking requests

    5.0 s

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

  • 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: 68

    68/100

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

  • Reduce unused CSS

    600 ms · 161 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Cookiebot, Google Fonts and GoDaddy), adding 213 KiB and 197 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Reduce unused JavaScript

    95 KiB

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

  • Use efficient cache lifetimes

    55 KiB

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

  • Improve image delivery

    20 KiB

    3 images could be 20 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    13 KiB

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

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

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

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

4 to fix77
  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Largest Contentful Paint: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”. Most of its time is element render delay (3.2 s).

  • Speed Index: 6.7 s

    6.7 s

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

  • Time to Interactive: 4.7 s

    4.7 s

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

  • Tap response (INP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 130 ms to 122 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-31, real Chrome visitors' largest content (lcp) went from 5.8 s to 5.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

4 to fix58
  • Page weight: 2.4 MB in 129 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 129 requests on a phone: images 962 KiB (11), scripts 617 KiB (54) and stylesheets 605 KiB (51). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    AirlinqGraphics-08.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 4 images far larger than shown

    401 KiB

    4 images are downloaded at several times the size a phone draws them, for example AirlinqGraphics-08.png at 7,375 px wide, shown at 370 px. Resized copies would save about 401 KiB.

  • 5 images in older formats

    5 images (512 KiB) 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.

  • About 0.7 g of CO₂ per visit

    0.67 g

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

Accessibility

3 to fixGoogle 9196
  • 8 text elements with low contrast

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

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

    All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 45 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: 45 passed and 4 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 10083
  • No H1 headline

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

  • Title is long (79 characters)

    Your title is 79 characters, so Google will cut it off around 60: “Ecosystem Enablement, Global Connectivity Solutions for OEM & Telecom | Airlinq”.

  • 45 internal links, 5 external

    The homepage links to 45 pages on airlinq.com and 5 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Airlinq enabling the development of next-gen mobility & edge solutions to deliver ecosystem monetization for automakers…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.airlinq.com/sitemap.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.

  • No llms.txt

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

Other pages

4 to fix81
  • 10 pages share 2 titles

    https://www.airlinq.com/platform, https://www.airlinq.com/mobilinq and https://www.airlinq.com/utilinq all use the title “IoT Connectivity & Application Management, 5G & NBIoT Ready Solutions…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.airlinq.com/blogs, https://www.airlinq.com/use-cases, https://www.airlinq.com/about-us and https://www.airlinq.com/career have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages share a meta description

    https://www.airlinq.com/platform, https://www.airlinq.com/mobilinq and https://www.airlinq.com/utilinq use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.airlinq.com/platform, https://www.airlinq.com/mobilinq, https://www.airlinq.com/autolinq, https://www.airlinq.com/utilinq, https://www.airlinq.com/marketlinq and https://www.airlinq.com/telecommunication and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 pages slow to respond

    https://www.airlinq.com/platform, https://www.airlinq.com/mobilinq, https://www.airlinq.com/autolinq, https://www.airlinq.com/utilinq, https://www.airlinq.com/marketlinq and https://www.airlinq.com/telecommunication and 6 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 20 found) and read each the way a search engine does.

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

  • 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

3 to fixGoogle 9285
  • 2 small tap targets

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

  • 2 JavaScript errors while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • 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: 2 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.

  • Only about 237 words

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

2 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact”, “Get a Demo” and “Book your demo”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, HubSpot and LinkedIn Insight.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

2 checks passed
  • Consent tool: Cookiebot

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

  • 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 airlinq.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 | Google Tag Manager
Hosting
GoDaddy

Hiring

Hiring
5 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on airlinq.com, including 8 speed issues, 2 SEO issues and 4 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