Website review, no card needed
communityfirstfl.org website review
Visit site (opens in a new tab)Reviewed 26 October 202631 issues · 75 checks
This review found 31 issues worth fixing on communityfirstfl.org, 10 of them high impact, across 75 checks. The most urgent: improve image delivery. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 195 ms |
| May 16, 2026 | 194 ms |
| May 23, 2026 | 194 ms |
| May 30, 2026 | 196 ms |
| Jun 6, 2026 | 204 ms |
| Jun 13, 2026 | 210 ms |
| Jun 20, 2026 | 213 ms |
| Jun 27, 2026 | 213 ms |
| Jul 4, 2026 | 212 ms |
| Jul 11, 2026 | 210 ms |
| Jul 18, 2026 | 208 ms |
| Jul 25, 2026 | 207 ms |
| Aug 1, 2026 | 206 ms |
| Aug 8, 2026 | 204 ms |
| Aug 15, 2026 | 205 ms |
| Aug 22, 2026 | 205 ms |
| Aug 29, 2026 | 205 ms |
| Sep 5, 2026 | 208 ms |
| Sep 12, 2026 | 207 ms |
| Sep 19, 2026 | 208 ms |
| Sep 26, 2026 | 209 ms |
| Oct 3, 2026 | 209 ms |
| Oct 10, 2026 | 206 ms |
| Oct 17, 2026 | 205 ms |
| Oct 24, 2026 | 204 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.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
53.0 s · 12.0 MB19 images could be 12.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 53.0 s faster on a phone.
Use efficient cache lifetimes
23.8 s · 5.5 MB40 files are served with short cache lifetimes, so returning visitors download them again (5.5 MB).
Render-blocking requests
1.4 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
7 third-party services on the page
7 third-party services load with your homepage (onlineaccess1.com, salemove.com and Google Tag Manager and others), adding 973 KiB and 976 ms of main-thread time.
Mobile performance score: 59
59/100Your mobile performance score is 59 (desktop: 63). Pages that score under 90 lose visitors before the first paint.
onlineaccess1.com adds 658 ms
658 msonlineaccess1.com costs a phone 658 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 JavaScript
150 ms · 431 KiBAbout 431 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
salemove.com adds 132 ms
132 mssalemove.com costs a phone 132 ms of main-thread work and 410 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
150 ms · 64 KiBAbout 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 173 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 1.2 s of it running JavaScript. That is comfortably low.
Server response: 44 ms
44 msYour server sent the HTML in 44 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: 63.1 s
63.1 sYour largest element takes 63.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A Checking Account that Rewards You! Earn a competitive 5.1…”.
Speed Index: 18.7 s
18.7 sVisually, the page fills in at 18.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 66.4 s
66.4 sThe page becomes fully interactive after 66.4 s. Good is under 3.8 s.
Real-user INP: 211 ms
211 msReal visitors wait 211 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 46% slower for real visitors
+46%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.4 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 209 ms
209 msScripts block taps and scrolling for 209 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 195 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 539 ms
539 msReal visitors wait 539 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.02
0.02The layout barely moves while loading (CLS 0.02, good is under 0.1).
Images and page weight
Page weight: 14.4 MB in 52 requests
14.4 MBYour homepage downloads 14.4 MB in 52 requests on a phone: images 13.2 MB (28), scripts 958 KiB (10) and fonts 98 KiB (4). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
713 KiB8 images are downloaded at several times the size a phone draws them, for example CFCU-Awesome-People-Work-Here.png at 1,304 px wide, shown at 360 px. Resized copies would save about 713 KiB.
16 images in older formats
16 images (1.8 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.
16 images below the first screen load straight away
16 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.1 g of CO₂ per visit
4.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.07 g of CO₂e: 489.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 text elements with low contrast
2 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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“A Checking Account that Rewards You!” and “A Checking Account that Rewards You!”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
147 internal links, 21 external
The homepage links to 147 pages on communityfirstfl.org and 21 external pages.
6 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Community First Credit Union: Serving Jacksonville, FL, and nearby communities for 90 years with premier banking servic…”.
Title: 39 characters
Your title is a healthy 39 characters: “Community First Credit Union of Florida”.
Canonical URL set
The canonical URL is https://www.communityfirstfl.org/.
Structured data in place
Structured data found: FinancialService.
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.communityfirstfl.org/sitemap.xml.
AI search readiness
4 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (757 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.communityfirstfl.org/llms.txt (10 KiB, 64 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 98 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
6 small tap targets
6 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 5 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 486 words of copy
The homepage carries about 486 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
15 calls to action
The homepage has 15 calls to action, for example “Register Your Account Online”, “Contact Us” and “Donation Request”.
1 short form
A short form (2 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and 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
2Opening the homepage sets 2 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.
8 other companies contacted
Loading the homepage contacts 8 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 communityfirstfl.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Sucuri
Company
- Employees
- 442
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on communityfirstfl.org, including 17 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.