Website review, no card needed
wefloridafinancial.com website review
Visit site (opens in a new tab)Reviewed 18 October 202651 issues · 90 checks
This review found 51 issues worth fixing on wefloridafinancial.com, 29 of them high impact, across 90 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 5.6 s |
| May 2, 2026 | 5.4 s |
| May 9, 2026 | 5.4 s |
| May 16, 2026 | 5.4 s |
| May 23, 2026 | 5.3 s |
| May 30, 2026 | 5.5 s |
| Jun 6, 2026 | 5.5 s |
| Jun 13, 2026 | 5.6 s |
| Jun 20, 2026 | 5.7 s |
| Jun 27, 2026 | 5.7 s |
| Jul 4, 2026 | 5.7 s |
| Jul 11, 2026 | 5.7 s |
| Jul 18, 2026 | 5.8 s |
| Jul 25, 2026 | 5.8 s |
| Aug 1, 2026 | 6.0 s |
| Aug 8, 2026 | 6.1 s |
| Aug 15, 2026 | 6.1 s |
| Aug 22, 2026 | 6.2 s |
| Aug 29, 2026 | 6.0 s |
| Sep 5, 2026 | 6.0 s |
| Sep 12, 2026 | 5.9 s |
| Sep 19, 2026 | 5.7 s |
| Sep 26, 2026 | 5.4 s |
| Oct 3, 2026 | 5.0 s |
| Oct 10, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 159 ms |
| May 2, 2026 | 161 ms |
| May 9, 2026 | 166 ms |
| May 16, 2026 | 161 ms |
| May 23, 2026 | 147 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 125 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 122 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 122 ms |
| Aug 1, 2026 | 122 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 124 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 125 ms |
| Sep 12, 2026 | 124 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 144 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 187 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.7 s
1.3 s
2.0 s
2.6 s
3.3 s
3.9 s
4.6 s
5.2 s
Speed
Use efficient cache lifetimes
52.7 s · 88.8 MB287 files are served with short cache lifetimes, so returning visitors download them again (88.8 MB).
Improve image delivery
39.4 s · 34.6 MB20 images could be 34.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 39.4 s faster on a phone.
Reduce unused JavaScript
8.1 s · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.1 s faster on a phone.
Render-blocking requests
9.1 s53 files block the first paint until they finish downloading. Deferring or inlining them could save about 9.1 s.
Reduce unused CSS
4.8 s · 1,003 KiBAbout 1,003 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Google Tag Manager adds 2.3 s
2.3 sGoogle Tag Manager costs a phone 2.3 s of main-thread work and 2.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Font display
2.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.0 s).
Mobile performance score: 20
20/100Your mobile performance score is 20 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.2 s
A phone's processor spends 6.2 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,122 HTML elements
The page has 3,122 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, Facebook and salemove.com and others), adding 4.1 MB and 3.3 s of main-thread time.
Facebook adds 562 ms
562 msFacebook costs a phone 562 ms of main-thread work and 684 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.
salemove.com adds 288 ms
288 mssalemove.com costs a phone 288 ms of main-thread work and 774 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 347 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 33 KiB33 KiB could be saved by minifying CSS.
Legacy JavaScript
60 KiBPolyfills for old browsers add 60 KiB JavaScript that modern phones do not need.
Minify JavaScript
24 KiB24 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 23 ms
23 msYour server sent the HTML in 23 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 LCP: 4.7 s
4.7 sReal visitors wait 4.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.2 s
2.2 sReal visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 9.5 s
9.5 sThe first text or image appears after 9.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 151.1 s
151.1 sYour largest element takes 151.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 32.1 s
32.1 sVisually, the page fills in at 32.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 240.8 s
240.8 sThe page becomes fully interactive after 240.8 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.325
0.325The layout shifts by 0.325 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 793 ms
793 msScripts block taps and scrolling for 793 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 225 ms
225 msReal visitors wait 225 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 159 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 5.6 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 92.7 MB in 463 requests
92.7 MBYour homepage downloads 92.7 MB in 463 requests on a phone: images 75.7 MB (85), media 7.3 MB (2) and scripts 5.2 MB (155). Under 2 MB keeps phones on slow connections fast.
9 images over 500 KB
9 images weigh 25.5 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
12.9 MB6 images are downloaded at several times the size a phone draws them, for example pexels-matt-weissinger-11139552.jpg at 6,720 px wide, shown at 340 px. Resized copies would save about 12.9 MB.
9 images in older formats
9 images (25.5 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.
7 images below the first screen load straight away
7 images further down the page (14.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 26.3 g of CO₂ per visit
26.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 26.27 g of CO₂e: 3152.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
69 text elements with low contrast
69 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
21 tap targets too small
21 tap targets are too small or too close together to hit reliably with a finger.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (41 elements)
All page content should be contained by landmarks: 41 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails 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.
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.
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5, h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 126 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 13 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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 XML sitemap
No XML sitemap at https://wefloridafinancial.com/site-map, so Google discovers your pages only by following links.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
158 internal links, 123 external
The homepage links to 158 pages on wefloridafinancial.com and 123 external pages.
5 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Bank with We Florida Financial Credit Union in South FL and enjoy great accounts and loans. Explore mortgages, savings …”.
Title: 63 characters
Your title is a healthy 63 characters: “We Florida Financial | South FL Credit Union | Banking Accounts”.
Canonical URL set
The canonical URL is https://wefloridafinancial.com/.
Structured data in place
Structured data found: Article, BankOrCreditUnion and Organization.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No llms.txt
There is no https://wefloridafinancial.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.
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,760 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 85 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
11 small tap targets
11 of 51 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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.
About 558 words of copy
The homepage carries about 558 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT”.
56 calls to action
The homepage has 56 calls to action, for example “Learn More - FAQs”, “Schedule Appointment” and “Contact”.
3 short forms
3 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
22 other companies contacted
Loading the homepage contacts 22 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 wefloridafinancial.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
- Joomla
- Framework
- jQuery
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on wefloridafinancial.com, including 26 speed issues, 4 SEO issues and 1 conversion gap. 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.