Website review, no card needed
aacreditunion.org website review
Visit site (opens in a new tab)Reviewed 30 October 202640 issues · 84 checks
This review found 40 issues worth fixing on aacreditunion.org, 15 of them high impact, across 84 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 185 ms |
| May 16, 2026 | 183 ms |
| May 23, 2026 | 184 ms |
| May 30, 2026 | 186 ms |
| Jun 6, 2026 | 192 ms |
| Jun 13, 2026 | 196 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 199 ms |
| Jul 4, 2026 | 201 ms |
| Jul 11, 2026 | 204 ms |
| Jul 18, 2026 | 204 ms |
| Jul 25, 2026 | 205 ms |
| Aug 1, 2026 | 206 ms |
| Aug 8, 2026 | 209 ms |
| Aug 15, 2026 | 213 ms |
| Aug 22, 2026 | 211 ms |
| Aug 29, 2026 | 207 ms |
| Sep 5, 2026 | 205 ms |
| Sep 12, 2026 | 203 ms |
| Sep 19, 2026 | 207 ms |
| Sep 26, 2026 | 208 ms |
| Oct 3, 2026 | 209 ms |
| Oct 10, 2026 | 207 ms |
| Oct 17, 2026 | 206 ms |
| Oct 24, 2026 | 207 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.8 s
1.3 s
1.7 s
2.1 s
2.5 s
2.9 s
3.3 s
Speed
Use efficient cache lifetimes
6.0 s · 1.1 MB52 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Reduce unused JavaScript
3.9 s · 710 KiBAbout 710 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.
Render-blocking requests
1.9 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
8 third-party services on the page
8 third-party services load with your homepage (onlineaccess1.com, Google Tag Manager and salemove.com and others), adding 1.4 MB and 1.3 s of main-thread time.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
onlineaccess1.com adds 740 ms
740 msonlineaccess1.com costs a phone 740 ms of main-thread work and 184 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.
Reduce unused CSS
610 ms · 76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.
Google Tag Manager adds 244 ms
244 msGoogle Tag Manager costs a phone 244 ms of main-thread work and 320 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.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
salemove.com adds 145 ms
145 mssalemove.com costs a phone 145 ms of main-thread work and 429 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.
Google CDN adds 83 ms
83 msGoogle CDN costs a phone 83 ms of main-thread work and 352 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.
Improve image delivery
150 ms · 136 KiB2 images could be 136 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
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: 8 ms
8 msYour server sent the HTML in 8 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.
Largest Contentful Paint: 19.3 s
19.3 sYour largest element takes 19.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THE RIGHT MOVE FOR THE HOLIDAYS Whether you're purchasing o…”.
Time to Interactive: 19.8 s
19.8 sThe page becomes fully interactive after 19.8 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user INP: 226 ms
226 msReal visitors wait 226 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 429 ms
429 msScripts block taps and scrolling for 429 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 185 ms to 207 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 484 ms
484 msReal visitors wait 484 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 88 requests
3.1 MBYour homepage downloads 3.1 MB in 88 requests on a phone: scripts 1.7 MB (33), fonts 680 KiB (3) and images 627 KiB (23). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
6 KiB1 image is downloaded at several times the size a phone draws it, for example picture--james-wilson.jpg at 960 px wide, shown at 310 px. Resized copies would save about 6 KiB.
1 image in older formats
1 image (456 KiB) is 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.
1 image below the first screen load straight away
1 image further down the page (103 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (4 elements)
Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (6 elements)
Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h4 → h6 and h3 → h6), 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).
2 checks passed
Every image has alt text
All 28 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (4 characters)
Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at aacreditunion.org/robots.txt, the first file search crawlers ask for.
8 links crawlers can't follow
8 links have no real href, so search engines can't follow them.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
107 internal links, 18 external
The homepage links to 107 pages on aacreditunion.org and 18 external pages.
4 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “American Airlines Credit Union proudly serves the air transportation industry. We are here to provide our members with …”.
One H1 headline
Your main headline reads: “THE RIGHT MOVE FOR THE HOLIDAYS”.
Canonical URL set
The canonical URL is https://www.aacreditunion.org/www.aacreditunion.org/.
XML sitemap found
Your XML sitemap is reachable at https://www.aacreditunion.org/sitemap.xml.
AI search readiness
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.aacreditunion.org/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,597 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
1 broken image
1 image failed to load on a phone, for example https://www.aacreditunion.org/.
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.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
12 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
About 663 words of copy
The homepage carries about 663 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
16 calls to action
The homepage has 16 calls to action, for example “Contact Us”, “Join Now” and “Why Join?”.
4 short forms
4 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 6 testimonial or review blocks and 5 customer or partner logos.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 2 of them by other companies (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.
17 other companies contacted
Loading the homepage contacts 17 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 aacreditunion.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- Analytics
- Google Tag Manager
- Hosting
- Episerver
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 aacreditunion.org, including 20 speed issues and 6 SEO issues. 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.