Website review, no card needed
roguecu.org website review
Visit site (opens in a new tab)Reviewed 2 November 202636 issues · 93 checks
This review found 36 issues worth fixing on roguecu.org, 14 of them high impact, across 93 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 1.8 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.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 112 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 140 ms |
| Jun 27, 2026 | 139 ms |
| Jul 4, 2026 | 135 ms |
| Jul 11, 2026 | 136 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 140 ms |
| Aug 1, 2026 | 152 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 133 ms |
| Aug 22, 2026 | 118 ms |
| Aug 29, 2026 | 101 ms |
| Sep 5, 2026 | 95 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 97 ms |
| Oct 3, 2026 | 98 ms |
| Oct 10, 2026 | 98 ms |
| Oct 17, 2026 | 98 ms |
| Oct 24, 2026 | 99 ms |
| Oct 31, 2026 | 97 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
Use efficient cache lifetimes
9.7 s · 2.2 MB86 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Reduce unused JavaScript
8.7 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.7 s faster on a phone.
Render-blocking requests
1.3 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 45
45/100Your mobile performance score is 45. 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 (talkdeskapp.com, Google Tag Manager and onelink-edge.com and others), adding 3.4 MB and 1.2 s of main-thread time.
Improve image delivery
900 ms · 374 KiB10 images could be 374 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Legacy JavaScript
550 ms · 73 KiBPolyfills for old browsers add 73 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.
talkdeskapp.com adds 314 ms
314 mstalkdeskapp.com costs a phone 314 ms of main-thread work and 2.0 MB 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 Tag Manager adds 284 ms
284 msGoogle Tag Manager costs a phone 284 ms of main-thread work and 379 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.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,104 HTML elements
The page has 2,104 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Maps adds 104 ms
104 msGoogle Maps costs a phone 104 ms of main-thread work and 361 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 174 ms. During a long task the page ignores taps.
Reduce unused CSS
90 ms · 71 KiBAbout 71 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 90 ms faster on a phone.
Minify JavaScript
90 ms · 18 KiB18 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 17 ms
17 msYour server sent the HTML in 17 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: 26.4 s
26.4 sYour largest element takes 26.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Where You Come First. At Rogue Credit Union, you're more th…”.
Time to Interactive: 29.4 s
29.4 sThe page becomes fully interactive after 29.4 s. Good is under 3.8 s.
Speed Index: 11.8 s
11.8 sVisually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.19
0.19For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.
Total Blocking Time: 428 ms
428 msScripts block taps and scrolling for 428 ms in total while the page loads. Good is under 200 ms.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 98 ms
98 msReal visitors wait 98 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 665 ms
665 msReal visitors wait 665 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 112 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.064
0.064The layout barely moves while loading (CLS 0.064, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 161 requests
4.9 MBYour homepage downloads 4.9 MB in 161 requests on a phone: scripts 2.8 MB (49), fonts 1.2 MB (29) and images 673 KiB (45). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
2 KiB2 images are downloaded at several times the size a phone draws them, for example new-mortgage-loans-promo-split-960x640.webp at 960 px wide, shown at 318 px. Resized copies would save about 2 KiB.
3 images below the first screen load straight away
3 images further down the page (198 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 166.3 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
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
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.
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.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (5 elements).
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Member-Owned Credit Union in Oregon, California & Idaho | Rogue Credit Union”.
Structured data has 1 problem
Structured data found (FAQPage, FinancialService, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
2 links with vague text
2 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 set, so this is minor.
214 internal links, 13 external
The homepage links to 214 pages on roguecu.org and 13 external pages.
6 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Rogue Credit Union is a member-owned credit union serving Oregon, Northern California & Western Idaho. Apply for an aut…”.
One H1 headline
Your main headline reads: “Where You Come First.”.
Canonical URL set
The canonical URL is https://www.roguecu.org/.
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.roguecu.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 (1,556 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.roguecu.org/llms.txt (11 KiB, 63 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 76 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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://bat.bing.com/action/0?ti=25023772&Ver=2&mid=aa664654-a228-4691-9e5f-42ab461758a5&bo=1&sid=a5dfd9d0d66311f1a7b0e95a436b159a&vid=a5e02af0d66311f1ae928346fc2c7e67&vids=1&msclkid=N&pi=918639831&lg.
11 small tap targets
11 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “The source list for Content Security Policy directive 'script-src' contains a source with an invalid path: 'https://www.roguecu.org/bat.js?ti=…”.
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
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 1,335 words of copy
The homepage carries about 1,335 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: “JOIN NOW”.
12 calls to action
The homepage has 12 calls to action, for example “Contact”, “Join Now” and “Apply For A Loan”.
Social proof on the page
Social proof on the homepage: 12 testimonial or review blocks and 2 customer or partner logos.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
9 cookies set on arrival
9Opening the homepage sets 9 cookies, 1 of them by other companies (measured from a US location before any click).
25 other companies contacted
Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 roguecu.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
- Tailwind CSS
- Hosting
- Cloudflare
Company
- Employees
- 1,192
- Founded
- 1956
- Headquarters
- Medford
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on roguecu.org, including 20 speed issues, 3 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.