Website review, no card needed

americantrustretirement.com logo

americantrustretirement.com website review

Visit site (opens in a new tab)Reviewed 4 November 202618 issues · 74 checks

This review found 18 issues worth fixing on americantrustretirement.com, 2 of them high impact, across 74 checks. The most urgent: page weight: 11.4 MB in 34 requests. 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
1.0 s687 msMay 16Oct 31726 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026928 ms
May 23, 2026926 ms
May 30, 2026919 ms
Jun 6, 2026921 ms
Jun 13, 2026922 ms
Jun 20, 2026912 ms
Jun 27, 2026929 ms
Jul 4, 2026926 ms
Jul 11, 2026932 ms
Jul 18, 2026965 ms
Jul 25, 2026970 ms
Aug 1, 2026986 ms
Aug 8, 2026949 ms
Aug 15, 2026881 ms
Aug 22, 2026849 ms
Aug 29, 2026812 ms
Sep 5, 2026806 ms
Sep 12, 2026817 ms
Sep 19, 2026841 ms
Sep 26, 2026831 ms
Oct 3, 2026790 ms
Oct 10, 2026769 ms
Oct 17, 2026733 ms
Oct 24, 2026730 ms
Oct 31, 2026726 ms
Real-visitor tap response (INP)75th percentile, phones
70 ms61 msMay 16Oct 3162 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202663 ms
May 23, 202663 ms
May 30, 202664 ms
Jun 6, 202664 ms
Jun 13, 202664 ms
Jun 20, 202663 ms
Jun 27, 202663 ms
Jul 4, 202663 ms
Jul 11, 202663 ms
Jul 18, 202663 ms
Jul 25, 202663 ms
Aug 1, 202664 ms
Aug 8, 202665 ms
Aug 15, 202666 ms
Aug 22, 202666 ms
Aug 29, 202664 ms
Sep 5, 202666 ms
Sep 12, 202667 ms
Sep 19, 202669 ms
Sep 26, 202669 ms
Oct 3, 202667 ms
Oct 10, 202663 ms
Oct 17, 202662 ms
Oct 24, 202662 ms
Oct 31, 202662 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 americantrustretirement.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

1 to fix95
  • Improve image delivery

    300 ms · 30 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, nitrocdn.com and Google Fonts), adding 355 KiB and 62 ms of main-thread time.

  • Reduce unused JavaScript

    74 KiB

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

  • 1 long task on the main thread

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

  • Reduce unused CSS

    13 KiB

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

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

3 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

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

  • Server response: 10 ms

    10 ms

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

Core Web Vitals

1 to fix100
  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Make your retirement plans tick with WorkSaveRetire. This i…”.

  • Tap response (INP) held steady for real visitors

    -2%

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

12 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user INP: 64 ms

    64 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 682 ms

    682 ms

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

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

    -21%

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

  • Time to Interactive: 3.6 s

    3.6 s

    The page is fully interactive after 3.6 s.

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

  • Cumulative Layout Shift: 0.002

    0.002

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

  • Speed Index: 1.1 s

    1.1 s

    Visually, the page fills in at 1.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 7 ms

    7 ms

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

Images and page weight

1 to fix70
  • Page weight: 11.4 MB in 34 requests

    11.4 MB

    Your homepage downloads 11.4 MB in 34 requests on a phone: media 10.8 MB (1), other files 240 KiB (17) and fonts 169 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • About 3.2 g of CO₂ per visit

    3.23 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8292
  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Headings should not be empty (4 elements)

    Headings should not be empty: 4 elements on the page fail 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.

  • 29 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • Meta description is long (235 characters)

    Your meta description is 235 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.

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

  • 39 internal links, 14 external

    The homepage links to 39 pages on americantrustretirement.com and 14 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Save Time, Reduce Liability and Scale Your Business with WorkSaveRetire”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Retirement Services & Solutions - American Trust Retirement”.

  • Canonical URL set

    The canonical URL is https://www.americantrustretirement.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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.americantrustretirement.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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.americantrustretirement.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 (733 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 10087
  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • About 351 words of copy

    The homepage carries about 351 words of visible text.

4 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Learn more” and “CCPA Request”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

  • 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

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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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 americantrustretirement.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 Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on americantrustretirement.com, including 2 speed issues, 3 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