Website review, no card needed
americafirst.com website review
Visit site (opens in a new tab)Reviewed 30 October 202649 issues · 92 checks
This review found 49 issues worth fixing on americafirst.com, 22 of them high impact, across 92 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.7 s |
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.7 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.7 s |
| Oct 24, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 295 ms |
| May 16, 2026 | 302 ms |
| May 23, 2026 | 300 ms |
| May 30, 2026 | 308 ms |
| Jun 6, 2026 | 319 ms |
| Jun 13, 2026 | 319 ms |
| Jun 20, 2026 | 320 ms |
| Jun 27, 2026 | 320 ms |
| Jul 4, 2026 | 313 ms |
| Jul 11, 2026 | 319 ms |
| Jul 18, 2026 | 316 ms |
| Jul 25, 2026 | 312 ms |
| Aug 1, 2026 | 312 ms |
| Aug 8, 2026 | 312 ms |
| Aug 15, 2026 | 313 ms |
| Aug 22, 2026 | 309 ms |
| Aug 29, 2026 | 296 ms |
| Sep 5, 2026 | 284 ms |
| Sep 12, 2026 | 276 ms |
| Sep 19, 2026 | 270 ms |
| Sep 26, 2026 | 273 ms |
| Oct 3, 2026 | 277 ms |
| Oct 10, 2026 | 273 ms |
| Oct 17, 2026 | 271 ms |
| Oct 24, 2026 | 269 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
How it loaded on a phone
0.4 s
0.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.0 s
3.5 s
Speed
Use efficient cache lifetimes
6.8 s · 2.6 MB48 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Reduce unused JavaScript
5.7 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.
Improve image delivery
3.3 s · 1.8 MB4 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.
Render-blocking requests
1.5 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,050 HTML elements
The page has 4,050 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, onelink-edge.com and Google Maps and others), adding 1.9 MB and 1.1 s of main-thread time.
Reduce unused CSS
750 ms · 207 KiBAbout 207 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google Tag Manager adds 504 ms
504 msGoogle Tag Manager costs a phone 504 ms of main-thread work and 678 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.
Minify JavaScript
350 ms · 141 KiB141 KiB could be saved by minifying JavaScript.
Legacy JavaScript
300 ms · 64 KiBPolyfills for old browsers add 64 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Maps adds 99 ms
99 msGoogle Maps costs a phone 99 ms of main-thread work and 376 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 180 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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: 157 ms
157 msYour server sent the HTML in 157 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 FCP: 3.9 s
3.9 sReal visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 34.5 s
34.5 sYour largest element takes 34.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “AFCU Container Background”.
Time to Interactive: 34.9 s
34.9 sThe page becomes fully interactive after 34.9 s. Good is under 3.8 s.
First Contentful Paint: 6.8 s
6.8 sThe first text or image appears after 6.8 s on a phone. Good is under 1.8 s.
Speed Index: 14.6 s
14.6 sVisually, the page fills in at 14.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 643 ms
643 msScripts block taps and scrolling for 643 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 413 ms
413 msReal visitors wait 413 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.134
0.134The layout shifts by 0.134 while loading, so content jumps under the reader's thumb. Good is under 0.1.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 295 ms to 269 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.7 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 7.2 MB in 164 requests
7.2 MBYour homepage downloads 7.2 MB in 164 requests on a phone: images 3.1 MB (36), scripts 2.4 MB (50) and fonts 1.3 MB (10). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
background-bottom.png weighs 769 KiB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
558 KiB2 images are downloaded at several times the size a phone draws them, for example background-bottom.png at 1,920 px wide, shown at 390 px. Resized copies would save about 558 KiB.
About 2.0 g of CO₂ per visit
2.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.04 g of CO₂e: 244.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
Certain ARIA roles must be contained by particular parents (10 elements)
Certain ARIA roles must be contained by particular parents: 10 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Form elements should have a visible label (2 elements)
Form elements should have a visible label: 2 elements on the page fail this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “America First Credit Union - Personal and Business Banking and Loan Services”.
4 H1 headlines
There are 4 <h1> headlines (“Certificate Accounts”, “Certificate Accounts” and “Low-Rate HELOCs”). One clear main headline is easier for people and search engines.
29 links with vague text
29 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Meta description is long (256 characters)
Your meta description is 256 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
559 internal links, 27 external
The homepage links to 559 pages on americafirst.com and 27 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.americafirst.com/.
Structured data in place
Structured data found: FAQPage and Organization.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.americafirst.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
No llms.txt
There is no https://www.americafirst.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 (2,198 words), so crawlers that don't run JavaScript still read it.
Other pages
8 links to non-canonical URLs
Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.americafirst.com/rv-loans.html, whose canonical is https://www.americafirst.com/loans/vehicle-loans/rv-loans.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://www.americafirst.com/about/help/faq/holiday-hours.html, https://www.americafirst.com/services/other-services/routing-number.html, https://www.americafirst.com/learn.html, https://www.americafirst.com/loans/vehicle-loans.html, https://www.americafirst.com/loans/vehicle-loans/auto-loans.html and https://www.americafirst.com/rv-loans.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 167 found) 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.
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 15 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
About 856 words of copy
The homepage carries about 856 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
27 calls to action
The homepage has 27 calls to action, for example “APPLY NOW”, “APPLY TODAY!” and “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and 2 trust badges.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk and 1 more (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.
22 cookies set on arrival
22Opening the homepage sets 22 cookies (measured from a US location before any click).
45 other companies contacted
Loading the homepage contacts 45 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 americafirst.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Afcu
Company
- Founded
- 1939
- Headquarters
- Riverdale
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on americafirst.com, including 25 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.