ameritas.com website review

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

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

11 images could be 611 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

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

2 third-party services load with your homepage (bc0a.com and Google Fonts), adding 1.0 MB and 21 ms of main-thread time.

bc0a.com costs a phone 21 ms of main-thread work and 946 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.

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

1 long task block the main thread while loading, the longest for 56 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying CSS.

1 file is served with short cache lifetimes, so returning visitors download them again (3 KiB).

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.

Your largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Financial Strategies for a Fulfilling Life When you have lo…”.

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

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

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

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

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

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

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

Your homepage downloads 2.0 MB in 83 requests on a phone: images 1.4 MB (63), stylesheets 265 KiB (8) and scripts 143 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

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

6 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: 7 elements on the page fail this check, rated moderate by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

The homepage links to 94 pages on ameritas.com and 9 external pages.

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

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

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 372 words of visible text.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 redirect=ameritas.com.hosted.spf-report.com”.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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.

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