wellthapp.com website review

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

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

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

About 321 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 53 (desktop: 76). Pages that score under 90 lose visitors before the first paint.

7 third-party services load with your homepage (Wistia, Hubspot and Google Tag Manager and others), adding 1.1 MB and 750 ms of main-thread time.

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

Wistia costs a phone 335 ms of main-thread work and 360 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.

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

Hubspot costs a phone 208 ms of main-thread work and 314 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.

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

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

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.

Your largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “glucometer-lifestylev2.jpg”.

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

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

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

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

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

feed-mockup2_-_28de80_-_e474eb9b62e73892c6e6cefa806a28e0041c weighs 488 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example feed-mockup2_-_28de80_-_e474eb9b62e73892c6e6cefa806a28e0041c at 874 px wide, shown at 140 px. Resized copies would save about 818 KiB.

Your homepage downloads 2.6 MB in 74 requests on a phone: images 1.2 MB (27), scripts 894 KiB (17) and fonts 477 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 34 pages on wellthapp.com and 8 external pages.

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.

There is no https://www.wellthapp.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.wellthapp.com/solution, https://www.wellthapp.com/outcomes, https://www.wellthapp.com/company/our-story, https://www.wellthapp.com/company/team, https://www.wellthapp.com/company/careers and https://www.wellthapp.com/resources and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wellthapp.com/who-we-help/medicare-advantage, https://www.wellthapp.com/solution, https://www.wellthapp.com/who-we-help/providers, https://www.wellthapp.com/who-we-help/medicaid, https://www.wellthapp.com/who-we-help/employers and https://www.wellthapp.com/who-we-help/aca-marketplace have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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 362 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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