Website review, no card needed

aar-insurance.com logo

aar-insurance.com website review

Visit site (opens in a new tab)Reviewed 2 November 202637 issues · 78 checks

This review found 37 issues worth fixing on aar-insurance.com, 20 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

Real-visitor load time (LCP)75th percentile, phones
7.2 s4.3 sMay 16Oct 314.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20266.7 s
May 23, 20266.5 s
May 30, 20266.5 s
Jun 6, 20266.5 s
Jun 13, 20266.6 s
Jun 20, 20266.6 s
Jun 27, 20266.5 s
Jul 4, 20266.3 s
Jul 11, 20266.2 s
Jul 18, 20266.2 s
Jul 25, 20266.2 s
Aug 1, 20266.4 s
Aug 8, 20266.3 s
Aug 15, 20266.4 s
Aug 22, 20266.4 s
Aug 29, 20266.5 s
Sep 5, 20266.8 s
Sep 12, 20266.8 s
Sep 19, 20266.9 s
Sep 26, 20266.8 s
Oct 3, 20266.8 s
Oct 10, 20266.5 s
Oct 17, 20266.1 s
Oct 24, 20265.3 s
Oct 31, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
237 ms188 msMay 16Oct 31194 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026211 ms
May 23, 2026206 ms
May 30, 2026206 ms
Jun 6, 2026208 ms
Jun 13, 2026211 ms
Jun 20, 2026215 ms
Jun 27, 2026217 ms
Jul 4, 2026206 ms
Jul 11, 2026200 ms
Jul 18, 2026204 ms
Jul 25, 2026205 ms
Aug 1, 2026212 ms
Aug 8, 2026217 ms
Aug 15, 2026211 ms
Aug 22, 2026212 ms
Aug 29, 2026213 ms
Sep 5, 2026212 ms
Sep 12, 2026207 ms
Sep 19, 2026210 ms
Sep 26, 2026213 ms
Oct 3, 2026218 ms
Oct 10, 2026231 ms
Oct 17, 2026214 ms
Oct 24, 2026202 ms
Oct 31, 2026194 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 aar-insurance.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aar-insurance.com at 1.5 s1.5 s
  2. aar-insurance.com at 2.9 s2.9 s
  3. aar-insurance.com at 4.4 s4.4 s
  4. aar-insurance.com at 5.9 s5.9 s
  5. aar-insurance.com at 7.3 s7.3 s
  6. aar-insurance.com at 8.8 s8.8 s
  7. aar-insurance.com at 10.3 s10.3 s
  8. aar-insurance.com at 11.7 s11.7 s

Speed

8 to fix36
  • Improve image delivery

    7.0 s · 5.1 MB

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

  • Render-blocking requests

    3.2 s

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

  • Reduce unused CSS

    1.1 s · 202 KiB

    About 202 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Font display

    700 ms

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

  • Main-thread work: 3.7 s

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

  • 3 long tasks on the main thread

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

  • 2,345 HTML elements

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

  • Reduce unused JavaScript

    176 KiB

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

  • Legacy JavaScript

    40 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (userway.org and Google Fonts), adding 77 KiB and 26 ms of main-thread time.

  • Minify CSS

    6 KiB

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

  • Use efficient cache lifetimes

    2 KiB

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

1 checks passed
  • Server response: 100 ms

    100 ms

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

Core Web Vitals

11 to fix33
  • 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.6 s

    5.6 s

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

  • Real-user CLS: 0.96

    0.96

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Cumulative Layout Shift: 1.842

    1.842

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

  • Largest Contentful Paint: 17.4 s

    17.4 s

    Your largest element takes 17.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (9.0 s).

  • Speed Index: 18.1 s

    18.1 s

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

  • Time to Interactive: 17.6 s

    17.6 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 16 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

3 checks passed
  • Real-user INP: 178 ms

    178 ms

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

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

    -25%

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

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

1 to fix0
  • Page weight: 10.0 MB in 202 requests

    10.0 MB

    Your homepage downloads 10.0 MB in 202 requests on a phone: images 8.5 MB (72), scripts 676 KiB (59) and fonts 450 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • About 2.8 g of CO₂ per visit

    2.83 g

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

Accessibility

6 to fix74
  • 15 images without alt text

    15 images have no alt text, which hurts accessibility and image search.

  • 10 buttons without a name

    10 buttons have no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 33 links without text

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

  • 17 text elements with low contrast

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

  • 10 tap targets too small

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (1 element).

SEO

5 to fixGoogle 7772
  • 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 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.

  • 17 links with vague text

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

  • 147 internal links, 40 external

    The homepage links to 147 pages on aar-insurance.com and 40 external pages.

4 checks passed
  • Title: 34 characters

    Your title is a healthy 34 characters: “AAR Insurance – You are in control”.

  • Canonical URL set

    The canonical URL is https://aar-insurance.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://aar-insurance.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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://aar-insurance.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.

Other pages

3 to fix65
  • 3 linked pages are broken

    Your homepage links to https://aar-insurance.com/business-enterprise-medical-plan, https://aar-insurance.com/school-insurance-cover and https://aar-insurance.com/landlord-insurance, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 7 pages without a meta description

    https://aar-insurance.com/help, https://aar-insurance.com/media-and-gallery, https://aar-insurance.com/careers, https://aar-insurance.com/contacts, https://aar-insurance.com/investor-relation and https://aar-insurance.com/family-and-individual-plan and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://aar-insurance.com/help, https://aar-insurance.com/media-and-gallery, https://aar-insurance.com/careers, https://aar-insurance.com/contacts, https://aar-insurance.com/investor-relation and https://aar-insurance.com/family-and-individual-plan and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://aar-insurance.com/family-and-individual-plan and https://aar-insurance.com/seniors-caare-medical-cover took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 5 console errors

    5 errors were logged to the browser console during Google's test (“Access to script at 'https://embed.tawk.to/5ac74babd7591465c7093f9e/1eg2jd4p5' from origin 'https:/…”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 1,314 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

7 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Contact Us”, “Buy Our Products” and “Buy Online”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 56 testimonial or review blocks and 2 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, LinkedIn Insight and TikTok Pixel.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 2 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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 aar-insurance.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
DigitalOcean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on aar-insurance.com, including 19 speed issues, 5 SEO issues and 1 conversion gap. 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