Programmable

Website review, no card needed

mypatientchart.org logo

mypatientchart.org website review

Visit site (opens in a new tab)Reviewed 12 October 202621 issues · 61 checks

This review found 21 issues worth fixing on mypatientchart.org, 5 of them high impact, across 61 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.7 s2.1 sApr 18Oct 32.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.6 s
Apr 25, 20262.6 s
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
101 ms95 msApr 18Oct 399 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202697 ms
Apr 25, 202696 ms
May 2, 202696 ms
May 9, 202696 ms
May 16, 202696 ms
May 23, 202696 ms
May 30, 202696 ms
Jun 6, 202696 ms
Jun 13, 202696 ms
Jun 20, 202697 ms
Jun 27, 202697 ms
Jul 4, 202698 ms
Jul 11, 202698 ms
Jul 18, 202698 ms
Jul 25, 202697 ms
Aug 1, 202697 ms
Aug 8, 202697 ms
Aug 15, 202697 ms
Aug 22, 202698 ms
Aug 29, 202698 ms
Sep 5, 2026100 ms
Sep 12, 202699 ms
Sep 19, 202699 ms
Sep 26, 202699 ms
Oct 3, 202699 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

www.mypatientchart.org (opens in a new tab)
Full-page screenshot of mypatientchart.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

2 checks passed

  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 431 ms of it running JavaScript. That is comfortably low.

  • Server response: 64 ms

    64 ms

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

Core Web Vitals

6 to fix67

  • 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 LCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 840 ms

    840 ms

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

  • Speed Index: 5.6 s

    5.6 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

5 checks passed

  • Real-user INP: 109 ms

    109 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85

  • Page weight: 2.2 MB in 47 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 47 requests on a phone: scripts 1.1 MB (18), images 493 KiB (8) and other files 323 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (114 KiB) is 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.

  • About 0.6 g of CO₂ per visit

    0.63 g

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

2 checks passed

  • 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

2 to fixGoogle 10096

  • 2 images without alt text

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

  • Page should contain a level-one heading (1 element)

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

1 checks passed

  • 40 automated accessibility rules passed

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

SEO

3 to fixGoogle 9282

  • No H1 headline

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

  • No XML sitemap

    No XML sitemap at https://www.mypatientchart.org/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at mypatientchart.org/robots.txt, the first file search crawlers ask for.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 7 internal links, 0 external

    The homepage links to 7 pages on mypatientchart.org and 0 external pages.

4 checks passed

  • Meta description: 151 characters

    Your meta description is 151 characters: “BJC HealthCare and Washington University Physicians MyChart offers patients personalized and secure online access to po…”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “MyChart - Login Page - BJC & WashU”.

  • Canonical URL set

    The canonical URL is https://www.mypatientchart.org/MyChart/Authentication/Login.

  • Structured data in place

    Structured data found: WebSite.

AI search readiness

1 to fix83

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

  • No llms.txt

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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

3 to fix83

  • 2 pages share a title

    https://www.mypatientchart.org/MyChart/app/account-recovery/recovery-choice and https://www.mypatientchart.org/MyChart/accesscheck.asp all use the title “MyChart”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.mypatientchart.org/MyChart/Help/Cookies, https://www.mypatientchart.org/MyChart/app/account-recovery/recovery-choice, https://www.mypatientchart.org/MyChart/accesscheck.asp and https://www.mypatientchart.org/MyChart/billing/guestpay/payasguest have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.mypatientchart.org/MyChart/app/account-recovery/recovery-choice and https://www.mypatientchart.org/MyChart/accesscheck.asp have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.mypatientchart.org/MyChart/app/account-recovery/recovery-choice and https://www.mypatientchart.org/MyChart/accesscheck.asp have 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.

  • 5 internal pages checked

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

4 checks passed

  • Linked pages load

    All 5 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 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10084

  • 1 broken image

    1 image failed to load on a phone, for example https://www.mypatientchart.org/MyChart/Authentication/Login?.

  • 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64

  • No social proof

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

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

  • Only about 42 words

    The homepage has only about 42 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign up now”.

  • 1 call to action

    The homepage has 1 call to action, for example “Sign up now”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage.

Privacy and tracking

  • 5 cookies set on arrival

    5

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

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 mypatientchart.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on mypatientchart.org, including 6 speed issues, 3 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