Website review, no card needed

airmar.com logo

airmar.com website review

Visit site (opens in a new tab)Reviewed 18 October 202648 issues · 69 checks

This review found 48 issues worth fixing on airmar.com, 20 of them high impact, across 69 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
6.2 s4.9 sApr 25Oct 106.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20265.2 s
May 2, 20265.1 s
May 9, 20265.1 s
May 16, 20265.2 s
May 23, 20265.2 s
May 30, 20265.2 s
Jun 6, 20265.3 s
Jun 13, 20265.2 s
Jun 20, 20265.2 s
Jun 27, 20265.4 s
Jul 4, 20265.5 s
Jul 11, 20265.6 s
Jul 18, 20265.7 s
Jul 25, 20265.7 s
Aug 1, 20265.7 s
Aug 8, 20265.8 s
Aug 15, 20265.8 s
Aug 22, 20265.9 s
Aug 29, 20265.8 s
Sep 5, 20265.9 s
Sep 12, 20265.9 s
Sep 19, 20265.9 s
Sep 26, 20266.0 s
Oct 3, 20266.0 s
Oct 10, 20266.0 s
Real-visitor tap response (INP)75th percentile, phones
174 ms135 msApr 25Oct 10154 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026163 ms
May 2, 2026155 ms
May 9, 2026156 ms
May 16, 2026155 ms
May 23, 2026148 ms
May 30, 2026148 ms
Jun 6, 2026140 ms
Jun 13, 2026139 ms
Jun 20, 2026145 ms
Jun 27, 2026153 ms
Jul 4, 2026157 ms
Jul 11, 2026169 ms
Jul 18, 2026164 ms
Jul 25, 2026154 ms
Aug 1, 2026149 ms
Aug 8, 2026142 ms
Aug 15, 2026147 ms
Aug 22, 2026152 ms
Aug 29, 2026153 ms
Sep 5, 2026152 ms
Sep 12, 2026153 ms
Sep 19, 2026154 ms
Sep 26, 2026154 ms
Oct 3, 2026154 ms
Oct 10, 2026154 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 airmar.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. airmar.com at 0.5 s0.5 s
  2. airmar.com at 1.0 s1.0 s
  3. airmar.com at 1.5 s1.5 s
  4. airmar.com at 2.0 s2.0 s
  5. airmar.com at 2.5 s2.5 s
  6. airmar.com at 3.0 s3.0 s
  7. airmar.com at 3.5 s3.5 s
  8. airmar.com at 4.0 s4.0 s

Speed

9 to fix58
  • Use efficient cache lifetimes

    2.0 s · 3.7 MB

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

  • Improve image delivery

    450 ms · 2.4 MB

    10 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused JavaScript

    910 ms · 193 KiB

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

  • Mobile performance score: 58

    58/100

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

  • Render-blocking requests

    450 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

  • 4 third-party services on the page

    4 third-party services load with your homepage (cloudfront.net, insitecloud.net and ipapi.co and others), adding 3.4 MB and 0 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • cloudfront.net adds 0 ms

    0 ms

    cloudfront.net costs a phone 0 ms of main-thread work and 3.1 MB 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.

  • insitecloud.net adds 0 ms

    0 ms

    insitecloud.net costs a phone 0 ms of main-thread work and 298 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.

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 16 ms

    16 ms

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

Core Web Vitals

12 to fix0
  • 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.

  • Real-user LCP: 5.9 s

    5.9 s

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

  • Real-user CLS: 1.21

    1.21

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

  • Real-user FCP: 4.6 s

    4.6 s

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

  • Largest Contentful Paint: 13.7 s

    13.7 s

    Your largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 14.4 s

    14.4 s

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

  • Real-user INP: 235 ms

    235 ms

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.193

    0.193

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

  • Speed Index: 4.9 s

    4.9 s

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

  • Total Blocking Time: 254 ms

    254 ms

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

  • 10 images without width and height

    10 images have no width and height attributes, so the layout jumps as each one loads.

  • 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 163 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    +18%

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

1 checks passed
  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

5 to fix33
  • 2 images over 500 KB

    2 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    1.6 MB

    8 images are downloaded at several times the size a phone draws them, for example trisonic-display-gauges-phone-v2.png at 1,024 px wide, shown at 191 px. Resized copies would save about 1.6 MB.

  • Page weight: 3.9 MB in 53 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 53 requests on a phone: images 3.4 MB (34), scripts 407 KiB (3) and other files 73 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 12 images in older formats

    12 images (3.1 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.

  • 8 images below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.11 g

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

Accessibility

6 to fixGoogle 8089
  • Images must have alternative text (5 elements)

    Images must have alternative text: 5 elements on the page fail this check, rated critical by axe-core.

  • <svg> elements with an img or image role must have alternative text (4 elements)

    <svg> elements with an img or image role must have alternative text: 4 elements on the page fail this check, rated serious by axe-core.

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

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

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

9 to fixGoogle 8548
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • 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.airmar.com/Catalog/Legacy-Products/DST800L-235-N2, 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.

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

  • No X (Twitter) card tag

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

1 checks passed
  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 590 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 590 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 9 cookies set on arrival

    9

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

Company

Founded
1982
Headquarters
Milford

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on airmar.com, including 21 speed issues, 9 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