Website review, no card needed
connexuscu.org website review
Visit site (opens in a new tab)Reviewed 29 October 202644 issues · 86 checks
This review found 44 issues worth fixing on connexuscu.org, 17 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 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.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 153 ms |
| May 16, 2026 | 154 ms |
| May 23, 2026 | 153 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 158 ms |
| Jun 20, 2026 | 159 ms |
| Jun 27, 2026 | 159 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 150 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 145 ms |
| Aug 1, 2026 | 149 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 164 ms |
| Aug 22, 2026 | 173 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 183 ms |
| Sep 12, 2026 | 185 ms |
| Sep 19, 2026 | 185 ms |
| Sep 26, 2026 | 184 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 172 ms |
| Oct 17, 2026 | 169 ms |
| Oct 24, 2026 | 161 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.8 s
2.2 s
2.6 s
3.1 s
3.5 s
Speed
Render-blocking requests
3.6 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Google Tag Manager adds 1.4 s
1.4 sGoogle Tag Manager costs a phone 1.4 s of main-thread work and 671 KiB 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.
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.7 s
A phone's processor spends 9.7 s on main-thread work while loading, 5.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1.3 MB and 2.7 s of main-thread time.
Reduce unused JavaScript
450 ms · 568 KiBAbout 568 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
750 ms · 139 KiBAbout 139 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 777 ms. During a long task the page ignores taps.
Improve image delivery
539 KiB3 images could be 539 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
389 KiB17 files are served with short cache lifetimes, so returning visitors download them again (389 KiB).
Facebook adds 304 ms
304 msFacebook costs a phone 304 ms of main-thread work and 210 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.
TikTok adds 309 ms
309 msTikTok costs a phone 309 ms of main-thread work and 156 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.
Legacy JavaScript
150 ms · 66 KiBPolyfills for old browsers add 66 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Total Blocking Time: 4.0 s
4.0 sScripts block taps and scrolling for 4.0 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 21.1 s
21.1 sThe page becomes fully interactive after 21.1 s. Good is under 3.8 s.
Largest Contentful Paint: 8.4 s
8.4 sYour largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Earn up to $3007 with Xtraordinary Checking.”.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
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.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 153 ms to 161 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-10-24, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 171 ms
171 msReal visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 532 ms
532 msReal visitors wait 532 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 14.6 MB in 135 requests
14.6 MBYour homepage downloads 14.6 MB in 135 requests on a phone: media 11.0 MB (1), scripts 1.7 MB (42) and images 1.0 MB (33). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
97 KiB1 image is downloaded at several times the size a phone draws it, for example bottom-right-Neighbors-Place-VTO-4-25DSC03075.png at 933 px wide, shown at 168 px. Resized copies would save about 97 KiB.
1 image below the first screen load straight away
1 image further down the page (137 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 4.1 g of CO₂ per visit
4.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.15 g of CO₂e: 497.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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 (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Home – High Yields, Low Rates, Online Services - Connexus Credit Union”.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
133 internal links, 4 external
The homepage links to 133 pages on connexuscu.org and 4 external pages.
6 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “Connexus Credit Union helps members reach their financial goals with higher yields, lower rates and innovative online s…”.
Canonical URL set
The canonical URL is https://www.connexuscu.org/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.connexuscu.org/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), 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.connexuscu.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
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 (553 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.connexuscu.org/mdr declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.connexuscu.org/mdr all use the title “Home – High Yields, Low Rates, Online Services - Connexus Credit Union”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.connexuscu.org/loans/heloc has 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 40 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
8 broken images
8 images failed to load on a phone, for example https://www.connexuscu.org/wp-content/uploads/search_icon_dark.svg.
8 small tap targets
8 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
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
Thin social proof
Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 284 words of copy
The homepage carries about 284 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us” and “Learn more”.
13 calls to action
The homepage has 13 calls to action, for example “Iconly/Bold/Message Contact Us”, “Apply for Loan” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 connexuscu.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
- Next.js
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on connexuscu.org, including 19 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.