Website review, no card needed

personalcapital.com logo

personalcapital.com website review

Visit site (opens in a new tab)Reviewed 31 October 202643 issues · 84 checks

This review found 43 issues worth fixing on personalcapital.com, 16 of them high impact, across 84 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
788 ms573 msMay 9Oct 24751 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026632 ms
May 16, 2026623 ms
May 23, 2026614 ms
May 30, 2026614 ms
Jun 6, 2026619 ms
Jun 13, 2026633 ms
Jun 20, 2026639 ms
Jun 27, 2026638 ms
Jul 4, 2026628 ms
Jul 11, 2026613 ms
Jul 18, 2026599 ms
Jul 25, 2026598 ms
Aug 1, 2026607 ms
Aug 8, 2026621 ms
Aug 15, 2026641 ms
Aug 22, 2026657 ms
Aug 29, 2026662 ms
Sep 5, 2026657 ms
Sep 12, 2026647 ms
Sep 19, 2026670 ms
Sep 26, 2026690 ms
Oct 3, 2026716 ms
Oct 10, 2026757 ms
Oct 17, 2026763 ms
Oct 24, 2026751 ms
Real-visitor tap response (INP)75th percentile, phones
53 ms50 msMay 9Oct 2453 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202650 ms
May 16, 202651 ms
May 23, 202651 ms
May 30, 202652 ms
Jun 6, 202652 ms
Jun 13, 202652 ms
Jun 20, 202652 ms
Jun 27, 202652 ms
Jul 4, 202652 ms
Jul 11, 202652 ms
Jul 18, 202652 ms
Jul 25, 202652 ms
Aug 1, 202651 ms
Aug 8, 202652 ms
Aug 15, 202653 ms
Aug 22, 202653 ms
Aug 29, 202653 ms
Sep 5, 202652 ms
Sep 12, 202652 ms
Sep 19, 202652 ms
Sep 26, 202652 ms
Oct 3, 202653 ms
Oct 10, 202653 ms
Oct 17, 202653 ms
Oct 24, 202653 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

Full-page screenshot of personalcapital.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. personalcapital.com at 0.4 s0.4 s
  2. personalcapital.com at 0.8 s0.8 s
  3. personalcapital.com at 1.1 s1.1 s
  4. personalcapital.com at 1.5 s1.5 s
  5. personalcapital.com at 1.9 s1.9 s
  6. personalcapital.com at 2.3 s2.3 s
  7. personalcapital.com at 2.6 s2.6 s
  8. personalcapital.com at 3.0 s3.0 s

Speed

13 to fix33
  • Improve image delivery

    6.5 s · 5.3 MB

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

  • Use efficient cache lifetimes

    5.8 s · 1.8 MB

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

  • Reduce unused JavaScript

    2.9 s · 990 KiB

    About 990 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 33

    33/100

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

  • Main-thread work: 4.8 s

    A phone's processor spends 4.8 s on main-thread work while loading, 2.6 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, Optanon and FontAwesome CDN and others), adding 2.5 MB and 1.9 s of main-thread time.

  • Avoid multiple page redirects

    902 ms

    The page goes through 1 redirect before it starts loading, costing about 902 ms. Link and advertise the final URL directly.

  • Google Tag Manager adds 788 ms

    788 ms

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

  • Optanon adds 447 ms

    447 ms

    Optanon costs a phone 447 ms of main-thread work and 339 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

    300 ms · 42 KiB

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

  • Amplitude Mobile Analytics adds 159 ms

    159 ms

    Amplitude Mobile Analytics costs a phone 159 ms of main-thread work and 621 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.

  • FontAwesome CDN adds 169 ms

    169 ms

    FontAwesome CDN costs a phone 169 ms of main-thread work and 490 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.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 63 KiB

    Polyfills for old browsers add 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 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.

1 checks passed
  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 62.6 s

    62.6 s

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

  • Time to Interactive: 64.2 s

    64.2 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Speed Index: 9.4 s

    9.4 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Largest content (LCP) got 21% slower for real visitors

    +21%

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

7 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: 2.0 s

    2.0 s

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

  • Real-user INP: 120 ms

    120 ms

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

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 656 ms

    656 ms

    Real visitors wait 656 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.038

    0.038

    The layout barely moves while loading (CLS 0.038, good is under 0.1).

Images and page weight

6 to fix29
  • Page weight: 17.6 MB in 196 requests

    17.6 MB

    Your homepage downloads 17.6 MB in 196 requests on a phone: images 10.1 MB (58), other files 4.4 MB (61) and scripts 2.8 MB (61). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

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

  • 32 images in older formats

    32 images (8.3 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.

  • 7 images below the first screen load straight away

    7 images further down the page (2.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    ira sideby.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    357 KiB

    1 image is downloaded at several times the size a phone draws it, for example ira sideby.png at 1,248 px wide, shown at 342 px. Resized copies would save about 357 KiB.

  • About 5.0 g of CO₂ per visit

    4.98 g

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

Accessibility

2 to fixGoogle 10098
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 6165
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Personal Finance Tools, Wealth Management, Guides | Personal Capital”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 3 links with vague text

    3 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.

  • 39 internal links, 3 external

    The homepage links to 39 pages on personalcapital.com and 3 external pages.

5 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Take control of your finances with Personal Capital's personal finance tools. Get access to wealth management services …”.

  • Canonical URL set

    The canonical URL is https://www.personalcapital.com/.

  • 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.personalcapital.com/sitemap.xml.

AI search readiness

2 to fix75
  • No Organization structured data

    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.

  • Some text only appears after JavaScript runs

    55%

    The HTML your server sends has 451 of the 813 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

1 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.

Other pages

4 to fix81
  • 2 pages share a title

    https://www.personalcapital.com/see-how-it-works and https://www.personalcapital.com/financial-software/fee-analyzer all use the title “Empower | Invest well. Live a little.™”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.personalcapital.com/wealth-management/private-client, https://www.personalcapital.com/wealth-management/personal-strategy and https://www.personalcapital.com/financial-software/retirement-planner have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.personalcapital.com/see-how-it-works and https://www.personalcapital.com/financial-software/fee-analyzer use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.personalcapital.com/calculators has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 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.

  • 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

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    13 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • No call to action on the first screen

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

  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • About 813 words of copy

    The homepage carries about 813 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Get Started” and “Contact Us”.

  • 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

  • 4 trackers load before any consent

    4

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

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 10 of them by other companies (measured from a US location before any click).

  • 16 other companies contacted

    Loading the homepage contacts 16 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 personalcapital.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Cloudflare

Company

Founded
2009
Headquarters
San Carlos

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on personalcapital.com, including 20 speed issues, 5 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25