troweprice.com website review

5 images could be 12.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 61.9 s faster on a phone.

About 6.1 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 30.4 s faster on a phone.

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.9 s faster on a phone.

Your mobile performance score is 39 (desktop: 47). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.5 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 3,142 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Optanon and others), adding 1.4 MB and 1.1 s of main-thread time.

39 files are served with short cache lifetimes, so returning visitors download them again (469 KiB).

9 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

Google Tag Manager costs a phone 648 ms of main-thread work and 620 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.

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

83 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 62 KiB JavaScript that modern phones do not need.

49 KiB could be saved by minifying CSS.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 158.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Scripts block taps and scrolling for 647 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 286 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

5 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-03, real Chrome visitors' tap response (inp) went from 204 ms to 199 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 32.1 MB in 444 requests on a phone: images 19.8 MB (46), stylesheets 6.0 MB (15) and scripts 5.6 MB (246). Under 2 MB keeps phones on slow connections fast.

4 images weigh 18.6 MB together. On a phone connection a single image that size takes seconds.

7 images (19.6 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.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

13 tap targets are too small or too close together to hit reliably with a finger.

Headings skip levels (h2 → h4, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

There are 2 <h1> headlines (“Discover your signals from the noise with our act…” and “Discover AI-fueled insights and client-first solu…”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 103 pages on troweprice.com and 9 external pages.

There is no https://www.troweprice.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.troweprice.com/en/us, https://www.troweprice.com/en/institutional, https://www.troweprice.com/en/za, https://www.troweprice.com/en/ca, https://www.troweprice.com/en/hk and https://www.troweprice.com/en/jp and 4 others all use the title “Invest with Confidence | T. Rowe Price”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.troweprice.com/en/us/retirement-plan-services/public/home and https://www.troweprice.com/zh-cn/cn have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.troweprice.com/en/institutional, https://www.troweprice.com/en/ae, https://www.troweprice.com/en/za, https://www.troweprice.com/en/ca, https://www.troweprice.com/en/au and https://www.troweprice.com/en/hk and 5 others 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.troweprice.com/en/institutional, whose canonical is https://www.troweprice.com/en/us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.troweprice.com/zh-cn/cn has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 83 found) and read each the way a search engine does.

4 images failed to load on a phone, for example https://www.troweprice.com/en/us.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 form on the homepage, so every lead has to click through to another page first.

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 1,148 words of visible text.

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

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