Website review, no card needed
rho.co website review
Visit site (opens in a new tab)Reviewed 29 October 202629 issues · 82 checks
This review found 29 issues worth fixing on rho.co, 13 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Rho
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
64DClosest competitors among SaaS 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.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 203 ms |
| May 16, 2026 | 212 ms |
| May 23, 2026 | 210 ms |
| May 30, 2026 | 217 ms |
| Jun 6, 2026 | 219 ms |
| Jun 13, 2026 | 254 ms |
| Jun 20, 2026 | 308 ms |
| Jun 27, 2026 | 321 ms |
| Jul 4, 2026 | 371 ms |
| Jul 11, 2026 | 371 ms |
| Jul 18, 2026 | 355 ms |
| Jul 25, 2026 | 357 ms |
| Aug 1, 2026 | 338 ms |
| Aug 8, 2026 | 320 ms |
| Aug 15, 2026 | 309 ms |
| Aug 22, 2026 | 290 ms |
| Aug 29, 2026 | 258 ms |
| Sep 5, 2026 | 262 ms |
| Sep 12, 2026 | 260 ms |
| Sep 19, 2026 | 252 ms |
| Sep 26, 2026 | 232 ms |
| Oct 3, 2026 | 214 ms |
| Oct 10, 2026 | 194 ms |
| Oct 17, 2026 | 200 ms |
| Oct 24, 2026 | 205 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
Speed
Reduce unused JavaScript
4.8 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 653 KiB39 files are served with short cache lifetimes, so returning visitors download them again (653 KiB).
Mobile performance score: 8
8/100Your mobile performance score is 8. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.3 s
A phone's processor spends 9.3 s on main-thread work while loading, 4.2 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, trygravity.ai and Hubspot and others), adding 2.2 MB and 1.8 s of main-thread time.
Google Tag Manager adds 783 ms
783 msGoogle Tag Manager costs a phone 783 ms of main-thread work and 686 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 · 150 KiBAbout 150 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 491 ms. During a long task the page ignores taps.
Render-blocking requests
400 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 400 ms.
Minify JavaScript
300 ms · 39 KiB39 KiB could be saved by minifying JavaScript.
trygravity.ai adds 279 ms
279 mstrygravity.ai costs a phone 279 ms of main-thread work and 26 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.
spara.co adds 126 ms
126 msspara.co costs a phone 126 ms of main-thread work and 935 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
200 ms · 72 KiBPolyfills for old browsers add 72 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Improve image delivery
89 KiB3 images could be 89 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 22 ms
22 msYour server sent the HTML in 22 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 CLS: 0.50
0.50For real visitors the layout shifts by 0.50 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 17.4 s
17.4 sYour largest element takes 17.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Everything your business does with money, in one place, plu…”.
Time to Interactive: 31.2 s
31.2 sThe page becomes fully interactive after 31.2 s. Good is under 3.8 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.47
0.47The layout shifts by 0.47 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 228 ms
228 msReal visitors wait 228 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 73% slower for real visitors
+73%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 images without width and height
2 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-10-24, real Chrome visitors' tap response (inp) went from 203 ms to 205 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 725 ms
725 msReal visitors wait 725 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 16.7 MB in 293 requests
16.7 MBYour homepage downloads 16.7 MB in 293 requests on a phone: media 12.2 MB (3), scripts 3.7 MB (180) and fonts 359 KiB (8). Under 2 MB keeps phones on slow connections fast.
About 4.7 g of CO₂ per visit
4.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.74 g of CO₂e: 569.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.
49 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: 49 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Business Banking and Corporate Cards for Startups and Scale-Ups | Rho”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
76 internal links, 17 external
The homepage links to 76 pages on rho.co and 17 external pages.
7 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Business banking that moves at startup speed and scales as you grow. Open accounts quickly, earn yield on idle cash, an…”.
One H1 headline
Your main headline reads: “Business banking for the AI era”.
Canonical URL set
The canonical URL is https://www.rho.co/.
Structured data in place
Structured data found: FinancialService 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.rho.co/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,865 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.rho.co/llms.txt (24 KiB, 120 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 40 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
13 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
About 1,566 words of copy
The homepage carries about 1,566 words of visible text.
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Request Demo” and “AI Demo”.
7 calls to action
The homepage has 7 calls to action, for example “Pricing”, “Request Demo” and “AI Demo”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 51 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, HubSpot and PostHog.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
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.
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
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 5 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
24 cookies set on arrival
24Opening the homepage sets 24 cookies (measured from a US location before any click).
49 other companies contacted
Loading the homepage contacts 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 rho.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager | PostHog
- Hosting
- Vercel
Hiring
- Hiring
- 43 open roles
- Teams
- GTM (19), Central (People, Finance, Legal) (12), Product (6), Engineering (5)
- Job board
- ashby
- Careers page
- www.rho.co/careers (opens in a new tab)
Company
- Employees
- 59
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on rho.co, including 24 speed issues and 2 SEO issues. 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.