Website review, no card needed
growfinancial.org website review
Visit site (opens in a new tab)Reviewed 18 November 202640 issues · 89 checks
This review found 40 issues worth fixing on growfinancial.org, 15 of them high impact, across 89 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.7 s |
| Nov 14, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 169 ms |
| Jun 13, 2026 | 166 ms |
| Jun 20, 2026 | 163 ms |
| Jun 27, 2026 | 160 ms |
| Jul 4, 2026 | 156 ms |
| Jul 11, 2026 | 159 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 162 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 171 ms |
| Aug 15, 2026 | 180 ms |
| Aug 22, 2026 | 189 ms |
| Aug 29, 2026 | 189 ms |
| Sep 5, 2026 | 177 ms |
| Sep 12, 2026 | 166 ms |
| Sep 19, 2026 | 161 ms |
| Sep 26, 2026 | 161 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 168 ms |
| Oct 17, 2026 | 166 ms |
| Oct 24, 2026 | 166 ms |
| Oct 31, 2026 | 170 ms |
| Nov 7, 2026 | 168 ms |
| Nov 14, 2026 | 171 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.6 s
1.1 s
1.7 s
2.3 s
2.8 s
3.4 s
3.9 s
4.5 s
Speed
Improve image delivery
36.4 s · 11.0 MB14 images could be 11.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 36.4 s faster on a phone.
Reduce unused JavaScript
3.0 s · 586 KiBAbout 586 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Render-blocking requests
2.3 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, salemove.com and Facebook and others), adding 1.2 MB and 1.4 s of main-thread time.
Use efficient cache lifetimes
900 ms · 186 KiB15 files are served with short cache lifetimes, so returning visitors download them again (186 KiB).
Google Tag Manager adds 686 ms
686 msGoogle Tag Manager costs a phone 686 ms of main-thread work and 522 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
600 ms · 132 KiBAbout 132 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
salemove.com adds 355 ms
355 mssalemove.com costs a phone 355 ms of main-thread work and 437 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: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
300 ms · 55 KiB55 KiB could be saved by minifying JavaScript.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 334 ms. During a long task the page ignores taps.
Legacy JavaScript
200 ms · 47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Minify CSS
150 ms · 21 KiB21 KiB could be saved by minifying CSS.
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: 3 ms
3 msYour server sent the HTML in 3 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: 65.8 s
65.8 sYour largest element takes 65.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 20.4 s
20.4 sVisually, the page fills in at 20.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 66.9 s
66.9 sThe page becomes fully interactive after 66.9 s. Good is under 3.8 s.
Total Blocking Time: 980 ms
980 msScripts block taps and scrolling for 980 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 281 ms
281 msReal visitors wait 281 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.163
0.163The layout shifts by 0.163 while loading, so content jumps under the reader's thumb. Good is under 0.1.
27 images without width and height
27 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 162 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 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.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 531 ms
531 msReal visitors wait 531 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 13.4 MB in 135 requests
13.4 MBYour homepage downloads 13.4 MB in 135 requests on a phone: images 11.2 MB (39), scripts 1.4 MB (38) and fonts 646 KiB (9). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
GRO-082-009A_HeroUpdate_02MAY25-1.jpg weighs 7.3 MB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
7.5 MB2 images are downloaded at several times the size a phone draws them, for example GRO-082-009A_HeroUpdate_02MAY25-1.jpg at 9,438 px wide, shown at 390 px. Resized copies would save about 7.5 MB.
3 images in older formats
3 images (8.2 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.
An image on the first screen is lazy-loaded
GRO-082-009A_HeroUpdate_02MAY25-1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
5 images below the first screen load straight away
5 images further down the page (123 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.8 g of CO₂ per visit
3.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.81 g of CO₂e: 457.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.
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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 30 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (21 characters)
Your title is only 21 characters: “Home - Grow Financial”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
15 links with vague text
15 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
143 internal links, 25 external
The homepage links to 143 pages on growfinancial.org and 25 external pages.
5 checks passed
One H1 headline
Your main headline reads: “We serve people,not profit.®”.
Canonical URL set
The canonical URL is https://www.growfinancial.org/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, Place and WebPage.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.growfinancial.org/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.growfinancial.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.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,036 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://www.growfinancial.org/personal/get-fit-account, https://www.growfinancial.org/personal/club-account and https://www.growfinancial.org/personal/credit-cards have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 71 found) and read each the way a search engine does.
6 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.
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
1 broken image
1 image failed to load on a phone, for example https://www.growfinancial.org/.
9 small tap targets
9 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Creating a worker from 'blob:https://www.growfinancial.org/ca463917-435d-4adb-9bfd-55fa709a1cea' violates the following…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
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 1,060 words of copy
The homepage carries about 1,060 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”.
15 calls to action
The homepage has 15 calls to action, for example “Contact”, “Contact Information” and “learn more”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Phone number on the homepage
Your phone number is on the homepage.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Xandr (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 4 of them by other companies (measured from a US location before any click).
30 other companies contacted
Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 growfinancial.org, 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
- WP Engine
Hiring
- Hiring
- 5 open roles
- Job board
- icims
Company
- Employees
- 620
- Headquarters
- Tampa
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 growfinancial.org, including 21 speed issues, 4 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.