Website review, no card needed

american-equity.com logo

american-equity.com website review

Visit site (opens in a new tab)Reviewed 28 October 202640 issues · 80 checks

This review found 40 issues worth fixing on american-equity.com, 18 of them high impact, across 80 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

Full-page screenshot of american-equity.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. american-equity.com at 0.4 s0.4 s
  2. american-equity.com at 0.8 s0.8 s
  3. american-equity.com at 1.1 s1.1 s
  4. american-equity.com at 1.5 s1.5 s
  5. american-equity.com at 1.9 s1.9 s
  6. american-equity.com at 2.3 s2.3 s
  7. american-equity.com at 2.6 s2.6 s
  8. american-equity.com at 3.0 s3.0 s

Speed

11 to fix45
  • Reduce unused JavaScript

    10.3 s · 2.4 MB

    About 2.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.3 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • Use efficient cache lifetimes

    1.1 s · 456 KiB

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

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 4.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (audioeye-services.com, Google Tag Manager and Wistia and others), adding 1.9 MB and 2.1 s of main-thread time.

  • audioeye-services.com adds 978 ms

    978 ms

    audioeye-services.com costs a phone 978 ms of main-thread work and 306 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.

  • Legacy JavaScript

    650 ms · 115 KiB

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

  • Google Tag Manager adds 591 ms

    591 ms

    Google Tag Manager costs a phone 591 ms of main-thread work and 646 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.

  • Wistia adds 216 ms

    216 ms

    Wistia costs a phone 216 ms of main-thread work and 330 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.

  • Optanon adds 91 ms

    91 ms

    Optanon costs a phone 91 ms of main-thread work and 384 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.

  • Document request latency

    151 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 14 long tasks on the main thread

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

  • Reduce unused CSS

    31 KiB

    About 31 KiB of CSS is downloaded but never applied on this page.

  • Improve image delivery

    19 KiB

    1 image could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

1 checks passed
  • Server response: 25 ms

    25 ms

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

Core Web Vitals

5 to fix55
  • First Contentful Paint: 13.6 s

    13.6 s

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

  • Largest Contentful Paint: 21.3 s

    21.3 s

    Your largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Newsweek - Most Trustworthy companies in America 2026, 4th …”.

  • Time to Interactive: 30.6 s

    30.6 s

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

  • Speed Index: 13.6 s

    13.6 s

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

  • Total Blocking Time: 335 ms

    335 ms

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

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

    0.092

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

Images and page weight

5 to fix14
  • Page weight: 4.9 MB in 102 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 102 requests on a phone: scripts 4.0 MB (45), images 316 KiB (19) and HTML 229 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Zz03MGEwYTBmYzVlODIxMWYxYmRmYTJlODQ2ZmUxMTk2Yg== weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    945 KiB

    1 image is downloaded at several times the size a phone draws it, for example Zz03MGEwYTBmYzVlODIxMWYxYmRmYTJlODQ2ZmUxMTk2Yg== at 3,000 px wide, shown at 358 px. Resized copies would save about 945 KiB.

  • 2 images in older formats

    2 images (1.2 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.

  • An image on the first screen is lazy-loaded

    Zz03MGEwYTBmYzVlODIxMWYxYmRmYTJlODQ2ZmUxMTk2Yg== 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).

  • About 1.4 g of CO₂ per visit

    1.39 g

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

Accessibility

4 to fixGoogle 9293
  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

5 to fixGoogle 9281
  • 2 H1 headlines

    There are 2 <h1> headlines (“Retirement starts with trust” and “Fixed index annuities (FIA)”). One clear main headline is easier for people and search engines.

  • Meta description is long (212 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

  • No social preview image

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

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

  • 23 internal links, 13 external

    The homepage links to 23 pages on american-equity.com and 13 external pages.

4 checks passed
  • Title: 49 characters

    Your title is a healthy 49 characters: “American Equity Investment Life Insurance Company”.

  • Canonical URL set

    The canonical URL is https://www.american-equity.com/.

  • 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.american-equity.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (1 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

Other pages

3 to fix81
  • 1 page points its canonical at the homepage

    https://american-equity.com/professionals declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 3 pages share a title

    /, https://american-equity.com/professionals and https://american-equity.com/usa-patriot-act-notice all use the title “American Equity Investment Life Insurance Company”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://american-equity.com/privacy and https://american-equity.com/usa-patriot-act-notice use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 7388
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=text&args[]= for the full message or use the non-m…”.

  • 1 distorted image

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

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • 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

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

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

  • About 720 words of copy

    The homepage carries about 720 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us” and “Register”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

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

  • 16 other companies contacted

    Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 american-equity.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
Next.js
Analytics
Google Tag Manager
Hosting
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on american-equity.com, including 16 speed issues, 5 SEO issues 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