Website review, no card needed

aarelectronics.aero logo

aarelectronics.aero website review

Visit site (opens in a new tab)Reviewed 1 November 202631 issues · 78 checks

This review found 31 issues worth fixing on aarelectronics.aero, 11 of them high impact, across 78 checks. The most urgent: improve image delivery. 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

Full-page screenshot of aarelectronics.aero (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aarelectronics.aero at 1.6 s1.6 s
  2. aarelectronics.aero at 3.2 s3.2 s
  3. aarelectronics.aero at 4.8 s4.8 s
  4. aarelectronics.aero at 6.4 s6.4 s
  5. aarelectronics.aero at 8.0 s8.0 s
  6. aarelectronics.aero at 9.6 s9.6 s
  7. aarelectronics.aero at 11.2 s11.2 s
  8. aarelectronics.aero at 12.8 s12.8 s

Speed

10 to fix50
  • Improve image delivery

    7.3 s · 1.4 MB

    8 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.3 s faster on a phone.

  • Use efficient cache lifetimes

    6.5 s · 1.3 MB

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

  • Reduce unused JavaScript

    5.0 s · 894 KiB

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

  • Render-blocking requests

    2.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google Maps and Optanon and others), adding 1.8 MB and 991 ms of main-thread time.

  • Reduce unused CSS

    900 ms · 233 KiB

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

  • Mobile performance score: 50

    50/100

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

  • Google Tag Manager adds 653 ms

    653 ms

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

  • Google Maps adds 222 ms

    222 ms

    Google Maps costs a phone 222 ms of main-thread work and 489 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.

  • Main-thread work: 2.1 s

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

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    50 ms · 20 KiB

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

  • Font display

    50 ms

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

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

  • Minify JavaScript

    7 KiB

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

1 checks passed
  • Server response: 91 ms

    91 ms

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

Core Web Vitals

6 to fix59
  • Largest Contentful Paint: 83.0 s

    83.0 s

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

  • Time to Interactive: 83.0 s

    83.0 s

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

  • Speed Index: 15.3 s

    15.3 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Total Blocking Time: 312 ms

    312 ms

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

  • 6 images without width and height

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

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

1 checks passed
  • Cumulative Layout Shift: 0.007

    0.007

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

Images and page weight

2 to fix63
  • Page weight: 15.2 MB in 188 requests

    15.2 MB

    Your homepage downloads 15.2 MB in 188 requests on a phone: other files 10.4 MB (63), images 2.3 MB (18) and scripts 2.0 MB (69). Under 2 MB keeps phones on slow connections fast.

  • 3 images below the first screen load straight away

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

  • 4 images in older formats

    4 images (413 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 4.3 g of CO₂ per visit

    4.32 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.32 g of CO₂e: 517.8 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

2 to fixGoogle 9798
  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

6 to fixGoogle 8572
  • No H1 headline

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

  • Title is short (22 characters)

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

  • Meta description is long (199 characters)

    Your meta description is 199 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 59 internal links, 3 external

    The homepage links to 59 pages on aarelectronics.aero and 3 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://aarelectronics.aero/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, 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.aviadynamics.com/page-sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://aarelectronics.aero/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.

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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 3 pages without a meta description

    https://aarelectronics.aero/request-for-quote, https://aarelectronics.aero/contact-us and https://aarelectronics.aero/markets have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://aarelectronics.aero/markets 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.

  • 4 pages slow to respond

    https://aarelectronics.aero/markets/aerospace, https://aarelectronics.aero/markets/agriculture, https://aarelectronics.aero/markets/construction and https://aarelectronics.aero/markets/on-highway took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • 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 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 7 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 291 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request Quote” and “Contact”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Request Quote” and “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 3 trackers load before any consent

    3

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

  • 17 cookies set on arrival

    17

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 aarelectronics.aero, 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
Oracle Cloud

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 aarelectronics.aero, including 16 speed issues, 6 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