Website review, no card needed

cloverhealth.com logo

cloverhealth.com website review

Visit site (opens in a new tab)Reviewed 31 October 202638 issues · 88 checks

This review found 38 issues worth fixing on cloverhealth.com, 6 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
4.2 s1.8 sMay 9Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.8 s
May 16, 20263.7 s
May 23, 20263.6 s
May 30, 20263.6 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.5 s
Jun 27, 20263.5 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.5 s
Jul 25, 20263.6 s
Aug 1, 20263.8 s
Aug 8, 20263.9 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.7 s
Sep 5, 20263.7 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.7 s
Oct 3, 20263.5 s
Oct 10, 20263.1 s
Oct 17, 20262.6 s
Oct 24, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
158 ms134 msMay 9Oct 24155 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026137 ms
May 16, 2026138 ms
May 23, 2026143 ms
May 30, 2026147 ms
Jun 6, 2026154 ms
Jun 13, 2026155 ms
Jun 20, 2026155 ms
Jun 27, 2026154 ms
Jul 4, 2026152 ms
Jul 11, 2026150 ms
Jul 18, 2026149 ms
Jul 25, 2026149 ms
Aug 1, 2026153 ms
Aug 8, 2026154 ms
Aug 15, 2026154 ms
Aug 22, 2026154 ms
Aug 29, 2026154 ms
Sep 5, 2026154 ms
Sep 12, 2026154 ms
Sep 19, 2026155 ms
Sep 26, 2026153 ms
Oct 3, 2026148 ms
Oct 10, 2026151 ms
Oct 17, 2026154 ms
Oct 24, 2026155 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 cloverhealth.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cloverhealth.com at 0.4 s0.4 s
  2. cloverhealth.com at 0.8 s0.8 s
  3. cloverhealth.com at 1.2 s1.2 s
  4. cloverhealth.com at 1.6 s1.6 s
  5. cloverhealth.com at 2.0 s2.0 s
  6. cloverhealth.com at 2.5 s2.5 s
  7. cloverhealth.com at 2.9 s2.9 s
  8. cloverhealth.com at 3.3 s3.3 s

Speed

10 to fix80
  • Render-blocking requests

    1.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Segment and Crazy Egg and others), adding 1.1 MB and 921 ms of main-thread time.

  • Mobile performance score: 80

    80/100

    Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    601 KiB

    About 601 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    450 ms · 101 KiB

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

  • Google Tag Manager adds 462 ms

    462 ms

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

  • Use efficient cache lifetimes

    453 KiB

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

  • Improve image delivery

    441 KiB

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

  • Main-thread work: 2.2 s

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

  • 1,514 HTML elements

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

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    50 KiB

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

  • Minify JavaScript

    29 KiB

    29 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    13 KiB

    13 KiB JavaScript is shipped twice across bundles.

  • 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: 6 ms

    6 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Time to Interactive: 15.2 s

    15.2 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Total Blocking Time: 524 ms

    524 ms

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

  • Speed Index: 5.4 s

    5.4 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

    The first text or image appears after 2.1 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) got 12% slower for real visitors

    +12%

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

6 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 INP: 160 ms

    160 ms

    Real visitors wait 160 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.

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

    -38%

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

  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Get the Medicare Benefits You Need”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 2.1 MB in 71 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 71 requests on a phone: scripts 1.2 MB (30), images 565 KiB (14) and fonts 197 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    25 KiB

    1 image is downloaded at several times the size a phone draws it, for example cms-5-star-ppo.png at 925 px wide, shown at 225 px. Resized copies would save about 25 KiB.

  • 2 images in older formats

    2 images (105 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.

  • 2 images below the first screen load straight away

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

  • About 0.6 g of CO₂ per visit

    0.60 g

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

Accessibility

5 to fixGoogle 8993
  • Unlabelled dropdowns

    2 dropdowns have no label.

  • Required ARIA attributes must be provided (1 element)

    Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

  • All page content should be contained by landmarks (54 elements)

    All page content should be contained by landmarks: 54 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

  • 38 links without text

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 44 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: 44 passed and 4 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 9287
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “2027 Medicare Advantage Plans | $0 Premium PPO Plans | Clover Health”.

  • No XML sitemap

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

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

  • 169 internal links, 8 external

    The homepage links to 169 pages on cloverhealth.com and 8 external pages.

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Explore Clover Health 2027 Medicare Advantage PPO plans: $0 to low premiums, dental, vision, OTC allowances and up to $…”.

  • One H1 headline

    Your main headline reads: “Get the Medicare Benefits You Need”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: ItemList, Organization, WebPage and WebSite.

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

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.

  • Text is in the HTML

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

Other pages

5 to fix76
  • 2 pages share a title

    https://www.cloverhealth.com/enroll-guide and https://www.cloverhealth.com/members/contact-us all use the title “Contact Us About Our Medicare Plans | Clover Health”. 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.cloverhealth.com/set-language/es, https://www.cloverhealth.com/plans/pharmacy-and-formulary, https://www.cloverhealth.com/understanding-medicare/medicare-tips and https://www.cloverhealth.com/blog/articles/medicare-plan-review-clover-health have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.cloverhealth.com/enroll-guide and https://www.cloverhealth.com/members/contact-us use the same meta description. A description written for each page earns more clicks.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.cloverhealth.com/set-language/es, whose canonical is https://www.cloverhealth.com/es. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.cloverhealth.com/plans/my-doctor-network has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.cloverhealth.com/set-language/es and https://www.cloverhealth.com/understanding-medicare/special-enrollment-periods-faq took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

3 to fixGoogle 10071
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5750661&Ver=2&mid=3ae13f2d-7985-4a5b-8248-2458ba1ac4e4&bo=1&sid=ad5250a0d55611f1bbda837d5e86f968&vid=ad526e10d55611f1aa7dbfb708c15cb2&vids=1&msclkid=N&pi=918639831&lg=.

  • 32 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.cloverhealth.com/filer_cloudrun_public/cms/css/3.11.1/cms.base.css' from origi…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 1,629 words of copy

    The homepage carries about 1,629 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get a Benefit Review” and “Contact Us”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Get a Benefit Review”, “Call Us” and “To Join: 1-800-836-6890 (TTY 711)”.

  • 3 short forms

    3 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks, 4 customer or partner logos, 1 trust badge and “Over 150,000 Members”.

  • Analytics in place

    Analytics detected: Segment.

  • Direct contact links

    Visitors can reach you directly: 24 phone links and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 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.

  • 20 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Segment
Hosting
Google Cloud

Hiring

Hiring
56 open roles
Teams
Clover Home Care (12), Clinical Operations (3), Engineering (3), Finance (3)
Job board
greenhouse

Company

Founded
2014
Headquarters
Franklin

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on cloverhealth.com, including 18 speed issues, 3 SEO issues and 1 conversion gap. 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