Website review, no card needed

kidney.org logo

kidney.org website review

Visit site (opens in a new tab)Reviewed 26 October 202650 issues · 94 checks

This review found 50 issues worth fixing on kidney.org, 21 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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
3.7 s2.4 sMay 9Oct 243.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.8 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.7 s
Aug 1, 20262.8 s
Aug 8, 20262.9 s
Aug 15, 20263.0 s
Aug 22, 20263.1 s
Aug 29, 20263.3 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Oct 24, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
427 ms312 msMay 9Oct 24400 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026337 ms
May 16, 2026338 ms
May 23, 2026335 ms
May 30, 2026331 ms
Jun 6, 2026329 ms
Jun 13, 2026326 ms
Jun 20, 2026325 ms
Jun 27, 2026325 ms
Jul 4, 2026325 ms
Jul 11, 2026325 ms
Jul 18, 2026328 ms
Jul 25, 2026342 ms
Aug 1, 2026350 ms
Aug 8, 2026355 ms
Aug 15, 2026363 ms
Aug 22, 2026376 ms
Aug 29, 2026393 ms
Sep 5, 2026408 ms
Sep 12, 2026414 ms
Sep 19, 2026408 ms
Sep 26, 2026404 ms
Oct 3, 2026398 ms
Oct 10, 2026395 ms
Oct 17, 2026397 ms
Oct 24, 2026400 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 kidney.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix27
  • Reduce unused JavaScript

    2.5 s · 1.1 MB

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

  • Render-blocking requests

    3.4 s

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

  • Use efficient cache lifetimes

    1.1 s · 412 KiB

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

  • Google Tag Manager adds 1.3 s

    1.3 s

    Google Tag Manager costs a phone 1.3 s of main-thread work and 1.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 27

    27/100

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

  • Main-thread work: 5.6 s

    A phone's processor spends 5.6 s on main-thread work while loading, 3.1 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, YouTube and reddit and others), adding 2.5 MB and 2.6 s of main-thread time.

  • Reduce unused CSS

    600 ms · 190 KiB

    About 190 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.

  • YouTube adds 597 ms

    597 ms

    YouTube costs a phone 597 ms of main-thread work and 981 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 362 ms. During a long task the page ignores taps.

  • 2,850 HTML elements

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

  • Improve image delivery

    123 KiB

    4 images could be 123 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    50 ms · 24 KiB

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

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 67 but mobile only 27. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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

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

  • Largest Contentful Paint: 11.9 s

    11.9 s

    Your largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “person offering support to another person through the phone…”.

  • Time to Interactive: 24.0 s

    24.0 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user INP: 358 ms

    358 ms

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

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

    +22%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Cumulative Layout Shift: 0.186

    0.186

    The layout shifts by 0.186 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 7 images without width and height

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

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

3 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • 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 TTFB: 651 ms

    651 ms

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

Images and page weight

2 to fix69
  • Page weight: 4.4 MB in 156 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 156 requests on a phone: scripts 2.6 MB (40), other files 1,012 KiB (45) and fonts 279 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    peers_hero_desktop_v5.jpg 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).

  • 2 images below the first screen load straight away

    2 images further down the page (79 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.24 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 7286
  • 15 buttons without a name

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

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • 3 images without alt text

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

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

  • 11 form fields without a label

    11 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (7 elements)

    Headings should not be empty: 7 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

4 to fixGoogle 8582
  • Title is short (26 characters)

    Your title is only 26 characters: “National Kidney Foundation”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is long (187 characters)

    Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.

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

  • 202 internal links, 34 external

    The homepage links to 202 pages on kidney.org and 34 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Coping with kidney disease or transplant?”.

  • Canonical URL set

    The canonical URL is https://www.kidney.org/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.kidney.org/sitemap.xml.

AI search readiness

1 to fix88
  • 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.kidney.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.

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,979 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    https://www.kidney.org/news-stories and https://www.kidney.org/news-listing all use the title “News and Stories | National Kidney Foundation”. 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.kidney.org/kidney-topics, https://www.kidney.org/node/45456, https://www.kidney.org/news-stories and https://www.kidney.org/news-listing have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.kidney.org/es/fundacion-nacional-rinon, whose canonical is https://www.kidney.org/es. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 147 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.

  • 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

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97071843&tm=gtm002&Ver=2&mid=973b73b2-4f4f-4def-89eb-1148758643dd&bo=1&sid=0245c880d0f411f1968ce1d4125d5322&vid=0245ff30d0f411f1bba709951e80b01a&vids=1&msclkid=N&gtm_t.

  • 33 small tap targets

    33 of 68 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    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.

  • A 15-field form

    Your longest form asks for 15 fields (5 required). Every extra field lowers completion.

  • 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 opening hours

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

  • No map or directions link

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

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

  • About 690 words of copy

    The homepage carries about 690 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Learn More”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Apply”, “Learn more about KDOQI” and “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 4 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 1 of them by other companies (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.

  • 38 other companies contacted

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

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

Upkeep, stack and company

Stack

CMS
Drupal
Framework
Tailwind CSS
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on kidney.org, including 22 speed issues, 4 SEO issues and 3 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