ritholtzwealth.com website review

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

71 files are served with short cache lifetimes, so returning visitors download them again (11.1 MB).

11 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 943 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 290 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Clarity and vidvisor.io and others), adding 6.3 MB and 589 ms of main-thread time.

Your mobile performance score is 84 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

vidvisor.io costs a phone 97 ms of main-thread work and 4.6 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 costs a phone 362 ms of main-thread work and 648 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.

YouTube costs a phone 0 ms of main-thread work and 922 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.

About 24 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

9 long tasks block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.

The page becomes fully interactive after 18.2 s. Good is under 3.8 s.

Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

Visually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “On the cutting edge of wealth management, there are no limi…”. Most of its time is element render delay (1.6 s).

4 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 79 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 17.0 MB in 110 requests on a phone: media 9.1 MB (2), images 5.7 MB (49) and scripts 1.7 MB (22). Under 2 MB keeps phones on slow connections fast.

3 images (123 KiB) 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.

By the Sustainable Web Design model, a visit to your homepage emits about 4.83 g of CO₂e: 579.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 buttons have no accessible name, so screen readers announce just “button”.

3 images have no alt text, which hurts accessibility and image search.

10 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is only 15 characters: “Ritholtz | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“We Focus On What Works.”, “YourLegacy,Elevated” and “Everything You Need.The Way you want to get it.”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 27 pages on ritholtzwealth.com and 49 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.ritholtzwealth.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.

https://www.ritholtzwealth.com/about-us and https://www.ritholtzwealth.com/about all use the title “About Us | Ritholtz Wealth Management”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ritholtzwealth.com/about-us and https://www.ritholtzwealth.com/about use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.ritholtzwealth.com/about, whose canonical is https://www.ritholtzwealth.com/about-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.ritholtzwealth.com/services and https://www.ritholtzwealth.com/disclosures have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ritholtzwealth.com/about-us and https://www.ritholtzwealth.com/contact took over 3 s to send their HTML from our server.

We fetched 7 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 760 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.

Opening the homepage sets 2 cookies (measured from a US location before any click).

Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.